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
