Symposium Re-boots

[Steve60]

Hi,

We're running Symp 4.5 and every now and then the system goes down and requires a manual re-boot. Is there a recommended manual re-boot schedule that would stop the system crashing every couple of months?

Thanks

 

[rfwhite]

Have you looked at any logs to see what actually happens especially just before it dives? Are you using HDX or any other external applications?

 

[Steve60]

There was nothing in the logs to indicate a problem and apart from the web client we're not connecting to anything external. We have networked Symposium (3 Symp servers on three sites and 1 network Symp Server).

I just thought it may be good prectice to re-boot maybe once a month??

 

[cgilmer]

I have had issue in the past with Reports scheduled with invalid destinations. This returns with every reboot until the reports are removed from the system. Users who schedule reboots and then have their IP lost or Computer name changed without un-scheduling reports. It sucks up memory until the system finally reboots.

Depending on how intensive the scheduled reports are I've seen it anywhere from 2 or 3 days to a few weeks or months.

As far as general reboots I tend to reboot once a month due to the fact that no matter how stable the Symposium software is or isn't it is still a windows operating system behind it.

 

[Steve60]

Thanks for this, just what I thought. I shall put this into pratice and look at the Reports schedulled too as suggested. Thanks for taking the time to help me.

 

[cgilmer]

Also you can try to validate this by bringing up the System Performance Monitor on the server and have it look at committed memory for processes. Watch it for a day or a few hours and you will see processes that don't do anything. Just remove them from being monitored until all that is left are the problem processes.

Then at least you can tell if there is a build-up or leak on the system. Nortel will tell you not to leave this up permanently due to it taking up CPU cycles and make sure you don't eave it set to very low update intervals like under 30 seconds.

 

[sandyml]

Is this a Symposium 4.2? (I take it that you have a Web Client 4.5.) To follow up on what cgilmer mentioned, do you have anybody with a "classic" client that may be running reports (that is, not using the Web Client). Does your Web Client server have more than 1 NIC card? Both of those can cause your SCCS to lock up if there are errors in running a report, if the NIC card is set for DHCP, etc.

 

[Steve60]

No, we're all using the web client, although that gives us other problems with missing data. We should be upgrading to v4.5 of the web client which will apparently iron out the bugs of previous versions.

 

[Momozone]

Do you have a remote alarm or are you getting any problems with the connection between you PBX and Symposium.

One thing we found was that symposium wasnt going down only the connection between symposium and our meridian was faulty.

new network cards and new wiring solved the problem for us.



MoMoZoNe