pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew T. O'Connor <matthew@zeut.net>
To: Joel Fradkin <jfradkin@wazagua.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: catastrophic error
Date: Thu, 12 May 2005 15:38:28 -0400
Message-ID: <4283B0B4.90800@zeut.net> (raw)
In-Reply-To: <000a01c55728$8abe41c0$797ba8c0@jfradkin>
References: <000a01c55728$8abe41c0$797ba8c0@jfradkin>

If you could connect to the database server from the web server and get 
data with PGAdmin then it doesn't' sound like a database or database 
server problem.  How is your web app connecting to the database?  ODBC?  
That might be a bit of an issue.  PgAdmin doesn't use ODBC, it uses 
libpq directly.

Joel Fradkin wrote:

> Hi,
>
>  
>
> I have been live for 4 days (vacuums run each night and backups done 
> each night).
>
> Today around 2:30 PM  EST my web app returned a catastrophic error.
>
> Both web servers appeared to have the issue.
>
> I could go on them and get data via pgadmin.
>
> I could log on the server (IIS servers are win2k and pg is Redhat AS4 
> running 8.0.2) and see it was not using much memory or cpu.
>
> Neither the web or database servers seemed stressed?
>
> Any ideas what I should look at?
>
> I re-booted the IIS servers and it did not fix the issue.
>
> I rebooted the database server and the web servers are back to connecting.
>
>  
>
> Being new to postgres I am not sure what to look at for the cause and 
> hopefully permanent fix to this.
>
>  
>
> Thanks in advance to any ideas (I did search the archive, but only saw 
> a mention of pre 8 versions and oid numbering wraparound).
>
>  
>
> Joel Fradkin
>
>  
>
> Wazagua, Inc.
> 2520 Trailmate Dr
> Sarasota, Florida 34243
> Tel.  941-753-7111 ext 305
>
>  
>
> jfradkin@wazagua.com <mailto:jfradkin@wazagua.com>
> www.wazagua.com <http://www.wazagua.com;
> Powered by Wazagua
> Providing you with the latest Web-based technology & advanced tools.
> © 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc
>  This email message is for the use of the intended recipient(s) and 
> may contain confidential and privileged information.  Any unauthorized 
> review, use, disclosure or distribution is prohibited.  If you are not 
> the intended recipient, please contact the sender by reply email and 
> delete and destroy all copies of the original message, including 
> attachments.
>
>  
>
>
>  
>
>  
>



view thread (6+ messages)  latest in thread

Message-ID: <4283B0B4.90800@zeut.net>
Permalink:  ../4283B0B4.90800@zeut.net/
Also on:    postgresql.org/message-id/4283B0B4.90800@zeut.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: matthew@zeut.net, jfradkin@wazagua.com
  Subject: Re: catastrophic error
  In-Reply-To: <4283B0B4.90800@zeut.net>
  References: <000a01c55728$8abe41c0$797ba8c0@jfradkin> <4283B0B4.90800@zeut.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox