That postgres db is being used on the network all day long.
- I use it from web apps through jdbc
- I use it from pgadmin on a windows laptop
- I use it from custom softwares on desktops

This problem arises only when I use bconsole on Bacula and the Director is separated from the DB.
Everything works fine only if the Director works on localhost DB.
In the logs, I did not put the Director's startup traces because they were a lot and they all went ok.

I really suspect this is something coming out only when I use bconsole.
I can't make a real test now, but because Director starts up very happy with the DB, I'm pretty sure that it would also run the scheduled backups happily.
Because I cannot use bconsole, then I cannot create volumes, and cannot verify this.

Someone can explain me what happens when I use "list volumes" on bconsole? there must be some difference in the way the DB is accessed at startup and when I use bconsole....

Gabriele.

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: Magnus Hagander <[EMAIL PROTECTED]>
A: Bill Moran <[EMAIL PROTECTED]> Gabriele Bulfon <[EMAIL PROTECTED]>
Cc: bacula-users@lists.sourceforge.net
Data: 21 settembre 2006 10.22.22 CEST
Oggetto: RE: [Bacula-users] Bacula and Postgres 8.1

> > 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.

//Magnus




-------------------------------------------------------------------------
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

Reply via email to