Comment 1 for bug 1553563

The only (debug) message I got from the Director upon an unsuccessful bconsole connection was the one produced in lib/bnet.c:566. So I debugged it and got this backtrace:

#0 init_bsock (jcr=jcr@entry=0x0, sockfd=sockfd@entry=7, who=who@entry=0x7efce66e958b "client",
    host=host@entry=0x7efce32b1320 "127.0.0.1", port=9101, client_addr=client_addr@entry=0x7efce32b0eb0) at bnet.c:565
#1 0x00007efce66b605e in bnet_thread_server (addr_list=addr_list@entry=0x20a65d8, max_clients=0,
    client_wq=client_wq@entry=0x688960 <ua_workq>,
    handle_client_request=handle_client_request@entry=0x4534b0 <handle_UA_client_request(void*)>) at bnet_server.c:222
#2 0x000000000045312c in connect_thread (arg=arg@entry=0x20a65d8) at ua_server.c:69
#3 0x00007efce66e6bdf in lmgr_thread_launcher (x=0x2108498) at lockmgr.c:1091
#4 0x00007efce648966a in start_thread (arg=0x7efce32b2700) at pthread_create.c:333
#5 0x00007efce5e3d01d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

It is strange, that bnet_thread_server() had been called with max_clients=0. In the calling location in dird/ua_server.c:69 "director->MaxConsoleConnect" is used as a parameter. "MaximumConsoleConnections" seems to be the according Director resource configuration variable (bacula-dir.conf) and it was not present in my configuration. While the documentation at http://www.bacula.org/7.0.x-manuals/en/main/Configuring_Director.html#SECTION001520000000000000000 clearly states a default value of 20, bconsole connections suddenly worked after explicitly setting it.

Further problems were an empty scheduled job list and manually started backup jobs just "waiting on max Client jobs". To get Bacula basically working on Xenial it seems, that at least the following configuration variables of bacula-dir.conf need explicit statements:

- In the Director resource:
  MaximumConsoleConnections
- In the Job resources:
  Enabled
- In the Client resources:
  Maximum Concurrent Jobs