Skip site navigation (1) Skip section navigation (2)

Re: terminating autovacuum process due to administrator command

From: Radovan Jablonovsky <radovan(dot)jablonovsky(at)replicon(dot)com>
To: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: terminating autovacuum process due to administrator command
Date: 2012-06-25 15:00:46
Message-ID: CAJYcdTsr++DEra_ttm8yWcKiDHMO7DDO2Lttwp1-e5BN3SmXbg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
Thanks for response,

How were the connections refused (error message)?
2012-06-13 13:45:38.809 MDT [25172]: [1-1] FATAL:  remaining connection
slots are reserved for non-replication superuser connections
2012-06-13 13:45:38.889 MDT [25173]: [1-1] FATAL:  remaining connection
slots are reserved for non-replication superuser connections
2012-06-13 13:45:38.895 MDT [25174]: [1-1] FATAL:  remaining connection
slots are reserved for non-replication superuser connections

Could it be that there are already max_connections sessions? max_connection
was set to 600, when issue occurred the db server had 85 connection and
server was under medium load.

Server details:
We're running postgres 9.1.1 linux x64 centos 5.8

aspdata=# select version();
                                                    version
---------------------------------------------------------------------------------------------------------------
 PostgreSQL 9.1.1 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2
20080704 (Red Hat 4.1.2-52), 64-bit


We currently have 1 DB we use for multiple independent tenant schemas. The
database size is current 56227005240 bytes as reported by pg_database_size.
There are 557 schemas each with about 1300 objects (760 tables 520 views).


On Mon, Jun 25, 2012 at 2:03 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>wrote:

> Radovan Jablonovsky wrote:
> > Could you please help with this peculiar problem?
> >
> >
> > In PostgreSQL log occurred this message:
> >
> > 2012-06-13 12:58:45.876 MDT [17536]: [1-1] FATAL:  terminating
> autovacuum process due to administrator
> > command
> > The server  worked for 48 minutes after and then it started refuse
> non-superuser connections, which
> > effectively rendered it unusable for client applications.
> > What could cause this behaviour?
>
> You gave very little information.
>
> How were the connections refused (error message)?
> Could it be that there are already max_connections sessions?
>
> Yours,
> Laurenz Albe
>



-- 

*Radovan Jablonovsky* | SaaS DBA | Phone 1-403-262-6519 (ext. 256) | Fax
1-403-233-8046****


*

Replicon | Hassle-Free Time & Expense Management Software - 7,300 Customers
- 70 Countries
www.replicon.com | facebook <http://www.facebook.com/Replicon.inc> |
twitter<http://twitter.com/Replicon>
 | blog <http://www.replicon.com/blog/> | contact
us<http://www.replicon.com/about_replicon/contact_us.aspx>

We are hiring! | search
jobs<http://tbe.taleo.net/NA2/ats/careers/searchResults.jsp?org=REPLICON&cws=1&act=sort&sortColumn=1&__utma=1.651918544.1299001662.1299170819.1299174966.10&__utmb=1.8.10.1299174966&__utmc=1&__utmx=-&__utmz=1.1299174985.10.3.utmcsr=google%7Cutmccn=(organic)%7Cutmcmd=organic%7Cutmctr=replicon%20careers&__utmv=1.%7C3=Visitor%20Type=Prospects=1,&__utmk=40578466>
*

In response to

Responses

pgsql-admin by date

Next:From: Kevin GrittnerDate: 2012-06-25 15:19:28
Subject: Re: starting postgres with an empty px_xlog folder
Previous:From: Mike BroersDate: 2012-06-25 14:45:25
Subject: Re: starting postgres with an empty px_xlog folder

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group