Thread: I get these about every 1.5 days

Steve W. Neal wrote:
> And then the database dies requiring me to reboot my server....any ideas?

How does it "require" you to reboot?

> Thanks!
>  
>  
> 2006-05-23 11:10:47 ERROR  : Could not resolve hostname localhost
> 2006-05-23 11:10:50 ERROR  : No connection to database.

Which logfile is that? Where is your database running
and where pgadmin? What kind of machine(s), operanding
system(s) ?


> (This never occurred before I loaded postgre and it only occurs when I
> launch pgadmin if I haven't rebooted my server for 1.5 days.....)

btw, there is no such thing as "postgre" :)

And even if - what I doubt - postgres has a problem, you never
need to reboot the whole server...

Regards
Tino

vanilla ms 2000 on hp dual processor with 4g ram and raid 5 disk array

postgre 8.0 and pgadmin 1.2 on the same drive

logfile is pgadmin.log which shows the error below

it is actually pdagmin that can't resolve local host - it requires a reboot...the application runs fine until pgadmin
islaunched - then the app dies requiring a server restart (stopping and starting services doesn't do it)....after a
serverreboot, pgadmin works fine for about 1.5 days - this scenario repeats about every 1.5 days. 

if it isn't postgre, what is it?  (I am not a sql person - yet!)



-----Original Message-----
From: Tino Wildenhain [mailto:tino@wildenhain.de]
Sent: Wednesday, May 24, 2006 2:48 PM
To: Steve W. Neal
Cc: pgadmin-support@postgresql.org
Subject: Re: [pgadmin-support] I get these about every 1.5 days


Steve W. Neal wrote:
> And then the database dies requiring me to reboot my server....any ideas?

How does it "require" you to reboot?

> Thanks!
>
>
> 2006-05-23 11:10:47 ERROR  : Could not resolve hostname localhost
> 2006-05-23 11:10:50 ERROR  : No connection to database.

Which logfile is that? Where is your database running
and where pgadmin? What kind of machine(s), operanding
system(s) ?


> (This never occurred before I loaded postgre and it only occurs when I
> launch pgadmin if I haven't rebooted my server for 1.5 days.....)

btw, there is no such thing as "postgre" :)

And even if - what I doubt - postgres has a problem, you never
need to reboot the whole server...

Regards
Tino

I blame Windows. Try using 127.0.0.1 instead of localhost.

-- Tino Didriksen

Steve W. Neal wrote:
> <snip> it is actually pdagmin that can't resolve local host </snip>