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

2014-10-15 Thread David Newman 
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
> tcp4   0  0 *.9102 *.*LISTEN
> tcp4   0  0 *.9103 *.*LISTEN
> tcp4   0  0 *.9101 *.*LISTEN
> 3) are your director and storage at the same host?
> 4) all the failed jobs presents the same connection error?
> 02-Oct 00:45 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
> to Storage daemon on backups.networktest.com:9103
> . ERR=Connection refused
> Retrying ...
> 
> It seems to me you have some networking problems

Thanks to Ana and Martin Simmons for helping find the root problem:
expired DNSSEC keys.

Fixing the DNSSEC issue got bacula working again.

Thanks again for your help!

dn

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2014-10-09 Thread Ana Emília M . Arruda 
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 *.*LISTEN
tcp4   0  0 *.9101 *.*LISTEN
3) are your director and storage at the same host?
4) all the failed jobs presents the same connection error?
02-Oct 00:45 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
to Storage daemon on backups.networktest.com:9103. ERR=Connection refused
Retrying ...

It seems to me you have some networking problems

Regards,
Ana

On Tue, Oct 7, 2014 at 1:56 PM, David Newman 
wrote:

> 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 tried this, it failed. Also, bconsole could
> > not connect.
> >
> > After a reboot, the rescheduled incremental backup worked for the first
> > few hosts. It's still running.
> >
> > When it's done, I'll change bacula-dir.conf back to the original time,
> > restart everything, and report back.
>
> An update: Incremental jobs for some (not all) of the hosts completed
> successfully after changing the start time in bacula-dir.conf. I do not
> see a pattern as to which ones failed or succeeded.
>
> After changing back to the original time and restarting via the
> bacula-dir script, all incremental jobs failed. The netstat utility says
> the backup machine is listening on ports 910[1-3]:
>
> $ sudo netstat -an -f inet | grep 910
> tcp4   0  0 *.9102 *.*LISTEN
> tcp4   0  0 *.9103 *.*LISTEN
> tcp4   0  0 *.9101 *.*LISTEN
>
> Thanks in advance for additional troubleshooting skills.
>
> dn
>
>
> >
> > dn
> >
> >
> >
> >>
> >> 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,
> >> >
> >> > 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 worked for years with FreeBSD 8.x and 9.x; the only
> >> difference is that it doesn't work with FreeBSD 10.x.
> >>
> >> Puzzling that manual backups work, but automated ones don't.
> >>
> >> dn
> >>
> >>
> >> >
> >> > Regards,
> >> > Ana
> >> >
> >> > On Thu, Oct 2, 2014 at 2:01 PM, David Newman <
> dnew...@networktest.com 
> >> > >>
> wrote:
> >> >
> >> > 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 also pasted the Schedule sections from bacula-dir.conf.
> >> >
> >> > Thanks in advance for troubleshooting clues.
> >> >
> >> > dn
> >> >
> >> >
> >> >
> >> > 02-Oct 00:35 nye-dir JobId 20983: Start Backup JobId 20983,
> >> > Job=ca.2014-10-01_23.05.00_04
> >> > 02-Oct 00:35 nye-dir JobId 20983: Warning: bsock.c:132 Could
> not connect
> >> > to Storage daemon on backups.networktest.com:9103 <
> http://backups.networktest.com:9103>
> >> > . ERR=Connection refused
> >> > Retrying ...
> >> > 02-Oct 00:40 nye-dir JobId 20983: Warning: bsock.c:132 Could
> not connect
> >> > to Storage daemon on backups.networktest.com:9103 <
> http://backups.networktest.com:9103>
> >> > . ERR=Connection refused
> >> > Retrying ...
> >> > 02-Oct 00:45 nye-dir JobId 20983: Warning: bsock.c:132 Could
> not connect
> >> > to Storage daemon on backups.networktest.com:9103 <
> http://backups.networktest.com:9103>
> >> > . ERR=Connection refused
> >> > Retrying ...
> >> > 02-Oct 00:50 nye-dir JobId 20983: Warning: b

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

2014-10-09 Thread Martin Simmons 
> 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 you're trying to run the job or not.
> > 
> > Great question. First time I tried this, it failed. Also, bconsole could
> > not connect.
> > 
> > After a reboot, the rescheduled incremental backup worked for the first
> > few hosts. It's still running.
> > 
> > When it's done, I'll change bacula-dir.conf back to the original time,
> > restart everything, and report back.
> 
> An update: Incremental jobs for some (not all) of the hosts completed
> successfully after changing the start time in bacula-dir.conf. I do not
> see a pattern as to which ones failed or succeeded.
> 
> After changing back to the original time and restarting via the
> bacula-dir script, all incremental jobs failed. The netstat utility says
> the backup machine is listening on ports 910[1-3]:
> 
> $ sudo netstat -an -f inet | grep 910
> tcp4   0  0 *.9102 *.*LISTEN
> tcp4   0  0 *.9103 *.*LISTEN
> tcp4   0  0 *.9101 *.*LISTEN
> 
> Thanks in advance for additional troubleshooting skills.

You could test the connectivity at regular intervals throughout the day using
a cron job to run nc:

nc -v -z backups.networktest.com 9103

__Martin


> 
> dn
> 
> 
> > 
> > dn
> > 
> > 
> > 
> >>
> >> 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,
> >> >
> >> > 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 worked for years with FreeBSD 8.x and 9.x; the only
> >> difference is that it doesn't work with FreeBSD 10.x.
> >>
> >> Puzzling that manual backups work, but automated ones don't.
> >>
> >> dn
> >>
> >>
> >> >
> >> > Regards,
> >> > Ana
> >> >
> >> > On Thu, Oct 2, 2014 at 2:01 PM, David Newman 
> >> mailto:dnew...@networktest.com>
> >> > >> 
> >> wrote:
> >> >
> >> > 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 also pasted the Schedule sections from bacula-dir.conf.
> >> >
> >> > Thanks in advance for troubleshooting clues.
> >> >
> >> > dn
> >> >
> >> >
> >> >
> >> > 02-Oct 00:35 nye-dir JobId 20983: Start Backup JobId 20983,
> >> > Job=ca.2014-10-01_23.05.00_04
> >> > 02-Oct 00:35 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
> >> connect
> >> > to Storage daemon on backups.networktest.com:9103 
> >> 
> >> > . ERR=Connection refused
> >> > Retrying ...
> >> > 02-Oct 00:40 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
> >> connect
> >> > to Storage daemon on backups.networktest.com:9103 
> >> 
> >> > . ERR=Connection refused
> >> > Retrying ...
> >> > 02-Oct 00:45 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
> >> connect
> >> > to Storage daemon on backups.networktest.com:9103 
> >> 
> >> > . ERR=Connection refused
> >> > Retrying ...
> >> > 02-Oct 00:50 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
> >> connect
> >> > to Storage daemon on backups.networktest.com:9103 
> >> 
> >> > . ERR=Connection refused
> >> > Retrying ...
> >> > 02-Oct 00:56 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
> >> connect
> >> > to Storage daemon on backups.networktest.com:9103 
> >> 
> >> > . ERR=Connection refused
> >> > Retrying ...
> >>

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

2014-10-07 Thread David Newman 
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 tried this, it failed. Also, bconsole could
> not connect.
> 
> After a reboot, the rescheduled incremental backup worked for the first
> few hosts. It's still running.
> 
> When it's done, I'll change bacula-dir.conf back to the original time,
> restart everything, and report back.

An update: Incremental jobs for some (not all) of the hosts completed
successfully after changing the start time in bacula-dir.conf. I do not
see a pattern as to which ones failed or succeeded.

After changing back to the original time and restarting via the
bacula-dir script, all incremental jobs failed. The netstat utility says
the backup machine is listening on ports 910[1-3]:

$ sudo netstat -an -f inet | grep 910
tcp4   0  0 *.9102 *.*LISTEN
tcp4   0  0 *.9103 *.*LISTEN
tcp4   0  0 *.9101 *.*LISTEN

Thanks in advance for additional troubleshooting skills.

dn


> 
> dn
> 
> 
> 
>>
>> 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,
>> >
>> > 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 worked for years with FreeBSD 8.x and 9.x; the only
>> difference is that it doesn't work with FreeBSD 10.x.
>>
>> Puzzling that manual backups work, but automated ones don't.
>>
>> dn
>>
>>
>> >
>> > 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 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 also pasted the Schedule sections from bacula-dir.conf.
>> >
>> > Thanks in advance for troubleshooting clues.
>> >
>> > dn
>> >
>> >
>> >
>> > 02-Oct 00:35 nye-dir JobId 20983: Start Backup JobId 20983,
>> > Job=ca.2014-10-01_23.05.00_04
>> > 02-Oct 00:35 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
>> connect
>> > to Storage daemon on backups.networktest.com:9103 
>> 
>> > . ERR=Connection refused
>> > Retrying ...
>> > 02-Oct 00:40 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
>> connect
>> > to Storage daemon on backups.networktest.com:9103 
>> 
>> > . ERR=Connection refused
>> > Retrying ...
>> > 02-Oct 00:45 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
>> connect
>> > to Storage daemon on backups.networktest.com:9103 
>> 
>> > . ERR=Connection refused
>> > Retrying ...
>> > 02-Oct 00:50 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
>> connect
>> > to Storage daemon on backups.networktest.com:9103 
>> 
>> > . ERR=Connection refused
>> > Retrying ...
>> > 02-Oct 00:56 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
>> connect
>> > to Storage daemon on backups.networktest.com:9103 
>> 
>> > . ERR=Connection refused
>> > Retrying ...
>> > 02-Oct 01:01 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
>> connect
>> > to Storage daemon on backups.networktest.com:9103 
>> 
>> > . ERR=Connection refused
>> > Retrying ...
>> > 02-Oct 01:05 nye-dir JobId 20983: Fatal error: bsock.c:138 Unable 
>> to
>> > connect to Storage daemon on backups.networktest.com:9103 
>>

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

2014-10-06 Thread David Newman 
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 connect.

After a reboot, the rescheduled incremental backup worked for the first
few hosts. It's still running.

When it's done, I'll change bacula-dir.conf back to the original time,
restart everything, and report back.

dn



> 
> 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,
> >
> > 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 worked for years with FreeBSD 8.x and 9.x; the only
> difference is that it doesn't work with FreeBSD 10.x.
> 
> Puzzling that manual backups work, but automated ones don't.
> 
> dn
> 
> 
> >
> > 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 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 also pasted the Schedule sections from bacula-dir.conf.
> >
> > Thanks in advance for troubleshooting clues.
> >
> > dn
> >
> >
> >
> > 02-Oct 00:35 nye-dir JobId 20983: Start Backup JobId 20983,
> > Job=ca.2014-10-01_23.05.00_04
> > 02-Oct 00:35 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
> connect
> > to Storage daemon on backups.networktest.com:9103 
> 
> > . ERR=Connection refused
> > Retrying ...
> > 02-Oct 00:40 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
> connect
> > to Storage daemon on backups.networktest.com:9103 
> 
> > . ERR=Connection refused
> > Retrying ...
> > 02-Oct 00:45 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
> connect
> > to Storage daemon on backups.networktest.com:9103 
> 
> > . ERR=Connection refused
> > Retrying ...
> > 02-Oct 00:50 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
> connect
> > to Storage daemon on backups.networktest.com:9103 
> 
> > . ERR=Connection refused
> > Retrying ...
> > 02-Oct 00:56 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
> connect
> > to Storage daemon on backups.networktest.com:9103 
> 
> > . ERR=Connection refused
> > Retrying ...
> > 02-Oct 01:01 nye-dir JobId 20983: Warning: bsock.c:132 Could not 
> connect
> > to Storage daemon on backups.networktest.com:9103 
> 
> > . ERR=Connection refused
> > Retrying ...
> > 02-Oct 01:05 nye-dir JobId 20983: Fatal error: bsock.c:138 Unable to
> > connect to Storage daemon on backups.networktest.com:9103 
> 
> > .
> > ERR=Connection refused
> >
> >
> >
> > # List of files to be backed up
> > # When to do the backups, full backup on first sunday of the month,
> > #  differential (i.e. incremental since full) every other sunday,
> > #  and incremental backups other days
> > Schedule {
> >   Name = "WeeklyCycle"
> >   Run = Full 1st sun at 23:05
> >   Run = Differential 2nd-5th sun at 23:05
> >   Run = Incremental mon-sat at 23:05
> > }
> >
> > # This schedule does the catalog. It starts after the WeeklyCycle
> > Schedule {
> >   Name = "WeeklyCycleAfterBackup"
> >   Run = Full sun-sat at 23:55
> > }
> >
> >
> > 
>

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

2014-10-03 Thread Ana Emília M . Arruda 
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,
> >
> > 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 worked for years with FreeBSD 8.x and 9.x; the only
> difference is that it doesn't work with FreeBSD 10.x.
>
> Puzzling that manual backups work, but automated ones don't.
>
> dn
>
>
> >
> > 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 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 also pasted the Schedule sections from bacula-dir.conf.
> >
> > Thanks in advance for troubleshooting clues.
> >
> > dn
> >
> >
> >
> > 02-Oct 00:35 nye-dir JobId 20983: Start Backup JobId 20983,
> > Job=ca.2014-10-01_23.05.00_04
> > 02-Oct 00:35 nye-dir JobId 20983: Warning: bsock.c:132 Could not
> connect
> > to Storage daemon on backups.networktest.com:9103
> > . ERR=Connection refused
> > Retrying ...
> > 02-Oct 00:40 nye-dir JobId 20983: Warning: bsock.c:132 Could not
> connect
> > to Storage daemon on backups.networktest.com:9103
> > . ERR=Connection refused
> > Retrying ...
> > 02-Oct 00:45 nye-dir JobId 20983: Warning: bsock.c:132 Could not
> connect
> > to Storage daemon on backups.networktest.com:9103
> > . ERR=Connection refused
> > Retrying ...
> > 02-Oct 00:50 nye-dir JobId 20983: Warning: bsock.c:132 Could not
> connect
> > to Storage daemon on backups.networktest.com:9103
> > . ERR=Connection refused
> > Retrying ...
> > 02-Oct 00:56 nye-dir JobId 20983: Warning: bsock.c:132 Could not
> connect
> > to Storage daemon on backups.networktest.com:9103
> > . ERR=Connection refused
> > Retrying ...
> > 02-Oct 01:01 nye-dir JobId 20983: Warning: bsock.c:132 Could not
> connect
> > to Storage daemon on backups.networktest.com:9103
> > . ERR=Connection refused
> > Retrying ...
> > 02-Oct 01:05 nye-dir JobId 20983: Fatal error: bsock.c:138 Unable to
> > connect to Storage daemon on backups.networktest.com:9103
> > .
> > ERR=Connection refused
> >
> >
> >
> > # List of files to be backed up
> > # When to do the backups, full backup on first sunday of the month,
> > #  differential (i.e. incremental since full) every other sunday,
> > #  and incremental backups other days
> > Schedule {
> >   Name = "WeeklyCycle"
> >   Run = Full 1st sun at 23:05
> >   Run = Differential 2nd-5th sun at 23:05
> >   Run = Incremental mon-sat at 23:05
> > }
> >
> > # This schedule does the catalog. It starts after the WeeklyCycle
> > Schedule {
> >   Name = "WeeklyCycleAfterBackup"
> >   Run = Full sun-sat at 23:55
> > }
> >
> >
> >
>  
> --
> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
> Reports
> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> > ___
> > Bacula-users mailing list
> > Bacula-users@lists.sourceforge.net
> > 
> > https://lists.sourceforge.net/lists/listinfo/bacula-users
> >
> >
>
>
> --
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> __

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

2014-10-03 Thread Heitor Faria 
>
> > - 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 other client machine, so you may want to make your scope test larger.

Regards,
-- 

Heitor Medrado de Faria
Precisa de treinamento Bacula? 15% de desconto no curso on-line pelo site:
bacula.com.br 
Need Bacula training? 10% discount coupon code at Udemy: bacula-users

+55 61 2021-8260
+55 61 8268-4220
Site: www.bacula.com.br
Facebook: heitor.faria 
Gtalk: heitorfa...@gmail.com

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2014-10-03 Thread David Newman 
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 worked for years with FreeBSD 8.x and 9.x; the only
difference is that it doesn't work with FreeBSD 10.x.

Puzzling that manual backups work, but automated ones don't.

dn


> 
> 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 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 also pasted the Schedule sections from bacula-dir.conf.
> 
> Thanks in advance for troubleshooting clues.
> 
> dn
> 
> 
> 
> 02-Oct 00:35 nye-dir JobId 20983: Start Backup JobId 20983,
> Job=ca.2014-10-01_23.05.00_04
> 02-Oct 00:35 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
> to Storage daemon on backups.networktest.com:9103
> . ERR=Connection refused
> Retrying ...
> 02-Oct 00:40 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
> to Storage daemon on backups.networktest.com:9103
> . ERR=Connection refused
> Retrying ...
> 02-Oct 00:45 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
> to Storage daemon on backups.networktest.com:9103
> . ERR=Connection refused
> Retrying ...
> 02-Oct 00:50 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
> to Storage daemon on backups.networktest.com:9103
> . ERR=Connection refused
> Retrying ...
> 02-Oct 00:56 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
> to Storage daemon on backups.networktest.com:9103
> . ERR=Connection refused
> Retrying ...
> 02-Oct 01:01 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
> to Storage daemon on backups.networktest.com:9103
> . ERR=Connection refused
> Retrying ...
> 02-Oct 01:05 nye-dir JobId 20983: Fatal error: bsock.c:138 Unable to
> connect to Storage daemon on backups.networktest.com:9103
> .
> ERR=Connection refused
> 
> 
> 
> # List of files to be backed up
> # When to do the backups, full backup on first sunday of the month,
> #  differential (i.e. incremental since full) every other sunday,
> #  and incremental backups other days
> Schedule {
>   Name = "WeeklyCycle"
>   Run = Full 1st sun at 23:05
>   Run = Differential 2nd-5th sun at 23:05
>   Run = Incremental mon-sat at 23:05
> }
> 
> # This schedule does the catalog. It starts after the WeeklyCycle
> Schedule {
>   Name = "WeeklyCycleAfterBackup"
>   Run = Full sun-sat at 23:55
> }
> 
> 
> 
> --
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> 
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> 
> https://lists.sourceforge.net/lists/listinfo/bacula-users
> 
> 

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2014-10-02 Thread Ana Emília M . Arruda 
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 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 also pasted the Schedule sections from bacula-dir.conf.
>
> Thanks in advance for troubleshooting clues.
>
> dn
>
>
>
> 02-Oct 00:35 nye-dir JobId 20983: Start Backup JobId 20983,
> Job=ca.2014-10-01_23.05.00_04
> 02-Oct 00:35 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
> to Storage daemon on backups.networktest.com:9103. ERR=Connection refused
> Retrying ...
> 02-Oct 00:40 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
> to Storage daemon on backups.networktest.com:9103. ERR=Connection refused
> Retrying ...
> 02-Oct 00:45 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
> to Storage daemon on backups.networktest.com:9103. ERR=Connection refused
> Retrying ...
> 02-Oct 00:50 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
> to Storage daemon on backups.networktest.com:9103. ERR=Connection refused
> Retrying ...
> 02-Oct 00:56 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
> to Storage daemon on backups.networktest.com:9103. ERR=Connection refused
> Retrying ...
> 02-Oct 01:01 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
> to Storage daemon on backups.networktest.com:9103. ERR=Connection refused
> Retrying ...
> 02-Oct 01:05 nye-dir JobId 20983: Fatal error: bsock.c:138 Unable to
> connect to Storage daemon on backups.networktest.com:9103.
> ERR=Connection refused
>
>
>
> # List of files to be backed up
> # When to do the backups, full backup on first sunday of the month,
> #  differential (i.e. incremental since full) every other sunday,
> #  and incremental backups other days
> Schedule {
>   Name = "WeeklyCycle"
>   Run = Full 1st sun at 23:05
>   Run = Differential 2nd-5th sun at 23:05
>   Run = Incremental mon-sat at 23:05
> }
>
> # This schedule does the catalog. It starts after the WeeklyCycle
> Schedule {
>   Name = "WeeklyCycleAfterBackup"
>   Run = Full sun-sat at 23:55
> }
>
>
>
> --
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Could not connect to Storage daemon

2014-10-02 Thread David Newman 
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 also pasted the Schedule sections from bacula-dir.conf.

Thanks in advance for troubleshooting clues.

dn



02-Oct 00:35 nye-dir JobId 20983: Start Backup JobId 20983,
Job=ca.2014-10-01_23.05.00_04
02-Oct 00:35 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
to Storage daemon on backups.networktest.com:9103. ERR=Connection refused
Retrying ...
02-Oct 00:40 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
to Storage daemon on backups.networktest.com:9103. ERR=Connection refused
Retrying ...
02-Oct 00:45 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
to Storage daemon on backups.networktest.com:9103. ERR=Connection refused
Retrying ...
02-Oct 00:50 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
to Storage daemon on backups.networktest.com:9103. ERR=Connection refused
Retrying ...
02-Oct 00:56 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
to Storage daemon on backups.networktest.com:9103. ERR=Connection refused
Retrying ...
02-Oct 01:01 nye-dir JobId 20983: Warning: bsock.c:132 Could not connect
to Storage daemon on backups.networktest.com:9103. ERR=Connection refused
Retrying ...
02-Oct 01:05 nye-dir JobId 20983: Fatal error: bsock.c:138 Unable to
connect to Storage daemon on backups.networktest.com:9103.
ERR=Connection refused



# List of files to be backed up
# When to do the backups, full backup on first sunday of the month,
#  differential (i.e. incremental since full) every other sunday,
#  and incremental backups other days
Schedule {
  Name = "WeeklyCycle"
  Run = Full 1st sun at 23:05
  Run = Differential 2nd-5th sun at 23:05
  Run = Incremental mon-sat at 23:05
}

# This schedule does the catalog. It starts after the WeeklyCycle
Schedule {
  Name = "WeeklyCycleAfterBackup"
  Run = Full sun-sat at 23:55
}


--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2007-10-14 Thread . . 
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 / firewalling issue.

On 10/14/07, Michel Meyers <[EMAIL PROTECTED]> wrote:
>
> -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
> refused
> >
> [...]
> >
> > I have attached my config files.
> > Can someone please help me getting this to work?
>
> in bacula-dir.conf:
>
> # Definition of file storage device
> Storage {
>   Name = File
> # Do not use "localhost" here
>   Address = Bacula# N.B. Use a fully qualified name here
>   SDPort = 9103
>   Password = "I9btKZLS4OEmTURkvQOsavE5lw81r5VZnGVN60REx"
>   Device = File
>   Media Type = File
> }
>
>
> Is the server's FQDN really 'Bacula'? And does netstat show it listening
> on the right interface? ('Connection refused' would indicate that the
> request reached a machine but the port was closed/not listening.)
>
> Greetings,
> Michel
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.7 (MingW32)
>
> iD8DBQFHEi0b2Vs+MkscAyURArz0AJ9/u9wUacUQJGjJ/BJFZC4/tH0/YwCffcMq
> R8n0Kp8U6cEUsqSUPZWJVLQ=
> =aWFY
> -END PGP SIGNATURE-
>
>
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2007-10-14 Thread Michel Meyers 
-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 refused
>
[...]
> 
> I have attached my config files.
> Can someone please help me getting this to work?

in bacula-dir.conf:

# Definition of file storage device
Storage {
  Name = File
# Do not use "localhost" here
  Address = Bacula# N.B. Use a fully qualified name here
  SDPort = 9103
  Password = "I9btKZLS4OEmTURkvQOsavE5lw81r5VZnGVN60REx"
  Device = File
  Media Type = File
}


Is the server's FQDN really 'Bacula'? And does netstat show it listening
on the right interface? ('Connection refused' would indicate that the
request reached a machine but the port was closed/not listening.)

Greetings,
Michel

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFHEi0b2Vs+MkscAyURArz0AJ9/u9wUacUQJGjJ/BJFZC4/tH0/YwCffcMq
R8n0Kp8U6cEUsqSUPZWJVLQ=
=aWFY
-END PGP SIGNATURE-


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2007-10-14 Thread mcodo 

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:
[EMAIL PROTECTED]:~# ps -ax | grep bacula
Warning: bad ps syntax, perhaps a bogus '-'? See
http://procps.sf.net/faq.html
 9346 ?Ssl0:00 /usr/sbin/bacula-sd -c /etc/bacula/bacula-sd.conf
-u bacula -g tape
 9356 ?Ssl0:00 /usr/sbin/bacula-fd -c /etc/bacula/bacula-fd.conf
 9516 ?Ssl0:00 /usr/sbin/bacula-dir -c
/etc/bacula/bacula-dir.conf -u bacula -g bacula
 9599 pts/0S+ 0:00 grep bacula


I have attached my config files.
Can someone please help me getting this to work?


http://www.nabble.com/file/p13119410/bacula-dir.conf bacula-dir.conf 
http://www.nabble.com/file/p13119410/bacula-fd.conf bacula-fd.conf 
http://www.nabble.com/file/p13119410/bacula-sd.conf bacula-sd.conf 
http://www.nabble.com/file/p13119410/bconsole.conf bconsole.conf 
http://www.nabble.com/file/p13119410/log log 

Paal Solvberg
-- 
View this message in context: 
http://www.nabble.com/Could-not-connect-to-Storage-daemon-on-Bacula%3A9103.-ERR%3DConnection-refused-tf4595398.html#a13119410
Sent from the Bacula - Users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2007-03-19 Thread Brian A. Seklecki 

> 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 (or don't return) different TCP and ICMP packets in
response to SYN packets that violate policies.

Cisco doesn't give you a lot of control; pf(4) / ipf(4) does etc.

~BAS

> It would be a big help to Win32 users if you would file a bug report with the 
> above message and something like "Incorrect Win32 network error message" as 
> the title.





IMPORTANT: This message contains confidential information and is intended only 
for the individual named. If the reader of this message is not an intended 
recipient (or the individual responsible for the delivery of this message to an 
intended recipient), please be advised that any re-use, dissemination, 
distribution or copying of this message is prohibited.  Please notify the 
sender immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system.



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2007-03-17 Thread Kern Sibbald 
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 
> hosts files, to rule out dns issues while I'm testing.  I'm using the 
> configs from my old server, stripped down to support just one client.
> 
> I get this error after starting a backup job:
> 
> You have messages.
> *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 ...

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.

It would be a big help to Win32 users if you would file a bug report with the 
above message and something like "Incorrect Win32 network error message" as 
the title.

> *
> 
> The server just sits there like this:
> 
> Running Jobs:
>  JobId Level   Name   Status
> ==
>   5831 Differe  jeff-t40.2007-03-16_21.24.41 is waiting for Client 
> jeff-t40-fd to connect to Storage jeff-t40-filestore
> 
> 
> and the client like this:
> 
> jeff-t40-fd Version: 2.0.3 (06 March 2007)  VSS Linux Cross-compile Win32
> Daemon started 16-Mar-07 20:32, 0 Jobs run since started.
>  Heap: bytes=19,076 max_bytes=20,872 bufs=83 max_bufs=94
>  Sizeof: boffset_t=8 size_t=4 debug=0 trace=1
> 
> Running Jobs:
> JobId 5831 Job jeff-t40.2007-03-16_21.24.41 is running.
> System or Console Job started: 16-Mar-07 21:24
> Files=0 Bytes=0 Bytes/sec=0
> Files Examined=0
> SDSocket closed.
> 
> 
> Any idea what might be going on ?
> 
> -
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
> 

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2007-03-17 Thread Jeff Dickens 

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   Status
==
  5831 Differe  jeff-t40.2007-03-16_21.24.41 is waiting for Client 
jeff-t40-fd to connect to Storage jeff-t40-filestore



and the client like this:

jeff-t40-fd Version: 2.0.3 (06 March 2007)  VSS Linux Cross-compile Win32
Daemon started 16-Mar-07 20:32, 0 Jobs run since started.
 Heap: bytes=19,076 max_bytes=20,872 bufs=83 max_bufs=94
 Sizeof: boffset_t=8 size_t=4 debug=0 trace=1

Running Jobs:
JobId 5831 Job jeff-t40.2007-03-16_21.24.41 is running.
System or Console Job started: 16-Mar-07 21:24
Files=0 Bytes=0 Bytes/sec=0
Files Examined=0
SDSocket closed.


Any idea what might be going on ?



Can you reach the bacula-sd on port 9102 from your client?

  
I figured it out.  It was a firewall issue on the server.  Thanks for 
pointing me in the right direction.


It would  be nice if I had had something other than "ERR: No error" to 
go on.


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2007-03-17 Thread Ralf Gross 
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   Status
> ==
>   5831 Differe  jeff-t40.2007-03-16_21.24.41 is waiting for Client 
> jeff-t40-fd to connect to Storage jeff-t40-filestore
> 
> 
> and the client like this:
> 
> jeff-t40-fd Version: 2.0.3 (06 March 2007)  VSS Linux Cross-compile Win32
> Daemon started 16-Mar-07 20:32, 0 Jobs run since started.
>  Heap: bytes=19,076 max_bytes=20,872 bufs=83 max_bufs=94
>  Sizeof: boffset_t=8 size_t=4 debug=0 trace=1
> 
> Running Jobs:
> JobId 5831 Job jeff-t40.2007-03-16_21.24.41 is running.
> System or Console Job started: 16-Mar-07 21:24
> Files=0 Bytes=0 Bytes/sec=0
> Files Examined=0
> SDSocket closed.
> 
> 
> Any idea what might be going on ?

Can you reach the bacula-sd on port 9102 from your client?

Ralf

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2007-03-16 Thread Jeff Dickens 
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 using the 
configs from my old server, stripped down to support just one client.

I get this error after starting a backup job:

You have messages.
*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   Status
==
  5831 Differe  jeff-t40.2007-03-16_21.24.41 is waiting for Client 
jeff-t40-fd to connect to Storage jeff-t40-filestore


and the client like this:

jeff-t40-fd Version: 2.0.3 (06 March 2007)  VSS Linux Cross-compile Win32
Daemon started 16-Mar-07 20:32, 0 Jobs run since started.
 Heap: bytes=19,076 max_bytes=20,872 bufs=83 max_bufs=94
 Sizeof: boffset_t=8 size_t=4 debug=0 trace=1

Running Jobs:
JobId 5831 Job jeff-t40.2007-03-16_21.24.41 is running.
System or Console Job started: 16-Mar-07 21:24
Files=0 Bytes=0 Bytes/sec=0
Files Examined=0
SDSocket closed.


Any idea what might be going on ?

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2006-12-08 Thread Jon Ingason 
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:
>>
>> run job="client-100" fileset="client File Set" level=Incremental
>> client="client-100-fd" pool="client-100" when="2006-12-07 12:59:47"
>> where="" storage="Fileclient-100"Run Backup job
>> JobName:  client-100
>> FileSet:  Client File Set
>> Level:Incremental
>> Client:   client-100-fd
>> Storage:  Fileclient-100
>> Pool: client-100
>> When: 2006-12-07 12:59:47
>> Priority: 14
>> OK to run? (yes/mod/no):
>> Job started. JobId=51
>> 07-Dec 12:59 bacula-dir: No prior Full backup Job record found.
>> 07-Dec 12:59 bacula-dir: No prior or suitable Full backup found. Doing
>> FULL backup.
>> 07-Dec 12:59 bacula-dir: Start Backup JobId 51,
>> Job=client-100.2006-12-07_12.59.50
>> 07-Dec 12:58 client-100-fd: client-100.2006-12-07_12.59.50 Warning:
>> bnet.c:853 Could not connect to Storage daemon on bacula:9103.
>> ERR=Operation not permitted
>> Retrying ...
> 
>> I have have other clients which are working well. It has probable
>> nothing to do with the client, but with the storage daemon. I have gone
>> through the configurations files and so on, but can't find anything
>> wrong.
>>
>> Are there someone who know more and can explain what can be wrong?
> 
> The bacula fd cannot connect to the storage daemon. That's also exactly
> what the log says.
> Make sure any firewall between the file daemon and the storage daemon
> allows the file daemon to connect to the storage daemon on port 9103.

Yes it was a firewall problem.

Thanks
> 
> Regards,
> Georg


--

Regards

Jon Ingason

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2006-12-07 Thread Zakai Kinan 
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 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:47"
> where="" storage="Fileclient-100"Run Backup job
> JobName:  client-100
> FileSet:  Client File Set
> Level:Incremental
> Client:   client-100-fd
> Storage:  Fileclient-100
> Pool: client-100
> When: 2006-12-07 12:59:47
> Priority: 14
> OK to run? (yes/mod/no):
> Job started. JobId=51
> 07-Dec 12:59 bacula-dir: No prior Full backup Job
> record found.
> 07-Dec 12:59 bacula-dir: No prior or suitable Full
> backup found. Doing
> FULL backup.
> 07-Dec 12:59 bacula-dir: Start Backup JobId 51,
> Job=client-100.2006-12-07_12.59.50
> 07-Dec 12:58 client-100-fd:
> client-100.2006-12-07_12.59.50 Warning:
> bnet.c:853 Could not connect to Storage daemon on
> bacula:9103.
> ERR=Operation not permitted
> Retrying ...
> 07-Dec 13:04 client-100-fd:
> client-100.2006-12-07_12.59.50 Warning:
> bnet.c:853 Could not connect to Storage daemon on
> bacula:9103.
> ERR=Operation not permitted
> Retrying ...
> 07-Dec 13:09 client-100-fd:
> client-100.2006-12-07_12.59.50 Warning:
> bnet.c:853 Could not connect to Storage daemon on
> bacula:9103.
> ERR=Operation not permitted
> Retrying ...
> 07-Dec 13:14 client-100-fd:
> client-100.2006-12-07_12.59.50 Warning:
> bnet.c:853 Could not connect to Storage daemon on
> bacula:9103.
> ERR=Operation not permitted
> Retrying ...
> 07-Dec 13:19 client-100-fd:
> client-100.2006-12-07_12.59.50 Warning:
> bnet.c:853 Could not connect to Storage daemon on
> bacula:9103.
> ERR=Operation not permitted
> Retrying ...
> 
> I have have other clients which are working well. It
> has probable
> nothing to do with the client, but with the storage
> daemon. I have gone
> through the configurations files and so on, but
> can't find anything wrong.
> 
> Are there someone who know more and can explain what
> can be wrong?
> 
> -- 
> Regards
> 
> Jon Ingason
> 
>
-
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get
> the chance to share your
> opinions on IT & business topics through brief
> surveys - and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/bacula-users
> 



 

Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2006-12-07 Thread Georg Altmann 


--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="client File Set" level=Incremental
> client="client-100-fd" pool="client-100" when="2006-12-07 12:59:47"
> where="" storage="Fileclient-100"Run Backup job
> JobName:  client-100
> FileSet:  Client File Set
> Level:Incremental
> Client:   client-100-fd
> Storage:  Fileclient-100
> Pool: client-100
> When: 2006-12-07 12:59:47
> Priority: 14
> OK to run? (yes/mod/no):
> Job started. JobId=51
> 07-Dec 12:59 bacula-dir: No prior Full backup Job record found.
> 07-Dec 12:59 bacula-dir: No prior or suitable Full backup found. Doing
> FULL backup.
> 07-Dec 12:59 bacula-dir: Start Backup JobId 51,
> Job=client-100.2006-12-07_12.59.50
> 07-Dec 12:58 client-100-fd: client-100.2006-12-07_12.59.50 Warning:
> bnet.c:853 Could not connect to Storage daemon on bacula:9103.
> ERR=Operation not permitted
> Retrying ...

> I have have other clients which are working well. It has probable
> nothing to do with the client, but with the storage daemon. I have gone
> through the configurations files and so on, but can't find anything wrong.
>
> Are there someone who know more and can explain what can be wrong?

The bacula fd cannot connect to the storage daemon. That's also exactly 
what the log says.
Make sure any firewall between the file daemon and the storage daemon 
allows the file daemon to connect to the storage daemon on port 9103.

Regards,
Georg

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

2006-12-07 Thread Jon Ingason 
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:47"
where="" storage="Fileclient-100"Run Backup job
JobName:  client-100
FileSet:  Client File Set
Level:Incremental
Client:   client-100-fd
Storage:  Fileclient-100
Pool: client-100
When: 2006-12-07 12:59:47
Priority: 14
OK to run? (yes/mod/no):
Job started. JobId=51
07-Dec 12:59 bacula-dir: No prior Full backup Job record found.
07-Dec 12:59 bacula-dir: No prior or suitable Full backup found. Doing
FULL backup.
07-Dec 12:59 bacula-dir: Start Backup JobId 51,
Job=client-100.2006-12-07_12.59.50
07-Dec 12:58 client-100-fd: client-100.2006-12-07_12.59.50 Warning:
bnet.c:853 Could not connect to Storage daemon on bacula:9103.
ERR=Operation not permitted
Retrying ...
07-Dec 13:04 client-100-fd: client-100.2006-12-07_12.59.50 Warning:
bnet.c:853 Could not connect to Storage daemon on bacula:9103.
ERR=Operation not permitted
Retrying ...
07-Dec 13:09 client-100-fd: client-100.2006-12-07_12.59.50 Warning:
bnet.c:853 Could not connect to Storage daemon on bacula:9103.
ERR=Operation not permitted
Retrying ...
07-Dec 13:14 client-100-fd: client-100.2006-12-07_12.59.50 Warning:
bnet.c:853 Could not connect to Storage daemon on bacula:9103.
ERR=Operation not permitted
Retrying ...
07-Dec 13:19 client-100-fd: client-100.2006-12-07_12.59.50 Warning:
bnet.c:853 Could not connect to Storage daemon on bacula:9103.
ERR=Operation not permitted
Retrying ...

I have have other clients which are working well. It has probable
nothing to do with the client, but with the storage daemon. I have gone
through the configurations files and so on, but can't find anything wrong.

Are there someone who know more and can explain what can be wrong?

-- 
Regards

Jon Ingason

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users