<div dir="ltr"><div>Ezequiel,</div><div>When I run rhn_check -vvvv, 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)<br></div><div><br></div><div>but then the next line is "loading keyring from rpmdb", so it looks like it gets the key from there.</div><div><br></div><div>I get those same messages though on both the machines that fail and the ones that succeed.</div><div><br></div><div>Paul<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 14, 2020 at 11:51 AM Paul Greene <<a href="mailto:paul.greene.va@gmail.com">paul.greene.va@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">What version of 7 are you running? (including kernel #?)<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 14, 2020 at 11:17 AM Ezequiel Sozzi <<a href="mailto:sozeze@gmail.com" target="_blank">sozeze@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Paul, <div><br></div><div>Versions should not be the problem, I'm managing almost 4000 servers with spacewalk and 35% are Centos6 while the other 65% are Centos7. </div><div>have you tried to perform a rhn_check -vvvv from the client? That could bring you more information. </div><div><br></div><div>BR, </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El vie., 14 de feb. de 2020 a la(s) 13:12, Paul Greene (<a href="mailto:paul.greene.va@gmail.com" target="_blank">paul.greene.va@gmail.com</a>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div></div><div>Ezequiel,</div><div><br></div><div>I tried it but it didn't seem to do anything. 😬</div><div></div><div>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.</div><div>Not sure where to go with this.</div><div>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.</div><div><br></div><div>Paul<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 13, 2020 at 7:23 PM Ezequiel Sozzi <<a href="mailto:sozeze@gmail.com" target="_blank">sozeze@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Paul, <div><br></div><div>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:</div><div><div style="box-sizing:border-box"><div><div><p><font size="4" face="arial, sans-serif">Disable all the plugins to disable rhnplugin: sed -i 's/plugins=1/plugins=0/g' /etc/yum.conf</font></p>
<p><font size="4" face="arial, sans-serif">Disable all the external repositores: yum-config-manager --disable \*</font></p>
<p><font size="4" face="arial, sans-serif">Re-enable all the plugins to enable rhnplugin: sed -i 's/plugins=0/plugins=1/g' /etc/yum.conf<br></font></p>
</div>
</div>
</div><div><font size="4" face="arial, sans-serif">Update all the packages related to rpm, rhn, and yum: yum update rpm* rhn* yum* -y</font></div></div><div><span style="font-family:"Segoe UI","Helvetica Neue","Apple Color Emoji","Segoe UI Emoji",Helvetica,Arial,sans-serif;font-size:14px"><br></span></div><div><span style="font-family:"Segoe UI","Helvetica Neue","Apple Color Emoji","Segoe UI Emoji",Helvetica,Arial,sans-serif;font-size:14px">This fix the issue. At least that's my experience. Hope this helps.</span></div><div><span style="font-family:"Segoe UI","Helvetica Neue","Apple Color Emoji","Segoe UI Emoji",Helvetica,Arial,sans-serif;font-size:14px"><br></span></div><div><span style="font-family:"Segoe UI","Helvetica Neue","Apple Color Emoji","Segoe UI Emoji",Helvetica,Arial,sans-serif;font-size:14px">BR,</span></div><div><span style="font-family:"Segoe UI","Helvetica Neue","Apple Color Emoji","Segoe UI Emoji",Helvetica,Arial,sans-serif;font-size:14px"><br></span></div><div><span style="font-family:"Segoe UI","Helvetica Neue","Apple Color Emoji","Segoe UI Emoji",Helvetica,Arial,sans-serif;font-size:14px">Ezequiel</span></div><div><span style="font-family:"Segoe UI","Helvetica Neue","Apple Color Emoji","Segoe UI Emoji",Helvetica,Arial,sans-serif;font-size:14px"><br></span></div><div><br></div></div><div dir="auto"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El jue., 13 de febrero de 2020 7:26 p. m., Paul Greene <<a href="mailto:paul.greene.va@gmail.com" target="_blank">paul.greene.va@gmail.com</a>> escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">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)".<br><br>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.<br><br>How can I address this error to get rid of the false "failed" messages?<br><br>I looked in /var/log/up2date on the clients that failed and get just these messages at the time the scheduled task failed:<br><br>up2date updateLoginfo() login info<br>up2date logging into up2date server<br>up2date successfully retrieved authentication token from up2date server</div>
_______________________________________________<br>
Spacewalk-list mailing list<br>
<a href="mailto:Spacewalk-list@redhat.com" rel="noreferrer" target="_blank">Spacewalk-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" rel="noreferrer noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a></blockquote></div>
_______________________________________________<br>
Spacewalk-list mailing list<br>
<a href="mailto:Spacewalk-list@redhat.com" target="_blank">Spacewalk-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a></blockquote></div></div>
_______________________________________________<br>
Spacewalk-list mailing list<br>
<a href="mailto:Spacewalk-list@redhat.com" target="_blank">Spacewalk-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a></blockquote></div>
_______________________________________________<br>
Spacewalk-list mailing list<br>
<a href="mailto:Spacewalk-list@redhat.com" target="_blank">Spacewalk-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a></blockquote></div>
</blockquote></div>