Bug 1071713
| Summary: | osa-dispatcher is dead, bud pid file exists | ||
|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | Zhang Hao <zhanghaousr> |
| Component: | Server | Assignee: | Michael Mráka <mmraka> |
| Status: | CLOSED NOTABUG | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-04-14 03:28:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1484117 | ||
this is a know issue we've been having with jabberd form time to time its database gets corrupted. no one is sure exactly why but the good news is you don't need the contents of jabberd's database so you can simply wipe it out and it will rebuild itself here is the workaround procedure run the following service osa-dispatcher stop service jabberd stop rm -f /var/lib/jabberd/db/* service jabberd start service osa-dispatcher start Thank you very much, now it works. This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug. |
Description of problem: While run spacewalk-service start, osa-dispatcher is OK,but osa-dispatcher is not running, #spacewalk-service status postmaster (pid 1907) is running... router (pid 2061) is running... sm (pid 2068) is running... c2s (pid 2075) is running... s2s (pid 2082) is running... tomcat6 (pid 2019) is running... [确定] httpd (pid 2050) is running... osa-dispatcher is dead，but pid file exists rhn-search is running (2185). cobblerd (pid 4835) is running... RHN Taskomatic is running (2408). osa-dispatcher.log: 2014/03/03 09:11:45 +09:00 2149 0.0.0.0: osad/jabber_lib.__init__ 2014/03/03 09:11:45 +09:00 2149 0.0.0.0: osad/jabber_lib.setup_connection('Connected to jabber server', 'localhost.localdomain') 2014/03/03 09:11:45 +09:00 2149 0.0.0.0: osad/jabber_lib.register('ERROR', 'Invalid password') What password for it? In my rhn.conf: # OSA configuration # server.jabber_server = localhost.localdomain osa-dispatcher.jabber_server = localhost.localdomain # set up SSL on the dispatcher osa-dispatcher.osa_ssl_cert = /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT If osa-dispatcher.jabber_username and osa-dispatcher.jabber_password are also need in rhn.conf, but if I add in rhn.conf it is same. Version-Release number of selected component (if applicable): #rpm -q spacewalk-backend osa-dispatcher spacewalk-backend-2.0.3-1.el6.noarch osa-dispatcher-5.11.27-1.el6.noarch #rpm -q postgresql postgresql-8.4.13-1.el6.x86_64