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

2016-09-07 Thread Kern Sibbald

  
  
Well, I am sorry, but if you upgrade
  from Ubuntu 14.04 and do not upgrade Bacula to one
  compiled to run on the new Ubuntu, there is little chance that the
  old version of Bacula
  will continue to work.  This is true of a lot of software.
  
  You should bring this problem up with Ubuntu to see what they
  recommend.
  
  Best regards,
  Kern
  
  
  On 09/07/2016 03:06 PM, Kyle Lampkin wrote:


  
  On 09/07/2016 06:25 AM, Kern Sibbald
wrote:
  
  

Where did you get the Bacula
  binaries and what version do you have?
  
  Kern
  
  On 09/06/2016 10:21 PM, Kyle Lampkin wrote:


  
  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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users




  
  
  Kern,
  The binaries were packaged for Ubuntu Server 14.04 and worked
flawlessly until the upgrade.The version was upgraded from
5.2.6+dfsg-9.1ubuntu3 to 7.0.5+dfsg-4build1 from the Ubuntu
packages for Server 16.04.1
  
  -- 
Kyle Lampkin
Website & Communication Coordinator
Hamilton United Methodist Church



  


--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


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

2016-09-07 Thread Marc Vanhoomissen
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/SUCCESS)

 

$ 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:ad...@hmsumc.org] 
Envoyé : mardi 6 septembre 2016 22:21
À : bacula-users@lists.sourceforge.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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


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

2016-09-07 Thread Kern Sibbald

  
  
Where did you get the Bacula binaries
  and what version do you have?
  
  Kern
  
  On 09/06/2016 10:21 PM, Kyle Lampkin wrote:


  
  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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users




  


--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Windows fd unable to communicate with linux sd

2016-09-07 Thread Hodges

Ralf,

Thanks for this idea. I have installed netcat on the windows box, and of 
course it is already on the linux box. Am struggling at the moment with 
how to use it, but will persvere


Steve


On 06/09/2016 12:13, Ralf Brinkmann wrote:

Am 06.09.2016 um 11:49 schrieb Hodges:

Anyway I set the firewall open to any machine on the local network when
I first hit the problem


hello Steve,

some years ago I made some tests with netcat to verify the network speed
between certain servers and the bacula host.

I'm not familiar with Bacula issues on Windows but there is a netcat
Windows version that might help:

https://joncraton.org/blog/46/netcat-for-windows/


 # netcat -h
[v1.10]
connect to somewhere:   netcat [-options] hostname port[s] [ports] ...
listen for inbound: netcat -l -p port [-options] [hostname] [port]
options:
-g gateway  source-routing hop point[s], up to 8
-G num  source-routing pointer: 4, 8, 12, ...
-h  this cruft
 -i secs delay interval for lines sent, ports 
scanned

-l  listen mode, for inbound connects
-n  numeric-only IP addresses, no DNS
-o file hex dump of traffic
-p port local port number
-r  randomize local and remote ports
-s addr local source address
-t  answer TELNET negotiation
-u  UDP mode
-v  verbose [use twice to be more verbose]
-w secs timeout for connects and final net reads
-z  zero-I/O mode [used for scanning]
port numbers can be individual or ranges: lo-hi [inclusive]




--
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users