Re: [Bacula-users] Could not connect to Storage daemon

On 10/9/14, 9:53 AM, Ana Emília M. Arruda wrote: > Hi David, > > Could you clarify some points? > > 1) your storage daemon is running on backups.networktest.com:9103 > .? > 2) who is listening on the 3 ports bellow? > $ sudo netstat -an -f inet | grep 910 > tc

Re: [Bacula-users] Could not connect to Storage daemon

Hi David, Could you clarify some points? 1) your storage daemon is running on backups.networktest.com:9103.? 2) who is listening on the 3 ports bellow? $ sudo netstat -an -f inet | grep 910 tcp4 0 0 *.9102 *.*LISTEN tcp4 0 0 *.9103

Re: [Bacula-users] Could not connect to Storage daemon

> On Tue, 07 Oct 2014 09:56:43 -0700, David Newman said: > > On 10/6/14, 9:20 PM, David Newman wrote: > > On 10/3/14, 7:47 AM, Ana Emília M. Arruda wrote: > >> Hi David, > >> > >> Have you tried to schedule the job at another time? Just for checking if > >> the problem is at the scheduled time

Re: [Bacula-users] Could not connect to Storage daemon

On 10/6/14, 9:20 PM, David Newman wrote: > On 10/3/14, 7:47 AM, Ana Emília M. Arruda wrote: >> Hi David, >> >> Have you tried to schedule the job at another time? Just for checking if >> the problem is at the scheduled time you're trying to run the job or not. > > Great question. First time I trie

Re: [Bacula-users] Could not connect to Storage daemon

On 10/3/14, 7:47 AM, Ana Emília M. Arruda wrote: > Hi David, > > Have you tried to schedule the job at another time? Just for checking if > the problem is at the scheduled time you're trying to run the job or not. Great question. First time I tried this, it failed. Also, bconsole could not connec

Re: [Bacula-users] Could not connect to Storage daemon

Hi David, Have you tried to schedule the job at another time? Just for checking if the problem is at the scheduled time you're trying to run the job or not. Regards, Ana On Fri, Oct 3, 2014 at 11:07 AM, David Newman wrote: > On 10/2/14, 8:03 PM, Ana Emília M. Arruda wrote: > > > Hi David, > >

Re: [Bacula-users] Could not connect to Storage daemon

> > > - the Bacula server can telnet to the backups.networktest.com > > address on > > port 9103. Just an observation, Mr. David: keep in mind that not only the Bacula Director machine needs to access the storage daemon one, port 9103 but also every ot

Re: [Bacula-users] Could not connect to Storage daemon

On 10/2/14, 8:03 PM, Ana Emília M. Arruda wrote: > Hi David, > > Have you checked about scheduled events that could be leading your > bacula-sd host unavailable at that time? Some kind of outage? Hi Ana, As far as I know there's no other service doing anything with bacula-sd. The same setup wor

Re: [Bacula-users] Could not connect to Storage daemon

Hi David, Have you checked about scheduled events that could be leading your bacula-sd host unavailable at that time? Some kind of outage? Regards, Ana On Thu, Oct 2, 2014 at 2:01 PM, David Newman wrote: > Bacula 5.2.12 installed as a pkg on FreeBSD 10.0-RELEASE-p9 > > Nightly backups fail wit

[Bacula-users] Could not connect to Storage daemon

Bacula 5.2.12 installed as a pkg on FreeBSD 10.0-RELEASE-p9 Nightly backups fail with "Connection refused" errors like those pasted below. However: - backups succeed when run manually from bconsole; and - the Bacula server can telnet to the backups.networktest.com address on port 9103. I've al

Re: [Bacula-users] Could not connect to Storage daemon on Bacula:9103. ERR=Connection refused

I agree. Probably will either be the fqdn of the server not being bacula. If this is coming from a remote host trying to backup to the server, might need to add the name bacula with its ip into the host file linux: /etc/host Windows: C:\WINDOWS\system32\drivers\etc\hosts Possibly an IPTables / f

Re: [Bacula-users] Could not connect to Storage daemon on Bacula:9103. ERR=Connection refused

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 mcodo wrote: > Hi. > I have set up a Ubuntu server with Bacula and Bacula-Webmin > It looks like things are working but when i start a job on the server I get > an error saying: > Could not connect to Storage daemon on Bacula:9103. ERR=Connection refu

[Bacula-users] Could not connect to Storage daemon on Bacula:9103. ERR=Connection refused

Hi. I have set up a Ubuntu server with Bacula and Bacula-Webmin It looks like things are working but when i start a job on the server I get an error saying: Could not connect to Storage daemon on Bacula:9103. ERR=Connection refused I know bacula-fd and bacula-sd and bacula-director is running: [

Re: [Bacula-users] Could not connect to Storage daemon - ERR=No error

> Unfortunately, the error message here is probably incorrect because at that > low level, it doesn't know about Win32. As a consequence, it is most likely > that packrat is not properly defined on jeff-t40-fd. > Ahhh so different socket API errors for TCP sockets? Different firewalls return

Re: [Bacula-users] Could not connect to Storage daemon - ERR=No error

On Saturday 17 March 2007 02:29, Jeff Dickens wrote: > I'm testing a new bacula server, running 2.0.3 installed from the el4 > rpm from sourceforge. > > My client is running WinXP, with the 2.0.3 winbacula from sourceforge. > > The client and the server both have each other's addresses in their

Re: [Bacula-users] Could not connect to Storage daemon - ERR=No error

Ralf Gross wrote: Jeff Dickens schrieb: [snip] *m 16-Mar 21:25 jeff-t40-fd: jeff-t40.2007-03-16_21.24.41 Warning: ../../lib/bnet.c:864 Could not connect to Storage daemon on packrat:9103. ERR=No error Retrying ... * The server just sits there like this: Running Jobs: JobId Level Name

Re: [Bacula-users] Could not connect to Storage daemon - ERR=No error

Jeff Dickens schrieb: [snip] > *m > 16-Mar 21:25 jeff-t40-fd: jeff-t40.2007-03-16_21.24.41 Warning: > ../../lib/bnet.c:864 Could not connect to Storage daemon on > packrat:9103. ERR=No error > Retrying ... > * > > The server just sits there like this: > > Running Jobs: > JobId Level Name

[Bacula-users] Could not connect to Storage daemon - ERR=No error

I'm testing a new bacula server, running 2.0.3 installed from the el4 rpm from sourceforge. My client is running WinXP, with the 2.0.3 winbacula from sourceforge. The client and the server both have each other's addresses in their hosts files, to rule out dns issues while I'm testing. I'm usi

Re: [Bacula-users] Could not connect to Storage daemon on bacula:9103. ERR=Operation not permitted

Georg Altmann skrev: > > > --On Donnerstag, 7. Dezember 2006 15:28 +0100 Jon Ingason > <[EMAIL PROTECTED]> wrote: > >> I have installed new bacula server 1.38.11 on debian testing/unstable >> runnig on PC and one of the clients, running on FreeBSD 6.1 version >> 1.38.5_1, is giving me problem: >

Re: [Bacula-users] Could not connect to Storage daemon on bacula:9103. ERR=Operation not permitted

I think this may be a permission problem. Check your permissions on both sides. ZK --- Jon Ingason <[EMAIL PROTECTED]> wrote: > I have installed new bacula server 1.38.11 on debian > testing/unstable > runnig on PC and one of the clients, running on > FreeBSD 6.1 version > 1.38.5_1, is giving

Re: [Bacula-users] Could not connect to Storage daemon on bacula:9103. ERR=Operation not permitted

--On Donnerstag, 7. Dezember 2006 15:28 +0100 Jon Ingason <[EMAIL PROTECTED]> wrote: > I have installed new bacula server 1.38.11 on debian testing/unstable > runnig on PC and one of the clients, running on FreeBSD 6.1 version > 1.38.5_1, is giving me problem: > > run job="client-100" fileset="

[Bacula-users] Could not connect to Storage daemon on bacula:9103. ERR=Operation not permitted

I have installed new bacula server 1.38.11 on debian testing/unstable runnig on PC and one of the clients, running on FreeBSD 6.1 version 1.38.5_1, is giving me problem: run job="client-100" fileset="client File Set" level=Incremental client="client-100-fd" pool="client-100" when="2006-12-07 12:59

Re: [Bacula-users] Could not connect to Storage

Hi Landon, I haven't experienced any problem yet. Could you please tell me any examples? A. >On Jan 16, 2006, at 8:12 AM, Andras Horvai wrote: > >>Hi Jari, >> >>Thanks for your answer, but the firewall was the problem. > >Your next problem will be that 1.36 and 1.38 are not compatible. =) > >-

Re: [Bacula-users] Could not connect to Storage

On Jan 16, 2006, at 8:12 AM, Andras Horvai wrote: Hi Jari, Thanks for your answer, but the firewall was the problem. Your next problem will be that 1.36 and 1.38 are not compatible. =) -landonf PGP.sig Description: This is a digitally signed message part

Re: [Bacula-users] Could not connect to Storage

Hi Jari, Thanks for your answer, but the firewall was the problem. A. >Andras Horvai wrote: >>Linux bacula 2.6.8-11-amd64-k8 #1 Wed Jun 1 01:03:08 CEST 2005 x86_64 >>GNU/Linux bacula-1.36.3 >>File daemon's version on the windows server is: 1.38.3 > >1.36 and 1.38 are not propably compatible enou

Re: [Bacula-users] Could not connect to Storage

Andras Horvai wrote: Linux bacula 2.6.8-11-amd64-k8 #1 Wed Jun 1 01:03:08 CEST 2005 x86_64 GNU/Linux bacula-1.36.3 File daemon's version on the windows server is: 1.38.3 1.36 and 1.38 are not propably compatible enough. --- This SF.net

[Bacula-users] Could not connect to Storage

Hi All, I'm new in the list. Here is the details: Linux bacula 2.6.8-11-amd64-k8 #1 Wed Jun 1 01:03:08 CEST 2005 x86_64 GNU/Linux bacula-1.36.3 File daemon's version on the windows server is: 1.38.3 The problem is this: I added 6 more pools. There is only one volume in each pool. And when the