Jan,
Thanks! This additional patch makes a huge difference.
I tested it with 250 osad clients running simultaneously and the peak
connection count was about 115 and it still seems to drop quickly when activity
ceases. Performance was noticeably better than it's been in a very long time.
Whe
I believe that to be correct based on reviewing kickstart files on hosts
configured with 1.8 vs 1.9. Thanks for the pointer to the bug.
On Wed, Mar 13, 2013 at 3:09 AM, Jan Pazdziora wrote:
> On Tue, Mar 12, 2013 at 04:03:32PM -0400, John Pittman wrote:
> > After upgrading my Spacewalk 1.8 syste
Yup, that fixed it. Thanks! :)
Cheers,
Piotr Maksymiuk
On 12 mar 2013, at 23:21, Mattias Giese wrote:
> On Tue, 12 Mar 2013 10:42:23 +0100
> "Maksymiuk, Piotr" wrote:
>
>> Hi
>>
>> Good catch! It does correlate, i didn't put in any gpg info for the
>> channel that didn't have the problem! So
On Tue, Mar 12, 2013 at 05:52:46PM +, Coffman, Anthony J wrote:
> I applied the patch and rebooted to start things from a clean slate.
>
> The patch doesn't seem to fix the issue.
>
> The Postgres DB idle connections are still rising to more than 1000 very
> rapidly and staying high even aft
Hello,
i've applied the patch on my development SW server (v1.9, RHEL 5, pgsql).
Before the patch, I received errors by email stating that postgresql
max_connections was reached.
After this patch, I don't have this issue anymore.
This dev server has only a couple of clients so I can't tell if this
On Tue, Mar 12, 2013 at 04:03:32PM -0400, John Pittman wrote:
> After upgrading my Spacewalk 1.8 system to 1.9 (and Centos 6.4), my
> kickstarts no longer push the gpg keys assigned to each profile. After a
> kickstart finishes, I receive NOKEY errors on any package installs from the
> assigned cha
