pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: ITS ONT Alcazar, Jose Aguedo C <jacalcazar@exportbank.com.ph>
To: Tim Allen <tim@proximity.com.au>
To: ITS ONT Alcazar, Jose Aguedo C <jacalcazar@exportbank.com.ph>
Cc: pgsql-admin@postgresql.org
Subject: Re: Major Problem, need help! Can't run our website!
Date: Tue, 15 Nov 2005 12:08:55 +0800
Message-ID: <227C7FFACEA9D9118BD600096BA5A7CA011E19C6@EIBPOST> (raw)

Can anyone help me on how to create this? I will personally do this in able
not to happen again. Or can you link me to the part of the archive that
re-creates xlog? Our internet here is soooooooooo slow.
Pleasssssssseeeeeeeee... Many thanks in advance!

-----Original Message-----
From: Tim Allen [mailto:tim@proximity.com.au]
Sent: Tuesday, November 15, 2005 11:40 AM
To: ITS ONT Alcazar, Jose Aguedo C
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Major Problem, need help! Can't run our website!


ITS ONT Alcazar, Jose Aguedo C wrote:
> Anyone!
> 
> Before anything else, I have no background in PostgreSQL. But I have a
> little knowledge in Linux. We used postgreSQL to run one of our website.
It
> runs in Redhat Linux 7.3. Our System Administrator, who used to maintain
> this server, had resigned and didn't have a proper documentation on how to
> maintain this server. Right now, our NEW System Administrator is clearing
> some logs in /var/lib/pgsql/data/pg_xlog in able to free some space in the
> /var file system. It used to work before, but now, its not working
anymore.

Ouch. Tell him to stop. Though it's probably too late. The transaction 
logs (ie anything you'll find in pg_xlog) are not disposable, they're an 
important part of the database. Your new sysadmin has presumably 
corrupted your database. So you've definitely lost any recent 
transactions. What you can probably do is at least get your database up 
and running again by re-creating the xlog (aka WAL) files with empty 
data. Maybe someone else will post telling you how to do that, otherwise 
search the mailing lists archives.

> Information below is the message we are encountering when we are trying to
> connect to the website. Please, ANYONE, help us!
> 
> Warning: Unable to connect to PostgreSQL server: could not connect to
> server: Connection refused Is the server running on host localhost and
> accepting TCP/IP connections on port 5432? in
> /var/lib/phplib-7.2d/php/db_pgsql.inc on line 48
> Database error: Link-ID == false, pconnect failed
> ODBC Error: 0 ()
> Session halted.
> 
> Thanks! --AGUEDO

Tim

-- 
-----------------------------------------------
Tim Allen          tim@proximity.com.au
Proximity Pty Ltd  http://www.proximity.com.au/




view thread (18+ messages)  latest in thread

Message-ID: <227C7FFACEA9D9118BD600096BA5A7CA011E19C6@EIBPOST>
Permalink:  ../227C7FFACEA9D9118BD600096BA5A7CA011E19C6@EIBPOST/
Also on:    postgresql.org/message-id/227C7FFACEA9D9118BD600096BA5A7CA011E19C6@EIBPOST

 · 

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: jacalcazar@exportbank.com.ph, tim@proximity.com.au
  Subject: Re: Major Problem, need help! Can't run our website!
  In-Reply-To: <227C7FFACEA9D9118BD600096BA5A7CA011E19C6@EIBPOST>
  References: <227C7FFACEA9D9118BD600096BA5A7CA011E19C6@EIBPOST>

* 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