I'm getting the same thing here clean install and update of redundant server... there is no /var/sipxdata/cfdata/servers file at all my directory looks like this now.
[root@localhost cfdata]# vdir /var/sipxdata/cfdata/ total 20 drwxr-xr-x. 2 sipx sipx 4096 Oct 22 20:50 1 drwxr-xr-x. 2 sipx sipx 4096 Oct 22 19:06 2 drwxr-xr-x. 2 sipx sipx 4096 Oct 22 20:50 3 drwxr-xr-x. 2 sipx sipx 4096 Oct 22 20:50 defaults -rw-r--r--. 1 sipx sipx 30 Oct 22 20:55 network.cfdat The end of the sipxagent log looks like this: cf3> Module context: sipx cf3> Activated classes: sipxsupervisor cf3> cf-agent aborted on defined class "sipxsupervisor" defined in bundle sipx_module Kyle On Mon, Oct 22, 2012 at 2:21 PM, Aaron Pursell <[email protected]> wrote: > I noticed there was new software out there so I updated and then ran reset > all again. > > One thing I did notice is that when you run it; it complains about > /var/sipxdata/cfdata/servers and unable to access it. > > Looking at the permissions I reset the owner of the directory to sipx like > the parent after running --reset-all it recreated all the files with ROOT as > the owner again. So not sure if this is part of the problem or not however > when it generates all the information in cfdata, it sets the owner to root > and then complains about not being able to access the file... > > > > > > Aaron Pursell > Network Security Administrator > Easter Seals-Goodwill Northern Rocky Mountain, Inc. > 4400 Central Ave > Great Falls, Montana 59405 > > (406) 771-3721 > [email protected] >>>> "Aaron Pursell" <[email protected]> 10/22/2012 9:37 AM >>> > Attached...A variety of errors. > > > Aaron Pursell > Network Security Administrator > Easter Seals-Goodwill Northern Rocky Mountain, Inc. > 4400 Central Ave > Great Falls, Montana 59405 > > (406) 771-3721 > [email protected] >>>> Douglas Hubler <[email protected]> 10/22/2012 9:21 AM >>> > I'll look into why order of arguments matters, but use > > sipxecs-setup --verbose --reset-all > > > > On Mon, Oct 22, 2012 at 11:12 AM, Aaron Pursell <[email protected]> wrote: >> I figured that something did happen, however it was a fresh build/install. >> >> Here is output of reset-all now... >> >> [root@gfgwph init.d]# sipxecs-setup --reset-all --verbose >> /usr/bin/sipxecs-setup:122:in `readline': No such file or directory - >> --verbose (Errno::ENOENT) >> from /usr/bin/sipxecs-setup:122:in `prompt' >> from /usr/bin/sipxecs-setup:107:in `prompt_confirm' >> from /usr/bin/sipxecs-setup:200:in `reset_all' >> from /usr/bin/sipxecs-setup:415 >> from /usr/lib/ruby/1.8/optparse.rb:1267:in `call' >> from /usr/lib/ruby/1.8/optparse.rb:1267:in `parse_in_order' >> from /usr/lib/ruby/1.8/optparse.rb:1254:in `catch' >> from /usr/lib/ruby/1.8/optparse.rb:1254:in `parse_in_order' >> from /usr/lib/ruby/1.8/optparse.rb:1248:in `order!' >> from /usr/lib/ruby/1.8/optparse.rb:1339:in `permute!' >> from /usr/lib/ruby/1.8/optparse.rb:1360:in `parse!' >> from /usr/bin/sipxecs-setup:428 >> This will wipe all configuration data from this server. Are you sure? [ >> enter 'y' or 'n' ] : [root@gfgwph init.d]# >> >> Does not even allow you to press "y". >> >> >> >> >> >> Aaron Pursell >> Network Security Administrator >> Easter Seals-Goodwill Northern Rocky Mountain, Inc. >> 4400 Central Ave >> Great Falls, Montana 59405 >> >> (406) 771-3721 >> [email protected] >>>>> Douglas Hubler <[email protected]> 10/22/2012 9:00 AM >>> >> >> On Mon, Oct 22, 2012 at 9:47 AM, Aaron Pursell <[email protected]> wrote: >>> Nothing responds on 5308, stopped iptables on both boxes, same outcome. >>> I've >>> attached the nofork output. >> >> Here are the telling lines >> >> cf3> !! Could not examine file >> "/etc/sipxpbx/sipxsupervisor-allowed-addrs.ini" in readfile >> cf3> !!! System error for stat: "No such file or directory" >> cf3> !! Could not examine file >> "/etc/sipxpbx/sipxsupervisor-allowed-users.ini" in readfile >> cf3> !!! System error for stat: "No such file or directory" >> >> These files are created as part of setup, something must have went >> silently wrong with sipxecs-setup on the secondary node. On the >> secondary node (192.168.1.32), try >> >> sipxecs-setup --reset-all --verbose >> >> and send output. >> _______________________________________________ >> 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/ > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- Kyle Haefner, M.S. Communication Systems Programmer Colorado State University Fort Collins, CO Phone: 970-491-1012 Email: [email protected] 01010010 01100101 01100001 01101100 00100000 01101101 01100101 01101110 00100000 01110000 01110010 01101111 01100111 01110010 01100001 01101101 00100000 01101001 01101110 00100000 01100010 01101001 01101110 01100001 01110010 01111001 00101110 _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
