Hello Mohamed, > Le 12 févr. 2024 à 15:45, Mohamed AIT EL HADJ via Bacula-users > <bacula-users@lists.sourceforge.net> a écrit : > > Hello, > > I'm using the latest version of Bacula,13.0.3, on Debian 11. The backups work > fine but the utility dbcheck dont work. > > I have a Postgresql database and when i start a dbcheck, he take 100% of my > RAM and CPU and he crashs with this error : > > Checking for Paths without a trailing slash > Found 0 bad Path records. > Checking for duplicate Path entries. > Found 0 duplicate Path records. > Checking for orphaned JobMedia entries. > Checking for orphaned File entries. This may take some time! > Checking for orphaned Path entries. This may take some time! > WARNING: connection stopped due to the sudden termination of another server > process > DETAIL: The postmaster has ordered this server process to cancel the current > transaction and exit because another server process exited abnormally and > that there is probably corrupt shared memory. > TIP: In a moment, you should be able to reconnect to the database and restart > your order. > Query failed: SELECT DISTINCT Path.PathId,File.PathId FROM Path LEFT OUTER > JOIN File ON (Path.PathId=File.PathId) WHERE File.PathId IS NULL LIMIT > 300000: ERR=FATAL: connections stopped following the request for > 'administrator > SYSCALL SSL error: EOF detected >
It’s not really a crash, you have reached some limits configured on your system, and Postgresql has decided to stop the query. Usually, everything depends on the postgresql server configuration, and by default, you have something like 64k of work_mem to deal with a multi-gigabyte database. I believe that over the time we did recommendations about the postgresql configuration, but you can apply the settings advised for « large systems ». Typically, 64MB of work_mem, 2GB of shared_mem, less frequent checkpoints, etc... > I understand that this dbcheck crashed because he take a lot of memory and > CPU but my question is, firstly, why this take that much of memory, because i > have another server running with bacula 9.4 and his dbcheck works perfectly > while its database is bigger. And secondly, what can i do to resolve this > issue. > I believe that the CPU is more a problem related with the Postgres configuration not suitable for your database. Best Regards, Eric _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
