Re: [Bacula-users] Failed to connect to Client -fd

2019-05-08 Thread Martin Simmons
The manual says that snapshot backups are supported in Bacula 7.2, but I've never tried them. __Martin > On Wed, 8 May 2019 17:56:22 +0530, preash raj said: > > Hi Martin, > > Thank you for pointing this out; it's fixed now, excellent! > > Just a heads up, can we create a snapshot backup

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-08 Thread preash raj
Hi Martin, Thank you for pointing this out; it's fixed now, excellent! Just a heads up, can we create a snapshot backup in Bacula? let me know if that works even in a upgraded version. On Fri, May 3, 2019 at 10:04 PM Martin Simmons wrote: > Yes, that's what I meant. > > It shows an error from

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-03 Thread Martin Simmons
Yes, that's what I meant. It shows an error from the remote fd: Connection from unknown Director bacula-dir at 109.73.166.242 rejected. It looks like the Director > Name in the bacula-fd.conf on the remote fd does not match the Director > Name in the bacula-dir.conf. __Martin > On Fri, 3

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-03 Thread preash raj
Hi Martin, >> while the bacula-dir and the remote bacula-fd were running with these command line args? You mean starting the bacula-dir in debug mode while I check the 'status client' in bconsole? It shows the below error while try to connect the clients using bconsole. the passwords looks fine,

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-02 Thread Martin Simmons
Did you run the failing bconsole command while the bacula-dir and the remote bacula-fd were running with these command line args? That should make it print more debug information for both of them. __Martin > On Thu, 2 May 2019 11:15:16 +0530, preash raj said: > > Hi Guys, > > I've tried d

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-02 Thread Alfred Weintoegl
Try: netstat -lnp |grep 910 (oder ss -lntp |less -S) ...should show on the Server something like: ... your ip-addr: 9101 ...LISTEN...(bacula-dir) ... 0.0.0.0:9102 ...LISTEN... (bacula-fd) ... 0.0.0.0:9103 ...LISTEN.. .(bacula-sd) and on the Client (at the other maschine): ... 0.0.0.0:9102

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-02 Thread Pieter Sybesma via Bacula-users
Maybe a silly question but do the addresses match at the client and director. Does the name client.hostname from client configuration resolve to the address of the client system? If its a different system the ditector cant connect to the file daemon. Plus is i rember correctly the file daemon sho

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-02 Thread preash raj
I've also tried debbuging bconsole too; please find the result attached. # bconsole -d 100 -dt Connecting to Director localhost:9101 02-May-2019 05:30:42 bconsole: bsock.c:236-0 Current host[ipv6:::1:9101] All host[ipv6:::1:9101] host[ipv4:127.0.0.1:65535] 02-May-2019 05:30:42 bconsole: bsock.c:23

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-01 Thread preash raj
Hi Guys, I've tried debugging after stopping the services, please check the server and client results below. Any clue? Bacula Server: = [root@bacula ~]# bacula-dir -f -d 100 bacula-dir: dird.c:223-0 Debug level = 100 bacula-dir: jcr.c:140-0 read_last_jobs seek to 192 bacula-dir: jcr.

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-01 Thread Martin Simmons
The output says: "bacula-dir is already running" -- you need to stop the existing process first. __Martin > On Wed, 1 May 2019 17:44:53 +0530, preash raj said: > > Hi, > > I've tried running the Bacula in debug mode and got the below results; I've > checked with the DB and make sure the pa

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-01 Thread preash raj
Hi, I've tried running the Bacula in debug mode and got the below results; I've checked with the DB and make sure the passwords are correct. Can you guys please guide me through this. The bacula files are located under /etc/bacula = [root@bacula]

Re: [Bacula-users] Failed to connect to Client -fd

2019-04-30 Thread Dimitri Maziuk via Bacula-users
On 4/30/19 11:42 AM, William Muriithi wrote: > Heitor, > > He is using Centos, and version 5.2.13 ended up being whats shipped by > RedHat. Very understandable > > Do you know why RedHat does ship something newer? Like even version 7? RedHat gets paid for supporting their customers. Presumably

Re: [Bacula-users] Failed to connect to Client -fd

2019-04-30 Thread William Muriithi
: preash raj Cc: bacula-users Subject: Re: [Bacula-users] Failed to connect to Client -fd Hello Preash, I strongly recommend using the newer 9.4.x versions from the Bacula.org project: http://bacula.us/script-installation-bacula-community-9-x-official-packages/ The 5.x versions do not really have

Re: [Bacula-users] Failed to connect to Client -fd

2019-04-30 Thread Heitor Faria
o: "bacula-users" > Sent: Tuesday, April 30, 2019 2:46:25 AM > Subject: [Bacula-users] Failed to connect to Client -fd > Hi, > I've installed and configured the free Bacula version 5.2.13, but I'm not able > to establish the connection with remote client the loca

Re: [Bacula-users] Failed to connect to Client -fd

2019-04-30 Thread Martin Simmons
Sorry, I don't know what other command line arguments your system needs. Use ps -efww | grep bacula to find the command lines for the current processes and add -f -d 100 to the end. __Martin > On Tue, 30 Apr 2019 19:04:55 +0530, preash raj said: > > Hi Martin, > > >> You could try runnin

Re: [Bacula-users] Failed to connect to Client -fd

2019-04-30 Thread preash raj
Hi Martin, >> You could try running the director and remote client with debug level 100 to print more information (add the command line arguments -f -d 100). Could you please let me know the exact full command for a debug run? On Tue, Apr 30, 2019 at 6:42 PM preash raj wrote: > Sure! will do.

Re: [Bacula-users] Failed to connect to Client -fd

2019-04-30 Thread Martin Simmons
> On Tue, 30 Apr 2019 11:16:25 +0530, preash raj said: > > Hi, > > I've installed and configured the free Bacula version 5.2.13, but I'm not > able to establish the connection with remote client the local backup works > fine. IP and port has been allowed in the firewall and telnet in both > m

[Bacula-users] Failed to connect to Client -fd

2019-04-29 Thread preash raj
Hi, I've installed and configured the free Bacula version 5.2.13, but I'm not able to establish the connection with remote client the local backup works fine. IP and port has been allowed in the firewall and telnet in both machines works fine. All the configurations are done as per the document: h