backup.pl | simple backup script for backing up data on one Linux server | Continuous Backup library

I've taken a look to many different topics and did not find an answer to my problem. I created 2 bash scripts on my Ubuntu server and I'm trying to execute them periodically. It seems they are running, but they produce nothing. They are executable:

I have spent two days now trying to get Bacula running again after upgrading from Ubuntu 14 to Ubuntu 16.04, but I am out of luck and need help.

Since the version of Bacula changed, I decided to start from scratch with the Ubuntu default config files and moved the old config files into a different folder. The apt installer/package-configurator properly fills out all the daemon-names and passwords in bacula-dir.conf, bacula-fs.conf and bacula-ds.conf

The problem: Bacula-dir does not start properly and seems to hang. The symptoms are:

1. No log file is created (/var/log/bacula/bacular.log)
2. bconsole connection fails (with error:

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.

However I have checked the passwords which have been created by the Ubuntu install/configuration script an they match.

After adding the line "local bacula bacula md5" to /etc/postgresql/9.5/main/pg_hba.conf access to the postgresql database works from the commmand-line ($ psql -d bacula -U bacula) using the same password as given in bacula-dir.conf.

What is most puzzling: I tried the same installation/configuration steps on another testing machine and there all is working as expected and I can connect with bconsole.

On my upgraded server however I can not find what causes the problem!

So far I have tried the following:

1. Completely purged all Bacula packages, then manually searched and removed all old configuration/log/run files in /etc/bacula/ and /var/ and then re-installed the packages
2. Downloaded the scripts drop_postgresql_tables and make_postgresql_tables from the Bacula source package and deleted and re-created the database tables with them
3. Used $ ps aux | grep bacula to list the running Bacula daemons and compare them with the test machine
4. Run bacula-dir with debug-option (-d 200) - please see the attached output
5. Checked file/folder permissions over and over again and compared with the working test machine
6. Firewall? All connections are on the same machine, so that shouldn't be the cause?

Question: What could possibly be wrong with my configuration? How can I narrow-down or isolate the problem?

Last thing I should mention: Bacula was used with mysql before and now after the upgrade to Ubuntu 16, PostgreSQL is used. All old Bacula packages were remove (purged) and the bacula...-mysql packages were replaced the with bacula-common-pgsql, bacula-director-pgsql and bacula-sd-pgsql. Also the database was started from scratch, but could that still somehow be the cause?

Bacula-dir debug output in syslog: