Bacula-users

[Bacula-users] TR: Bacula not working after Ubuntu Server upgrade to 16.04.1

2016-09-07 08:30:27
Subject: [Bacula-users] TR: Bacula not working after Ubuntu Server upgrade to 16.04.1
From: "Marc Vanhoomissen" <veramtex AT veramtex DOT com>
To: <bacula-users AT lists.sourceforge DOT net>
Date: Wed, 7 Sep 2016 14:13:08 +0200

I have exactly the same problem and so far could not figure out what to do.  I have Ubuntu 16.04.1 LTS and Bacula 7.0.5.  I just ran an upgrade (do-release-upgrade).

 

One thing about the ‘bad; vendor preset’.  I think this is to interpret as ‘Vendor preset: enabled’, because I have seen the same information checking the status of other routines (apache2, apport, postfix,…). I have no idea why the ‘bad’ is there but all routines work. 

 

$systemctl status apache2

● apache2.service - LSB: Apache2 web server

   Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)

   Active: active (running) since mar 2016-09-06 02:11:57 CEST; 1 day 11h ago

     Docs: man:systemd-sysv-generator(8)

  Process: 2208 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCE                            SS)

 

$ systemctl status apport

 

● apport.service - LSB: automatic crash report generation

   Loaded: loaded (/etc/init.d/apport; bad; vendor preset: enabled)

   Active: active (exited) since mar 2016-09-06 02:11:43 CEST; 1 day 11h ago

     Docs: man:systemd-sysv-generator(8)

  Process: 2041 ExecStart=/etc/init.d/apport start (code=exited, status=0/SUCCESS)

 

 

I am also very confused by the change in the name between bacula-dir and bacula-director.  Which one is the right one?

 

Marc Vanhoomissen

Veramtex SA

 

De : Kyle Lampkin [mailto:admin AT hmsumc DOT org]
Envoyé : mardi 6 septembre 2016 22:21
À : bacula-users AT lists.sourceforge DOT net
Objet : [Bacula-users] Bacula not working after Ubuntu Server upgrade to 16.04.1

 

sudo systemctl restart bacula-dir
Failed to restart bacula-dir.service: Unit bacula-dir.service not found.

Running bacula-director starts correctly, although it gives this strange this strange Bad; vendor preset:

$ sudo systemctl restart bacula-director
$ sudo systemctl status bacula-director
● bacula-director.service - LSB: Start Bacula Director at boot time
   Loaded: loaded (/etc/init.d/bacula-director; bad; vendor preset: enabled)
   Active: active (exited) since lun 2016-08-22 15:15:45 CEST; 14s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 31465 ExecStop=/etc/init.d/bacula-director stop (code=exited, status=0/SUCCESS)
  Process: 31476 ExecStart=/etc/init.d/bacula-director start (code=exited, status=0/SUCCESS)
 
 22 15:15:45 servex systemd[1]: Stopped LSB: Start Bacula Director at boot time.
 22 15:15:45 servex systemd[1]: Starting LSB: Start Bacula Director at boot time...
 22 15:15:45 servex bacula-director[31476]:  * Starting Bacula Director... bacula-dir
 22 15:15:45 servex bacula-director[31476]:    ...done.
 22 15:15:45 servex systemd[1]: Started LSB: Start Bacula Director at boot time.

But I cannot use the console:

$ sudo bconsole
Connecting to Director localhost:9101
$
after a few minutes it goes back to system prompt, without any errors or entries in /var/log/bacula/bacula.log
 
-- 
Kyle Lampkin
Website & Communication Coordinator
Hamilton United Methodist Church
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
<Prev in Thread] Current Thread [Next in Thread>