norm will not run on any of the new sles 10 oes2 sp3 servers

[postaszewski]

We just migrated from netware 6.5 sp8 to SLES 10 sp3 with OES2 sp3. All new hardware. We have roughly 8 servers and norm will not run on any of the servers.

We check to see if httpstkd is running and its not. if i do a rcnovell-httpstkd restart, it starts the service and we're able to hit the login screen at https://10.10.2.5:8009/ but as soon as we enter the credentials and try to log in, the browser sends us to a cannot display page. If i run a rcnovell-httpstkd status it tells me its dead and no longer running.

Logging in seems to kill the service. Any idea where i should start?

Thanks.

[kjhurni]

Is LUM up and running?

rcnamcd status

And have you checked your eDir SSL certs (go into iMangler -> Novell Certificate Server-> Repair default certificates)

IF any of the certs are outdated, they'll get updated, but then you'll need to refresh your NAM cache:

namconfig -k
(login as admin)
then:
rcnamcd restart

then try firing up the httpstkd

[postaszewski]

LUM was up and running. The certificates were fine but i ran through the repair and said to only replace if invalid that returned no errors. did the namconfig -k and the namcd restart and tried reloading httpstkd and got the same results.

I visit http://10.10.2.5:8009 i get the norm login page. I enter the credentials and try to log in and get a page cannot be displayed error. I check to see if httpstkd is running by doing a status and it says it's dead but there's still a pid running

novell-httpstkd (19950) is dead, but /var/run/httpstkd.pid exists.