Also version 1.8 has a lot of improvements with PostgreSQL so an update may help you. But I'm curious what's the iowait on the pegged cpu?



-- Sent from my HP Pre3


On Feb 21, 2013 11:16 AM, Jan Pazdziora <[email protected]> wrote:

On Tue, Jan 08, 2013 at 11:44:04AM -0500, Boyd, Robert wrote:
> Sometime this morning my spacewalk server pegged 100% on cpu utilization and has been staying there ever since. I tried a reboot, and just for grins updated errata/packages on the server. After rebooting it's still pegging the cpu usage with this process:
>
> postgres 2888 77.7 1.3 470128 53708 ? Rs 10:35 52:05 postgres: spaceuser spaceschema 127.0.0.1(46206) SELECT
>
> I am able to use the Spacewalk admin website without any problem other than a bit of slow response.
> How can I discover what is causing this (and hopefully fix it)?

Try

select * from pg_stat_activity;

to see what select is causing the trouble and whether it's one select
which is taking many minutes or a stream of selects..

--
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

Reply via email to