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

[Paul Greene]

Ok, I thought I'd found the error (but maybe not). The systems that seemed
to be working correctly had their clients installed from a tarball of all
the RPMs needed to install the client. The newer systems that were all
failing got their rhn* packages from our local yum repos. The RPMs from the
tarball, at least most of them, had newer versions than the ones installed
from the yum repos.
So, I built a new system, used the tarballed RPM files to register the
client to the Spacewalk server, and the remote tasks worked correctly. (I
created a task, ran 'rhn_check -' to run the task right away) The new
system had a kernel # 3.10.0-1062.el7.x86_64.
Then I did a yum update, which left me with kernel #
3.10.0-1062.9.1.el7.x86_64.
After the update, the scheduled tasks started failing again but the errors
were different - I was getting back this in the output of rhn_check:
D: Sending back response(1, 'Script failed', {'output': ' ', 'base64enc':
1, 'process_end': '2020-02-14- 17:56:28', 'return _code': 256,
'process_start': '2020-02-14 17:56:28'})
Nothing more about "Invalid function call ."


On Fri, Feb 14, 2020 at 2:23 PM Stefan Bluhm 
wrote:

> Hello Paul,
>
> please check that your up2date config file contains the FQDN. Also make
> sure it is the same FQDN that the Spacewalk server is configured fore.
>
> Best wishes,
>
> Stefan
>
> ----------
> *Von: *"Paul Greene" 
> *An: *spacewalk-list@redhat.com
> *Gesendet: *Freitag, 14. Februar 2020 18:15:17
> *Betreff: *Re: [Spacewalk-list] "Invalid function call attempted (code 6)"
>
> Ezequiel,
> When I run rhn_check -, the only line in there that looks like an
> error message is "couldn't find any keys in /var/lib/rpm/pubkeys/*.key",
> (the pubkey folder doesn't exist)
>
> but then the next line is "loading keyring from rpmdb", so it looks like
> it gets the key from there.
>
> I get those same messages though on both the machines that fail and the
> ones that succeed.
>
> Paul
>
> On Fri, Feb 14, 2020 at 11:51 AM Paul Greene 
> wrote:
>
>> What version of 7 are you running? (including kernel #?)
>>
>> On Fri, Feb 14, 2020 at 11:17 AM Ezequiel Sozzi  wrote:
>>
>>> Hi Paul,
>>> Versions should not be the problem, I'm managing almost 4000 servers
>>> with spacewalk and 35% are Centos6 while the other 65% are Centos7.
>>> have you tried to perform a rhn_check - from the client? That could
>>> bring you more information.
>>>
>>> BR,
>>>
>>> El vie., 14 de feb. de 2020 a la(s) 13:12, Paul Greene (
>>> paul.greene...@gmail.com) escribió:
>>>
>>>> Ezequiel,
>>>>
>>>> I tried it but it didn't seem to do anything.  😬
>>>> These systems have no connection to the internet - our repositories are
>>>> all internal to the network (one repo for base, one for updates, and one
>>>> for EPEL), and they have all the latest updates anyway, so there was
>>>> nothing to update.
>>>> Not sure where to go with this.
>>>> Just to add to my second post - older versions of CentOS 7 aren't
>>>> having issues, and there's many systems still on CentOS 6 that don't have
>>>> any issues either. So that leads me to believe there's something about the
>>>> differences in OS versions that are the root of the problem.
>>>>
>>>> Paul
>>>>
>>>> On Thu, Feb 13, 2020 at 7:23 PM Ezequiel Sozzi 
>>>> wrote:
>>>>
>>>>> Hi Paul,
>>>>> This a more often issue than everybody things, in order to fix this,
>>>>> what we do is to run the next commands on the client side:
>>>>>
>>>>> Disable all the plugins to disable rhnplugin: sed -i
>>>>> 's/plugins=1/plugins=0/g' /etc/yum.conf
>>>>>
>>>>> Disable all the external repositores: yum-config-manager --disable \*
>>>>>
>>>>> Re-enable all the plugins to enable rhnplugin: sed -i
>>>>> 's/plugins=0/plugins=1/g' /etc/yum.conf
>>>>> Update all the packages related to rpm, rhn, and yum: yum update rpm*
>>>>> rhn* yum* -y
>>>>>
>>>>> This fix the issue. At least that's my experience. Hope this helps.
>>>>>
>>>>> BR,
>>>>>
>>>>> Ezequiel
>>>>>
>>>>>
>>>>>
>>>&g

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

[Stefan Bluhm]

Hello Paul, 

please check that your up2date config file contains the FQDN. Also make sure it 
is the same FQDN that the Spacewalk server is configured fore. 

Best wishes, 

Stefan 


Von: "Paul Greene"  
An: spacewalk-list@redhat.com 
Gesendet: Freitag, 14. Februar 2020 18:15:17 
Betreff: Re: [Spacewalk-list] "Invalid function call attempted (code 6)" 

Ezequiel, 
When I run rhn_check -, the only line in there that looks like an error 
message is "couldn't find any keys in /var/lib/rpm/pubkeys/*.key", (the pubkey 
folder doesn't exist) 

but then the next line is "loading keyring from rpmdb", so it looks like it 
gets the key from there. 

I get those same messages though on both the machines that fail and the ones 
that succeed. 

Paul 

On Fri, Feb 14, 2020 at 11:51 AM Paul Greene < [ 
mailto:paul.greene...@gmail.com | paul.greene...@gmail.com ] > wrote: 



What version of 7 are you running? (including kernel #?) 

On Fri, Feb 14, 2020 at 11:17 AM Ezequiel Sozzi < [ mailto:soz...@gmail.com | 
soz...@gmail.com ] > wrote: 

BQ_BEGIN

Hi Paul, 
Versions should not be the problem, I'm managing almost 4000 servers with 
spacewalk and 35% are Centos6 while the other 65% are Centos7. 
have you tried to perform a rhn_check - from the client? That could bring 
you more information. 

BR, 

El vie., 14 de feb. de 2020 a la(s) 13:12, Paul Greene ( [ 
mailto:paul.greene...@gmail.com | paul.greene...@gmail.com ] ) escribió: 

BQ_BEGIN

Ezequiel, 

I tried it but it didn't seem to do anything. 😬 
These systems have no connection to the internet - our repositories are all 
internal to the network (one repo for base, one for updates, and one for EPEL), 
and they have all the latest updates anyway, so there was nothing to update. 
Not sure where to go with this. 
Just to add to my second post - older versions of CentOS 7 aren't having 
issues, and there's many systems still on CentOS 6 that don't have any issues 
either. So that leads me to believe there's something about the differences in 
OS versions that are the root of the problem. 

Paul 

On Thu, Feb 13, 2020 at 7:23 PM Ezequiel Sozzi < [ mailto:soz...@gmail.com | 
soz...@gmail.com ] > wrote: 

BQ_BEGIN

Hi Paul, 
This a more often issue than everybody things, in order to fix this, what we do 
is to run the next commands on the client side: 


Disable all the plugins to disable rhnplugin: sed -i 's/plugins=1/plugins=0/g' 
/etc/yum.conf 

Disable all the external repositores: yum-config-manager --disable \* 

Re-enable all the plugins to enable rhnplugin: sed -i 's/plugins=0/plugins=1/g' 
/etc/yum.conf 
Update all the packages related to rpm, rhn, and yum: yum update rpm* rhn* yum* 
-y 

This fix the issue. At least that's my experience. Hope this helps. 

BR, 

Ezequiel 



El jue., 13 de febrero de 2020 7:26 p. m., Paul Greene < [ 
mailto:paul.greene...@gmail.com | paul.greene...@gmail.com ] > escribió: 

BQ_BEGIN

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? 

I looked in /var/log/up2date on the clients that failed and get just these 
messages at the time the scheduled task failed: 

up2date updateLoginfo() login info 
up2date logging into up2date server 
up2date successfully retrieved authentication token from up2date server 
___ 
Spacewalk-list mailing list 
[ mailto:Spacewalk-list@redhat.com | Spacewalk-list@redhat.com ] 
[ https://www.redhat.com/mailman/listinfo/spacewalk-list | 
https://www.redhat.com/mailman/listinfo/spacewalk-list ] 



___ 
Spacewalk-list mailing list 
[ mailto:Spacewalk-list@redhat.com | Spacewalk-list@redhat.com ] 
[ https://www.redhat.com/mailman/listinfo/spacewalk-list | 
https://www.redhat.com/mailman/listinfo/spacewalk-list ] 

BQ_END

___ 
Spacewalk-list mailing list 
[ mailto:Spacewalk-list@redhat.com | Spacewalk-list@redhat.com ] 
[ https://www.redhat.com/mailman/listinfo/spacewalk-list | 
https://www.redhat.com/mailman/listinfo/spacewalk-list ] 

BQ_END

___ 
Spacewalk-list mailing list 
[ mailto:Spacewalk-li

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

[Paul Greene]

Ezequiel,
When I run rhn_check -, the only line in there that looks like an error
message is "couldn't find any keys in /var/lib/rpm/pubkeys/*.key", (the
pubkey folder doesn't exist)

but then the next line is "loading keyring from rpmdb", so it looks like it
gets the key from there.

I get those same messages though on both the machines that fail and the
ones that succeed.

Paul

On Fri, Feb 14, 2020 at 11:51 AM Paul Greene 
wrote:

> What version of 7 are you running? (including kernel #?)
>
> On Fri, Feb 14, 2020 at 11:17 AM Ezequiel Sozzi  wrote:
>
>> Hi Paul,
>>
>> Versions should not be the problem, I'm managing almost 4000 servers with
>> spacewalk and 35% are Centos6 while the other 65% are Centos7.
>> have you tried to perform a rhn_check - from the client? That could
>> bring you more information.
>>
>> BR,
>>
>> El vie., 14 de feb. de 2020 a la(s) 13:12, Paul Greene (
>> paul.greene...@gmail.com) escribió:
>>
>>> Ezequiel,
>>>
>>> I tried it but it didn't seem to do anything.  😬
>>> These systems have no connection to the internet - our repositories are
>>> all internal to the network (one repo for base, one for updates, and one
>>> for EPEL), and they have all the latest updates anyway, so there was
>>> nothing to update.
>>> Not sure where to go with this.
>>> Just to add to my second post - older versions of CentOS 7 aren't having
>>> issues, and there's many systems still on CentOS 6 that don't have any
>>> issues either. So that leads me to believe there's something about the
>>> differences in OS versions that are the root of the problem.
>>>
>>> Paul
>>>
>>> On Thu, Feb 13, 2020 at 7:23 PM Ezequiel Sozzi  wrote:
>>>
 Hi Paul,

 This a more often issue than everybody things, in order to fix this,
 what we do is to run the next commands on the client side:

 Disable all the plugins to disable rhnplugin: sed -i
 's/plugins=1/plugins=0/g' /etc/yum.conf

 Disable all the external repositores: yum-config-manager --disable \*

 Re-enable all the plugins to enable rhnplugin: sed -i
 's/plugins=0/plugins=1/g' /etc/yum.conf
 Update all the packages related to rpm, rhn, and yum: yum update rpm*
 rhn* yum* -y

 This fix the issue. At least that's my experience. Hope this helps.

 BR,

 Ezequiel



 El jue., 13 de febrero de 2020 7:26 p. m., Paul Greene <
 paul.greene...@gmail.com> escribió:

> 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?
>
> I looked in /var/log/up2date on the clients that failed and get just
> these messages at the time the scheduled task failed:
>
> up2date updateLoginfo() login info
> up2date logging into up2date server
> up2date successfully retrieved authentication token from up2date server
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list

 ___
 Spacewalk-list mailing list
 Spacewalk-list@redhat.com
 https://www.redhat.com/mailman/listinfo/spacewalk-list
>>>
>>> ___
>>> Spacewalk-list mailing list
>>> Spacewalk-list@redhat.com
>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>> ___
>> Spacewalk-list mailing list
>> Spacewalk-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[Paul Greene]

What version of 7 are you running? (including kernel #?)

On Fri, Feb 14, 2020 at 11:17 AM Ezequiel Sozzi  wrote:

> Hi Paul,
>
> Versions should not be the problem, I'm managing almost 4000 servers with
> spacewalk and 35% are Centos6 while the other 65% are Centos7.
> have you tried to perform a rhn_check - from the client? That could
> bring you more information.
>
> BR,
>
> El vie., 14 de feb. de 2020 a la(s) 13:12, Paul Greene (
> paul.greene...@gmail.com) escribió:
>
>> Ezequiel,
>>
>> I tried it but it didn't seem to do anything.  😬
>> These systems have no connection to the internet - our repositories are
>> all internal to the network (one repo for base, one for updates, and one
>> for EPEL), and they have all the latest updates anyway, so there was
>> nothing to update.
>> Not sure where to go with this.
>> Just to add to my second post - older versions of CentOS 7 aren't having
>> issues, and there's many systems still on CentOS 6 that don't have any
>> issues either. So that leads me to believe there's something about the
>> differences in OS versions that are the root of the problem.
>>
>> Paul
>>
>> On Thu, Feb 13, 2020 at 7:23 PM Ezequiel Sozzi  wrote:
>>
>>> Hi Paul,
>>>
>>> This a more often issue than everybody things, in order to fix this,
>>> what we do is to run the next commands on the client side:
>>>
>>> Disable all the plugins to disable rhnplugin: sed -i
>>> 's/plugins=1/plugins=0/g' /etc/yum.conf
>>>
>>> Disable all the external repositores: yum-config-manager --disable \*
>>>
>>> Re-enable all the plugins to enable rhnplugin: sed -i
>>> 's/plugins=0/plugins=1/g' /etc/yum.conf
>>> Update all the packages related to rpm, rhn, and yum: yum update rpm*
>>> rhn* yum* -y
>>>
>>> This fix the issue. At least that's my experience. Hope this helps.
>>>
>>> BR,
>>>
>>> Ezequiel
>>>
>>>
>>>
>>> El jue., 13 de febrero de 2020 7:26 p. m., Paul Greene <
>>> paul.greene...@gmail.com> escribió:
>>>
 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?

 I looked in /var/log/up2date on the clients that failed and get just
 these messages at the time the scheduled task failed:

 up2date updateLoginfo() login info
 up2date logging into up2date server
 up2date successfully retrieved authentication token from up2date server
 ___
 Spacewalk-list mailing list
 Spacewalk-list@redhat.com
 https://www.redhat.com/mailman/listinfo/spacewalk-list
>>>
>>> ___
>>> Spacewalk-list mailing list
>>> Spacewalk-list@redhat.com
>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>> ___
>> Spacewalk-list mailing list
>> Spacewalk-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[Ezequiel Sozzi]

Hi Paul,

Versions should not be the problem, I'm managing almost 4000 servers with
spacewalk and 35% are Centos6 while the other 65% are Centos7.
have you tried to perform a rhn_check - from the client? That could
bring you more information.

BR,

El vie., 14 de feb. de 2020 a la(s) 13:12, Paul Greene (
paul.greene...@gmail.com) escribió:

> Ezequiel,
>
> I tried it but it didn't seem to do anything.  😬
> These systems have no connection to the internet - our repositories are
> all internal to the network (one repo for base, one for updates, and one
> for EPEL), and they have all the latest updates anyway, so there was
> nothing to update.
> Not sure where to go with this.
> Just to add to my second post - older versions of CentOS 7 aren't having
> issues, and there's many systems still on CentOS 6 that don't have any
> issues either. So that leads me to believe there's something about the
> differences in OS versions that are the root of the problem.
>
> Paul
>
> On Thu, Feb 13, 2020 at 7:23 PM Ezequiel Sozzi  wrote:
>
>> Hi Paul,
>>
>> This a more often issue than everybody things, in order to fix this,
>> what we do is to run the next commands on the client side:
>>
>> Disable all the plugins to disable rhnplugin: sed -i
>> 's/plugins=1/plugins=0/g' /etc/yum.conf
>>
>> Disable all the external repositores: yum-config-manager --disable \*
>>
>> Re-enable all the plugins to enable rhnplugin: sed -i
>> 's/plugins=0/plugins=1/g' /etc/yum.conf
>> Update all the packages related to rpm, rhn, and yum: yum update rpm*
>> rhn* yum* -y
>>
>> This fix the issue. At least that's my experience. Hope this helps.
>>
>> BR,
>>
>> Ezequiel
>>
>>
>>
>> El jue., 13 de febrero de 2020 7:26 p. m., Paul Greene <
>> paul.greene...@gmail.com> escribió:
>>
>>> 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?
>>>
>>> I looked in /var/log/up2date on the clients that failed and get just
>>> these messages at the time the scheduled task failed:
>>>
>>> up2date updateLoginfo() login info
>>> up2date logging into up2date server
>>> up2date successfully retrieved authentication token from up2date server
>>> ___
>>> Spacewalk-list mailing list
>>> Spacewalk-list@redhat.com
>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>> ___
>> Spacewalk-list mailing list
>> Spacewalk-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[Paul Greene]

Ezequiel,

I tried it but it didn't seem to do anything.  😬
These systems have no connection to the internet - our repositories are all
internal to the network (one repo for base, one for updates, and one for
EPEL), and they have all the latest updates anyway, so there was nothing to
update.
Not sure where to go with this.
Just to add to my second post - older versions of CentOS 7 aren't having
issues, and there's many systems still on CentOS 6 that don't have any
issues either. So that leads me to believe there's something about the
differences in OS versions that are the root of the problem.

Paul

On Thu, Feb 13, 2020 at 7:23 PM Ezequiel Sozzi  wrote:

> Hi Paul,
>
> This a more often issue than everybody things, in order to fix this,
> what we do is to run the next commands on the client side:
>
> Disable all the plugins to disable rhnplugin: sed -i
> 's/plugins=1/plugins=0/g' /etc/yum.conf
>
> Disable all the external repositores: yum-config-manager --disable \*
>
> Re-enable all the plugins to enable rhnplugin: sed -i
> 's/plugins=0/plugins=1/g' /etc/yum.conf
> Update all the packages related to rpm, rhn, and yum: yum update rpm* rhn*
> yum* -y
>
> This fix the issue. At least that's my experience. Hope this helps.
>
> BR,
>
> Ezequiel
>
>
>
> El jue., 13 de febrero de 2020 7:26 p. m., Paul Greene <
> paul.greene...@gmail.com> escribió:
>
>> 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?
>>
>> I looked in /var/log/up2date on the clients that failed and get just
>> these messages at the time the scheduled task failed:
>>
>> up2date updateLoginfo() login info
>> up2date logging into up2date server
>> up2date successfully retrieved authentication token from up2date server
>> ___
>> Spacewalk-list mailing list
>> Spacewalk-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[Ezequiel Sozzi]

Hi Paul,

This a more often issue than everybody things, in order to fix this,
what we do is to run the next commands on the client side:

Disable all the plugins to disable rhnplugin: sed -i
's/plugins=1/plugins=0/g' /etc/yum.conf

Disable all the external repositores: yum-config-manager --disable \*

Re-enable all the plugins to enable rhnplugin: sed -i
's/plugins=0/plugins=1/g' /etc/yum.conf
Update all the packages related to rpm, rhn, and yum: yum update rpm* rhn*
yum* -y

This fix the issue. At least that's my experience. Hope this helps.

BR,

Ezequiel



El jue., 13 de febrero de 2020 7:26 p. m., Paul Greene <
paul.greene...@gmail.com> escribió:

> 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?
>
> I looked in /var/log/up2date on the clients that failed and get just these
> messages at the time the scheduled task failed:
>
> up2date updateLoginfo() login info
> up2date logging into up2date server
> up2date successfully retrieved authentication token from up2date server
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[Paul Greene]

Just to add some more info that might be relevant.
The spacewalk server itself is running CentOS 7.7, kernel
3.10.0-1062.9.1.el7.x86_64, and most of the clients that are failing are
running the same kernel.
There's some machines running an older kernel - 3.10.0-862.14.4.el7.x86_64
- and on these machines they seem to reliably run the task without problems.
A small number of machines on the newer kernel succeed with the task, but
most don't.

On Thu, Feb 13, 2020 at 5:25 PM Paul Greene 
wrote:

> 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?
>
> I looked in /var/log/up2date on the clients that failed and get just these
> messages at the time the scheduled task failed:
>
> up2date updateLoginfo() login info
> up2date logging into up2date server
> up2date successfully retrieved authentication token from up2date server
>
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[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?

I looked in /var/log/up2date on the clients that failed and get just these
messages at the time the scheduled task failed:

up2date updateLoginfo() login info
up2date logging into up2date server
up2date successfully retrieved authentication token from up2date server
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[Paul Greene]

Please don't hijack threads

On Tue, Jan 21, 2020 at 4:27 PM Muhammad Mosleh Uddin 
wrote:

> No. That wasn’t the issue..
> It was the repo issue..
> Thanks for your support
>
> On Tue, Jan 21, 2020 at 4:01 PM Robert Paschedag 
> wrote:
>
>> At least one "Action" is missing in /usr/share/rhn/actions that has the
>> checkNeedUpdate
>>
>> Robert
>>
>> ⁣sent from my mobile device​
>>
>>
>>  Originale Nachricht 
>> Von: Muhammad Mosleh Uddin 
>> Gesendet: Tue Jan 21 17:18:21 GMT+01:00 2020
>> An: spacewalk-list@redhat.com
>> Betreff: Re: [Spacewalk-list] Invalid function call attempted (code 6)
>>
>> Hi.
>> Thanks for your respond.
>> No, it wasnt the issue.
>>
>>
>> On Mon, Jan 20, 2020 at 4:52 AM Michael Mraka 
>> wrote:
>>
>> > 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@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
>> >
>> > It looks like yum-rhn-plugin is missing on the client.
>> >
>> > Regards,
>> >
>> > --
>> > Michael Mráka
>> > System Management Engineering, Red Hat
>> >
>> > ___
>> > Spacewalk-list mailing list
>> > Spacewalk-list@redhat.com
>> > https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>>
>>
>> --
>>
>>
>>
>>
>> Muhammad Mosleh Uddin
>>
>>
>> 
>>
>> ___
>> Spacewalk-list mailing list
>> Spacewalk-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>>
>> ___
>> Spacewalk-list mailing list
>> Spacewalk-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> --
> Sent from Iphone
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[Muhammad Mosleh Uddin]

No. That wasn’t the issue..
It was the repo issue..
Thanks for your support

On Tue, Jan 21, 2020 at 4:01 PM Robert Paschedag 
wrote:

> At least one "Action" is missing in /usr/share/rhn/actions that has the
> checkNeedUpdate
>
> Robert
>
> ⁣sent from my mobile device​
>
>
>  Originale Nachricht 
> Von: Muhammad Mosleh Uddin 
> Gesendet: Tue Jan 21 17:18:21 GMT+01:00 2020
> An: spacewalk-list@redhat.com
> Betreff: Re: [Spacewalk-list] Invalid function call attempted (code 6)
>
> Hi.
> Thanks for your respond.
> No, it wasnt the issue.
>
>
> On Mon, Jan 20, 2020 at 4:52 AM Michael Mraka 
> wrote:
>
> > 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@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
> >
> > It looks like yum-rhn-plugin is missing on the client.
> >
> > Regards,
> >
> > --
> > Michael Mráka
> > System Management Engineering, Red Hat
> >
> > ___
> > Spacewalk-list mailing list
> > Spacewalk-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
>
> --
>
>
>
>
> Muhammad Mosleh Uddin
>
>
> 
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list

-- 
Sent from Iphone
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[Robert Paschedag]

At least one "Action" is missing in /usr/share/rhn/actions that has the 
checkNeedUpdate

Robert

⁣sent from my mobile device​


 Originale Nachricht 
Von: Muhammad Mosleh Uddin 
Gesendet: Tue Jan 21 17:18:21 GMT+01:00 2020
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Invalid function call attempted (code 6)

Hi.
Thanks for your respond.
No, it wasnt the issue.


On Mon, Jan 20, 2020 at 4:52 AM Michael Mraka 
wrote:

> 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@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
>
> It looks like yum-rhn-plugin is missing on the client.
>
> Regards,
>
> --
> Michael Mráka
> System Management Engineering, Red Hat
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list



-- 




Muhammad Mosleh Uddin




___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list


___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[Muhammad Mosleh Uddin]

Hi.
Thanks for your respond.
No, it wasnt the issue.


On Mon, Jan 20, 2020 at 4:52 AM Michael Mraka 
wrote:

> 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@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
>
> It looks like yum-rhn-plugin is missing on the client.
>
> Regards,
>
> --
> Michael Mráka
> System Management Engineering, Red Hat
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list



-- 




Muhammad Mosleh Uddin
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[Michael Mraka]

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@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

It looks like yum-rhn-plugin is missing on the client.

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [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@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@test01 yum.repos.d]# /usr/sbin/osad -
2020-01-17 15:47:26 osad._setup_config: Updating configuration
2020-01-17 15:47:26 jabber_lib.setup_connection: Connecting to
f01.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
f01.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 
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
f01.4m.com
2020-01-17 15:47:26 jabber_lib.push_to_background: Pushing process into
background


[root@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 
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 
> 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@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list



-- 




Muhammad Mosleh Uddin
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[Paul Greene]

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 
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@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[Michael Mraka]

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@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[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?
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Invalid function call attempted (code 6) during bootstrap config deploy

[DiOrio, Max]

Hi,

Just getting set up with Spacewalk and testing my first bootstrap client setup 
of a RHEL 7.4 client.

It successfully deployed the activation key, subscribed to the channels and 
installed/updated the packages, however it failed deploying the config files to 
the system with "Client execution returned "Invalid function call attempted" 
(code 6)".

However I can re-push the config files from the Spacewalk web page and osad 
picks up the task and updates them on the client successfully.

I can't seem to find any client side logs for bootstrap either.  Any thoughts?

Max DiOrio
Global Systems Administrator
[cid:image002.jpg@01D26A5C.D5C0BF00]
201 Fuller Road, Suite 202
Albany, NY 12203-3621
Phone: +518-238-6516 | Mobile: +518-944-5289
max.dio...@ieeeglobalspec.com

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list