Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
I have been updating with each of the new 1.38.3's when they come out, but I am still having an issue with "waiting to reserve a device". The first 1.38.3 update allowed it to perform backups, but it now waits exactly 30 minutes before starting. When the job is scheduled to start, it immediately issues a "waiting to reserve a device" email... 30 minutes later it starts backing up. It seems like if I restart bacula, the first scheduled job actually runs normally (ie right when scheduled), but then all subsequent jobs have a 30 minute delay. Any ideas? I will make a log with full debugging and see if that yields any clues. james Kern Sibbald wrote: On Friday 16 December 2005 10:02, Volker Dierks wrote: Hello Kern, do you think that this problem also affects me? My plan was to test the beta (released 10. Dec) and two drives today with a new tape set. Quite posibbly -- try the 14 Dec 05 version instead ... To give you a little reminder: A HP 2/20 Library with 10 tapes on the left side in pool DRIVE-1 and 10 tapes on the right side in pool DRIVE-2. I'm allways loading the first tape from any pool and mount it. So there's no mtx stuff at the beginning of the backup, but definitely later when tapes got full. Are you going to release the fixed version in the next few hours? I am going to release the second BETA 1.38.3 now. It has a number of fixes. I've had so many things going on that I don't remember the context of your problems, but I would *strongly* suggest that anyone having reservation or job hanging problems with 1.38.2 or the first 1.38.3 BETA should try the second version (14 December 2005). Thanks, Volker Kern Sibbald wrote: Hello Rick, Thanks for the debug output. I think I have now found the problem in the algorithm at least the problem that is hitting you. This time, I'm 100% that I have found at least one major problem. I'm going to run code through all my tests here on two machines, then on Solaris and FreeBSD. Once I've done that I'll make the new code available -- probably this evening. On Thursday 15 December 2005 06:31, Rick Knight wrote: Kern Sibbald wrote: On Wednesday 14 December 2005 04:22, Rick Knight wrote: Kern Sibbald wrote: Hello, If you are able to reproduce this easily, could you turn on level 100 by putting -d100 on the command line when you start it, then capture the output. This may help me understand what is going on. I've tried everything I can to duplicate this, but all my tests run fine. Hmmm. Normally, it wouldn't be the OS that is causing problems, but I'm open to almost any suggestion -- the goal being to fix it ... On Tuesday 13 December 2005 22:07, James Peverill wrote: I suspect that there are two problems here. 1. You probably don't have Maximume Concurrent Jobs set in your director's storage resource, and 2. it looks like there may be a problem with the way the SD in 1.38 is trying to open drives, which cause it to wait. I'm working on a solution to that now. Thanks, Rick Knight Kern, Adding the Max Concurrent Jobs = 4 didn't mak any difference. I added OPTIONS='-d100' to the bacula startup script, started bacula and ran thru all the jobs, capturing all of the output. Log file attached. The only thing that looks obvious to me are the python errors or messages. I may rebuild bacula without python support this weekend and see if it helps. I did not have this problem with 1.38.1. Thanks again, Rick Knight
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
On Friday 16 December 2005 10:02, Volker Dierks wrote:
> Hello Kern,
>
> do you think that this problem also affects me? My plan was to test
> the beta (released 10. Dec) and two drives today with a new tape set.
Quite posibbly -- try the 14 Dec 05 version instead ...
>
> To give you a little reminder:
> A HP 2/20 Library with 10 tapes on the left side in pool DRIVE-1 and
> 10 tapes on the right side in pool DRIVE-2. I'm allways loading the
> first tape from any pool and mount it. So there's no mtx stuff at the
> beginning of the backup, but definitely later when tapes got full.
>
> Are you going to release the fixed version in the next few hours?
I am going to release the second BETA 1.38.3 now. It has a number of fixes.
I've had so many things going on that I don't remember the context of your
problems, but I would *strongly* suggest that anyone having reservation or
job hanging problems with 1.38.2 or the first 1.38.3 BETA should try the
second version (14 December 2005).
>
> Thanks,
> Volker
>
> Kern Sibbald wrote:
> > Hello Rick,
> >
> > Thanks for the debug output. I think I have now found the problem in the
> > algorithm at least the problem that is hitting you. This time, I'm 100%
> > that I have found at least one major problem.
> >
> > I'm going to run code through all my tests here on two machines, then on
> > Solaris and FreeBSD. Once I've done that I'll make the new code
> > available -- probably this evening.
> >
> > On Thursday 15 December 2005 06:31, Rick Knight wrote:
> >>Kern Sibbald wrote:
> >>>On Wednesday 14 December 2005 04:22, Rick Knight wrote:
> Kern Sibbald wrote:
> >Hello,
> >
> >If you are able to reproduce this easily, could you turn on level 100
> > by putting -d100 on the command line when you start it, then capture
> > the output. This may help me understand what is going on.
> >
> >I've tried everything I can to duplicate this, but all my tests run
> >fine.
> >
> >Hmmm. Normally, it wouldn't be the OS that is causing problems, but
> > I'm open to almost any suggestion -- the goal being to fix it ...
> >
> >On Tuesday 13 December 2005 22:07, James Peverill wrote:
> >>>
> >>>I suspect that there are two problems here. 1. You probably don't have
> >>>Maximume Concurrent Jobs set in your director's storage resource, and 2.
> >>>it looks like there may be a problem with the way the SD in 1.38 is
> >>>trying to open drives, which cause it to wait. I'm working on a
> >>> solution to that now.
> >>>
> Thanks,
> Rick Knight
> >>
> >>Kern,
> >>
> >>Adding the Max Concurrent Jobs = 4 didn't mak any difference. I added
> >>OPTIONS='-d100' to the bacula startup script, started bacula and ran
> >>thru all the jobs, capturing all of the output. Log file attached. The
> >>only thing that looks obvious to me are the python errors or messages. I
> >>may rebuild bacula without python support this weekend and see if it
> >>helps. I did not have this problem with 1.38.1.
> >>
> >>Thanks again,
> >>Rick Knight
--
Best regards,
Kern
(">
/\
V_V
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
Hello Kern, do you think that this problem also affects me? My plan was to test the beta (released 10. Dec) and two drives today with a new tape set. To give you a little reminder: A HP 2/20 Library with 10 tapes on the left side in pool DRIVE-1 and 10 tapes on the right side in pool DRIVE-2. I'm allways loading the first tape from any pool and mount it. So there's no mtx stuff at the beginning of the backup, but definitely later when tapes got full. Are you going to release the fixed version in the next few hours? Thanks, Volker Kern Sibbald wrote: Hello Rick, Thanks for the debug output. I think I have now found the problem in the algorithm at least the problem that is hitting you. This time, I'm 100% that I have found at least one major problem. I'm going to run code through all my tests here on two machines, then on Solaris and FreeBSD. Once I've done that I'll make the new code available -- probably this evening. On Thursday 15 December 2005 06:31, Rick Knight wrote: Kern Sibbald wrote: On Wednesday 14 December 2005 04:22, Rick Knight wrote: Kern Sibbald wrote: Hello, If you are able to reproduce this easily, could you turn on level 100 by putting -d100 on the command line when you start it, then capture the output. This may help me understand what is going on. I've tried everything I can to duplicate this, but all my tests run fine. Hmmm. Normally, it wouldn't be the OS that is causing problems, but I'm open to almost any suggestion -- the goal being to fix it ... On Tuesday 13 December 2005 22:07, James Peverill wrote: I suspect that there are two problems here. 1. You probably don't have Maximume Concurrent Jobs set in your director's storage resource, and 2. it looks like there may be a problem with the way the SD in 1.38 is trying to open drives, which cause it to wait. I'm working on a solution to that now. Thanks, Rick Knight Kern, Adding the Max Concurrent Jobs = 4 didn't mak any difference. I added OPTIONS='-d100' to the bacula startup script, started bacula and ran thru all the jobs, capturing all of the output. Log file attached. The only thing that looks obvious to me are the python errors or messages. I may rebuild bacula without python support this weekend and see if it helps. I did not have this problem with 1.38.1. Thanks again, Rick Knight --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
Hello Rick,
Thanks for the debug output. I think I have now found the problem in the
algorithm at least the problem that is hitting you. This time, I'm 100% that
I have found at least one major problem.
I'm going to run code through all my tests here on two machines, then on
Solaris and FreeBSD. Once I've done that I'll make the new code available --
probably this evening.
On Thursday 15 December 2005 06:31, Rick Knight wrote:
> Kern Sibbald wrote:
> >On Wednesday 14 December 2005 04:22, Rick Knight wrote:
> >>Kern Sibbald wrote:
> >>>Hello,
> >>>
> >>>If you are able to reproduce this easily, could you turn on level 100 by
> >>>putting -d100 on the command line when you start it, then capture the
> >>>output. This may help me understand what is going on.
> >>>
> >>>I've tried everything I can to duplicate this, but all my tests run
> >>> fine.
> >>>
> >>>Hmmm. Normally, it wouldn't be the OS that is causing problems, but I'm
> >>>open to almost any suggestion -- the goal being to fix it ...
> >>>
> >>>On Tuesday 13 December 2005 22:07, James Peverill wrote:
> >
> >I suspect that there are two problems here. 1. You probably don't have
> >Maximume Concurrent Jobs set in your director's storage resource, and 2.
> > it looks like there may be a problem with the way the SD in 1.38 is
> > trying to open drives, which cause it to wait. I'm working on a solution
> > to that now.
> >
> >>Thanks,
> >>Rick Knight
>
> Kern,
>
> Adding the Max Concurrent Jobs = 4 didn't mak any difference. I added
> OPTIONS='-d100' to the bacula startup script, started bacula and ran
> thru all the jobs, capturing all of the output. Log file attached. The
> only thing that looks obvious to me are the python errors or messages. I
> may rebuild bacula without python support this weekend and see if it
> helps. I did not have this problem with 1.38.1.
>
> Thanks again,
> Rick Knight
--
Best regards,
Kern
(">
/\
V_V
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
On Wednesday 14 December 2005 04:22, Rick Knight wrote: > Kern Sibbald wrote: > >Hello, > > > >If you are able to reproduce this easily, could you turn on level 100 by > >putting -d100 on the command line when you start it, then capture the > > output. This may help me understand what is going on. > > > >I've tried everything I can to duplicate this, but all my tests run fine. > > > >Hmmm. Normally, it wouldn't be the OS that is causing problems, but I'm > > open to almost any suggestion -- the goal being to fix it ... > > > >On Tuesday 13 December 2005 22:07, James Peverill wrote: > >>I am also getting this error since upgrading to 1.38 from the 1.36 > >>branch... been trying to figure out why for a few days now. > >> > >>I am also running slackware 10... I wonder if this is related. Not > >>running 2.4 kernel though, running 2.6.11.12 right now. I am backing up > >>to disk, not tapes. Manually scheduled jobs run just fine, and > >>automatic jobs run sometimes (the first job)... but most of the time > >>they block indefinitely with "waiting to reserve a device". > >> > >>I figured I had just screwed up a configuration file somehow, but I have > >>tweaked my configuration files with no improvement. Maybe this is tied > >>to a package in slackware 10? Any other users running slackware 10 with > >>1.38 successfully? > >> > >>james peverill > >> > >>Richard W. Knight wrote: > >>>Kern Sibbald wrote: > On Tuesday 13 December 2005 13:43, Rick Knight wrote: > >Kern Sibbald wrote: > >>Hello, > >> > >>On Monday 12 December 2005 19:35, Richard W. Knight wrote: > >>>Hi all, > >>> > >>>A couple of weeks ago I upgraded my Bacula installation from 1.34 to > >>>1.38.1. I made a few other changes at the same time and everything > >>>has > >>>been working well since. Yesterday I decided to upgrade to 1.38.3. I > >>>built from source using the same configuration options that I used > >>> to build 1.38.1 with the addition of "--with-python". The build > >>> went OK, > >>>no errors. I stopped 1.38.1 and started 1.38.3. Everything seemed > >>>to be > >>>OK. I ran a couple of small test backups and there were no errors > >>>so I > >>>assumed that the upgrade went fine. Last night the scheduled > >>>backup ran > >>>and after the first job, instead of continuing on to the next job, > >>>I got > >>>this message ... > >>> > >>>12-Dec 07:29 MyJob-SMB-sd: Job MyJob.2005-12-12_01.05.01 waiting to > >>>reserve a device. > >>> > >>>This morning, when I first saw this message, I just did a mount from > >>>bconsole and the job continued, I have bacula configured for 6 > >>>jobs per > >>>media and the tape wasn't full so the job should have just started > >>>as it > >>>hallways has. Now it's time to backup up the catalog, to file, and > >>>I'm > >>>getting the same message. > >>> > >>>I have an HP DDS2 drive, no changer, running on Slackware 10. I'm > >>>using > >>>the same conf files the worked fine on 1.38.1. Can anyone tell me > >>> why I'm now getting this error message? > >> > >>You are not by any chance running on a 2.4 kernel with /lib/tls? > >> > >>Could you send me your bacula-dir.conf and bacula-sd.conf along > >>with the > >>job report that shows the jobs blocking? > >> > >>>Thanks, > >>>RickKnight > >>> > >>> > >>>--- > >>>This SF.net email is sponsored by: Splunk Inc. Do you grep through > >>>log > >>>files for problems? Stop! Download the new AJAX search engine that > >>>makes searching your log files as easy as surfing the web. > >>> DOWNLOAD SPLUNK! > >>> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > >>> ___ > >>>Bacula-users mailing list > >>>Bacula-users@lists.sourceforge.net > >>>https://lists.sourceforge.net/lists/listinfo/bacula-users > > > >Thanks Kern, > > > >I am running a 2.4.26 kernel, but I don't know about /lib/tls. I don't > >have a /lib/tls on my system. How can I tell? > > Try: > > ls -l /lib/tls > > If it exists, then that could explain why it *appears* that Bacula is > not seeing some pthread broadcasts that would allow it to continue. > This is a bit of a long shot, but at this point, I need to consider > all possibilities ... > > In the mean time, I'll take a careful look at your config. Perhaps I > have missed something important that I can add to my test cases. All > my tests here succeeded perfectly ... > > By the way, getting the message that a job is waiting to reserve a > drive is not in itself bad. This happens in my test case. However, at > some point when the drive is available, the job should continue as it > does in my test case. > >
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
Hello, Please copy the list ... On Wednesday 14 December 2005 04:12, Rick Knight wrote: > Kern Sibbald wrote: > >Hello, > > > >If you are able to reproduce this easily, could you turn on level 100 by > >putting -d100 on the command line when you start it, then capture the > > output. This may help me understand what is going on. > > > >I've tried everything I can to duplicate this, but all my tests run fine. > > > >Hmmm. Normally, it wouldn't be the OS that is causing problems, but I'm > > open to almost any suggestion -- the goal being to fix it ... > > > >On Tuesday 13 December 2005 22:07, James Peverill wrote: > >>I am also getting this error since upgrading to 1.38 from the 1.36 > >>branch... been trying to figure out why for a few days now. > >> > >>I am also running slackware 10... I wonder if this is related. Not > >>running 2.4 kernel though, running 2.6.11.12 right now. I am backing up > >>to disk, not tapes. Manually scheduled jobs run just fine, and > >>automatic jobs run sometimes (the first job)... but most of the time > >>they block indefinitely with "waiting to reserve a device". > >> > >>I figured I had just screwed up a configuration file somehow, but I have > >>tweaked my configuration files with no improvement. Maybe this is tied > >>to a package in slackware 10? Any other users running slackware 10 with > >>1.38 successfully? > >> > >>james peverill > >> > >>Richard W. Knight wrote: > >>>Kern Sibbald wrote: > On Tuesday 13 December 2005 13:43, Rick Knight wrote: > >Kern Sibbald wrote: > >>Hello, > >> > >>On Monday 12 December 2005 19:35, Richard W. Knight wrote: > >>>Hi all, > >>> > >>>A couple of weeks ago I upgraded my Bacula installation from 1.34 to > >>>1.38.1. I made a few other changes at the same time and everything > >>>has > >>>been working well since. Yesterday I decided to upgrade to 1.38.3. I > >>>built from source using the same configuration options that I used > >>> to build 1.38.1 with the addition of "--with-python". The build > >>> went OK, > >>>no errors. I stopped 1.38.1 and started 1.38.3. Everything seemed > >>>to be > >>>OK. I ran a couple of small test backups and there were no errors > >>>so I > >>>assumed that the upgrade went fine. Last night the scheduled > >>>backup ran > >>>and after the first job, instead of continuing on to the next job, > >>>I got > >>>this message ... > >>> > >>>12-Dec 07:29 MyJob-SMB-sd: Job MyJob.2005-12-12_01.05.01 waiting to > >>>reserve a device. > >>> > >>>This morning, when I first saw this message, I just did a mount from > >>>bconsole and the job continued, I have bacula configured for 6 > >>>jobs per > >>>media and the tape wasn't full so the job should have just started > >>>as it > >>>hallways has. Now it's time to backup up the catalog, to file, and > >>>I'm > >>>getting the same message. > >>> > >>>I have an HP DDS2 drive, no changer, running on Slackware 10. I'm > >>>using > >>>the same conf files the worked fine on 1.38.1. Can anyone tell me > >>> why I'm now getting this error message? > >> > >>You are not by any chance running on a 2.4 kernel with /lib/tls? > >> > >>Could you send me your bacula-dir.conf and bacula-sd.conf along > >>with the > >>job report that shows the jobs blocking? > >> > >>>Thanks, > >>>RickKnight > >>> > >>> > >>>--- > >>>This SF.net email is sponsored by: Splunk Inc. Do you grep through > >>>log > >>>files for problems? Stop! Download the new AJAX search engine that > >>>makes searching your log files as easy as surfing the web. > >>> DOWNLOAD SPLUNK! > >>> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > >>> ___ > >>>Bacula-users mailing list > >>>Bacula-users@lists.sourceforge.net > >>>https://lists.sourceforge.net/lists/listinfo/bacula-users > > > >Thanks Kern, > > > >I am running a 2.4.26 kernel, but I don't know about /lib/tls. I don't > >have a /lib/tls on my system. How can I tell? > > Try: > > ls -l /lib/tls > > If it exists, then that could explain why it *appears* that Bacula is > not seeing some pthread broadcasts that would allow it to continue. > This is a bit of a long shot, but at this point, I need to consider > all possibilities ... > > In the mean time, I'll take a careful look at your config. Perhaps I > have missed something important that I can add to my test cases. All > my tests here succeeded perfectly ... > > By the way, getting the message that a job is waiting to reserve a > drive is not in itself bad. This happens in my test case. However, at > some point when the drive is available, the job should continue as it >
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
Kern Sibbald wrote: Hello, If you are able to reproduce this easily, could you turn on level 100 by putting -d100 on the command line when you start it, then capture the output. This may help me understand what is going on. I've tried everything I can to duplicate this, but all my tests run fine. Hmmm. Normally, it wouldn't be the OS that is causing problems, but I'm open to almost any suggestion -- the goal being to fix it ... On Tuesday 13 December 2005 22:07, James Peverill wrote: Kern, I modified the bacula startup script to start with -d100. Attached is the output. Also, I noticed that when the first job ends, Knight-Linux-SMB, bconsole/status/dir shows the drive as not mounted. When I mount the drive, bacula claims the drive is already mounted, but then the job continues. My runafter script has not run at this point, but when it does, it also ejects the tape so I don't think that it's causing this problem. Also, looking at the attached file, I can see a couple of python errors "pythonlib.c:94 No script dir". Could this be the problem? Thank again, RickKnight [EMAIL PROTECTED]:/etc/bacula# ./bacula start Starting the Bacula Storage daemon bacula-sd: stored_conf.c:613 Inserting device res: DAT-8 Starting the Bacula File daemon knight-linux-SMB-sd: jcr.c:113 read_last_jobs seek to 188 knight-linux-SMB-sd: jcr.c:120 Read num_items=10 knight-linux-SMB-sd: pythonlib.c:94 No script dir. prog=SDStartUp knight-linux-SMB-sd: stored.c:451 calling init_dev /tmp/bacula_cat knight-linux-SMB-sd: dev.c:242 init_dev: tape=0 dev_name=/tmp/bacula_cat knight-linux-SMB-sd: stored.c:453 SD init done /tmp/bacula_cat knight-linux-SMB-sd: stored.c:451 calling init_dev /dev/nst0 knight-linux-SMB-sd: dev.c:242 init_dev: tape=2 dev_name=/dev/nst0 knight-linux-SMB-sd: stored.c:453 SD init done /dev/nst0 knight-linux-SMB-sd: bnet_server.c:83 Addresses host[ipv4:0.0.0.0:9103] knight-linux-SMB-fd: jcr.c:113 read_last_jobs seek to 188 knight-linux-SMB-fd: jcr.c:120 Read num_items=10 knight-linux-SMB-fd: pythonlib.c:94 No script dir. prog=FDStartUp knight-linux-SMB-fd: filed.c:238 filed: listening on port 9102 knight-linux-SMB-fd: bnet_server.c:83 Addresses host[ipv4:0.0.0.0:9102] Starting the Bacula Director daemon bacula-dir: dird.c:128 Debug level = 100 bacula-dir: mysql.c:81 db_open first time bacula-dir: mysql.c:142 mysql_init done bacula-dir: mysql.c:162 mysql_real_connect done bacula-dir: mysql.c:164 db_user=bacula db_name=bacula db_password=passwd_deleted knight-linux-SMB-dir: jcr.c:113 read_last_jobs seek to 188
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
Kern Sibbald wrote: Hello, If you are able to reproduce this easily, could you turn on level 100 by putting -d100 on the command line when you start it, then capture the output. This may help me understand what is going on. I've tried everything I can to duplicate this, but all my tests run fine. Hmmm. Normally, it wouldn't be the OS that is causing problems, but I'm open to almost any suggestion -- the goal being to fix it ... On Tuesday 13 December 2005 22:07, James Peverill wrote: I am also getting this error since upgrading to 1.38 from the 1.36 branch... been trying to figure out why for a few days now. I am also running slackware 10... I wonder if this is related. Not running 2.4 kernel though, running 2.6.11.12 right now. I am backing up to disk, not tapes. Manually scheduled jobs run just fine, and automatic jobs run sometimes (the first job)... but most of the time they block indefinitely with "waiting to reserve a device". I figured I had just screwed up a configuration file somehow, but I have tweaked my configuration files with no improvement. Maybe this is tied to a package in slackware 10? Any other users running slackware 10 with 1.38 successfully? james peverill Richard W. Knight wrote: Kern Sibbald wrote: On Tuesday 13 December 2005 13:43, Rick Knight wrote: Kern Sibbald wrote: Hello, On Monday 12 December 2005 19:35, Richard W. Knight wrote: Hi all, A couple of weeks ago I upgraded my Bacula installation from 1.34 to 1.38.1. I made a few other changes at the same time and everything has been working well since. Yesterday I decided to upgrade to 1.38.3. I built from source using the same configuration options that I used to build 1.38.1 with the addition of "--with-python". The build went OK, no errors. I stopped 1.38.1 and started 1.38.3. Everything seemed to be OK. I ran a couple of small test backups and there were no errors so I assumed that the upgrade went fine. Last night the scheduled backup ran and after the first job, instead of continuing on to the next job, I got this message ... 12-Dec 07:29 MyJob-SMB-sd: Job MyJob.2005-12-12_01.05.01 waiting to reserve a device. This morning, when I first saw this message, I just did a mount from bconsole and the job continued, I have bacula configured for 6 jobs per media and the tape wasn't full so the job should have just started as it hallways has. Now it's time to backup up the catalog, to file, and I'm getting the same message. I have an HP DDS2 drive, no changer, running on Slackware 10. I'm using the same conf files the worked fine on 1.38.1. Can anyone tell me why I'm now getting this error message? You are not by any chance running on a 2.4 kernel with /lib/tls? Could you send me your bacula-dir.conf and bacula-sd.conf along with the job report that shows the jobs blocking? Thanks, RickKnight --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users Thanks Kern, I am running a 2.4.26 kernel, but I don't know about /lib/tls. I don't have a /lib/tls on my system. How can I tell? Try: ls -l /lib/tls If it exists, then that could explain why it *appears* that Bacula is not seeing some pthread broadcasts that would allow it to continue. This is a bit of a long shot, but at this point, I need to consider all possibilities ... In the mean time, I'll take a careful look at your config. Perhaps I have missed something important that I can add to my test cases. All my tests here succeeded perfectly ... By the way, getting the message that a job is waiting to reserve a drive is not in itself bad. This happens in my test case. However, at some point when the drive is available, the job should continue as it does in my test case. Also, the .conf files are attached along with the log. Thanks again, RickKnight Kern, I just got another job log email. Something I noticed is a clock difference between the Director and File daemons. The two lines below are from this mornings log (also attached). Could that be causing a problem? 12-Dec 19:29 knight-linux-SMB-sd: Job Knight-Linux.2005-12-12_01.05.01 waiting to reserve a device. 13-Dec 04:33 knight-linux-fd: DIR and FD clocks differ by 676 seconds, FD automatically adjusting. Thanks again, Rick Knight 12-Dec 04:29 knight-linux-SMB-dir: Start Backup JobId 559, Job=Knight-Linux.2005-12-12_01.05.01 12-Dec 04:29 knight-linux-SMB-s
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
Hello, If you are able to reproduce this easily, could you turn on level 100 by putting -d100 on the command line when you start it, then capture the output. This may help me understand what is going on. I've tried everything I can to duplicate this, but all my tests run fine. Hmmm. Normally, it wouldn't be the OS that is causing problems, but I'm open to almost any suggestion -- the goal being to fix it ... On Tuesday 13 December 2005 22:07, James Peverill wrote: > I am also getting this error since upgrading to 1.38 from the 1.36 > branch... been trying to figure out why for a few days now. > > I am also running slackware 10... I wonder if this is related. Not > running 2.4 kernel though, running 2.6.11.12 right now. I am backing up > to disk, not tapes. Manually scheduled jobs run just fine, and > automatic jobs run sometimes (the first job)... but most of the time > they block indefinitely with "waiting to reserve a device". > > I figured I had just screwed up a configuration file somehow, but I have > tweaked my configuration files with no improvement. Maybe this is tied > to a package in slackware 10? Any other users running slackware 10 with > 1.38 successfully? > > james peverill > > Richard W. Knight wrote: > > Kern Sibbald wrote: > >> On Tuesday 13 December 2005 13:43, Rick Knight wrote: > >>> Kern Sibbald wrote: > Hello, > > On Monday 12 December 2005 19:35, Richard W. Knight wrote: > > Hi all, > > > > A couple of weeks ago I upgraded my Bacula installation from 1.34 to > > 1.38.1. I made a few other changes at the same time and everything > > has > > been working well since. Yesterday I decided to upgrade to 1.38.3. I > > built from source using the same configuration options that I used to > > build 1.38.1 with the addition of "--with-python". The build went > > OK, > > no errors. I stopped 1.38.1 and started 1.38.3. Everything seemed > > to be > > OK. I ran a couple of small test backups and there were no errors > > so I > > assumed that the upgrade went fine. Last night the scheduled > > backup ran > > and after the first job, instead of continuing on to the next job, > > I got > > this message ... > > > > 12-Dec 07:29 MyJob-SMB-sd: Job MyJob.2005-12-12_01.05.01 waiting to > > reserve a device. > > > > This morning, when I first saw this message, I just did a mount from > > bconsole and the job continued, I have bacula configured for 6 > > jobs per > > media and the tape wasn't full so the job should have just started > > as it > > hallways has. Now it's time to backup up the catalog, to file, and > > I'm > > getting the same message. > > > > I have an HP DDS2 drive, no changer, running on Slackware 10. I'm > > using > > the same conf files the worked fine on 1.38.1. Can anyone tell me why > > I'm now getting this error message? > > You are not by any chance running on a 2.4 kernel with /lib/tls? > > Could you send me your bacula-dir.conf and bacula-sd.conf along > with the > job report that shows the jobs blocking? > > > Thanks, > > RickKnight > > > > > > --- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through > > log > > files for problems? Stop! Download the new AJAX search engine that > > makes searching your log files as easy as surfing the web. DOWNLOAD > > SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > > ___ > > Bacula-users mailing list > > Bacula-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bacula-users > >>> > >>> Thanks Kern, > >>> > >>> I am running a 2.4.26 kernel, but I don't know about /lib/tls. I don't > >>> have a /lib/tls on my system. How can I tell? > >> > >> Try: > >> > >> ls -l /lib/tls > >> > >> If it exists, then that could explain why it *appears* that Bacula is > >> not seeing some pthread broadcasts that would allow it to continue. > >> This is a bit of a long shot, but at this point, I need to consider > >> all possibilities ... > >> > >> In the mean time, I'll take a careful look at your config. Perhaps I > >> have missed something important that I can add to my test cases. All > >> my tests here succeeded perfectly ... > >> > >> By the way, getting the message that a job is waiting to reserve a > >> drive is not in itself bad. This happens in my test case. However, at > >> some point when the drive is available, the job should continue as it > >> does in my test case. > >> > >>> Also, the .conf files are attached along with the log. > >>> > >>> Thanks again, > >>> RickKnight > > > > Kern, > > > > I just got another job log email. Something I noticed is a clock > > difference between the Director and File daemons. The two lines below > > ar
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
I am also getting this error since upgrading to 1.38 from the 1.36 branch... been trying to figure out why for a few days now. I am also running slackware 10... I wonder if this is related. Not running 2.4 kernel though, running 2.6.11.12 right now. I am backing up to disk, not tapes. Manually scheduled jobs run just fine, and automatic jobs run sometimes (the first job)... but most of the time they block indefinitely with "waiting to reserve a device". I figured I had just screwed up a configuration file somehow, but I have tweaked my configuration files with no improvement. Maybe this is tied to a package in slackware 10? Any other users running slackware 10 with 1.38 successfully? james peverill Richard W. Knight wrote: Kern Sibbald wrote: On Tuesday 13 December 2005 13:43, Rick Knight wrote: Kern Sibbald wrote: Hello, On Monday 12 December 2005 19:35, Richard W. Knight wrote: Hi all, A couple of weeks ago I upgraded my Bacula installation from 1.34 to 1.38.1. I made a few other changes at the same time and everything has been working well since. Yesterday I decided to upgrade to 1.38.3. I built from source using the same configuration options that I used to build 1.38.1 with the addition of "--with-python". The build went OK, no errors. I stopped 1.38.1 and started 1.38.3. Everything seemed to be OK. I ran a couple of small test backups and there were no errors so I assumed that the upgrade went fine. Last night the scheduled backup ran and after the first job, instead of continuing on to the next job, I got this message ... 12-Dec 07:29 MyJob-SMB-sd: Job MyJob.2005-12-12_01.05.01 waiting to reserve a device. This morning, when I first saw this message, I just did a mount from bconsole and the job continued, I have bacula configured for 6 jobs per media and the tape wasn't full so the job should have just started as it hallways has. Now it's time to backup up the catalog, to file, and I'm getting the same message. I have an HP DDS2 drive, no changer, running on Slackware 10. I'm using the same conf files the worked fine on 1.38.1. Can anyone tell me why I'm now getting this error message? You are not by any chance running on a 2.4 kernel with /lib/tls? Could you send me your bacula-dir.conf and bacula-sd.conf along with the job report that shows the jobs blocking? Thanks, RickKnight --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users Thanks Kern, I am running a 2.4.26 kernel, but I don't know about /lib/tls. I don't have a /lib/tls on my system. How can I tell? Try: ls -l /lib/tls If it exists, then that could explain why it *appears* that Bacula is not seeing some pthread broadcasts that would allow it to continue. This is a bit of a long shot, but at this point, I need to consider all possibilities ... In the mean time, I'll take a careful look at your config. Perhaps I have missed something important that I can add to my test cases. All my tests here succeeded perfectly ... By the way, getting the message that a job is waiting to reserve a drive is not in itself bad. This happens in my test case. However, at some point when the drive is available, the job should continue as it does in my test case. Also, the .conf files are attached along with the log. Thanks again, RickKnight Kern, I just got another job log email. Something I noticed is a clock difference between the Director and File daemons. The two lines below are from this mornings log (also attached). Could that be causing a problem? 12-Dec 19:29 knight-linux-SMB-sd: Job Knight-Linux.2005-12-12_01.05.01 waiting to reserve a device. 13-Dec 04:33 knight-linux-fd: DIR and FD clocks differ by 676 seconds, FD automatically adjusting. Thanks again, Rick Knight 12-Dec 04:29 knight-linux-SMB-dir: Start Backup J
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
On Tuesday 13 December 2005 19:44, Richard W. Knight wrote:
...
> >>
> >>I just got another job log email. Something I noticed is a clock
> >>difference between the Director and File daemons. The two lines below
> >>are from this mornings log (also attached). Could that be causing a
> >>problem?
> >
> >No, that cannot be causing the problem. For some reason the signals that
> > are sent to wake up the waiting thread are not properly delivered, or
> > there is something else going on.
> >
> >Thanks for your files and the log.
>
> Your welcome Kern, I hope they help.
>
> >I would recommend that you put double quotes arount the "HP SureStore
> > DAT-8" name *everywhere* it appears in your conf file.
>
> Will do.
>
> >Can you tell me a few more things?
> >
> >1. Did you finally have to use the "mount command to free up the
> >Knight-Linux_SMB job? -- if so, I'm impressed because you had to be up at
> > 4am to do it -- if not, where is the problem?
>
> I had to use the mount command to get bacula to start the job.
> Knight-Linux-SMB runs first, then Knight-Linux runs, followed by
> Catalog. After Knight-Linux-SMB finished, instead of just continuing on
> with Knight-Linux, bacula just sits with the "waiting to reserve a
> device" message. If I just mount the device, the job does continue. But,
> I just realized something else. I have a "run after" job that rewinds
> the tape and then ejects it. It didn't seem to be a problem with 1.38.1,
> but it may be causing the pause now?
Yes, this is undoubtedly the problem. With earlier versions of Bacula, you
could unmount a tape almost any time, but with version 1.38, it *knows* what
tape is in what drive, and if you suddenly remove a tape without telling it,
it will cause problems.
Modify your "run after" script to do a Bacula "unmount", then rewind and eject
the tape, followed by a Bacula "mount" at that point, it should be OK.
Alternatively, you might be able to set a Poll Interval and get it to work --
the problem is that I have not tested polling recently ...
> I'm at work now, so I can't check
> it but I will when I get home tonight.
> And yes, I am up at about 4:00 most mornings. I have a long commute to
> work so I get up, early, spend about 15 minutes in my home office with
> coffee and email. If a tape needs attention, I do that then too.
>
> >2. Can you show me the log output of the job that Knight-Linux_SMB was
> > waiting for?
>
> I'll attach a log that shows both jobs, before and after. Oops, I can't
> access the log files from work, so I'll send them tonight.
>
> Thanks again Kern,
> Rick Knight
>
...
--
Best regards,
Kern
(">
/\
V_V
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
Kern Sibbald wrote: On Tuesday 13 December 2005 17:54, Richard W. Knight wrote: Kern Sibbald wrote: On Tuesday 13 December 2005 13:43, Rick Knight wrote: Kern Sibbald wrote: Hello, On Monday 12 December 2005 19:35, Richard W. Knight wrote: Hi all, A couple of weeks ago I upgraded my Bacula installation from 1.34 to 1.38.1. I made a few other changes at the same time and everything has been working well since. Yesterday I decided to upgrade to 1.38.3. I built from source using the same configuration options that I used to build 1.38.1 with the addition of "--with-python". The build went OK, no errors. I stopped 1.38.1 and started 1.38.3. Everything seemed to be OK. I ran a couple of small test backups and there were no errors so I assumed that the upgrade went fine. Last night the scheduled backup ran and after the first job, instead of continuing on to the next job, I got this message ... 12-Dec 07:29 MyJob-SMB-sd: Job MyJob.2005-12-12_01.05.01 waiting to reserve a device. This morning, when I first saw this message, I just did a mount from bconsole and the job continued, I have bacula configured for 6 jobs per media and the tape wasn't full so the job should have just started as it hallways has. Now it's time to backup up the catalog, to file, and I'm getting the same message. I have an HP DDS2 drive, no changer, running on Slackware 10. I'm using the same conf files the worked fine on 1.38.1. Can anyone tell me why I'm now getting this error message? You are not by any chance running on a 2.4 kernel with /lib/tls? Could you send me your bacula-dir.conf and bacula-sd.conf along with the job report that shows the jobs blocking? Thanks, RickKnight Thanks Kern, I am running a 2.4.26 kernel, but I don't know about /lib/tls. I don't have a /lib/tls on my system. How can I tell? Try: ls -l /lib/tls If it exists, then that could explain why it *appears* that Bacula is not seeing some pthread broadcasts that would allow it to continue. This is a bit of a long shot, but at this point, I need to consider all possibilities ... In the mean time, I'll take a careful look at your config. Perhaps I have missed something important that I can add to my test cases. All my tests here succeeded perfectly ... By the way, getting the message that a job is waiting to reserve a drive is not in itself bad. This happens in my test case. However, at some point when the drive is available, the job should continue as it does in my test case. Also, the .conf files are attached along with the log. Thanks again, RickKnight Hello Rick, Kern, I just got another job log email. Something I noticed is a clock difference between the Director and File daemons. The two lines below are from this mornings log (also attached). Could that be causing a problem? No, that cannot be causing the problem. For some reason the signals that are sent to wake up the waiting thread are not properly delivered, or there is something else going on. Thanks for your files and the log. Your welcome Kern, I hope they help. I would recommend that you put double quotes arount the "HP SureStore DAT-8" name *everywhere* it appears in your conf file. Will do. Can you tell me a few more things? 1. Did you finally have to use the "mount command to free up the Knight-Linux_SMB job? -- if so, I'm impressed because you had to be up at 4am to do it -- if not, where is the problem? I had to use the mount command to get bacula to start the job. Knight-Linux-SMB runs first, then Knight-Linux runs, followed by Catalog. After Knight-Linux-SMB finished, instead of just continuing on with Knight-Linux, bacula just sits with the "waiting to reserve a device" message. If I just mount the device, the job does continue. But, I just realized something else. I have a "run after" job that rewinds the tape and then ejects it. It didn't seem to be a problem with 1.38.1, but it may be causing the pause now? I'm at work now, so I can't check it but I will when I get home tonight. And yes, I am up at about 4:00 most mornings. I have a long commute to work so I get up, early, spend about 15 minutes in my home office with coffee and email. If a tape needs attention, I do that then too. 2. Can you show me the log output of the job that Knight-Linux_SMB was waiting for? I'll attach a log that shows both jobs, before and after. Oops, I can't access the log files from work, so I'll send them tonight. Thanks again Kern, Rick Knight I was a bit surprised to see the waiting to reserver a device message printed a number of times, but after looking at the code, it was perfectly OK. 12-Dec 19:29 knight-linux-SMB-sd: Job Knight-Linux.2005-12-12_01.05.01 waiting to reserve a device. 13-Dec 04:33 knight-linux-fd: DIR and FD clocks differ by 676 seconds, FD automatically adjusting. Thanks again, Rick Knight
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
On Tuesday 13 December 2005 17:54, Richard W. Knight wrote:
> Kern Sibbald wrote:
> >On Tuesday 13 December 2005 13:43, Rick Knight wrote:
> >>Kern Sibbald wrote:
> >>>Hello,
> >>>
> >>>On Monday 12 December 2005 19:35, Richard W. Knight wrote:
> Hi all,
>
> A couple of weeks ago I upgraded my Bacula installation from 1.34 to
> 1.38.1. I made a few other changes at the same time and everything has
> been working well since. Yesterday I decided to upgrade to 1.38.3. I
> built from source using the same configuration options that I used to
> build 1.38.1 with the addition of "--with-python". The build went OK,
> no errors. I stopped 1.38.1 and started 1.38.3. Everything seemed to be
> OK. I ran a couple of small test backups and there were no errors so I
> assumed that the upgrade went fine. Last night the scheduled backup ran
> and after the first job, instead of continuing on to the next job, I
> got this message ...
>
> 12-Dec 07:29 MyJob-SMB-sd: Job MyJob.2005-12-12_01.05.01 waiting to
> reserve a device.
>
> This morning, when I first saw this message, I just did a mount from
> bconsole and the job continued, I have bacula configured for 6 jobs per
> media and the tape wasn't full so the job should have just started as
> it hallways has. Now it's time to backup up the catalog, to file, and
> I'm getting the same message.
>
> I have an HP DDS2 drive, no changer, running on Slackware 10. I'm using
> the same conf files the worked fine on 1.38.1. Can anyone tell me why
> I'm now getting this error message?
> >>>
> >>>You are not by any chance running on a 2.4 kernel with /lib/tls?
> >>>
> >>>Could you send me your bacula-dir.conf and bacula-sd.conf along with the
> >>>job report that shows the jobs blocking?
> >>>
> Thanks,
> RickKnight
> >>Thanks Kern,
> >>
> >>I am running a 2.4.26 kernel, but I don't know about /lib/tls. I don't
> >>have a /lib/tls on my system. How can I tell?
> >
> >Try:
> >
> > ls -l /lib/tls
> >
> >If it exists, then that could explain why it *appears* that Bacula is not
> >seeing some pthread broadcasts that would allow it to continue. This is a
> > bit of a long shot, but at this point, I need to consider all
> > possibilities ...
> >
> >In the mean time, I'll take a careful look at your config. Perhaps I have
> >missed something important that I can add to my test cases. All my tests
> >here succeeded perfectly ...
> >
> >By the way, getting the message that a job is waiting to reserve a drive
> > is not in itself bad. This happens in my test case. However, at some
> > point when the drive is available, the job should continue as it does in
> > my test case.
> >
> >>Also, the .conf files are attached along with the log.
> >>
> >>Thanks again,
> >>RickKnight
Hello Rick,
>
> Kern,
>
> I just got another job log email. Something I noticed is a clock
> difference between the Director and File daemons. The two lines below
> are from this mornings log (also attached). Could that be causing a
> problem?
No, that cannot be causing the problem. For some reason the signals that are
sent to wake up the waiting thread are not properly delivered, or there is
something else going on.
Thanks for your files and the log.
I would recommend that you put double quotes arount the "HP SureStore DAT-8"
name *everywhere* it appears in your conf file.
Can you tell me a few more things?
1. Did you finally have to use the "mount command to free up the
Knight-Linux_SMB job? -- if so, I'm impressed because you had to be up at 4am
to do it -- if not, where is the problem?
2. Can you show me the log output of the job that Knight-Linux_SMB was waiting
for?
I was a bit surprised to see the waiting to reserver a device message printed
a number of times, but after looking at the code, it was perfectly OK.
>
> 12-Dec 19:29 knight-linux-SMB-sd: Job Knight-Linux.2005-12-12_01.05.01
> waiting to reserve a device. 13-Dec 04:33 knight-linux-fd: DIR and FD
> clocks differ by 676 seconds, FD automatically adjusting.
>
>
> Thanks again,
> Rick Knight
--
Best regards,
Kern
(">
/\
V_V
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
Kern Sibbald wrote: On Tuesday 13 December 2005 13:43, Rick Knight wrote: Kern Sibbald wrote: Hello, On Monday 12 December 2005 19:35, Richard W. Knight wrote: Hi all, A couple of weeks ago I upgraded my Bacula installation from 1.34 to 1.38.1. I made a few other changes at the same time and everything has been working well since. Yesterday I decided to upgrade to 1.38.3. I built from source using the same configuration options that I used to build 1.38.1 with the addition of "--with-python". The build went OK, no errors. I stopped 1.38.1 and started 1.38.3. Everything seemed to be OK. I ran a couple of small test backups and there were no errors so I assumed that the upgrade went fine. Last night the scheduled backup ran and after the first job, instead of continuing on to the next job, I got this message ... 12-Dec 07:29 MyJob-SMB-sd: Job MyJob.2005-12-12_01.05.01 waiting to reserve a device. This morning, when I first saw this message, I just did a mount from bconsole and the job continued, I have bacula configured for 6 jobs per media and the tape wasn't full so the job should have just started as it hallways has. Now it's time to backup up the catalog, to file, and I'm getting the same message. I have an HP DDS2 drive, no changer, running on Slackware 10. I'm using the same conf files the worked fine on 1.38.1. Can anyone tell me why I'm now getting this error message? You are not by any chance running on a 2.4 kernel with /lib/tls? Could you send me your bacula-dir.conf and bacula-sd.conf along with the job report that shows the jobs blocking? Thanks, RickKnight --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users Thanks Kern, I am running a 2.4.26 kernel, but I don't know about /lib/tls. I don't have a /lib/tls on my system. How can I tell? Try: ls -l /lib/tls If it exists, then that could explain why it *appears* that Bacula is not seeing some pthread broadcasts that would allow it to continue. This is a bit of a long shot, but at this point, I need to consider all possibilities ... In the mean time, I'll take a careful look at your config. Perhaps I have missed something important that I can add to my test cases. All my tests here succeeded perfectly ... By the way, getting the message that a job is waiting to reserve a drive is not in itself bad. This happens in my test case. However, at some point when the drive is available, the job should continue as it does in my test case. Also, the .conf files are attached along with the log. Thanks again, RickKnight Kern, I just got another job log email. Something I noticed is a clock difference between the Director and File daemons. The two lines below are from this mornings log (also attached). Could that be causing a problem? 12-Dec 19:29 knight-linux-SMB-sd: Job Knight-Linux.2005-12-12_01.05.01 waiting to reserve a device. 13-Dec 04:33 knight-linux-fd: DIR and FD clocks differ by 676 seconds, FD automatically adjusting. Thanks again, Rick Knight 12-Dec 04:29 knight-linux-SMB-dir: Start Backup JobId 559, Job=Knight-Linux.2005-12-12_01.05.01 12-Dec 04:29 knight-linux-SMB-sd: Job Knight-Linux.2005-12-12_01.05.01 waiting to reserve a device. 12-Dec 05:29 knight-linux-SMB-sd: Job Knight-Linux.2005-12-12_01.05.01 waiting to reserve a device. 12-Dec 07:29 knight-linux-SMB-sd: Job Knight-Linux.2005-12-12_01.05.01 waiting to reserve a device. 12-Dec 11:29 knight-linux-SMB-sd: Job Knight-Linux.2005-12-12_01.05.01 waiting to reserve a device. 12-Dec 19:29 knight-linux-SMB-sd: Job Knight-Linux.2005-12-12_01.05.01 waiting to reserve a device. 13-Dec 04:33 knight-linux-fd: DIR and FD clocks differ by 676 seconds, FD automatically adjusting. 13-Dec 04:22 knight-linux-SMB-sd: Volume "DailyIncr-0011" previously written, moving to end of data. 13-Dec 04:22 knight-linux-SMB-sd: Ready to append to end of Volume "DailyIncr-0011" at file=4. 13-Dec 04:44 knight-linux-SMB-dir: Bacula 1.38.3 (09Dec05): 13-Dec-2005 04:44:48 JobId: 559 Job:Knight-Linux.2005-12-12_01.05.01 Backup Level: Incremental, since=2005-12-11 01:07:20 Client: "knight-linux-fd" i686-pc-linux-gnu,slackware,Slackware 9.0.0 FileSet:"Knight-Linux" 2005-11-21 21:06:17 Pool: "DailyPool" Storage:"HPSureStoreDAT-8" Scheduled time: 12-Dec-2005 01:05:00 Start time: 12-Dec-2005 04:29:22 End time: 13
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
On Tuesday 13 December 2005 13:43, Rick Knight wrote:
> Kern Sibbald wrote:
> >Hello,
> >
> >On Monday 12 December 2005 19:35, Richard W. Knight wrote:
> >>Hi all,
> >>
> >>A couple of weeks ago I upgraded my Bacula installation from 1.34 to
> >>1.38.1. I made a few other changes at the same time and everything has
> >>been working well since. Yesterday I decided to upgrade to 1.38.3. I
> >>built from source using the same configuration options that I used to
> >>build 1.38.1 with the addition of "--with-python". The build went OK,
> >>no errors. I stopped 1.38.1 and started 1.38.3. Everything seemed to be
> >>OK. I ran a couple of small test backups and there were no errors so I
> >>assumed that the upgrade went fine. Last night the scheduled backup ran
> >>and after the first job, instead of continuing on to the next job, I got
> >>this message ...
> >>
> >>12-Dec 07:29 MyJob-SMB-sd: Job MyJob.2005-12-12_01.05.01 waiting to
> >> reserve a device.
> >>
> >>This morning, when I first saw this message, I just did a mount from
> >>bconsole and the job continued, I have bacula configured for 6 jobs per
> >>media and the tape wasn't full so the job should have just started as it
> >>hallways has. Now it's time to backup up the catalog, to file, and I'm
> >>getting the same message.
> >>
> >>I have an HP DDS2 drive, no changer, running on Slackware 10. I'm using
> >>the same conf files the worked fine on 1.38.1. Can anyone tell me why
> >>I'm now getting this error message?
> >
> >You are not by any chance running on a 2.4 kernel with /lib/tls?
> >
> >Could you send me your bacula-dir.conf and bacula-sd.conf along with the
> > job report that shows the jobs blocking?
> >
> >>Thanks,
> >>RickKnight
> >>
> >>
> >>---
> >>This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> >>files for problems? Stop! Download the new AJAX search engine that
> >> makes searching your log files as easy as surfing the web. DOWNLOAD
> >> SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> >>___
> >>Bacula-users mailing list
> >>Bacula-users@lists.sourceforge.net
> >>https://lists.sourceforge.net/lists/listinfo/bacula-users
>
> Thanks Kern,
>
> I am running a 2.4.26 kernel, but I don't know about /lib/tls. I don't
> have a /lib/tls on my system. How can I tell?
Try:
ls -l /lib/tls
If it exists, then that could explain why it *appears* that Bacula is not
seeing some pthread broadcasts that would allow it to continue. This is a bit
of a long shot, but at this point, I need to consider all possibilities ...
In the mean time, I'll take a careful look at your config. Perhaps I have
missed something important that I can add to my test cases. All my tests
here succeeded perfectly ...
By the way, getting the message that a job is waiting to reserve a drive is
not in itself bad. This happens in my test case. However, at some point when
the drive is available, the job should continue as it does in my test case.
> Also, the .conf files are attached along with the log.
>
> Thanks again,
> RickKnight
--
Best regards,
Kern
(">
/\
V_V
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
Kern Sibbald wrote:
Hello,
On Monday 12 December 2005 19:35, Richard W. Knight wrote:
Hi all,
A couple of weeks ago I upgraded my Bacula installation from 1.34 to
1.38.1. I made a few other changes at the same time and everything has
been working well since. Yesterday I decided to upgrade to 1.38.3. I
built from source using the same configuration options that I used to
build 1.38.1 with the addition of "--with-python". The build went OK,
no errors. I stopped 1.38.1 and started 1.38.3. Everything seemed to be
OK. I ran a couple of small test backups and there were no errors so I
assumed that the upgrade went fine. Last night the scheduled backup ran
and after the first job, instead of continuing on to the next job, I got
this message ...
12-Dec 07:29 MyJob-SMB-sd: Job MyJob.2005-12-12_01.05.01 waiting to reserve
a device.
This morning, when I first saw this message, I just did a mount from
bconsole and the job continued, I have bacula configured for 6 jobs per
media and the tape wasn't full so the job should have just started as it
hallways has. Now it's time to backup up the catalog, to file, and I'm
getting the same message.
I have an HP DDS2 drive, no changer, running on Slackware 10. I'm using
the same conf files the worked fine on 1.38.1. Can anyone tell me why
I'm now getting this error message?
You are not by any chance running on a 2.4 kernel with /lib/tls?
Could you send me your bacula-dir.conf and bacula-sd.conf along with the job
report that shows the jobs blocking?
Thanks,
RickKnight
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Thanks Kern,
I am running a 2.4.26 kernel, but I don't know about /lib/tls. I don't
have a /lib/tls on my system. How can I tell? Also, the .conf files are
attached along with the log.
Thanks again,
RickKnight
#
# Default Bacula Director Configuration file
#
# The only thing that MUST be changed is to add one or more
# file or directory names in the Include directive of the
# FileSet resource.
#
# For Bacula release 1.34.5 (21 June 2004) -- slackware Slackware 9.0.0
#
# You might also want to change the default email address
# from root to your address. See the "mail" and "operator"
# directives in the Messages resource.
#
Director {# define myself
Name = knight-linux-SMB-dir
DIRport = 9101# where we listen for UA connections
QueryFile = "/etc/bacula/query.sql"
WorkingDirectory = "/etc/bacula/work"
PidDirectory = "/var/run"
Maximum Concurrent Jobs = 1
Password = "justforbackup" # Console password
Messages = Standard
}
#JobDefs {
# Name = "DefaultJob"
# Type = Backup
# Level = Incremental
# Client = knight-linux-SMB-fd
# FileSet = "Full Set"
# Schedule = "WeeklyCycle"
# Storage = File
# Messages = Standard
# Pool = Default
# Priority = 10
#}
#
# Define the main nightly save backup job
# By default, this job will back up to disk in /tmp
#Job {
# Name = "WeeklySave"
# JobDefs = "DefaultJob"
# Level = Full
# Storage = Exabyte 8505XL
# Pool = WeeklyPool
# Write Bootstrap = "/etc/bacula/work/WeeklySave.bsr"
#}
Job {
Name = "Knight-Linux SMB"
# JobDefs = "DefaultJob"
Type = Backup
Client = knight-linux-SMB-fd
FileSet = "Knight-Linux SMB"
Schedule = WeeklyCycle
Storage = HP SureStore DAT-8
Messages = Standard
Pool = Default
Max Start Delay = 22h
Write Bootstrap = "/etc/bacula/work/NightlySave.bsr"
}
Job {
Name = "Knight-Linux"
Type = Backup
Client = knight-linux-fd
FileSet = "Knight-Linux"
Schedule = WeeklyCycle
Storage = HP SureStore DAT-8
Messages = Standard
Pool = Default
Max Start Delay = 22h
Write Bootstrap = "/etc/bacula/work/NightlySave_knight-linux.bsr"
}
# Backup the catalog database (after the nightly save)
Job {
Name = "BackupCatalog"
# JobDefs = "DefaultJob"
Level = Full
Type = backup
Client = knight-linux-SMB-fd
FileSet="Catalog"
Schedule = "WeeklyCycleAfterBackup"
Storage = File
Messages = Standard
Pool = Default
# This creates an ASCII copy of the catalog
RunBeforeJob = "/etc/bacula/make_catalog_backup bacula bacula justforbackup"
# This deletes the copy of the catalog
#RunAfterJob = "/etc/bacula/delete_catalog_backup"
RunAfterJob = "/etc/bacula/end_of_backup.sh"
Write Bootstrap = "/etc/bacula/work/BackupCatalog.bsr"
Priority = 11 # run after main backup
}
# Standard Restore template, to be changed by Console program
Job {
Name = "Restore Knight-Linux SMB"
Type = Restore
Re: [Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
Hello,
On Monday 12 December 2005 19:35, Richard W. Knight wrote:
> Hi all,
>
> A couple of weeks ago I upgraded my Bacula installation from 1.34 to
> 1.38.1. I made a few other changes at the same time and everything has
> been working well since. Yesterday I decided to upgrade to 1.38.3. I
> built from source using the same configuration options that I used to
> build 1.38.1 with the addition of "--with-python". The build went OK,
> no errors. I stopped 1.38.1 and started 1.38.3. Everything seemed to be
> OK. I ran a couple of small test backups and there were no errors so I
> assumed that the upgrade went fine. Last night the scheduled backup ran
> and after the first job, instead of continuing on to the next job, I got
> this message ...
>
> 12-Dec 07:29 MyJob-SMB-sd: Job MyJob.2005-12-12_01.05.01 waiting to reserve
> a device.
>
> This morning, when I first saw this message, I just did a mount from
> bconsole and the job continued, I have bacula configured for 6 jobs per
> media and the tape wasn't full so the job should have just started as it
> hallways has. Now it's time to backup up the catalog, to file, and I'm
> getting the same message.
>
> I have an HP DDS2 drive, no changer, running on Slackware 10. I'm using
> the same conf files the worked fine on 1.38.1. Can anyone tell me why
> I'm now getting this error message?
You are not by any chance running on a 2.4 kernel with /lib/tls?
Could you send me your bacula-dir.conf and bacula-sd.conf along with the job
report that shows the jobs blocking?
>
> Thanks,
> RickKnight
>
>
> ---
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
--
Best regards,
Kern
(">
/\
V_V
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Error "waiting to reserve a device" after upgrade to 1.38.3
Hi all, A couple of weeks ago I upgraded my Bacula installation from 1.34 to 1.38.1. I made a few other changes at the same time and everything has been working well since. Yesterday I decided to upgrade to 1.38.3. I built from source using the same configuration options that I used to build 1.38.1 with the addition of "--with-python". The build went OK, no errors. I stopped 1.38.1 and started 1.38.3. Everything seemed to be OK. I ran a couple of small test backups and there were no errors so I assumed that the upgrade went fine. Last night the scheduled backup ran and after the first job, instead of continuing on to the next job, I got this message ... 12-Dec 07:29 MyJob-SMB-sd: Job MyJob.2005-12-12_01.05.01 waiting to reserve a device. This morning, when I first saw this message, I just did a mount from bconsole and the job continued, I have bacula configured for 6 jobs per media and the tape wasn't full so the job should have just started as it hallways has. Now it's time to backup up the catalog, to file, and I'm getting the same message. I have an HP DDS2 drive, no changer, running on Slackware 10. I'm using the same conf files the worked fine on 1.38.1. Can anyone tell me why I'm now getting this error message? Thanks, RickKnight --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
