Re: [Bacula-users] postgres createdb for bacula fails

[dmitri maziuk]

On 2021-05-03 7:38 PM, Dan Langille wrote:

On Mon, May 3, 2021, at 6:16 PM, kjohn...@eclypse.org wrote:



DETAIL:  The chosen LC_CTYPE setting requires encoding "UTF8".




$ createdb -E SQL_ASCII -T template0 bacula
$ dropdb bacula
$ export LC_ALL=C
$ createdb -E SQL_ASCII -T template0 bacula
$

Works there. I suspect it is something specific to the environment.


I guess freebsd doesn't set LC_CTYPE? Postgres falls back on LC_ALL only 
if that (and IIRC some *LANG* too) isn't set.


Dima


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] postgres createdb for bacula fails

[Dan Langille]

On Mon, May 3, 2021, at 6:16 PM, kjohn...@eclypse.org wrote:

> The next step in my testing is to create an empty bacula database on the
> test system and restore it from the pg_dump file created on the conversion
> system.  I have learned that the bacula postgres database needs to have
> encoding SQL_ASCII.  

For what it's worth, SQL_ASCII was decided upon many years ago.

> Here's the difficulty.  As user bacula on the test system:
> 
> $ export LC_ALL=C
> $ createdb -E SQL_ASCII -T template0 bacula
> createdb: database creation failed: ERROR:  encoding "SQL_ASCII" does not
> match locale "en_US.UTF-8"
> DETAIL:  The chosen LC_CTYPE setting requires encoding "UTF8".
> 
> Probably, fixing this is something that everyone else knows.  Unfortunately,
> my Google searches find too much or almost nothing.  A specific search of
> the mailing list archive found a discussion of why SQL_ASCII was so
> important (circa 2009),

The decision was made earlier I think.

> but not an answer to this problem.  At least, not
> one that I recognized.  (same failure without the export, by the way).  The
> documentation for Bacula 7.4
> (https://www.bacula.org/7.4.x-manuals/en/main/Installing_Configuring_Post.ht
> ml) also states that SQL_ASCII is essential, but I did not recognize a
> solution to this problem there.

I think the problem is more PostgreSQL & environment specific. Here is my test
on FreeBSD 12.2 with PostgreSQL 12.6 - these commands are run as the postgres
user:

$ createdb -E SQL_ASCII -T template0 bacula
$ dropdb bacula
$ export LC_ALL=C
$ createdb -E SQL_ASCII -T template0 bacula
$ 

Works there. I suspect it is something specific to the environment.

What do you have for this value?

$ echo $locale

$ 


-- 
  Dan Langille
  d...@langille.org


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2

[Heitor Faria]

>> Despite of the not-working testimonials in this thread, until now I see no
>> related bug reports in the Bacula bug tracker: [
>> https://bugs.bacula.org/view_all_bug_page.php |
>> https://bugs.bacula.org/view_all_bug_page.php ]
>> IMHO it would be of great help if you could make the bug reports with the
>> maximum details, such as:
>> - bacula.org package versions you are trying to install.
>> - libs3 version and installation commands
>> - operating system exact version
>> - bacula-sd -d 200 loading debug output
>> - steps to reproduce the error.
>> I believe this is the fastest way of the bacula.org team to address this 
>> problem
>> properly.
>> Regards,

> Problem has been reported.
Hello Sruckh: the error you reported is different from the OP. 
For everyone also having the: "Apr 27 20:59:59 backup bacula-sd[498]: 
cloud_dev.c:1001 Could not open Cloud driver type=1 for Device=.", you are 
encouraged also to full a bug report. 
> Thank You.
Regards, 
-- 

MSc Heitor Faria (Miami/USA) 
Bacula LATAM CEO 

mobile1: + 1 909 655-8971 
mobile2: + 55 61 98268-4220 
[ https://www.linkedin.com/in/msc-heitor-faria-5ba51b3 ] 
[ http://www.bacula.com.br/ ] 

América Latina 
[ http://bacula.lat/ | bacula.lat ] | [ http://www.bacula.com.br/ | 
bacula.com.br ] 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] postgres createdb for bacula fails

[kjohnson]

As time permits, I am working on an sqlite to postgres conversion of a
bacula database, in preparation for upgrading from Debian 9 to Debian 10.
For a variety of reasons I believe I am pretty close.  But...

There are three systems involved:  the live server (Debian 9), the system
where the database conversion occurs, and a test system (Debian 9) that I am
using to confirm to the extent possible that the database conversion has
been successful.

The next step in my testing is to create an empty bacula database on the
test system and restore it from the pg_dump file created on the conversion
system.  I have learned that the bacula postgres database needs to have
encoding SQL_ASCII.  

Here's the difficulty.  As user bacula on the test system:

$ export LC_ALL=C
$ createdb -E SQL_ASCII -T template0 bacula
createdb: database creation failed: ERROR:  encoding "SQL_ASCII" does not
match locale "en_US.UTF-8"
DETAIL:  The chosen LC_CTYPE setting requires encoding "UTF8".

Probably, fixing this is something that everyone else knows.  Unfortunately,
my Google searches find too much or almost nothing.  A specific search of
the mailing list archive found a discussion of why SQL_ASCII was so
important (circa 2009), but not an answer to this problem.  At least, not
one that I recognized.  (same failure without the export, by the way).  The
documentation for Bacula 7.4
(https://www.bacula.org/7.4.x-manuals/en/main/Installing_Configuring_Post.ht
ml) also states that SQL_ASCII is essential, but I did not recognize a
solution to this problem there.

bacula 7.4.4
postgres 9.6

A solution to this problem, or a fairly tight direction to the relevant
documentation would be very much appreciated.  Thanks in advance for your
attention.

Ken




___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2

[sruckh--- via Bacula-users]

On 2021-05-03 14:25, Heitor Faria wrote:


Hello  r0002,

Despite of the not-working testimonials in this thread, until now I see 
no related bug reports in the Bacula bug tracker: 
https://bugs.bacula.org/view_all_bug_page.php
IMHO it would be of great help if you could make the bug reports with 
the maximum details, such as:


- bacula.org package versions you are trying to install.
- libs3 version and installation commands
- operating system exact version
- bacula-sd -d 200 loading  debug output
- steps to reproduce the error.

I believe this is the fastest way of the bacula.org team to address 
this problem properly.


Regards,


Problem has been reported.

Thank You.___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2

[Heitor Faria]

Hello r0002, 

Despite of the not-working testimonials in this thread, until now I see no 
related bug reports in the Bacula bug tracker: [ 
https://bugs.bacula.org/view_all_bug_page.php | 
https://bugs.bacula.org/view_all_bug_page.php ] 
IMHO it would be of great help if you could make the bug reports with the 
maximum details, such as: 

- bacula.org package versions you are trying to install. 
- libs3 version and installation commands 
- operating system exact version 
- bacula-sd -d 200 loading debug output 
- steps to reproduce the error. 

I believe this is the fastest way of the bacula.org team to address this 
problem properly. 

Regards, 

> I have tried for weeks to get the S3 module to work on the Community edition 
> of
> Bacula, to no avail.

> Are you working with the community edition, or the paid edition?

> Regards,

> Al
> On 5/2/21 1:17 PM, sruckh--- via Bacula-users wrote:

>> On 2021-04-30 09:23, Heitor Faria wrote:
>>> Hello,

 If you read the email thread, I was not asking for technical help. I was 
 simply
 asking if anyone has had success with the S3 plugin. With the lack of
 responses, I can only assume nobody has got it working.

>>> Of course. After less than 20 hours from the original post that was the only
>>> possible assumption. I guess everyone have to, voluntarily and promptly,
>>> provide the answers that you need.
 Which means the plugin does not work, so it should be removed from the 
 repo.

>>> I personally know at least 10 administrators that use the CBacula 9/11 
>>> version
>>> Cloud driver in different sectors. It also works in one of my lab machines:

>> I am running bacula 9.6.7 on CentOS 7 where the packages came from [
>> https://bacula.org/packages/x/rpms/9.6.7/el7/x86_64/ |
>> https://bacula.org/packages/x/rpms/9.6.7/el7/x86_64/ ] . In my 
>> case
>> the S3 drivers seemed to stop working after 9.6.5 (if I remember correctly. 
>> It
>> was a couple of versions ago when it stopped working).
>> With the current packages, bacula-mysql-9.6.7-1.el7.x86_64,
>> bacula-aligned-9.6.7-1.el7.x86_64, bacula-cloud-storage-9.6.7-1.el7.x86_64, 
>> and
>> bacula-libs-9.6.7-1.el7.x86_64, the S3LIB files (discussed in this thread
>> earlier) are provided by package bacula-cloud-storage. The libs3.so.4 file 
>> gets
>> installed in /opt/bacula/lib64/. The problem being that if you do a ldd on
>> /opt/bacula/plugins/bacula-sd-cloud-driver-9.6.7.so it shows it uses,
>> libs3.so.4, but that it is missing. So I tried to create the file
>> /etc/ld.so.conf.d/bacula.conf and added /opt/bacula/lib64 path to the file 
>> and
>> ran ldconfig to rebuild the cache. By doing this, running ldd on
>> bacula-sd-cloud-driver-9.6.7.so now shows libs3.so.4 coming from
>> /opt/bacula/lib64.
>> Unfortunately, even with this change, a configuration that used to work fine 
>> in
>> older versions of bacula, no longer work in the current version installed. 
>> The
>> S3 drivers seems to load, but I ultimately end up with this error: 3999 Error
>> with the upload: ERR=RequestTorrentOfBucketError .
>> On a hunch, I went ahead and built an RPM package from the link provided 
>> earlier
>> in the thread for the libs3 library. I went ahead and installed this RPM 
>> after
>> building it and the libs3.so.4 file is now in /usr/lib/ . I went ahead and
>> removed the /etc/ld.so.conf.d/bacula.conf, and again rebuilt the cache with
>> ldconfig. Now when running ldd on bacula-sd-cloud-driver-9.6.7.so the
>> libs3.so.4 now shows to be coming from /usr/lib/ .
>> Unfortunately, I get the same error as before. This time, I just went into
>> bconsole, and tried to use the cloud command to upload the volume. After a 
>> few
>> minutes the bconsole command times out with the exact error mentioned above
>> that is received when trying to perform a backup.
>> This exact configuration used to work going straight to S3 cloud bucket, and
>> also when using minio as a middle-man to go to Backblaze storage before they
>> supported native S3 commands.
>> So, in my experience, the S3 cloud plugin has not worked for me after 
>> something
>> changed from an older version.

>> ___
>> Bacula-users mailing list [ mailto:Bacula-users@lists.sourceforge.net |
>> Bacula-users@lists.sourceforge.net ] [
>> https://lists.sourceforge.net/lists/listinfo/bacula-users |
>> https://lists.sourceforge.net/lists/listinfo/bacula-users ]

> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users

-- 

MSc Heitor Faria (Miami/USA) 
Bacula LATAM CEO 

mobile1: + 1 909 655-8971 
mobile2: + 55 61 98268-4220 
[ https://www.linkedin.com/in/msc-heitor-faria-5ba51b3 ] 
[ http://www.bacula.com.br/ ] 

América Latina 
[ http://bacula.lat/ | bacula.lat ] | [ http://www.bacula.com.br/ | 
bacula.com.br ] 

Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2

[r0...@nxlplyx.com]

Hi Struckh,

I have tried for weeks to get the S3 module to work on the Community
edition of Bacula, to no avail.

Are you working with the community edition, or the paid edition?

Regards,

Al

On 5/2/21 1:17 PM, sruckh--- via Bacula-users wrote:
>
> On 2021-04-30 09:23, Heitor Faria wrote:
>
>> Hello,
>>
>> If you read the email thread, I was not asking for technical
>> help. I was simply asking if anyone has had success with the S3
>> plugin. With the lack of responses, I can only assume nobody has
>> got it working.
>>
>> Of course. After less than 20 hours from the original post that was
>> the only possible assumption. I guess everyone have to, voluntarily
>> and promptly, provide the answers that you need.
>>
>> Which means the plugin does not work, so it should be removed
>> from the repo.
>>
>> I personally know at least 10 administrators that use the CBacula
>> 9/11 version Cloud driver in different sectors. It also works in one
>> of my lab machines:
>  
> I am running bacula 9.6.7 on CentOS 7 where the packages came
> from https://bacula.org/packages/x/rpms/9.6.7/el7/x86_64/
>  . 
> In my case the S3 drivers seemed to stop working after 9.6.5 (if I
> remember correctly.  It was a couple of versions ago when it stopped
> working).
>  
> With the current packages, bacula-mysql-9.6.7-1.el7.x86_64,
> bacula-aligned-9.6.7-1.el7.x86_64,
> bacula-cloud-storage-9.6.7-1.el7.x86_64, and
> bacula-libs-9.6.7-1.el7.x86_64, the S3LIB files (discussed in this
> thread earlier) are provided by package bacula-cloud-storage. The
> libs3.so.4 file gets installed in /opt/bacula/lib64/.  The problem
> being that if you do a ldd on
> /opt/bacula/plugins/bacula-sd-cloud-driver-9.6.7.so it shows it uses,
> libs3.so.4, but that it is missing.  So I tried to create the file
> /etc/ld.so.conf.d/bacula.conf and added /opt/bacula/lib64 path to the
> file and ran ldconfig to rebuild the cache.  By doing this, running
> ldd on bacula-sd-cloud-driver-9.6.7.so now shows libs3.so.4 coming
> from /opt/bacula/lib64.
>  
> Unfortunately, even with this change, a configuration that used to
> work fine in older versions of bacula, no longer work in the current
> version installed.  The S3 drivers seems to load, but I ultimately end
> up with this error:  3999 Error with the upload:
> ERR=RequestTorrentOfBucketError .
>  
> On a hunch, I went ahead and built an RPM package from the link
> provided earlier in the thread for the libs3 library.  I went ahead
> and installed this RPM after building it and the libs3.so.4 file is
> now in /usr/lib/ .  I went ahead and removed the
> /etc/ld.so.conf.d/bacula.conf, and again rebuilt the cache with
> ldconfig.  Now when running ldd on bacula-sd-cloud-driver-9.6.7.so the
> libs3.so.4 now shows to be coming from /usr/lib/ .
>  
> Unfortunately, I get the same error as before.  This time, I just went
> into bconsole, and tried to use the cloud command to upload the
> volume.  After a few minutes the bconsole command times out with the
> exact error mentioned above that is received when trying to perform a
> backup.
>  
> This exact configuration used to work going straight to S3 cloud
> bucket, and also when using minio as a middle-man to go to Backblaze
> storage before they supported native S3 commands.
>  
> So, in my experience, the S3 cloud plugin has not worked for me after
> something changed from an older version.
>
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Fatal error: catreq.c:751 fread attr spool error. Wanted 1478509141 bytes, maximum permitted 10000000 bytes

[Peter Milesson]

Hi folks,

Answering my own question. Installing bacula 9.2.2 solved this problem.

Best regards,

Peter

On 2021-05-01 15:05, Peter Milesson wrote:

Hi folks,

When running monthly full backup on a Linux server, the following 
error occurred in the final steps of the backup process, when 
despooling attributes. Previous log entry was: Sending spooled attrs 
to the Director. Despooling 180,651,607 bytes ...


Fatal error: catreq.c:751 fread attr spool error. Wanted 1478509141 
bytes, maximum permitted 1000 bytes


It has been reported previously in this list on 15 February 2021, 
without any obvious solution.


The number of backed up files are 576,816, and the backup size is 
1,024,746,654,774 (1.024 TB).


Both the backup server and client runs Bacula 9.0.6, and both with OS 
CentOS 7.8. This is the first time I have seen this message since I 
installed the system 4 years ago.


There is plenty of space in the spool directory, plenty of RAM, the 
data is directly written to virtual tapes (mhvtl) without data 
spooling, and there is no line compression, as the network connection 
is 10Gbits/s, with the bottleneck being the disk subsystem on the 
backup server (RAID10).


Suggestions are very welcome.

Best regards,

Peter






___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users




___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users