Your message dated Wed, 21 Sep 2016 00:13:08 +0200
with message-id <8737ku6wzv....@arioch.leonhardt.eu>
and subject line Re: Bug#584135: bacula-director-mysql: "Max Run Time"
directive does not work as described
has caused the Debian Bug report #584135,
regarding bacula-director-mysql: "Max Run Time" directive does not work as
described
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
584135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bacula-director-mysql
Version: 5.0.1-1~bpo50+1
Severity: normal
Hi,
The "Max Run Time" directive for Bacula Director is described at [1] like this:
| Max Run Time = time
| The time specifies the maximum allowed time that a job may run, counted from
| when the job starts, (not necessarily the same as when the job was
scheduled).
However, the job start is something like 10 seconds from the scheduled time even
if the job never starts due to waiting in the queue of SD. The end result is
that
even if the job never runs, the job is cancelled after the time expires as if
"Max Run Sched Time" was specified instead of "Max Run Time". See attached a log
for such a job as an example.
Thanks
[1] http://www.bacula.org/5.0.x-manuals/en/main/main/Configuring_Director.html
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT policy: (990, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bacula-director-mysql depends on:
ii bacula-common 5.0.1-1~bpo50+1 network backup, recovery and verif
ii bacula-common-mysql 5.0.1-1~bpo50+1 network backup, recovery and verif
ii bacula-director-common 5.0.1-1~bpo50+1 network backup, recovery and verif
ii dbconfig-common 1.8.39 common framework for packaging dat
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii libc6 2.7-18lenny2 GNU C Library: Shared libraries
ii libgcc1 1:4.3.2-1.1 GCC support library
ii libmysqlclient15off 5.0.51a-24+lenny3 MySQL database client library
ii libssl0.9.8 0.9.8g-15+lenny6 SSL shared libraries
ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3
ii libwrap0 7.6.q-16 Wietse Venema's TCP wrappers libra
ii mysql-client-5.0 [mysq 5.0.51a-24+lenny3 MySQL database client binaries
ii python2.5 2.5.2-15+lenny1 An interactive high-level object-o
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages bacula-director-mysql recommends:
ii mysql-server 5.0.51a-24+lenny3 MySQL database server (metapackage
ii mysql-server-5.0 [mysq 5.0.51a-24+lenny3 MySQL database server binaries
bacula-director-mysql suggests no packages.
-- debconf information:
bacula-director-mysql/passwords-do-not-match:
bacula-director-mysql/mysql/admin-user: root
bacula-director-mysql/dbconfig-upgrade: true
bacula-director-mysql/purge: false
bacula-director-mysql/remove-error: abort
bacula-director-mysql/missing-db-package-error: abort
bacula-director-mysql/remote/newhost:
bacula-director-mysql/internal/skip-preseed: false
* bacula-director-mysql/dbconfig-install: true
bacula-director-mysql/db/app-user: bacula
bacula-director-mysql/upgrade-backup: true
bacula-director-mysql/database-type: mysql
bacula-director-mysql/install-error: abort
bacula-director-mysql/db/dbname: bacula
bacula-director-mysql/mysql/method: unix socket
bacula-director-mysql/remote/host:
bacula-director-mysql/internal/reconfiguring: false
bacula-director-mysql/upgrade-error: abort
bacula-director-mysql/dbconfig-reinstall: false
bacula-director-mysql/remote/port:
bacula-director-mysql/dbconfig-remove:
28-May 00:40 hercules-dir JobId 422: No prior Full backup Job record found.
28-May 00:40 hercules-dir JobId 422: No prior or suitable Full backup found in catalog. Doing FULL backup.
28-May 02:40 hercules-dir JobId 422: Fatal error: Max run time exceeded. Job canceled.
28-May 02:40 hercules-dir JobId 422: Bacula hercules-dir 5.0.1 (24Feb10): 28-May-2010 02:40:14
Build OS: i486-pc-linux-gnu debian 5.0.4
JobId: 422
Job: cobra--maildir-teodor_backup.2010-05-28_00.40.01_03
Backup Level: Full (upgraded from Incremental)
Client: "cobra" 5.0.1 (24Feb10) x86_64-pc-linux-gnu,debian,5.0.4
FileSet: "cobra--maildir-teodor_fileset" 2010-05-28 00:40:01
Pool: "cobra--maildir-teodor_pool" (From Job resource)
Catalog: "MyCatalog" (From Client resource)
Storage: "hercules--cobra_filestorage" (From Job resource)
Scheduled time: 28-May-2010 00:40:01
Start time: 28-May-2010 02:40:14
End time: 28-May-2010 02:40:14
Elapsed time: 0 secs
Priority: 10
FD Files Written: 0
SD Files Written: 0
FD Bytes Written: 0 (0 B)
SD Bytes Written: 0 (0 B)
Rate: 0.0 KB/s
Software Compression: None
VSS: no
Encryption: no
Accurate: no
Volume name(s):
Volume Session Id: 0
Volume Session Time: 0
Last Volume Bytes: 0 (0 B)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status:
SD termination status:
Termination: Backup Canceled
--- End Message ---
--- Begin Message ---
Version: 7.4.3+dfsg-1
Hi Teodor,
I've tested the "Max Run Time" directive in the current version 7.4.3
and there it apparently works as expected.
Therefore I'm closing this bug.
In case you are still experiencing this bug on a current version of
bacula, please reply to this email.
- Carsten
--- End Message ---
