Jon Ingason 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?
The debug mode has saved me in numerous occasions. It often helps give
me insight into why I'm getting the error I'm getting. I'd recommend
stopping the director (such as, ./bacula-ctl-dir stop, and then starting
it in debug mode, such as ./bacula-dir -d 100). Then, in a second
console, try to run the job.
Spam detection software, running on the system "mail.appraiseutah.com", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: Jon Ingason 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 [...]
Content analysis details: (7.4 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
0.9 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers
0.5 DNS_FROM_RFC_ABUSE RBL: Envelope sender in abuse.rfc-ignorant.org
0.9 DNS_FROM_RFC_WHOIS RBL: Envelope sender in whois.rfc-ignorant.org
2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address
[24.10.159.195 listed in dnsbl.sorbs.net]
1.4 DNS_FROM_RFC_POST RBL: Envelope sender in
postmaster.rfc-ignorant.org
1.7 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP
[24.10.159.195 listed in combined.njabl.org]
-------------------------------------------------------------------------
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
