> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Yang, Huijun (CAR:9D30) > Sent: Tuesday, April 14, 2009 1:04 PM > To: Lawrence, Scott (BL60:9D30) > Cc: [email protected] > Subject: Re: [sipX-dev] sipxecs-setup failed with r15164 > > On Tue, 2009-04-14 at 11:32 -0400, Huijun Yang wrote: > > > "2009-04-14T15:02:45.041243Z":0:SETUP:INFO:huijunsipx.ca.norte > l.com:setu > p:0:sipxecs-setup:setup:"\nExecuting:\n service sipxecs start" > > > > > "2009-04-14T15:02:46.041363Z":0:SETUP:INFO:huijunsipx.ca.norte > l.com:setu > p:0:sipxecs-setup:setup:"UNEXPECTED EXCEPTION CAPTURED:\n\n<type > 'exceptions.OSError'>: [Errno 2] No such file or directory > (exception occured in file: /usr/lib/python2.5/os.py, line: 392)" > > http://track.sipfoundry.org/browse/XECS-2495 is created to > track the issue. >
This is happening because the EDE script is calling sipxecs-setup with sudo. (Paul is going to rethink this). sipxecs-setup at the very end calls "service sipxecs start" if it thinks the caller is root - but service is not in your path if you aren't really root. Is there any reason not to call /sbin/service instead of just service? (that's what it does for chkconfig) _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
