I upgraded my 5.2 system to 7 in place with no configuration changes 
required using the packages from 
http://repos.fedorapeople.org/repos/slaanesh/bacula7/epel-6/x86_64/.

The 5.2 install used packages from 
https://repos.fedorapeople.org/repos/slaanesh/bacula/epel-6/x86_64/, so 
your mileage may vary depending on where your 5.2 came from.


On 2014-10-08 09:19, Bryn Hughes wrote:
> I tried initially with my 5.x config. I then re-wrote a new config from
> scratch and tested.  And then when that didn't work I also tried using
> the bundled default configuration.
> 
> I'm quite confident that this is going to turn out to be an issue 
> around
> a version of a library I've compiled again or something of the sort.
> 
> Bryn
> 
> On 14-10-07 12:49 PM, Jonathan Bayer wrote:
>> ok.
>> 
>> Are you using a migrated config, or a new one?
>> 
>> What system are you running on?
>> 
>> I'm asking because I'm running a 7.0.5 on a CentOS 6 box without any
>> problems.
>> 
>> 
>> JBB
>> 
>> On 10/7/14, 3:06 PM, Bryn Hughes wrote:
>>> Yup, I've gone as far as to reboot the server just to make absolutely
>>> sure it wasn't an old process hanging about.  Plus starting 
>>> everything
>>> manually in debug mode rules that out.
>>> 
>>> Bryn
>>> 
>>> On 14-10-07 12:01 PM, Jonathan Bayer wrote:
>>>> This happened to me the other day.
>>>> 
>>>> Make sure that ALL the bacula processes are stopped.  My problem was
>>>> that one of them was continuing to hang around with the old config.
>>>> Drove me up the wall until I figured it out.
>>>> 
>>>> 
>>>> JBB
>>>> 
>>>> 
>>>> On 10/7/14, 2:00 PM, Bryn Hughes wrote:
>>>>> I've been having some issues with my old 5.2.6 installation and I
>>>>> thought it would be a good idea to upgrade to a more recent Bacula
>>>>> version, so I downloaded v7.0.5 and also the 'debian' files to 
>>>>> allow me
>>>>> to build packages.  I'm using Ubuntu 12.04.
>>>>> 
>>>>> I have not been able to get communication working between the 
>>>>> console
>>>>> and the director, I am getting an Authorization Error indicating 
>>>>> that I
>>>>> probably have something wrong with my password, yet I've quadruple
>>>>> checked everything in that regard.
>>>>> 
>>>>> Steps I've taken:
>>>>> 
>>>>> - Started from scratch on the config files - I am using the base 
>>>>> config
>>>>> included in the package with nothing else in it
>>>>> - Dumped the database and started from scratch
>>>>> - Restarted everything
>>>>> 
>>>>> I'm fairly certain at this point that I have a bug related to
>>>>> authorization as there's not really any other options left.  I had 
>>>>> a
>>>>> completely working installation with 5.2.6 and I've been using 
>>>>> Bacula
>>>>> for a loooong time so I'm confident the config is all ok. Is there 
>>>>> a
>>>>> known issue around using v7.0.5 on Ubuntu 12.04?  This smells like 
>>>>> a
>>>>> library compatibility issue or something similar to me...
>>>>> 
>>>>> Here's the relevant parts of the config files:
>>>>> 
>>>>> Director {                            # define myself
>>>>>        Name = DIRNAME.local-dir
>>>>>        DIRport = 9101                # where we listen for UA 
>>>>> connections
>>>>>        QueryFile = "/opt/bacula/scripts/query.sql"
>>>>>        WorkingDirectory = "/opt/bacula/working"
>>>>>        PidDirectory = "/opt/bacula/working"
>>>>>        Maximum Concurrent Jobs = 20
>>>>>        Password = "79gG9MACp9ZkQWoXSVxtOglRRxJL_hCuT"         # 
>>>>> Console password
>>>>>        Messages = Daemon
>>>>> }
>>>>> 
>>>>> Director {
>>>>>        Name = DIRNAME.local-dir
>>>>>        DIRport = 9101
>>>>>        address = DIRNAME.local
>>>>>        Password = "79gG9MACp9ZkQWoXSVxtOglRRxJL_hCuT"
>>>>> }
>>>>> 
>>>>> When I start the director with debug mode, I get:
>>>>> 
>>>>> /opt/bacula/bin/bacula-dir -c /opt/bacula/etc/bacula-dir.conf -d100 
>>>>> -f
>>>>> bacula-dir: dird.c:194-0 Debug level = 100
>>>>> bacula-dir: address_conf.c:264-0 Initaddr 0.0.0.0:9101
>>>>> bacula-dir: jcr.c:128-0 read_last_jobs seek to 192
>>>>> bacula-dir: jcr.c:135-0 Read num_items=0
>>>>> bacula-dir: dir_plugins.c:148-0 Load dir plugins
>>>>> bacula-dir: dir_plugins.c:150-0 No dir plugin dir!
>>>>> bacula-dir: mysql.c:697-0 db_init_database first time
>>>>> bacula-dir: mysql.c:165-0 mysql_init done
>>>>> bacula-dir: mysql.c:190-0 mysql_real_connect done
>>>>> bacula-dir: mysql.c:192-0 db_user=###### db_name=###### 
>>>>> db_password=######
>>>>> bacula-dir: mysql.c:215-0 opendb ref=1 connected=1 db=1129b20
>>>>> bacula-dir: mysql.c:237-0 closedb ref=0 connected=1 db=1129b20
>>>>> bacula-dir: mysql.c:244-0 close db=1129b20
>>>>> DIRNAME.local-dir: bnet_server.c:87-0 Addresses 0.0.0.0:9101
>>>>> DIRNAME.local-dir: job.c:1528-0 wstorage=File1
>>>>> DIRNAME.local-dir: job.c:1537-0 wstore=File1 where=Job resource
>>>>> DIRNAME.local-dir: job.c:1211-0 JobId=0 created
>>>>> Job=*JobMonitor*.2014-10-07_10.42.26_01
>>>>> DIRNAME.local-dir: bnet.c:566-0 who=client host=###.###.###.### 
>>>>> port=9101
>>>>> 
>>>>> bconsole -d100
>>>>> Connecting to Director DIRNAME.local:9101
>>>>> bconsole: bsock.c:208-0 Current ###.###.###.###:9101 All
>>>>> ###.###.###.###:9101
>>>>> bconsole: bsock.c:137-0 who=Director daemon host=DIRNAME.local 
>>>>> port=9101
>>>>> bconsole: bsock.c:310-0 OK connected to server  Director daemon
>>>>> DIRNAME.local:9101.
>>>>> Director authorization problem.
>>>>> Most likely the passwords do not agree.
>>>>> If you are using TLS, there may have been a certificate validation 
>>>>> error
>>>>> during the TLS handshake.
>>>>> Please see
>>>>> http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION00260000000000000000
>>>>> for help.
>>>>> 
>>> 
> 
> 
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS 
> Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users