Hi,
Theses are just warnings, don’t worry too much about it.
Regards
Davide
On Mon, 8 Jan 2018 at 14:53, jesus moreno wrote:
> Hi:
>
> I have upgrade Debian 9 Stretch from a Debian 8.10 with bacula-fd 9.0.5. I
> want to check the compilation of bacula in the new Debian System, using
> bacula
Concerning the readdir_r messages, please complain to the GCC
developers who seem to take great pleasure (sarcastic) at adding
such warnings to newer versions of the compiler. In fact their
warning is total nonsense because Bacula automatically fixes any
potentia
I'm confused as to why Volumes are not being created. They do not exist on
disk. This is not a newly configured system.
Is "No autolabel because polling" relevant? see below.
Said backup has been running for several days. I have confirmed space is
available (about 6TB free) and that files can
On 01/09/18 08:57, Kern Sibbald wrote:
> Concerning the readdir_r messages, please complain to the GCC developers
> who seem to take great pleasure (sarcastic) at adding such warnings to
> newer versions of the compiler. In fact their warning is total nonsense
> because Bacula automatically fixes
> On Tue, 9 Jan 2018 14:57:59 +0100, Kern Sibbald said:
>
> Concerning the readdir_r messages, please complain to the GCC
> developers who seem to take great pleasure (sarcastic) at adding
> such warnings to newer versions of the compiler. In fact their
> warning is total nonsense because Bac
On 01/09/2018 07:24 AM, Dan Langille wrote:
> I'm confused as to why Volumes are not being created. They do not exist on
> disk. This is not a newly configured system.
>
> Is "No autolabel because polling" relevant? see below.
>
> Said backup has been running for several days. I have confirmed
On 2018-01-09 10:29, Martin Simmons wrote:
On Tue, 9 Jan 2018 14:57:59 +0100, Kern Sibbald said:
Concerning the readdir_r messages, please complain to the GCC
developers who seem to take great pleasure (sarcastic) at adding
such warnings to newer versions of the compiler. In fact their
warning
> On Jan 9, 2018, at 12:20 PM, Bill Arlofski wrote:
>
> On 01/09/2018 07:24 AM, Dan Langille wrote:
>> I'm confused as to why Volumes are not being created. They do not exist on
>> disk. This is not a newly configured system.
>>
>> Is "No autolabel because polling" relevant? see below.
>>
>>
Further to below, looks like SD is just sitting there waiting for bytes that
are not coming, while next job is queued.
Is correct procedure to restart SD?
Writing: Full Backup job Backup2NasDto-Tape JobId=15020
Volume="NASFull-0005"
pool="NASFullPool" device="LTO-6" (/dev/nst0)
spoo
On 01/09/2018 10:43 AM, Dan Langille wrote:
> The 'update pool' is not required if just bumping maxvols.
>
> Thank you.
Confirmed.
list pool=xxx and show pool=xxx after an update confirm your statement.
That's what I get for multitasking I guess. :)
We now return you to your regularly schedul
hi All
This is annoying: literally half way through a 3.6 TB backup.
09-Jan 19:20 TapeServer JobId 15020: Writing spooled data to Volume.
Despooling 50,000,033,879 bytes ...
09-Jan 19:32 TapeServer JobId 15020: Despooling elapsed time = 00:11:35,
Transfer rate = 71.94 M Bytes/second
09-Jan 19:3
On Tuesday, 09 January 2018 9:02:16 PM SAST Ian Douglas wrote:
> The Inc job uses different tapes to Full job, but Director is not requesting
> tape change because it's waiting for SD to say its finished, I suppose...
Looks like it eventually timed out and has requested the tape change.
Guess wi
I wonder if this line is related:
bacula-sd-01-sd: mount.c:663-269534 No autolabel because polling.
If no labeling, then no volume is created.
See
https://gist.github.com/dlangille/513cb50351f7bc6ab6d33a6859b20326#file-bacula-trace-L84
bacula-sd-01-sd: mount.c:182-269534 want vol=FullAuto-8
--
Dan Langille - BSDCan / PGCon
d...@langille.org
> On Jan 9, 2018, at 3:01 PM, Dan Langille wrote:
>
> I wonder if this line is related:
>
>
> bacula-sd-01-sd: mount.c:663-269534 No autolabel because polling.
>
> If no labeling, then no volume is created.
>
> See
> https://gist.github.
> On Jan 9, 2018, at 3:07 PM, Dan Langille wrote:
>
>> On Jan 9, 2018, at 3:01 PM, Dan Langille wrote:
>>
>> I wonder if this line is related:
>>
>>
>> bacula-sd-01-sd: mount.c:663-269534 No autolabel because polling.
>>
>> If no labeling, then no volume is created.
>>
>> See
>> https://gi
Ian
What version of bacula are you running? I had a lot of issues with version
7.4 with these types of errors. Once I upgrade to 9.X all these error went away
And I have had not further SD failures. If you're your not running 9.X then I
would recommend an upgrade.
jeff
-Original Mes
Hi,
I ran the update over the weekend and it updated the kernel and mariadb as
well as many others. Bacula is not connecting to the storage daemon now.
Can someone tell me what the following error means:
Fatal error: Bad response to Storage command: wanted 2000 OK storage, got
2902 Bad storage
17 matches
Mail list logo