Re: [Spacewalk-list] Debian client not picking up scheduled jobs

Fri, 27 Mar 2015 02:40:04 -0700

Hi Cipher,
 
coming closer. I installed the spacewalk packages from testing and tried again. The first time, the action has been picked up, but there was still 2 directories missing
 
/var/lib/up2date (for timestamp file) and
/var/spool/rhn/remote-script
 
for the script (like you said).
 
Because these directories were missing, it seems, that there have been faultiy records put into the spacewalk database. Every later try to execute a remote command failed (the actions hasn't been found on the server).
 
To verify that, I removed the system from spacewalk, re-registered and retried => works!
 
But know, I have another problem. Just tried to update a package, the client did that, but also removed its spacewalk packages (?!?!)
 
root@deb-inst-test:~# rhn_check -vv
D: check_action{'action': "<?xml version='1.0'?>\n<methodCall>\n<methodName>packages.update</methodName>\n<params>\n<param>\n<value><array><data>\n<value><array><data>\n<value><string>file</string></value>\n<value><string>5.11</string></value>\n<value><string>2+deb7u7</string></value>\n<value><string></string></value>\n<value><string>amd64-deb</string></value>\n</data></array></value>\n</data></array></value>\n</param>\n</params>\n</methodCall>\n", 'version': 2, 'id': 71505}
updateLoginInfo() login info
D: login(forceUpdate=True) invoked
logging into up2date server
D: rpcServer: Calling XMLRPC up2date.login
D: writeCachedLogin() invoked
D: Wrote pickled loginInfo at 1427448054.83 with expiration of 1427451654.83 seconds.
successfully retrieved authentication token from up2date server
D: logininfo:{'X-RHN-Server-Id': 1000010443, 'X-RHN-Auth-Server-Time': '1427448055.4', 'X-RHN-Auth': 'GlUAmC3eSJG9c/Xks9lcjzidAuTr5sCHD6PLHqoUuqI=', 'X-RHN-Auth-Channels': [['wheezy', '20150125104421', '1', '1'], ['wheezy-security', '20150128162205', '0', '1'], ['wheezy-updates', '20150123153327', '0', '1']], 'X-RHN-Auth-User-Id': '', 'X-RHN-Auth-Expire-Offset': '3600.0'}
D: handle_action{'action': "<?xml version='1.0'?>\n<methodCall>\n<methodName>packages.update</methodName>\n<params>\n<param>\n<value><array><data>\n<value><array><data>\n<value><string>file</string></value>\n<value><string>5.11</string></value>\n<value><string>2+deb7u7</string></value>\n<value><string></string></value>\n<value><string>amd64-deb</string></value>\n</data></array></value>\n</data></array></value>\n</param>\n</params>\n</methodCall>\n", 'version': 2, 'id': 71505}
D: handle_action actionid = 71505, version = 2
D: do_call packages.update([['file', '5.11', '2+deb7u7', '', 'amd64-deb']],){'cache_only': None}
D: Called update[['file', '5.11', '2+deb7u7', '', 'amd64-deb']]
Apt-Spacewalk: Updating sources.list
(Lese Datenbank ... 23243 Dateien und Verzeichnisse sind derzeit installiert.)
Entfernen von apt-transport-spacewalk ...
Entfernen von rhnsd ...
Entfernen von rhncfg ...
Entfernen von rhn-client-tools ...
Trigger für man-db werden verarbeitet ...
(Lese Datenbank ... 22847 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Ersetzen von file 5.11-2+deb7u6 (durch .../file_5.11-2+deb7u7_amd64.deb) ...
Ersatz für file wird entpackt ...
Vorbereitung zum Ersetzen von libmagic1:amd64 5.11-2+deb7u6 (durch .../libmagic1_5.11-2+deb7u7_amd64.deb) ...
Ersatz für libmagic1:amd64 wird entpackt ...
Trigger für man-db werden verarbeitet ...
libmagic1:amd64 (5.11-2+deb7u7) wird eingerichtet ...
file (5.11-2+deb7u7) wird eingerichtet ...
D: Sending back response(0, 'update OK', {})
D: do_call packages.checkNeedUpdate('rhnsd=1',){}
D: Attempt to call an unsupported action packages.checkNeedUpdate('rhnsd=1',)
D: local action status: (6, 'Invalid function call attempted', {})
D: rpcServer: Calling XMLRPC registration.welcome_message
root@deb-inst-test:~#
 
Now I know about my previous error (missing directory, faulty entry within db?), I'll retry with the spacewalk packages from debian-wheezy.
 
Regards,
Robert
Gesendet: Donnerstag, 26. März 2015 um 19:30 Uhr
Von: Cypher <[email protected]>
An: [email protected]
Betreff: Re: [Spacewalk-list] Debian client not picking up scheduled jobs
hm. I suggest updating the rhn-client-tools to latest version. The Debian and Ubuntu repos are really slow getting new versions and some packages are missing entirely. Read here how to build the package yourself http://www.devops-blog.net/spacewalk/registering-ubuntu-and-debian-servers-with-spacewalk
 
Besides that, what helped me getting this to work: Schedule an action like remote execution and then do rhn_check -vv on the client. Thats also how I found the directory was missing where it puts temp stuff.
 
On Thu, Mar 26, 2015 at 7:12 PM, Robert Paschedag <[email protected]> wrote:
Hey Phil,

just checked... the directory is there.

It looks like, the client does not find any action to perform.

Regards
Robert

Am 26.03.2015 17:07 schrieb Cypher <[email protected]>:
>
> Hey,
>
> Juts to make sure, did you create the directory /var/spool/rhn/ as I described in my blog article ?
> Other thing I noticed, your rhn-client-tools is very outdated. I'm using 1.8.26.4
>
> Best, Phil
>
> On Thu, Mar 26, 2015 at 3:18 PM, Robert Paschedag <[email protected]> wrote:
>>
>> Hi,
>>  
>> does someone have a debian wheezy (7.8) client running agains a spacewalk 2.2 server?
>>  
>> I installed the "default" debian packages
>>  
>> ii  apt-transport-spacewalk            1.0.6-2.1                      all          APT transport for communicating with Spacewalk servers
>> ii  python-rhn                         2.5.52-1                       all          Python libraries for the RHN project
>> ii  rhn-client-tools                   1.8.9-3                        amd64        Red Hat Network Client Tools
>> ii  rhncfg                             5.10.14-1ubuntu1~saucy2        all          Red Hat Network Configuration Management Client is some tools
>> ii  rhnsd                              5.0.4-3                        amd64        Red Hat Update Agent
>>  
>> to connect to spacewalk and tried the rhncfg package from http://www.devops-blog.net/spacewalk/spacewalk-remote-command-execution-with-ubuntu-debian-clients#more-504 and activated everything with
>>  
>> rhn-actions-control --enable-all
>>  
>> When I run "rhn_check" on the client, it seems to run only the "local" jobs. Scheduled jobs are not picked up
>>  
>> Any help will be appreciated.
>>  
>> Kind regards,
>> Robert
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> [email protected]
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>

_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to