Re: [Bacula-users] Bacula and Postgres 8.1
What was the operating system running the Director?How were the postgres client libraries compiled?My latest postgres libraries was built with this configuration on Solaris 10 sparc:./configure --prefix=/iserver --without-readline --enable-thread-safety 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: Dan Langille [EMAIL PROTECTED]A: Gabriele Bulfon [EMAIL PROTECTED] Cc: bacula-users@lists.sourceforge.net Data: 21 settembre 2006 16.26.54 CESTOggetto: Re: [Bacula-users] Bacula and Postgres 8.1On 21 Sep 2006 at 16:13, Gabriele Bulfon wrote: ..I did the test. Specifying "localhost" and "5432" on "DB Address" and "DB Port" works fine. Gabriele: There is something, somewhere, odd/wrong about your configuration. I do not know if it is Bacula or PostgreSQL or something else. Within the past few weeks, I tried running with a remote PostgreSQL database (remote as in on another server in the same LAN). There were no issues. I think we need more information (as mentioned by Bill). Let's start over. Please post your bsoncole.conf, bacula-dir.conf, and bacula- sd.conf files. -- Dan Langille : Software Developer looking for work my resume: http://www.freebsddiary.org/dan_langille.php - 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.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and Postgres 8.1
While googling I've found this:http://groups.google.it/group/linux.debian.bugs.dist/browse_thread/thread/34e9ffb7d8d2a1ea/1ae2be653af8e4d8%231ae2be653af8e4d8Maybe my problem is connected to this bug?I don't have a bacula unix user though, and I don't need it.How can I be sure bacula is using the correct credentials I specified in the conf file? 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: [EMAIL PROTECTED] Cc: bacula-users@lists.sourceforge.net Data: 25 settembre 2006 14.20.45 CESTOggetto: Re: [Bacula-users] Bacula and Postgres 8.1 What was the operating system running the Director?How were the postgres client libraries compiled?My latest postgres libraries was built with this configuration on Solaris 10 sparc:./configure --prefix=/iserver --without-readline --enable-thread-safety 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: Dan Langille [EMAIL PROTECTED]A: Gabriele Bulfon [EMAIL PROTECTED] Cc: bacula-users@lists.sourceforge.net Data: 21 settembre 2006 16.26.54 CESTOggetto: Re: [Bacula-users] Bacula and Postgres 8.1On 21 Sep 2006 at 16:13, Gabriele Bulfon wrote: ..I did the test. Specifying "localhost" and "5432" on "DB Address" and "DB Port" works fine. Gabriele: There is something, somewhere, odd/wrong about your configuration. I do not know if it is Bacula or PostgreSQL or something else. Within the past few weeks, I tried running with a remote PostgreSQL database (remote as in on another server in the same LAN). There were no issues. I think we need more information (as mentioned by Bill). Let's start over. Please post your bsoncole.conf, bacula-dir.conf, and bacula- sd.conf files. -- Dan Langille : Software Developer looking for work my resume: http://www.freebsddiary.org/dan_langille.php - 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.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and Postgres 8.1
On 25 Sep 2006 at 15:45, Gabriele Bulfon wrote: While googling I've found this: http://groups.google.it/group/linux.debian.bugs.dist/browse_thread/thread/34e9ffb7d8d2a1ea/1ae2be653af8e4d8%231ae2be653af8e4d8 Maybe my problem is connected to this bug? I don't have a bacula unix user though, and I don't need it. http://www.bacula.org/rel-manual/Bacula_Security_Issues.html mentions that it is not necessary to run Bacula as root. Best practice dictates that if something does not have to run as root, it should not run as root. Do as you wish. How can I be sure bacula is using the correct credentials I specified in the conf file? Test it. Configure PostgreSQL such that it accepts connections only from that which you specify. Or you could monitor the connections. PostgreSQL allows you to monitor connections. There are several ways to do this. You can also issue the select * from pg_stat_activity ; query in psql. You also need to set stats_command_string = on in postgresql.conf See http://www.postgresql.org/docs/8.1/static/runtime-config- statistics.html -- Dan Langille : Software Developer looking for work my resume: http://www.freebsddiary.org/dan_langille.php - 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.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and Postgres 8.1
How can I be sure bacula is using the correct credentials I specified in the conf file? Test it. Configure PostgreSQL such that it accepts connections only from that which you specify. Or you could monitor the connections. PostgreSQL allows you to monitor connections. There are several ways to do this. Or to just log every connection (set log_connections). You can also issue the select * from pg_stat_activity ; query in psql. You also need to set stats_command_string = on in postgresql.conf You don't need that to just see who is logged in. You only need that if you need to see what query is currently executing. //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.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
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.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and Postgres 8.1
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 desktopsThis 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 bconsoleGabriele. 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 CESTOggetto: 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.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
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.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
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 CESTOggetto: Re: [Bacula-users] Bacula and Postgres 8.1In 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.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and Postgres 8.1
..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 CESTOggetto: 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 CESTOggetto: Re: [Bacula-users] Bacula and Postgres 8.1In 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.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and Postgres 8.1
This foray has gotten very frustrating for me. Please excuse if the following replies seem inflammatory, but it comes from an honest desire to _really_ help. In response to Gabriele Bulfon [EMAIL PROTECTED]: 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. Please put some effort in to formatting your emails. I'm tired of fixing your line wrapping. 72 chars is the standard. Now. I'm going to assume 1 of two things: 1) You're a super expert on both Bacula and PostgreSQL. This is evident because you can look at logs and _know_ that certain parts are not important because you _know_ that those sections show normal behaviour. You're so smart that you refuse to send those sections of the logs in spite of multiple requests for them. Obviously, there's absolutely no chance that you could be mistaken, since the system is running so smoothly. 2) There's something in the logs that you find embarrassing. If #1 is the case, then just fix the problem yourself. If #2 is the case, then I have no advice. I really suspect this is something coming out only when I use bconsole. While this could be true, I find it unlikely and not indicated by the evidence you're providing. bconsole talks to the director and the director talks to the database. It appears as if bconsole is able to contact the director, and the errors seem to indicate a connection problem between the director and the database. The fact that this only occurs when you use the director is a silly benchmark, since the _only_ other thing you've managed to get the director to do is start. 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. Those are some outlandish assumptions you're making there. If the director fails on a status storage then I find it difficult to imagine that it could succeed in backing anything up. Because I cannot use bconsole, then I cannot create volumes, and cannot verify this. Yes, you can. You could create autolabeled disk volumes in the config, create a test backup job, schedule it to run frequently and you'd find out very quickly. 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 No. bconsole - director, then director - db in the same way it does anything else. You've still yet to provide any kind of network debugging. For crying out loud, do a tcpdump -s0 -w /some/file port 5432 during the failure and post the resultant file somewhere. And, quite frankly, the last several emails have amounted to you politely saying, I don't agree with your advice, and therefore, won't take it. Based on this, I'm tempted to stop giving it. If you know so much about how bacula works, why are you still stuck? If you want any _real_ help, you're going to have to post some serious information somewhere. It's amazing that the open source community is generally willing to wade through such data and provide assistance for free. But I find it even more amazing that you repeated _refuse_ to take advantage of such free debugging. -- 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.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and Postgres 8.1
On 21 Sep 2006 at 16:13, Gabriele Bulfon wrote: ..I did the test. Specifying localhost and 5432 on DB Address and DB Port works fine. Gabriele: There is something, somewhere, odd/wrong about your configuration. I do not know if it is Bacula or PostgreSQL or something else. Within the past few weeks, I tried running with a remote PostgreSQL database (remote as in on another server in the same LAN). There were no issues. I think we need more information (as mentioned by Bill). Let's start over. Please post your bsoncole.conf, bacula-dir.conf, and bacula- sd.conf files. -- Dan Langille : Software Developer looking for work my resume: http://www.freebsddiary.org/dan_langille.php - 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.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
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 connectionHope you can help.Gabriele.==I rised debug to 500.Before the I issue the "list volumes" on bconsole, I see a LOT LOT of debug about postgres selects going through very fine.Once I run the bconsole command I find this:iserver-dir: scheduler.c:253 enter find_runs()iserver-dir: scheduler.c:289 Got job: Enterprise Backupiserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:289 Got job: Backup Aliseoiserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:289 Got job: Backup ZetaFaxiserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:289 Got job: Backup Centralinoiserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:289 Got job: BackupCatalogiserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:355 Leave find_runs()iserver-dir: bsys.c:70 pthread_cond_timedwait sec=60 usec=0iserver-dir: ua_cmds.c:1615 Open databaseiserver-dir: postgresql.c:77 db_open first timeiserver-dir: bsys.c:70 pthread_cond_timedwait sec=5 usec=0iserver-dir: bsys.c:77 pthread_cond_timedwait stat=145 ERR=Connection timed out Gabriele Bulfon - Sonicle S.r.l.Tel +39 028246016 Int. 30 - Fax +39 028243880Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALYhttp://www.sonicle.com --Da: Bill Moran [EMAIL PROTECTED]A: Gabriele Bulfon [EMAIL PROTECTED] Cc: bacula-users@lists.sourceforge.net Data: 19 settembre 2006 14.53.29 CESTOggetto: Re: [Bacula-users] Bacula and Postgres 8.1 In response to Gabriele Bulfon [EMAIL PROTECTED]: Hello, I open again the question about Bacula working on Postgres. This time, I really need to have Director and Postgres run on two different machines. The reason: I only have one Solaris machine and one Windows machine, so I cannot move the Director to the Windows machine together with Postgres (as far as I know, the Director is still not supported on Windows). What happens is that once I add the needed entries to the bacula-dir.conf to connect to the new machine (DB Address and DB Port), Director starts (and with log enabled to 500, I can see a lot of queries correctly handled), but when I run bconsole on the Director, the Director initially responds with the prompt, then any command that needs DB access (such as "list volumes") hangs for some seconds and then fails saying that it cannot connect to the DB. If I look at the log, I can see some timeout failures. How can I investigate more this? Why the first queries go through correctly, and then they fail with bconsole? Please help...I really need to move the DB on the other machine Help: 1) Provide the logs you captured, not your interpretation of them. Nobody is going to be able to diagnose "I can see some timeout failures" 2) Bump up connection logging on the PostgreSQL server. You'll want to provide those logs as well. 3) Put some effort into formatting your emails so they're readable. -- Bill Moran Collaborative Fusion Inc. - Take Surveys. E
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 connectionHope you can help.Gabriele.==I rised debug to 500.Before the I issue the "list volumes" on bconsole, I see a LOT LOT of debug about postgres selects going through very fine.Once I run the bconsole command I find this:iserver-dir: scheduler.c:253 enter find_runs()iserver-dir: scheduler.c:289 Got job: Enterprise Backupiserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:289 Got job: Backup Aliseoiserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:289 Got job: Backup ZetaFaxiserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:289 Got job: Backup Centralinoiserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:289 Got job: BackupCatalogiserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0iserver-dir: scheduler.c:355 Leave find_runs()iserver-dir: bsys.c:70 pthread_cond_timedwait sec=60 usec=0iserver-dir: ua_cmds.c:1615 Open databaseiserver-dir: postgresql.c:77 db_open first timeiserver-dir: bsys.c:70 pthread_cond_timedwait sec=5 usec=0iserver-dir: bsys.c:77 pthread_cond_timedwait stat=145 ERR=Connection timed out Gabriele Bulfon - Sonicle S.r.l.Tel +39 028246016 Int. 30 - Fax +39 028243880Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALYhttp://www.sonicle.com --Da: Bill Moran [EMAIL PROTECTED]A: Gabriele Bulfon [EMAIL PROTECTED] Cc: bacula-users@lists.sourceforge.net Data: 19 settembre 2006 14.53.29 CESTOggetto: Re: [Bacula-users] Bacula and Postgres 8.1 In response to Gabriele Bulfon [EMAIL PROTECTED]: Hello, I open again the question about Bacula working on Postgres. This time, I really need to have Director and Postgres run on two different machines. The reason: I only have one Solaris machine and one Windows machine, so I cannot move the Director to the Windows machine together with Postgres (as far as I know, the Director is still not supported on Windows). What happens is that once I add the needed entries to the bacula-dir.conf to connect to the new machine (DB Address and DB Port), Director starts (and with log enabled to 500, I can see a lot of queries correctly handled), but when I run bconsole on the Director, the Director initially responds with the prompt, then any command that needs DB access (such as "list volumes") hangs for some seconds and then fails saying that it cannot connect to the DB. If I look at the log, I can see some timeout failures. How can I investigate more this? Why the first queries go through correctly, and then they fail with bconsole? Please help...I really need to move the DB on the other machine Help: 1) Provide the logs you captured, not your interpretation of them. Nobody is going to be able to diagnose "I can see some timeout failures" 2) Bump up connection logging on the PostgreSQL server. You'll want to provide those logs as well. 3) Put some effort into formatting your emails so they're readable. -- Bill Moran Collaborative Fusion Inc. - Take Surveys. E
Re: [Bacula-users] Bacula and Postgres 8.1
In response to Gabriele Bulfon [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. Any network control devices between these two systems? (firewalls, routers, managed switches?) Ensure all your speed and duplexing match up. Grab some tcpdumps off the network while this is happening, and see if anything looks fishy. Do it on both ends of the connection and see if packets are getting lost. Can you use psql on the system running the director to connect manually to the PostgreSQL database? Can you run a long running query without getting disconnected (SELECT COUNT(*) FROM some big table will generally take a while) Hope you can help. Gabriele. == I rised debug to 500. Before the I issue the list volumes on bconsole, I see a LOT LOT of debug about postgres selects going through very fine. That's funny, because I don't see any in your attached logs. Once I run the bconsole command I find this: iserver-dir: scheduler.c:253 enter find_runs() iserver-dir: scheduler.c:289 Got job: Enterprise Backup iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:289 Got job: Backup Aliseo iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:289 Got job: Backup ZetaFax iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:289 Got job: Backup Centralino iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:289 Got job: BackupCatalog iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:332 [EMAIL PROTECTED]: run_now=0 run_nh=0 iserver-dir: scheduler.c:355 Leave find_runs() iserver-dir: bsys.c:70 pthread_cond_timedwait sec=60 usec=0 iserver-dir: ua_cmds.c:1615 Open database iserver-dir: postgresql.c:77 db_open first time iserver-dir: bsys.c:70 pthread_cond_timedwait sec=5 usec=0 iserver-dir: bsys.c:77 pthread_cond_timedwait stat=145 ERR=Connection timed out 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 -- 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.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula and Postgres 8.1
Hello,I open again the question about Bacula working on Postgres.This time, I really need to have Director and Postgres run on two different machines.The reason: I only have one Solaris machine and one Windows machine, so I cannot move the Director to the Windows machine together with Postgres (as far as I know, the Director is still not supported on Windows).What happens is that once I add the needed entries to the bacula-dir.conf to connect to the new machine (DB Address and DB Port), Director starts (and with log enabled to 500, I can see a lot of queries correctly handled), but when I run bconsole on the Director, the Director initially responds with the prompt, then any command that needs DB access (such as "list volumes") hangs for some seconds and then fails saying that it cannot connect to the DB.If I look at the log, I can see some timeout failures.How can I investigate more this? Why the first queries go through correctly, and then they fail with bconsole?Please help...I really need to move the DB on the other machineGabriele. 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 - 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.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and Postgres 8.1
In response to Gabriele Bulfon [EMAIL PROTECTED]: Hello, I open again the question about Bacula working on Postgres. This time, I really need to have Director and Postgres run on two different machines. The reason: I only have one Solaris machine and one Windows machine, so I cannot move the Director to the Windows machine together with Postgres (as far as I know, the Director is still not supported on Windows). What happens is that once I add the needed entries to the bacula-dir.conf to connect to the new machine (DB Address and DB Port), Director starts (and with log enabled to 500, I can see a lot of queries correctly handled), but when I run bconsole on the Director, the Director initially responds with the prompt, then any command that needs DB access (such as list volumes) hangs for some seconds and then fails saying that it cannot connect to the DB. If I look at the log, I can see some timeout failures. How can I investigate more this? Why the first queries go through correctly, and then they fail with bconsole? Please help...I really need to move the DB on the other machine Help: 1) Provide the logs you captured, not your interpretation of them. Nobody is going to be able to diagnose I can see some timeout failures 2) Bump up connection logging on the PostgreSQL server. You'll want to provide those logs as well. 3) Put some effort into formatting your emails so they're readable. -- 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.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
