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 <[email protected]> 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 > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
