Anyone ever come across a Unity server(2.4.6) mysteriously locking up every so often? The server appears to be working fine, but it locks up hard every so often and needs to be taken down dirty and rebooted.<br>Any ideas???<br><br>Alan White<br>SBC<br>Systems Engineer<br><br>
Any event log messages prior to the dirty restart that might give us a clue? when you say every so often, how far apart are we talking about? Do you notice any resource issues prior to this (i.e. the swap file starts kicking in, system gets slow and then hits the dirt)?
It's unusual for Windows to completely freeze up without a Dr. Watson or something. Even if it were a resource leak (i.e. memory or handle leaks) it wouldn't normally lock up windows, it'd bog things down good and bad and maybe take a Unity process out of action but not freeze the entire system hard like that... haven't seen that.
We've checked the logs and there are no indications of any "events" that would indicate a disaster or lack of resources. The only log events that show are the ones that say that the server went down unexpectedly (i.e. when we finally have to reboot because nothing is working).
As far as how often these events are occuring, the customer stated that the box was locking up once a day for about a week prior to our dispatch.
We reapplied the SP's today in hopes that that may be the problem. There are no other applications running on the server at all.
We went back and went over the event log with a fine tooth comb and did discover a Process ID 26 - Virtual Memory is running low error. The server has 6 volumes that are 4 gig in size each. Can you give us any idea as to what the page file size for the server should be AND should it be applied to each volume or only on the primary that holds the OS?
One last thing.. We notice that the license count on the WIN NT shows one license count.. There are about 200 users that utilize the Unity system. Should the Windows license be somewhere approaching that or does it only count the one connection from Unity?
Lack of virtual memory could cause issues, but I would be curious to know which process was the one with ID 26. Maybe you can setup a performance monitor session on the system to check how the virtual memory is growing and which process is eating it up. I think Microsoft recommendation is to have the virtual memory be 1.5 times that of the physical memory of the system. There are some items on this topic available on the Microsoft site. Is the client running the web based Status Monitor? This is one process that eats up memory and should not be left running for more than 15 minutes on the Unity server.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...