On Fri, Apr 20, 2007 at 04:59:33PM -0700, Ross Boylan wrote:
On Fri, Apr 20, 2007 at 06:51:18PM -0500, John Goerzen wrote:
On Fri, Apr 20, 2007 at 04:07:14PM -0700, Ross Boylan wrote:
All of this is reminding me of why I held off on the upgrade. Is it
to late for me to downgrade back to
On Fri, Apr 20, 2007 at 10:51:12PM -0700, Ross Boylan wrote:
There are at least two problems that might thwart an automatic
upgrade:
1) configuration files contain invalid parameters.
That is true, but we can't do anything about that automatically.
2) databases in non-standard places or
On Sat, Apr 21, 2007 at 09:31:07AM -0500, John Goerzen wrote:
On Fri, Apr 20, 2007 at 10:51:12PM -0700, Ross Boylan wrote:
There are at least two problems that might thwart an automatic
upgrade:
1) configuration files contain invalid parameters.
That is true, but we can't do anything
Package: bacula-director-pgsql
Version: 2.0.3-2
Severity: normal
May warrant higher severity; I don't know what shape bacula is in, and
my current dist-upgrade appears to be hung (though during the setup of
a different package).
I would appreciate knowing if my installation is OK and, if not,
On Fri, Apr 20, 2007 at 11:11:07AM -0700, Ross Boylan wrote:
Ok.
Stopping Bacula Director: bacula-dir.
Starting Bacula Director: 20-Apr 10:35 bacula-dir: ERROR TERMINATION at
parse_conf.c:884
Config error: Keyword AcceptAnyVolume not permitted in this resource.
Perhaps you left the trailing
On Fri, Apr 20, 2007 at 02:34:02PM -0500, John Goerzen wrote:
On Fri, Apr 20, 2007 at 11:11:07AM -0700, Ross Boylan wrote:
Ok.
Stopping Bacula Director: bacula-dir.
Starting Bacula Director: 20-Apr 10:35 bacula-dir: ERROR TERMINATION at
parse_conf.c:884
Config error: Keyword
On Fri, Apr 20, 2007 at 06:51:18PM -0500, John Goerzen wrote:
On Fri, Apr 20, 2007 at 04:07:14PM -0700, Ross Boylan wrote:
All of this is reminding me of why I held off on the upgrade. Is it
to late for me to downgrade back to the version I was using?
If the database did not get
On Fri, Apr 20, 2007 at 04:07:14PM -0700, Ross Boylan wrote:
All of this is reminding me of why I held off on the upgrade. Is it
to late for me to downgrade back to the version I was using?
If the database did not get successfully upgraded, and the configuration
is unmodified, it should work
The first error is
Setting up bacula-director-pgsql (2.0.3-2) ...
Installing new version of config file /etc/bacula/scripts/make_catalog_backup
...
dbconfig-common: writing config to
/etc/dbconfig-common/bacula-director-pgsql.conf
Replacing config file
9 matches
Mail list logo
