can't log into to console or server 1

[fluid11]

There was a network problem yesterday with one of our switches. Since then, I have the following errors on the server (below). I'm running 2 NetWare 5.1 (SP3) servers. I can log in and it runs the login script and I can still access the volumes on both servers, but I cannot log into the console. It says invalid password on server #2 when trying to unlock the screensaver.

POLICY MANAGER - Server is unable to obtain a server base license unit. Connection to this server is NOT allowed. Ensure that licensing units are available and verify NLS operation. Error # C0001005.

POLICY MANAGER - Unable to obtain a connection license unit. Operation will continue. Contact your network administrator to verify that licensing services are functioning properly and that license units are available. Error #C0001006


Cache memory allocator out of available memory.


Short term memory allocator is out of memory.
5755935 attempts to get more memory failed.
request size in bytes 686 from Module SLPTCP.NLM


Cannot digest critical NICI infrastructure data:| NICI configuration File. Error -1400.


Unrecoverable internal error. | NICI Cryptography Service will not be available.


Error registering service in SAPHandler. Error code - 12

masv.nlm could not initialize

masv.nlm could not initialize



Any ideas? I'm going to restart the server tomorrow morning. I don't even know how I'm going to shut it down since I can't access the console. I'll have to flip the power switch.

Any help before tomorrow (or after) is greatly appreciated.

Chris

 

[TheBoySmith]

You can do a <left-shift> <ctrl> <alt> & then <escape>, if the server responds you can then do a down. If that fails then the power off is the only real way.

If the server struggles to come back up then take the lan connection out and bring it up. You will have to configure slp, then plug back in the lan connection.

good luck. Lee Smith
Associated Network Services
Snr Systems Engineer
Lee.Smith@ANSPLC.Com

 

[fluid11]

I know another way if the <left-shift> <ctrl> <alt> & then <escape> key sequences don't work....I can drop kick the server out the window

Any idea what causes this?

Chris

 

[TheBoySmith]

The errors posted point to loads of problems but I suspect that you have got a server that wants a reboot.

There is another way of getting into a debugger screen but its as bad as power off, (or throwing).

When you bring the server back up, take it off the lan and i would suggest doing a dsrepair, repair local ds with rebuild operational schema.


(Working late in the office on migrating to a new server from almost dead server)

I know how it feels fluid........... Lee Smith
Associated Network Services
Snr Systems Engineer
Lee.Smith@ANSPLC.Com

 

[fluid11]

The servers uptime as of right now is 3 months. The last time it was down was when I had to replace the UPS it was on so the server has been pretty reliable. Its working right now, but something has to be done before something serious happens (if it hasn't already). How often do you reboot your NetWare servers? Do you do it periodically or just when it needs it?

When you say take it off of the LAN, do you mean pull the cable out, remove the NIC, or unload the drivers (or something similar)?

Rebuild operational schema? Never heard of that one. Is that something I should normally do when doing a dsrepair or only in situations like these?

Thanks,
Chris

 

[TheBoySmith]

There is no need to reboot a server unless you need to. Netware 5 etc sorts its memory out so its not like nw3.x and the likes.

Pull the lan cable out of the server is sufficient.(Wouldn't risk asking you to take a screw driver to its insides at the moment).

Re-build op schema is something I do when I have had a problem with a server. As my job is to fix our customers servers it tends to be a standard with me but no need to do it on a server just for the sake of it.

I surprised its working. Although it would be better to drop it now before it cause serious damage to nds etc. This is not to say the errors you are getting will cause problems but a manged fix is better than waiting for it to completely die and have to try and resurrect it from the ashes. Lee Smith
Associated Network Services
Snr Systems Engineer
Lee.Smith@ANSPLC.Com

 

[fluid11]

Thanks for your help. I'm coming in early tomorrow morning before everyone arrives and I'll do it then. No need to disrupt service for everyone if its still working fine. If NDS does get messed up, it &quot;shouldn't&quot; be too much of a problem since this is my second NetWare server and it only holds a read/write replica of the NDS database. Hopefully (fingers crossed) I can just reboot it and run a dsrepair and it will be fixed. I'll let you know tomorrow how it went.

Thanks,
Chris

 

[TheBoySmith]

cool.

best of luck. Lee Smith
Associated Network Services
Snr Systems Engineer
Lee.Smith@ANSPLC.Com

 

[salserocito]

Basically, the C0001006 Errors are caused by not having any more licensed connections available on the Server. All of them are currently in use.

The &quot;Cache memory allocator out of available memory&quot; error is seen when you have no more available resources (Memory) available for the system to utilize.

The errors referring to NICI are also License related.

This server is screaming for a reboot.

I haven't tried it on a locked console, but can also try <CNTL> <ALT> <ESC>. If that works, it will allow you to down the Server right then and there.

Good Luck.

 

[fluid11]

I tried Ctrl+Alt+Esc (which is the Hung Console Screen), but it didn't work so I was forced into a dirty reboot. I decided against drop kicking the server out the window as I will need it again. After the reboot, everything was fine. I ran dsrepair and it found 3 errors and fixed them all. I ran it again and it didn't find anymore errors.

Before the reboot, the server was not using the server license assigned to it for whatever reason. Thats why I couldn't even log into the console. I have no idea what causes this.

I thought that NetWare servers were known for not having to reboot them? They were up for 3 months before this happened, which is still a lot better than you can say for most Windows servers

Thanks to all who replied,
Chris

 

[dan]

Now that you got it up....
You might want to enable rconsole or rconsolej for future reference. If you can't login to the server console, you could get in the back door and maybe run DSREPAIR or at least do a clean DOWN.
Dan

 

[fluid11]

rconsolej was up. The server didn't allow a connection through that either. Weird.

ChrisP