Re: [Bacula-users] Bacula and Postgres 8.1

[Gabriele Bulfon]

..I did the test.
Specifying "localhost" and "5432" on "DB Address" and "DB Port" works fine.

Gabriele Bulfon - Sonicle S.r.l. Tel +39 028246016 Int. 30 - Fax +39 028243880 Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY http://www.sonicle.com

---

Da: Gabriele Bulfon <[EMAIL PROTECTED]>
A: Bill Moran <[EMAIL PROTECTED]> Magnus Hagander <[EMAIL PROTECTED]>
Cc: bacula-users@lists.sourceforge.net
Data: 21 settembre 2006 16.08.48 CEST
Oggetto: Re: [Bacula-users] Bacula and Postgres 8.1

I really doubt it's a network issue, in this case.
I would find the problem on all the other applications using the same postgres.
And consider that I can replicate the problem ALWAYS.

Any Bacula installation I have (10-12) will react the same once I move the DB away from localhost.

I will do another test: on localhost machines I usually omit the "DB Address" and "DB Port", so that it defaults to localhost.
I will test a machine running Director and DB on localhost, but specify the two parameters as "localhost" and "5432".....

Gabriele Bulfon - Sonicle S.r.l. Tel +39 028246016 Int. 30 - Fax +39 028243880 Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY http://www.sonicle.com

----------------------------------------------------------------------------------

Da: Bill Moran <[EMAIL PROTECTED]>
A: Magnus Hagander <[EMAIL PROTECTED]>
Cc: Gabriele Bulfon <[EMAIL PROTECTED]> bacula-users@lists.sourceforge.net
Data: 21 settembre 2006 15.51.52 CEST
Oggetto: Re: [Bacula-users] Bacula and Postgres 8.1

In response to "Magnus Hagander" <[EMAIL PROTECTED]>:

> > > Sorry for not resending the needed informations, I already sent
> > them when I first encountered the problem. But then I could solve
> > this by moving the Director together with the DB (I had another
> > Solaris machine in that situation).
> > > I'm appending the original infos here.
> > > On postgres, I just find this debug, after getting the error from
> > bconsole:
> > > LOG: unexpected EOF on client connection
> >
> > This seems to indicate that you have a networking issue.
>
> That message alone, not necessarily. It will be logged by PosgreSQL
> anytime a connection goes away without getting the close message. So a
> client program exiting without doing PQfinish() will cause this, for
> example (and this is way way common, unfortunately). Or a client program
> crashing, of course.
>
> It *can* be a sign of network issues, absolutely. But it can also be
> something else.

Agreed. I gues the point I was trying to make was that, based on the
messages from the server and the "timeout" messages on the client, my
best guess at this point is that it's a network problem.

But it wouldn't be the first time if I were wrong.

--
Bill Moran
Collaborative Fusion Inc.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users