[cisco-voip] Restart selected Unity Connection 8.5 services every 700 hours?

[Lelio Fulgenzi]

i think many people accepted that reasoning when things were running on Windows, and, in fact, we went to a monthly restart in order to avoid issues. however, with our Unity Connection 7.1, we had it running for almost (if not over) a year before we restarted. if something needs to be restarted every month to work, it really needs to be re-written. if it's Cisco code, they have no excuse. if it's part of the RHEL kernel or underlying service, again, no excuse. they have access to the source code and should make efforts to fix it as responsible members of the open source community. 


--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Brian Globerman" <bgloberman at gmail.com> 
To: cisco-voip at puck.nether.net 
Sent: Friday, December 23, 2011 4:31:29 PM 
Subject: [cisco-voip] Restart selected Unity Connection 8.5 services every 700 hours? 

I had a TAC issue several months ago with delays in MWI and message 
delivery to Exchange. TAC engineer suggested restarting core Unity 
services after about 700 hours of use to avoid future occurrences of 
these problems. 

Question: is it common practice to bounce selected services or just 
reboot server every 700 hours? If the former, which core services 
should be restarted periodically? 

Thanks, 
Brian Globerman 
_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20111223/f804adc4/attachment.html>