Hello Tom, It looks like ejabberd is at least returning errors (code 503 - cancel), so perhaps it is running ok, but not authenticating properly. Try re-registering your ejabberd users:
sudo ejabberdctl unregister router epworth-eg sudo ejabberdctl unregister evergreen epworth-eg sudo ejabberdctl register router epworth-eg your_password_goes_here sudo ejabberdctl register evergreen epworth-eg your_password_goes_here Restart everything and try again. It would also be interesting to see if the settings_tester.pl script connects to ejabberd successfully. DW >>> Tom Patterson <[EMAIL PROTECTED]> 4/30/2008 8:43 AM >>> Dan, I followed the directions below but still got error messages when doing the finalize step. The logs are attached. Thanks for the help. Tom Patterson ________________________________________ From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Dan Wells [EMAIL PROTECTED] Sent: Tuesday, April 29, 2008 4:42 PM To: [email protected] Subject: RE: [OPEN-ILS-DEV] EG client login error Hello Tom, Your router log looks fine for what little is in there. John's advice to run the settings_tester.pl is always a good thing to try, though make sure you set your PERL5LIB for the shell before you run it ( export PERL5LIB=/openils/lib/perl5 ) since the Ubuntu wiki page doesn't alter any .bashrc files. It sounds like you have been careful in checking your settings, though, so I would recommend just trying to stop and start the whole stack again and seeing what happens. First: sudo -u opensrf /openils/bin/osrf_ctl.sh -c /openils/conf/opensrf_core.xml -a stop_all After the machine comes to rest, run: ps ax | grep "OpenSRF" and kill any lingering processes listed there which sometimes get stuck for a bit. After that, I would recommend deleting or moving aside all the current log files, then restarting the system one step at a time: sudo -u opensrf /openils/bin/osrf_ctl.sh -c /openils/conf/opensrf_core.xml -a start_router sudo -u opensrf /openils/bin/osrf_ctl.sh -c /openils/conf/opensrf_core.xml -a start_perl sudo -u opensrf /openils/bin/osrf_ctl.sh -c /openils/conf/opensrf_core.xml -a start_c sudo /etc/init.d/apache2 restart After that, try the OPAC finalize step ( sudo -u opensrf ./autogen.sh /openils/conf/opensrf_core.xml ), and if that works, try to logging in using srfsh: /openils/bin/srfsh srfsh% login admin open-ils If any of the above doesn't work, tar up your fresh log directory and send it along. Thanks, DW >>> Tom Patterson <[EMAIL PROTECTED]> 4/29/2008 8:30 AM >>> Dan, I have checked the settings in the opensrf_core.xml file and the opensrf.xml file and as far as I can see they are set correctly. When starting the router there were no errors. Here is the log output after executing the commands below and trying to use client: router 2008-04-28 17:04:05 [INFO:12410:osrf_router_main.c:83:] Router adding trusted server: epworth-eg router 2008-04-28 17:04:05 [INFO:12410:osrf_router_main.c:86:] Router adding trusted client: epworth-eg router 2008-04-29 07:33:51 [WARN:12411:osrf_router_main.c:10:] Received signal [2], cleaning up... router 2008-04-29 07:33:51 [WARN:12411:osrf_router.c:64:] Top level select call failed with errno 4 router 2008-04-29 07:34:00 [INFO:15935:osrf_router_main.c:70:] Router connecting as: server: epworth-eg port: 5222 user: router resource: router router 2008-04-29 07:34:00 [INFO:15935:osrf_router_main.c:83:] Router adding trusted server: epworth-eg router 2008-04-29 07:34:00 [INFO:15935:osrf_router_main.c:86:] Router adding trusted client: epworth-eg Thanks, Tom Patterson ________________________________________ From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Dan Wells [EMAIL PROTECTED] Sent: Monday, April 28, 2008 4:02 PM To: [email protected] Subject: RE: [OPEN-ILS-DEV] EG client login error Tom, Double check your opensrf_core.xml file and make sure your passwords are all set properly. After that, try: sudo -u opensrf /openils/bin/osrf_ctl.sh -c /openils/conf/opensrf_core.xml -a stop_router then: sudo -u opensrf /openils/bin/osrf_ctl.sh -c /openils/conf/opensrf_core.xml -a start_router Let us know if the router starts without error, and also if you get any ERR or WARN lines in the router.log file. DW
