Until this issue is fixed, here is the workaround the engineers found: Add a 63rd user, restart sipX. You can then continue adding more users.
I have verified this works. Very strange indeed -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Josh M. Patten Sent: Friday, February 25, 2011 3:19 PM To: sipXecs developer discussions Subject: Re: [sipx-dev] 4.4 XML-RPC Laurentiu, here is the ticket (George assigned to you): http://track.sipfoundry.org/browse/XX-9475 ________________________________________ From: [email protected] [[email protected]] on behalf of Josh M. Patten [[email protected]] Sent: Thursday, February 24, 2011 4:59 PM To: George Niculae Cc: sipXecs developer discussions Subject: Re: [sipx-dev] 4.4 XML-RPC Hmmm For some reason when I do a ps | aux all the sipX processes show up as uid 101 instead of being translated to their respective username of sipXecs In addition to that there was a sipxsupervisor process that was running as root. I rebooted the server to see if it comes up again as root, we'll see what happens -----Original Message----- From: George Niculae [mailto:[email protected]] Sent: Thursday, February 24, 2011 4:53 PM To: Josh M. Patten Cc: sipXecs developer discussions Subject: Re: [sipx-dev] 4.4 XML-RPC On Fri, Feb 25, 2011 at 12:40 AM, Josh M. Patten <[email protected]> wrote: > XML-RPC Error: null. Cannot retrieve snapshot from host > expovoip.bc.local > > Go figure....... Can you check permissions on sipxecs directories (e.g. var/sipxdata) George _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
