Hello List,
At the beginning everything was OK. I updated the system two days ago.
Packages below updated.
postfix:amd64 (3.1.8-0+deb9u1, 3.1.9-0+deb9u2), gnupg-agent:amd64
(2.1.18-8~deb9u3, 2.1.18-8~deb9u4), libxapian30:amd64 (1.4.3-2+deb9u2,
1.4.3-2+deb9u3), libsystemd0:amd64 (232-25+deb9u8, 232-25+deb9u9),
postfix-sqlite:amd64 (3.1.8-0+deb9u1, 3.1.9-0+deb9u2), libc6:amd64
(2.24-11+deb9u3, 2.24-11+deb9u4), udev:amd64 (232-25+deb9u8,
232-25+deb9u9), locales:amd64 (2.24-11+deb9u3, 2.24-11+deb9u4),
libpq5:amd64 (9.6.10-0+deb9u1, 9.6.11-0+deb9u1), libudev1:amd64
(232-25+deb9u8, 232-25+deb9u9), libc-l10n:amd64 (2.24-11+deb9u3,
2.24-11+deb9u4), libc-bin:amd64 (2.24-11+deb9u3, 2.24-11+deb9u4),
systemd-sysv:amd64 (232-25+deb9u8, 232-25+deb9u9), gpgv:amd64
(2.1.18-8~deb9u3, 2.1.18-8~deb9u4), libpam-systemd:amd64 (232-25+deb9u8,
232-25+deb9u9), systemd:amd64 (232-25+deb9u8, 232-25+deb9u9),
multiarch-support:amd64 (2.24-11+deb9u3, 2.24-11+deb9u4), gnupg:amd64
(2.1.18-8~deb9u3, 2.1.18-8~deb9u4), linux-image-4.9.0-8-amd64:amd64
(4.9.130-2, 4.9.144-3), base-files:amd64 (9.9+deb9u7, 9.9+deb9u8)
Then Storage Daemon service started not working at the startup. Stopping
and restarting doesn't work. It seems active but exited!
# service bacula-sd status
● bacula-sd.service - LSB: Start Bacula Storage daemon at boot time
Loaded: loaded (/etc/init.d/bacula-sd; generated; vendor preset:
enabled)
Active: active (exited) since Thu 2019-02-21 10:17:45 +03; 10h ago
Docs: man:systemd-sysv-generator(8)
Process: 481 ExecStart=/etc/init.d/bacula-sd start (code=exited,
status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/bacula-sd.service
Feb 21 10:17:42 LinSrv systemd[1]: Starting LSB: Start Bacula Storage
daemon at boot time...
Feb 21 10:17:45 LinSrv bacula-sd[481]: Starting Bacula Storage Daemon:
bacula-sd
Feb 21 10:17:45 LinSrv systemd[1]: Started LSB: Start Bacula Storage
daemon at boot time.
#
Errors in the logs while backing up:
19-Feb 23:24 LinSrv-dir JobId 30: Begin pruning Jobs older than 6 months .
19-Feb 23:24 LinSrv-dir JobId 30: No Jobs found to prune.
19-Feb 23:24 LinSrv-dir JobId 30: Begin pruning Files.
19-Feb 23:24 LinSrv-dir JobId 30: No Files found to prune.
19-Feb 23:24 LinSrv-dir JobId 30: End auto prune.
19-Feb 23:24 LinSrv-dir JobId 30: shell command: run AfterJob
"/opt/bacula/scripts/delete_catalog_backup"
20-Feb 12:56 LinSrv-dir JobId 31: Start Backup JobId 31,
Job=BackupServotel5.2019-02-20_12.56.34_03
20-Feb 12:57 LinSrv-dir JobId 31: Warning: bsockcore.c:203 Could not
connect to Storage daemon on LinSrv:9103. ERR=Connection refused
Retrying ...
20-Feb 13:07 LinSrv-dir JobId 31: Warning: bsockcore.c:203 Could not
connect to Storage daemon on LinSrv:9103. ERR=Connection refused
Retrying ...
20-Feb 13:17 LinSrv-dir JobId 31: Warning: bsockcore.c:203 Could not
connect to Storage daemon on LinSrv:9103. ERR=Connection refused
Retrying ...
20-Feb 13:26 LinSrv-dir JobId 31: Fatal error: bsockcore.c:209 Unable to
connect to Storage daemon on LinSrv:9103. ERR=Connection refused
20-Feb 13:26 LinSrv-dir JobId 31: Error: Bacula LinSrv-dir 9.4.2 (04Feb19):
If I stop the system service and start it manually from command line
with "bacula-sd -d 200 -c /opt/bacula/etc/bacula-sd.conf" command then I
can get status of storage daemon and the backups are working as
expected. I couldn't see any errors.
I tried to reinstall bacula but no luck. The system is uptodate Debian
Stretch 9.7, Bacula 9.4.2 installed with community setup script.
I would be grateful for any kind of help and tip.
Best regards.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
