hat.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 /v
etreff: 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
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
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
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,
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
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
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
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
on" 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+0
ce
>
>
> 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.
>
ewalk-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 spacew
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
> >
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
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
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
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
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
18 matches
Mail list logo
