Periodically, maybe once or twice every few weeks, we see our instance of Asterisk 1.4.7 just close out without warning and we have to reload the module. We're running CentOS. Has anyone else seen this before? Core show version: Asterisk 1.4.7 built by root @ XXXXXX on a i686 running Linux on 2007-07-11 00:21:57 UTC Uname -a: Linux XXXXXX 2.6.9-55.0.2.EL #1 Tue Jun 26 14:08:18 EDT 2007 i686 athlon i386 GNU/Linux Ryan M. Colbert Director of Information Technology Rissman, Barrett, Hurt, Donahue & McLain, P.A. 201 E. Pine Street, Suite 1500 Orlando, FL 32801 (407) 517-3105 - Direct Telephone (407) 839-0120 - Main Office (407) 841-9726 - Fax http://www.rissman.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20071115/0e6c859a/attachment.htm
On Thursday 15 November 2007 11:33:46 Ryan M. Colbert wrote:> Periodically, maybe once or twice every few weeks, we see our instance of > Asterisk 1.4.7 just close out without warning and we have to reload the > module. We're running CentOS. Has anyone else seen this before? > > Core show version: Asterisk 1.4.7 built by root @ XXXXXX on a i686 running > Linux on 2007-07-11 00:21:57 UTC Uname -a: Linux XXXXXX 2.6.9-55.0.2.EL #1 > Tue Jun 26 14:08:18 EDT 2007 i686 athlon i386 GNU/LinuxThat's a really old version, and many bugs have since been fixed. Have you considered updating to the current version? -- Tilghman
At 11:33 11/15/2007, Ryan M. Colbert wrote:>Periodically, maybe once or twice every few >weeks, we see our instance of Asterisk 1.4.7 >just close out without warning and we have to >reload the module. We?re running CentOS. Has anyone else seen this before? > >Core show version: Asterisk 1.4.7 built by root >@ XXXXXX on a i686 running Linux on 2007-07-11 00:21:57 UTC >Uname ?a: Linux XXXXXX 2.6.9-55.0.2.EL #1 Tue >Jun 26 14:08:18 EDT 2007 i686 athlon i386 GNU/LinuxThere probably have been a few bugs fixed since 1.4.7. Latest version is 1.4.13: http://www.asterisk.org/downloads Perhaps running a Cron job to reboot in the middle of the night would solve some of these problems: crontab -e 0 4 * * * /sbin/shutdown -r now