> 
> 
> On Sep 21, 2011, at 3:22 PM, Troy Kocher wrote:
> 
>> Listers, 
>> 
>> I've installed a new bacula server recently and am working to get it in 
>> production.  It's FreeBSD 8.2-RELEASE, (GENERIC), with a default build of 
>> Bacula 5.0.3 sever & client, from the ports tree.  The previous server was 
>> 5.0.0_1 on Freebsd 7.4. I brought over my pgsql database, my configs, and my 
>> data to the new server.  It appears I've done something to cause the 
>> director to run in ipv6 only.  Is this by default in 5.0.3? If so how do I 
>> correct it?  Have I made an error in the dir config?  Please see below for 
>> my details.
>> 
>> foobar# head /usr/local/etc/bacula-dir.conf
>> 
>> Director {                            # define myself
>> Name = foobar-dir
>> Dirport = 9101                # where we listen for UA connections
>> QueryFile = "/usr/local/share/bacula/query.sql"
>> WorkingDirectory = "/data/working"
>> PidDirectory = "/var/run"
>> Maximum Concurrent Jobs = 20
>> Password = "mypassword"         # Console password
>> Messages = Daemon
>> }
>> foobar# bacula start
>> Starting the Bacula Storage daemon
>> Starting the Bacula File daemon
>> Starting the Bacula Director daemon
>> foobar# bconsole
>> Connecting to Director foobar:9101
>> ^C
>> foobar# sockstat
>> USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS    
>>   
>> bacula   bacula-dir 36947 3  tcp6   ::1:26407             ::1:5432
>> bacula   bacula-dir 36947 4  tcp6   ::1:65226             ::1:5432
>> bacula   bacula-dir 36947 5  tcp6   ::1:31295             ::1:5432
> 
> This is a connection from bacula-dir to your PostgresSQL database.  I don't 
> see bacula-dir listening on 9101 yet…

> You also said:
> 
>> Some additional details here, after about 30s the bacula-dir ipv6 seems to 
>> die and the only thing left listening is my bacula-fd & bacula-sd.  
> 
> That makes me suspect the database connection.  I would start bacula-dir in 
> the foreground with -d SOMEVALUE and see what messages you got.

 PostgreSQL is local, interesting that bacula-dir still attempts to find the 
database server on ipv6?!

> 
>> root     bacula-fd  36940 3  tcp4   *:9102                *:*
>> bacula   bacula-sd  36932 3  tcp4   *:9103                *:*
>> 
>> 
>> Any assistance would really be appreciated.

Thanks you Dan!  the issue was the PostgreSQL database permission and 
configuration.  It's all corrected and working now.  

>> 
>> Thanks
>> Troy Kocher
>> 
>> 
> 
> -- 
> Dan Langille - http://langille.org
> 
> 


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users