[Spacewalk-list] client checks in, but OSAD continues to end up "offline" when package update attempted

[Andy Ingham]

CentOS 5 (x86_64) client trying to use a spacewalk 1.7 server


Within the spacewalk GUI:

"OSA Status" consistently switches to "offline" shortly after I schedule a
package update
                   
                   
                
                
The client, however, is still successfully "checking in" with spacewalk.





Nothing noteworthy in any logs, near as I can tell, but for completeness,
here are some snippets
SERVER-SIDE:
In /var/log/rhn/rhn_server_xmlrpc.log :

	2012/04/13 15:19:16 -04:00 8377 10.148.42.119:
xmlrpc/registration.welcome_message('lang: None',)
	2012/04/13 15:19:16 -04:00 8380 10.148.42.119:
xmlrpc/registration.register_osad
	2012/04/13 15:19:16 -04:00 8379 10.148.42.119:
xmlrpc/registration.register_osad_jid
	2012/04/13 15:20:21 -04:00 8375 10.148.42.119:
xmlrpc/queue.get(1000010007, 2, 'checkins enabled')
	2012/04/13 15:20:21 -04:00 8756 10.148.42.119:
xmlrpc/up2date.login(1000010007,)
	2012/04/13 15:20:21 -04:00 8757 10.148.42.119:
xmlrpc/up2date.listChannels(1000010007,)


In /var/log/rhn/rhn_taskomatic_daemon.log :

	INFO   | jvm 1    | 2012/04/13 15:45:00 | 2012-04-13 15:45:00,022
[DefaultQuartzScheduler_Worker-6] INFO
com.redhat.rhn.taskomatic.task.SessionCleanup - 4 stale session(s) deleted

CLIENT-SIDE:


In /var/log/up2date:
	[Fri Apr 13 15:09:31 2012] up2date Updating package profile
	[Fri Apr 13 15:20:21 2012] up2date updateLoginInfo() login info
	[Fri Apr 13 15:20:21 2012] up2date logging into up2date server
	[Fri Apr 13 15:20:21 2012] up2date successfully retrieved authentication
token from up2date server




Thoughts?
What else do I check?

TIA,
Andy