[Spacewalk-list] Are there any docs forconfiguring the client for a push?

[Michael ORourke]

----- Original Message ----- 
From: <m.roth2006 at rcn.com>
To: <spacewalk-list at redhat.com>
Sent: Thursday, February 19, 2009 4:43 PM
Subject: Re: [Spacewalk-list] Are there any docs forconfiguring the client 
for a push?


> Mairin,
>
>>Date: Thu, 19 Feb 2009 14:05:31 -0500
>>From: Máirín Duffy <duffy at redhat.com>
>>m.roth2006 at rcn.com wrote:
>>> Are there any? I can't seem to create a profile for my
>>> client. None was created when I registered it, and when I
>>> try rhn-profile-sync, it fails with error communicating
>>> with server in /var/log/up2date on the client, and not
>>> connected to Oracle on the server.
>>
>>Can you provide us the full error from the up2date log?
>
> Certainly:
> [Wed Feb 18 13:22:09 2009] up2date Error communicating with server. The 
> message was:
> Internal Server Error
> [Wed Feb 18 13:22:09 2009] up2date
> Traceback (most recent call last):
>  File "/usr/sbin/rhn-profile-sync", line 54, in ?
>    cli.run()
>  File "/usr/share/rhn/up2date_client/rhncli.py", line 65, in run
>    sys.exit(self.main() or 0)
>  File "/usr/sbin/rhn-profile-sync", line 42, in main
>    rhnPackageInfo.updatePackageProfile()
>  File "/usr/share/rhn/up2date_client/rhnPackageInfo.py", line 27, in 
> updatePackageProfile
>    rpmUtils.getInstalledPackageList(getArch=1))
>  File "/usr/share/rhn/up2date_client/rhnserver.py", line 50, in __call__
>    return rpcServer.doCall(method, *args, **kwargs)
>  File "/usr/share/rhn/up2date_client/rpcServer.py", line 263, in doCall
>    raise up2dateErrors.CommunicationError(e.errmsg)
> up2date_client.up2dateErrors.CommunicationError: Error communicating with 
> server. The message was:
> Internal Server Error
>
>>
>>Where is the Oracle error message? Can you provide that?
>
>>From /usr/lib/oracle//xe/app/oracle/admin/XE/bdump/alert_XE.log:
> Wed Feb 18 13:20:41 2009
> Errors in file 
> /usr/lib/oracle/xe/app/oracle/admin/XE/udump/xe_ora_16495.trc:
> ORA-07445: exception encountered: core dump [evapls()+133] [SIGSEGV] 
> [Address not mapped to object] [0x4] [] []
>
> And in catalina.out, I get the usual 50million lines of a java exception 
> when, about 15 min. earlier than the above, I tried to schedule a profile 
> update from spacewalk via browser, for the client system: null pointer 
> exception
>>>
>>> There must be *something* that I need to do to make the
>>> profile, so I can set up a push.
>>
>>By setting up a push, do you mean configuring the client for
>>OSAD?
>>
>>https://fedorahosted.org/spacewalk/wiki/OSADSetup
>
> What is OSAD? I saw setup instructions for it, but nothing that told me in 
> the client setup docs what it was, or why it was needed, at least in the 
> client setup docs, which end with the registration. Is this a daemon that 
> needs to run on the client? Is it needed on the server, as well?
>>
>>Or are you talking about rhnpush-ing content into a channel?
>
> Oh, no, I've got that working just fine, thanks. Did I post the script I 
> wrote for that?
>
>>(I am assuming the former since the latter doesn't have much
>>to do with a client system)
>
> Right: we don't plan to have the client pull the update, but rather push 
> it from the server.
>>>
>>> Oh, and when I scheduled a push via browser/spacewalk, it
>>> errored out.
>>
>>Okay? What error message did you get? Is the osad daemon
>>running on the Satellite? Does the client you're trying to
>>push to have an active OSAD status in its system details page?
>
> I'd have to rerun it. First, though, could you tell me, or point me to a 
> doc, that tells me about OSAD, other than just how to set it up?

You definetly want OSAD running, on both the client and the server.  Because 
the rhnsd daemon defaults to 'checking in' every 240 minutes.  So if you 
schedule a push, reboot, or a remote command on the client from the 
spacewalk server, it may take up to 4 hours before it executes.  What OSAD 
does is check with the server to see if there are any pending operations 
scheduled for it, if so then it executes /usr/sbin/rhn_check  (same thing 
that the rhnsd daemon does when it wakes up).
-Mike

>
> Thanks!
>
>   mark
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list