[Spacewalk-list] Invalid function call attempted (code 6)

[Muhammad Mosleh Uddin]

i paul,
my rhel client is not pulling package from spacewalk server.
my spacewalk client is test01. spacewalk can sync redhat channel and I see
some packages.

[root at test01 yum.repos.d]# rhn_check -vv
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 at test01 yum.repos.d]# /usr/sbin/osad -vvvv
2020-01-17 15:47:26 osad._setup_config: Updating configuration
2020-01-17 15:47:26 jabber_lib.setup_connection: Connecting to
fxxxx01.4m.com
2020-01-17 15:47:26 jabber_lib._get_jabber_client:
2020-01-17 15:47:26 jabber_lib._get_jabber_client: Connecting to
fxxxx01.4m.com
2020-01-17 15:47:26 jabber_lib.__init__:
2020-01-17 15:47:26 jabber_lib.__init__:
2020-01-17 15:47:26 jabber_lib.check_cert: Loading cert <X509Name object
'/C=US/ST=New York/L=New York/O=4m.com /OU=IT/CN= fxxxx01.4m.com '>
2020-01-17 15:47:26 jabber_lib.connect:
2020-01-17 15:47:26 jabber_lib.process: 300
2020-01-17 15:47:26 jabber_lib.process: None
2020-01-17 15:47:26 jabber_lib.connect: Preparing for TLS handshake
2020-01-17 15:47:26 jabber_lib.process: None
2020-01-17 15:47:26 jabber_lib.process: None
2020-01-17 15:47:26 jabber_lib.setup_connection: Connected to jabber server
fxxxx01.4m.com
2020-01-17 15:47:26 jabber_lib.push_to_background: Pushing process into
background


[root at test01 yum.repos.d]# yum repolist
Loaded plugins: product-id, rhnplugin, search-disabled-repos,
subscription-manager
This system is receiving updates from RHN Classic or Red Hat Satellite.
repo id
 repo name
  status
rhel7base-x86_64
rhel7base-x86_64
 0
repolist: 0


On Fri, Jan 17, 2020 at 3:17 PM Paul Greene <paul.greene.va at gmail.com>
wrote:

> I checked into a few systems that failed and looked for logs at the time
> the failure supposedly happened, and it just had these 3 lines at that
> specific time:
>
> up2date updateLoginfo() login info
> up2date logging into up2date server
> up2date successfully retrieved authentication token from up2date server
>
> On Fri, Jan 17, 2020 at 7:45 AM Michael Mraka <michael.mraka at redhat.com>
> wrote:
>
>> Paul Greene:
>> > I have a spacewalk 2.9 server with CentOS 7 clients. When I run a
>> scheduled
>> > remote command on 50 systems, usually about half of the systems will get
>> > marked as "failed" with the error "Invalid function call attempted (code
>> > 6)".
>> >
>> > They all have the same configuration, and every line put in the remote
>> > command will run just fine from a command prompt. If I go into a system
>> > that has been marked "failed" and manually verify if the command did
>> what
>> > it was supposed to do, many times it actually did succeed, but was still
>> > marked "failed". And there are some that did in fact fail.
>> >
>> > How can I address this error to get rid of the false "failed" messages?
>>
>> Hello Paul,
>>
>> There should be more detailed error message in /var/log/up2date on
>> failed client.
>>
>> Regards,
>>
>> --
>> Michael Mráka
>> System Management Engineering, Red Hat
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list



-- 




Muhammad Mosleh Uddin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20200117/dd7cfe4c/attachment.htm>