Description of problem: While regisered to spacewalk proxy, osad is not picking events. Version-Release number of selected component (if applicable): Proxy 1.6.5-1.el6 # rpm -qa | grep proxy spacewalk-proxy-package-manager-1.6.5-1.el6.noarch spacewalk-proxy-installer-1.6.7-1.el6.noarch spacewalk-proxy-common-1.6.5-1.el6.noarch spacewalk-proxy-docs-1.1.1-1.el6.noarch spacewalk-proxy-broker-1.6.5-1.el6.noarch spacewalk-proxy-redirect-1.6.5-1.el6.noarch spacewalk-proxy-management-1.6.5-1.el6.noarch spacewalk-proxy-monitoring-1.6.1-1.el6.noarch spacewalk-proxy-html-1.1.1-1.el6.noarch spacewalk-proxy-selinux-1.1.1-1.el6.noarch (against Spacewalk 1.6, partly 1.7 ...) # rpm -qa | grep spacewalk spacewalk-selinux-1.6.2-1.el5 spacewalk-backend-config-files-common-1.7.19-1.el5 spacewalk-backend-package-push-server-1.7.19-1.el5 spacewalk-java-config-1.6.102-1.el5 spacewalk-setup-jabberd-1.6.5-1.el5 spacewalk-monitoring-selinux-1.6.2-1.el5 spacewalk-admin-1.6.3-1.el5 spacewalk-search-1.6.8-1.el5 spacewalk-common-1.5.1-1.el5 spacewalk-backend-sql-1.7.19-1.el5 spacewalk-backend-config-files-tool-1.7.19-1.el5 spacewalk-branding-1.6.4-1.el5 spacewalk-config-1.6.4-1.el5 spacewalk-slf4j-1.6.1-1.el5 spacewalk-pxt-1.6.38-1.el5 spacewalk-backend-libs-1.7.19-1.el5 spacewalk-grail-1.6.38-1.el5 spacewalk-java-oracle-1.6.102-1.el5 spacewalk-taskomatic-1.6.102-1.el5 spacewalk-backend-server-1.7.19-1.el5 spacewalk-backend-xmlrpc-1.7.19-1.el5 spacewalk-backend-iss-1.7.19-1.el5 spacewalk-backend-xp-1.7.19-1.el5 spacewalk-repo-1.7-4.el5 spacewalk-client-repo-1.7-4.el5 spacewalk-java-lib-1.6.102-1.el5 spacewalk-base-1.6.38-1.el5 spacewalk-java-1.6.102-1.el5 rh-tests-Spacewalk-Installer-Sanity-Yum-install-spacewalk-oracle-1.0-5 spacewalk-backend-1.7.19-1.el5 spacewalk-backend-xml-export-libs-1.7.19-1.el5 spacewalk-backend-applet-1.7.19-1.el5 spacewalk-backend-iss-export-1.7.19-1.el5 spacewalk-certs-tools-1.6.7-1.el5 spacewalk-base-minimal-1.6.38-1.el5 spacewalk-doc-indexes-1.1.1-1.el5 spacewalk-monitoring-1.4.1-1.el5 spacewalk-schema-1.6.42-1.el5 spacewalk-backend-sql-oracle-1.7.19-1.el5 spacewalk-backend-config-files-1.7.19-1.el5 spacewalk-html-1.6.38-1.el5 spacewalk-setup-1.6.5-1.el5 spacewalk-sniglets-1.6.38-1.el5 spacewalk-oracle-1.5.1-1.el5 spacewalk-backend-app-1.7.19-1.el5 spacewalk-backend-tools-1.7.19-1.el5 (on client we had osad-5.10.34-1.el5) How reproducible: Always, deterministic Steps to Reproduce: 1. Register client to proxy. 1.5. (Make sure osad is running on client, you may want to restart osad if it was already running.) 2. Schedule event (e.g. enable monitoring and then schedule remote command). Actual results: Nothing happens (I have been observing only for something more that half an hour, but I think that it does not work). Expected results: Scheduled event is picked up. Additional info: I have checked, that it works directly against spacewalk. When client is registered to proxy, OSA status is shown unknown. After (re)starting osad status changes to offline. Pinging system (via WebUI) adds info about last pinged, restarting osad typically removes this info. (So it seems that at least some information is propagated to spacewalk.) Looking at connection reveals, that osad process has open (TCP) connection to proxy, process c2s in particular. There does not seems to be any (persistent) connection directly to server. (But that may be ok(?)) This was all run over IPv6.
This is caused by s2s not communicating between two instances of jabberd server. I find this relevant report in upstream: https://bugs.launchpad.net/jabberd2/+bug/374687 Flipping to jabberd. Can you please communicate with upstream to do some release and rebase to it?
jabberd-2.2.16-1.fc18 is available. This should include the above mentioned fix. Does this help?
It would be very nice to have this also in EPEL 5,6 (even fedora 17 isn't released as final), as otherwise it won't help us much (and I might not be able to do anything with it for quite long period of time). Are you willing to do EPEL releases under this Bz or do you prefer different way of tracking it (say new Bz)?
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.