I didn't see a reply on this, so I'll add what I can... Having a session replaced means you have two servers using the same Jabber ID (from osad-auth.conf). In my case, it was from VMWare cloning, and not properly cleaning up Spacewalk registration. The SW server logs should say what IPs are involved in the dueling sessions. (In your post, they were the same, but NAT or log editing may explain that.) Log on to them both and make sure /etc/sysconfig/rhn/systemid and /etc/sysconfig/rhn/osad-auth.conf are different.
On Mon, Oct 10, 2011 at 5:24 AM, Jan Pazdziora <[email protected]> wrote: > On Tue, Sep 13, 2011 at 09:02:52PM -0500, Nikhil Anand wrote: >> >> So what's going on with c2s and sm that cause these errors? Is it possible >> to tweak the timeout after which a session is "replaced"? More importantly, >> is the error I have considered normal? >> > > Hello community members, > > do you have any hints or recommendations for Nikhil? > > -- > Jan Pazdziora > Principal Software Engineer, Satellite 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
