Hi, 04.07.2007 17:40,, Alfredo Marchini wrote:: > Hi, > The system and db logs doesn't tell me anything about this problem, like > all the director processes or thread are locked concurrently. > If I restart only bacula-dir without restarting bacula-sd and 16 > bacula-fd the system restart working fine.
It might be possible that the DIR is busy working on the catalog (like pruning data) and just needs more time. You can check this using 'mysqladmin processlist', for example. > Now I have already restarted bacula-dir and all works fine (I backup 16 > servers, I cannot take it in offline mode or someone kill me this > evening), so I'm not able to reproduce the error until about 10-15 days. > Last time that I'd got this problem I used top and I didn't find > anything strange. Ok, so let's assume the hardware, OS and relevant applications are running ok. > But the test with time command will be the first when It will rehappen. > I don't think that the problem is with database, when I connect to > database with mysql command line to db bacula it works fine and quickly. Bacula uses its own, internal locking, so you won't necessarily notice anything from outside of Bacula. > One thing: > I've setted for most of my fd 14 days for file and job retention. > One o two fd are setted to 7 days for both file and job retention. > The volume retention period is always setted to 14 days. > > I've got sufficient disk space Sounds interesting... I never have sufficient disk space :-) > to use only one pool for 7 and 14 days > retention client backup. > > Another thing is the maximum concurrent jobs : > On director = 30 > On storage side director configuration file = 60 > On storage = 60 Quite a lot, I think. Running up to 30 jobs in parallel might load your backup server beyond its reasonable working maximum, but that depends on your hardware, software, and requirements. > Can this parameters gives me this problem? Unlikely. > These are the only parameters that I'm not sure to have understood where > i've read the manual. > The others i think are correctly configured. If you can reproduce the problem, issue a 'setdebug level=400 trace=1 dir' shortly before you expect the problem and look at the resulting trace file... it will have detailed information about what the DIR is doing. Arno > Thank you again > bye > > > Arno Lehmann wrote: >> Hi, >> >> 04.07.2007 16:51,, Alfredo Marchini wrote:: >> >>> Hi all, >>> I've installed with rpm, on a Linux Fedora Core 6, a bacula-dir and >>> bacula-sd daemon. >>> On this server there is also a Mysql-5.0.x server that correctly talks >>> with bacula daemons. >>> Also there is a RAID-5 partition of a size of 1TB where I save my backups. >>> The server make backups of 16 bacula-fd that I've got in my LAN. >>> I've configured 1 pool with 18 volumes of 50Gb, with a retention period >>> of 14 days and autoprune and recycle set to yes. >>> All works fine for some days. >>> Today (after some days, but is not the first time) I've noticed that >>> bacula doesn't run scheduled backup jobs. >>> So I use bconsole and ask status of director, and director is locked, >>> doesn't give me any answer, and any error. >>> I need to press CTRL+c to quit bconsole, I retry asking the status of >>> storage, and doesn't give me any answer, and any error. >>> Same behaviour if I ask the status of any of 16 file daemon that I've >>> configured in my director. >>> I don't know why. >>> >> We'll try to find that out... >> >> It might be a locked-up database, for example. In that case, try a >> command that doesn't require catalog access, like time. >> >> If that doesn't reply, I'd recommend attaching strace to the DIR >> processes to see what they're doing (unless you're more comfortable >> with gdb...) >> >> Also, use df and free to verify the necessary system resources are >> available (memory and disk space), and check with ps or top and vmstat >> if any process is using extraordinary amounts of CPU, ram, or I/O >> capacity. >> >> If 'time' gets you a reply, but anything requiring catalog access >> doesn't, check for database problems in the database logs or the >> system logs. >> >> The system logs might tell you about problems anyway, so I recommend >> having a look at them anyway. >> >> >>> If you need the director, storage or file-daemon configuration I need to >>> prepare them, but is not a problem. >>> >> Not yet... >> >> Arno >> >> > > -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
