[Spacewalk-list] fedora17 osad problems

[Jan Pazdziora]

On Sat, Nov 10, 2012 at 05:06:15PM +0400, Yuriy Demchenko wrote:
> Hi,
> 
> I'm having troubles with OSA daemon on fedora 17 machines - it doesnt work.
> using osad.noarch 5.11.10-1.fc17 from spacewalk-1.8-client fedora17
> repository and spacewalk 1.8
> when i try to start it, I'm getting this:
> >[root at fedtest ~]# systemctl status osad.service
> >osad.service - OSAD daemon
> >          Loaded: loaded (/usr/lib/systemd/system/osad.service; enabled)
> >          Active: failed (Result: exit-code) since Sat, 10 Nov
> >2012 16:46:35 +0400; 35s ago
> >         Process: 26886 ExecStart=/usr/sbin/osad --pid-file
> >$PIDFile (code=exited, status=2)
> >          CGroup: name=systemd:/system/osad.service
> >
> >Nov 10 16:46:35 fedtest osad[26886]: Usage: osad [options]
> >Nov 10 16:46:35 fedtest osad[26886]: osad: error: --pid-file
> >option require
> error message pretty obvious, so I've changed systemd file
> osad.service and put full path instead of var $PIDFile
> now systemd starts service

That change sounds correct.

> but it dies in a second:
> >[root at fedtest ~]# systemctl status osad.service
> >osad.service - OSAD daemon
> >          Loaded: loaded (/usr/lib/systemd/system/osad.service; enabled)
> >          Active: inactive (dead) since Sat, 10 Nov 2012 16:56:05
> >+0400; 1min 13s ago
> >         Process: 27155 ExecStart=/usr/sbin/osad --pid-file
> >/var/run/osad.pid (code=exited, status=0/SUCCESS)
> >          CGroup: name=systemd:/system/osad.service
> I've turned on debug logging, but found nothing useful in log -
> process just dies after "pushing into background" and no more
> messages in log:
> >2012-11-10 16:56:05 jabber_lib._auth_dispatch: <features><address
> >xmlns = 'http://affinix.com/jabber/address'
> >>192.168.10.50</address><mechanisms xmlns =
> >'urn:ietf:params:xml:ns:xmpp-sasl' ><mechanism>EXTERNAL</mechanism><mechanism>PLAIN</mechanism><mechanism>DIGEST-MD5</mechanism></mechanisms><auth
> >xmlns = 'http://jabber.org/features/iq-auth'  /><register xmlns =
> >'http://jabber.org/features/iq-register' /></features>
> >2012-11-10 16:56:05 jabber_lib.connect: connect returning
> >2012-11-10 16:56:05 jabber_lib.setup_connection: Connected to
> >jabber server spacewalk.spb.stone.local
> >2012-11-10 16:56:05 jabber_lib.push_to_background: Pushing process
> >into background

Is there anything in /var/log/audit/audit.log, by any chance?

> I've tried osad-5.10.41-1.fc16.noarch from spacewalk-1.7-client repo
> - it starts/stops fine via sysV, but doesnt work too - somehow it
> cant connect to jabber server (firewalls and selinux disabled, both
> spacewalk-server and machine have fully resolvable fqdn).
> >jabber_lib.main: Unable to connect to jabber servers, sleeping 105 seconds

Could it be time sync issue (if using SSL)? Are you able to connect to
that jabberd directly, with nc or telnet?

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat