Re: [Spacewalk-list] Error code 32

2018-03-23 Thread Soham Chakraborty
Hi Robert/Michael et al So I noticed that there are two fixes. The first solution is to remove the repodata of the offending channels from /var/cache/rhn/repodata and then wait for the metadata to be regenerated. I don't know what that does but apparently it fixes it. The second thing is I ran

Re: [Spacewalk-list] Error code 32

2018-03-15 Thread Michael Mraka
Soham Chakraborty: > Hi all, > > I am trying to figure out whether anyone has seen this problem. After I > posted this thread, I had some discussion with Jan Hutar and although I > tried all the steps he suggested (which are below), I am still stuck with > this problem. ... > The spacewalk-schema

Re: [Spacewalk-list] Error code 32

2018-03-13 Thread Robert Paschedag
Am 13. März 2018 15:57:22 MEZ schrieb Soham Chakraborty : >Hi all, > >I am trying to figure out whether anyone has seen this problem. After I >posted this thread, I had some discussion with Jan Hutar and although I >tried all the steps he suggested (which are below), I am

Re: [Spacewalk-list] Error code 32

2018-03-13 Thread Soham Chakraborty
Hi all, I am trying to figure out whether anyone has seen this problem. After I posted this thread, I had some discussion with Jan Hutar and although I tried all the steps he suggested (which are below), I am still stuck with this problem. 1) So far, I have tried to increase the memory in

[Spacewalk-list] Error code 32

2017-08-15 Thread Soham Chakraborty
Hi all, I faced an odd problem today while trying to update my clients. I had several security patches and I got most of them installed but few of the updates refused to get installed and I could not install them manually as well. The error message from event logs of spacewalk say this: Client