Re: [Bacula-users] Bacula-dir 5.01 no listen
On 03/12/11 21:19, Steen Meyer wrote: > The problem turned out to be missing permissions on the working directory: > chown -R bacula:root /var/cache/bacula > Then Bacula-dir start and listen also when started normally It is worth noting that this is not a failure of bacula, it is a failure of the package from which Bacula was installed to properly set the directory permissions, and that this is easier to get right if the Bacula recommended filesystem layout for Bacula is followed. -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater It's not the years, it's the mileage. -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula-dir 5.01 no listen
Torsdag den 11. Marts 2010 13:49:15 skrev John Drescher: > > You can help me? > > First off remove 127.0.0.1 and local host from all bacula > configuration files. Using either of these will prevent bacula from > being a network backup program. Secondly start the director from the > console > > bacula-dir -c /etc/bacula/bacula-dir.conf -d 100 I had a similar issue with 5.03 - for the record: Bacula-dir started, but did not listen. bacula-dir -t -c /etc/bacula/bacula-dir.conf revealed an issue with the database: I had to grant privileges to the database not only after database creation, but also after the table creation. Then Bacula-dir started again - without listening - and with no errors in the logs sudo bacula-dir -c /etc/bacula/bacula-dir.conf -d 100 made Bacula-dir start and listen without errors. The problem turned out to be missing permissions on the working directory: chown -R bacula:root /var/cache/bacula Then Bacula-dir start and listen also when started normally Tanks for the great tip - now that Bacula itself is so sparce with information -- Steen -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula-dir 5.01 no listen
2010/3/11 mario parreño :
> Hi Greg, first, thanks for reading the question.
>
> I execute netstat -tanp
> debian-bacula:/etc/bacula# netstat -tanp
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address Foreign Address
> State PID/Program name
> tcp 0 0 127.0.0.1:3306 0.0.0.0:*
> LISTEN 2427/mysqld
> tcp 0 0 0.0.0.0:9102 0.0.0.0:*
> LISTEN 25815/bacula-fd
> tcp 0 0 0.0.0.0:9103 0.0.0.0:*
> LISTEN 25794/bacula-sd
> tcp 0 0 0.0.0.0:111 0.0.0.0:*
> LISTEN 1961/portmap
> tcp 0 0 127.0.0.1:631 0.0.0.0:*
> LISTEN 2537/cupsd
> tcp 0 0 0.0.0.0:36023 0.0.0.0:*
> LISTEN 1978/rpc.statd
> tcp 0 0 127.0.0.1:25 0.0.0.0:*
> LISTEN 2835/exim4
> tcp 0 0 192.168.47.129:46738 92.122.207.136:80
> ESTABLISHED 3299/firefox-bin
> tcp 0 0 192.168.47.129:54912 65.55.149.123:80
> ESTABLISHED 3299/firefox-bin
> tcp6 0 0 ::1:631 :::*
> LISTEN 2537/cupsd
>
> I view the ports 9102 y 9103 listen, but no 9101.
>
> My files conf are:
>
> DIRECTOR:
> Director { # define myself
> Name = debian-bacula-dir
> DIRport = 9101 # where we listen for UA connections
> QueryFile = "/etc/bacula/query.sql"
> WorkingDirectory = "/var/bacula/working"
> PidDirectory = "/var/run"
> Maximum Concurrent Jobs = 1
> Password = "0rHjNtqeYu3kOIIrGl+WW0MlO7zoDq+Cxo7sb1tvFKLR" #
> Console password
> Messages = Daemon
> }
> .
> .
> Client {
> Name = debian-bacula-fd
> Address = 127.0.0.1
> FDPort = 9102
> Catalog = MyCatalog
> Password = "yyjjEFvz/Jf3YknWe10jibTL9S3oI02Zv2QOsLznX5vd" #
> password for FileDaemon
> File Retention = 30 days # 30 days
> Job Retention = 6 months # six months
> AutoPrune = yes # Prune expired Jobs/Files
> }
> .
> .
> Storage {
> Name = File
> # Do not use "localhost" here
> Address = 127.0.0.1 # N.B. Use a fully qualified name here
> SDPort = 9103
> Password = "zV6DkSAOLoXSL96779RE75yFyrS1r2wYKFAtaydwbdFs"
> Device = FileStorage
> Media Type = File
> }
>
> STORAGE
>
> Storage { # definition of myself
> Name = debian-bacula-sd
> SDPort = 9103 # Director's port
> WorkingDirectory = "/var/bacula/working"
> Pid Directory = "/var/run"
> Maximum Concurrent Jobs = 20
> }
>
> Director {
> Name = debian-bacula-dir
> Password = "zV6DkSAOLoXSL96779RE75yFyrS1r2wYKFAtaydwbdFs"
> }
>
>
> CLIENT
>
> Director {
> Name = debian-bacula-mon
> Password = "mM1qkD9zXeGCRiscDEpSHW6I60v2IZZb8Qo/zVdlRfse"
> Monitor = yes
> }
> ..
>
> FileDaemon { # this is me
> Name = debian-bacula-fd
> FDport = 9102 # where we listen for the director
> WorkingDirectory = /var/bacula/working
> Pid Directory = /var/run
> Maximum Concurrent Jobs = 20
> }
>
> NOTE: when I installed Bacula 2.4.4 bconsole no connected with director, and
> the solution was
> stop director
> execute bacula-dir -d 100 -c /etc/bacula-dir.conf
>
>
>
> You can help me?
First off remove 127.0.0.1 and local host from all bacula
configuration files. Using either of these will prevent bacula from
being a network backup program. Secondly start the director from the
console
bacula-dir -c /etc/bacula/bacula-dir.conf -d 100
and email the error you get. I am going to guess that the database is
either not configured or not running.
John
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
