[Bacula-users] Fatal error: catreq.c:751 fread attr spool error. Wanted 1478509141 bytes, maximum permitted 10000000 bytes
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
Re: [Bacula-users] Unable to upgrade to bacula 11.0.2. SOLVED.
On 2021-04-30 at 16:37:19 Erik P. Olsen wrote: > I have originally installed bacula 9.6.5 using the fedora repository, so I > did an > ordinary upgrade using dnf upgrade. The upgrade ran without any indication of > failure > but bacula turned out to be broken. I must add to the info that I am running > mysql in > the flavour of mariadb. Mysql was up and running and so was bacula-fd and > bacula-sd but > bacula-dir didn't start. I thought I had to upgrade the catalogue, so I ran > the script > update_bacula_tables but it failed: > > [erik@Erik-PC bacula]$ /usr/libexec/bacula/update_mysql_tables > > This script will update a Bacula MySQL database > from any from version 12-15 or 1014-1021 to version 1022 > which is needed to convert from any Bacula Enterprise > version 4.0.x or later to version 12.4.x > or Bacula Community versions 5.0.x, 5.2.x, 7.4.x, 9.x.x to > Community version 11.0 > > Depending on the current version of your catalog, you may > have to run this script multiple times > > ERROR 1044 (42000): Access denied for user ''@'localhost' to database 'bacula' > > Unable to detect database version, you can specify connection information > on the command line. > Error. Cannot upgrade this database. > __ > > Is this a packaging error that should be reported to fedora or have I > misunderstood > something? > > I have now downgraded bacula 11.0.2 to version 9.6.5 and now bacula runs > flawlessly as > usual and since I don't need the new version that much I can use the system > as is > without problems but of course I'll like to have bacula upgraded for safety > reasons. > After a number of failing attempts I finally found the solution in the following series of commands (all run as root): systemctl stop mysql.service systemctl stop bacula-dir.service systemctl stop bacula-fd.service systemctl stop bacula-sd.service dnf upgrade bacula-* alternatives --set libbaccats.so /usr/lib64/libbaccats-mysql.so systemctl enable mysql.service systemctl start mysql.service cd /usr/libexec/bacula ./update_bacula_tables mysql systemctl enable bacula-dir.service systemctl enable bacula-fd.service systemctl enable bacula-sd.service systemctl start bacula-dir.service systemctl start bacula-fd.service systemctl start bacula-sd.service And now bacula 11.0.2 ran without any problem. the update_bacula_tables mysql took about 15 minutes. -- Erik P. Olsen - Copenhagen, Denmark Fedora 33/64 bit xfce Claws-Mail POP3 Gramps 5.1.3 Bacula 11.0.2 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users