Trying psql was the first check I did when I saw the problem.
As you suggested, I tried with snoop, and verified that the 280 was actually connecting to the correct machine.
So, I looked into the postgres.log of the remote db machine...and found this.... :
LOG: incomplete startup packet
So I monitored the log during bacula Director startup: everything was ok.
Then I monitored during bconsole "list volumes", and the LOG came up....
....?!?!?!
Postgres is absolutely the same version. Solaris 10 is the same release.
The only difference is that the 280 is a SPARC processor, and the DB machine is an Intel one.
If I use "psql" from the 280 and connect to the DB on Intel, I can issue any "select" on the bacula db.
I even created the DB using the scripts on the 280, adding "-h intel-machine".
...pls...help....I am confused....
Sorry, I'm no expert in postgres but what I would do is:
- check google results for that postgres error
- sniff deeper the net and have a look at packet contents, first logging a successful connection (e.g. that one from psql) to see what it's expected to be there, and then logging the problematic connection from bacula, and comparing the two results.
- raise debug level in postgres (is it possible?)
--
Maxx
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
