So I figured out that RLS is indeed working...when the list is tiny. I think the problem lies in ResourceListServer.cpp because I think the sShutdownChangeDelay = 10; value is being used on startup, hence causing an overflow and crash. Here is a suggestion:
change: const int ResourceListServer::sRunningChangeDelay = 100; const int ResourceListServer::sShutdownChangeDelay = 10; to const int ResourceListServer::sRunningChangeDelay = 500; const int ResourceListServer::sShutdownChangeDelay = 100; Josh Patten Brazos County Network Engineer 979.361.4676 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of George Niculae Sent: Monday, May 16, 2011 6:25 AM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] 4.4 sipXrls dead On Mon, May 16, 2011 at 1:53 AM, Josh M. Patten <[email protected]> wrote: > http://track.sipfoundry.org/browse/XX-9614 > > We managed to get the SSL and VM deposit issues ironed out but the RLS > problem still remains, and it appears to be TLS related (see tracker > issue above). What's strange is that I have a 4.4.0-192 system that I > updated to > 4.4.0-202 and it does not have this issue. > Can you check permissions for var/sipxdata/tmp/imdb.* You may also want to try stop sipxrls, delete these files and restart sipxrls George _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
