I had similar issues when scaling to 6,000 or so systems and it took me months of searching and trying different things to find enable_snapshots in /etc/rhn/rhn.conf... After setting that to 0 Spacewalk having the same issue. Try it out, it may work for you as well...
In /etc/rhn/rhn.conf: enable_snapshots = 0 On Wed, Mar 22, 2017 at 11:47 AM Konstantin Raskoshnyi <[email protected]> wrote: > No any errors. > Postgres spawns a lot of processes + httpd. > So it takes around 300 seconds to run config channel on for each machine. > > On Wed, Mar 22, 2017 at 4:50 AM Michael Mraka <[email protected]> > wrote: > > Konstantin Raskoshnyi: > > We have ~1000 clients, in the evening spacewalk runs a lot of commands > > (checks files revisions for example) > > > > I'm receiving ~1000 tracebacks, clients can't connect to spacewalk. > > > > 1. Usually sp as ~300 processes, during those task ~ 1000 > > 2. I didn't change any tomcat/httpd settings > > 3. Only changed postgres setttings to be optimized for 64Gb or ram > ... > > 4. > > Any thoughts how to optimize get back sp to life? Thanks > > Hello Konstantin, > > First you have to identify which component is the bottleneck. > What's the error in traceback? > Are there any clues in /var/log/httpd/*error_log? Tomcat timeout, > postgresql timeouts, etc.? > > 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
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
