troubleshooting:problems_starting_evergreen
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
troubleshooting:problems_starting_evergreen [2007/05/08 21:20] – Add starting problem troubleshooting tips dbs | troubleshooting:problems_starting_evergreen [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | =====Troubleshooting: | ||
+ | ====Ensure your fully qualified hostname is what you think it is==== | ||
+ | ===Problem=== | ||
+ | When you try to start Evergreen, you receive the error message < | ||
+ | at / | ||
+ | ===Solution=== | ||
+ | This error message means that the | ||
+ | OpenSRF Perl service was unable to find an element in '' | ||
+ | < | ||
+ | < | ||
+ | ... | ||
+ | </ | ||
+ | </ | ||
+ | ...</ | ||
+ | |||
+ | To determine the fully qualified hostname of your system, run the following command | ||
+ | at the command line: | ||
+ | |||
+ | < | ||
+ | |||
+ | If the output from this command does not match the opening and closing element name in your '' | ||
+ | |||
+ | //Aside: the command '' | ||
+ | |||
+ | ==== Problems connecting to the jabber server ==== | ||
+ | ===Problem=== | ||
+ | When you try to start Evergreen, you receive an error message like:< | ||
+ | !!!!Unable to connect router to jabber server localhost... exiting</ | ||
+ | ===Solution #1=== | ||
+ | Your Jabber server may not be running. You can look for the jabber server process in your list of processes: | ||
+ | < | ||
+ | You can also try to telnet to port 5222 on your jabber server - for example:< | ||
+ | telnet localhost 5222 | ||
+ | </ | ||
+ | ===Solution #2=== | ||
+ | OpenSRF may not be pointed at the correct hostname in '' | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | <!-- do not change this --> | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | list of router domains we should register with. | ||
+ | We must at least have our default jabber domain in here. | ||
+ | --> | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | <!-- Our jabber domain, currenlty only one domain is supported --> | ||
+ | < | ||
+ | </ | ||
+ | ... | ||
+ | </ | ||
+ | |||
+ | ====Problems connecting to the settings server==== | ||
+ | ===Problem=== | ||
+ | ''/ | ||
+ | < | ||
+ | 2007/ | ||
+ | "/ | ||
+ | MessageWrapper received bad XML : error = :1: namespace error: | ||
+ | Namespace prefix stream on error is not defined | ||
+ | < | ||
+ | ^ at | ||
+ | / | ||
+ | ... | ||
+ | Replaced by new connection</ | ||
+ | ===Cause=== | ||
+ | Recent versions of ejabber have a setting for the maximum number of times a single user is allowed to simultaneously connect to the ejabber server. The default of '' | ||
+ | |||
+ | ===Solution=== | ||
+ | Increase the '' | ||
+ | {max_user_sessions, |