[Spacewalk-list] Spacewalk 2.8 - Pushing Errata Patches Failing

[Eric Griswold]

Hi Robert,

Thank you for the information.

rhn-actions-control is all enabled:
[client]$ rhn-actions-control --report
deploy is enabled
diff is enabled
upload is enabled
mtime_upload is enabled
run is enabled

/usr/share/rhn/actions/ contains
-rw-r--r--. 1 root root  2364 Apr 10 22:05 errata.py
-rw-r--r--. 2 root root  2196 Apr 10 22:05 errata.pyc
-rw-r--r--. 2 root root  2196 Apr 10 22:05 errata.pyo
-rw-r--r--. 1 root root 20398 Apr 10 22:05 packages.py
-rw-r--r--. 1 root root 16680 Apr 10 22:05 packages.pyc
-rw-r--r--. 1 root root 16598 Apr 10 22:05 packages.pyo


-----Original Message-----
From: Robert Paschedag [mailto:robert.paschedag at web.de]
Sent: Thursday, May 24, 2018 11:09 AM
To: spacewalk-list at redhat.com; Eric Griswold <Eric.Griswold at ipreo.com>; spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.8 - Pushing Errata Patches Failing

Am 24. Mai 2018 16:49:39 MESZ schrieb Eric Griswold <Eric.Griswold at ipreo.com>:
>This is the outcome of 'rhn_check -vvv' on the client
>
>D: opening  db environment /var/lib/rpm cdb:0x401
>D: opening  db index       /var/lib/rpm/Packages 0x400 mode=0x0
>D: locked   db index       /var/lib/rpm/Packages
>D: opening  db index       /var/lib/rpm/Providename 0x400 mode=0x0
>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
>D: closed   db index       /var/lib/rpm/Providename
>D: closed   db index       /var/lib/rpm/Packages
>D: closed   db environment /var/lib/rpm
>
>From: Eric Griswold
>Sent: Wednesday, May 23, 2018 8:07 AM
>To: 'spacewalk-list at redhat.com' <spacewalk-list at redhat.com>
>Subject: Spacewalk 2.8 - Pushing Errata Patches Failing
>
>Hello -
>
>I am new to spacewalk, but am running into some issues pushing patches
>from my spacewalk server. I imported an internal repo to the spacewalk
>server. I then added two test clients to the inventory. The server is
>successfully able to see the clients and all of their information. My
>Errata list is populated with CentOS advisories. When I attempt to push
>the errata patches to the clients, they fail.
>
>The error I am receiving on failure: 'Invalid function call attempted'
>
>/var/spacewalk/systemlogs is emtpy. I am not finding much in
>/var/log/rhn/ I'm not sure where else I should be searching for logs.
>
>Appreciate any support here & where I should be hunting logs for this
>software.
>
>Thanks,
>Eric
>
>
>
>********* Confidential Disclaimer *********
>
>This e-mail message and any attachments are confidential.
>Dissemination, distribution or copying of this e-mail or any
>attachments by anyone other than the intended recipient is prohibited.
>If you are not the intended recipient, please notify Ipreo immediately
>by replying to this e-mail, and destroy all copies of this e-mail and
>any attachments. If you have received this e-mail as part of a
>marketing communication and you would like to unsubscribe from future
>marketing communications, please review our privacy
>policy<http://info.ipreo.com/Ipreo-Private-Policy.html> for more
>information.

Please look, if you have your rhn-actions installed and enabled.

Check rhn-actions-control and /usr/share/rhn/actions/ for presents of errata.py.

Robert
--
sent from my mobile device


********* Confidential Disclaimer *********

This e-mail message and any attachments are confidential. Dissemination, distribution or copying of this e-mail or any attachments by anyone other than the intended recipient is prohibited. If you are not the intended recipient, please notify Ipreo immediately by replying to this e-mail, and destroy all copies of this e-mail and any attachments. If you have received this e-mail as part of a marketing communication and you would like to unsubscribe from future marketing communications, please review our privacy policy<http://info.ipreo.com/Ipreo-Private-Policy.html> for more information.