Menu
▾
▴
bacula-bugs — To receive copies of Bacula bugs only -- do not submit to it.
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(149) |
Jul
(77) |
Aug
(75) |
Sep
(181) |
Oct
(120) |
Nov
(109) |
Dec
(138) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(37) |
Feb
(111) |
Mar
(115) |
Apr
(90) |
May
(135) |
Jun
(116) |
Jul
(93) |
Aug
(63) |
Sep
(73) |
Oct
(100) |
Nov
(145) |
Dec
(90) |
| 2006 |
Jan
(54) |
Feb
(79) |
Mar
(159) |
Apr
(70) |
May
(55) |
Jun
(92) |
Jul
(33) |
Aug
(70) |
Sep
(68) |
Oct
(107) |
Nov
(34) |
Dec
|
| 2007 |
Jan
|
Feb
(76) |
Mar
(96) |
Apr
(126) |
May
(107) |
Jun
(90) |
Jul
(95) |
Aug
(94) |
Sep
(159) |
Oct
(143) |
Nov
(114) |
Dec
(46) |
| 2008 |
Jan
(110) |
Feb
(62) |
Mar
(81) |
Apr
(101) |
May
(49) |
Jun
(100) |
Jul
(112) |
Aug
(102) |
Sep
(88) |
Oct
(72) |
Nov
(121) |
Dec
(79) |
| 2009 |
Jan
(50) |
Feb
(93) |
Mar
(139) |
Apr
(110) |
May
(122) |
Jun
(114) |
Jul
(149) |
Aug
(117) |
Sep
(96) |
Oct
(118) |
Nov
(112) |
Dec
(25) |
| 2010 |
Jan
(45) |
Feb
(206) |
Mar
(123) |
Apr
(147) |
May
(121) |
Jun
(68) |
Jul
(84) |
Aug
(77) |
Sep
(50) |
Oct
(34) |
Nov
(49) |
Dec
(31) |
| 2011 |
Jan
(65) |
Feb
(74) |
Mar
(72) |
Apr
(62) |
May
(50) |
Jun
(25) |
Jul
(47) |
Aug
(43) |
Sep
(35) |
Oct
(58) |
Nov
(90) |
Dec
(67) |
| 2012 |
Jan
(82) |
Feb
(44) |
Mar
(95) |
Apr
(60) |
May
(77) |
Jun
(118) |
Jul
(53) |
Aug
(14) |
Sep
(88) |
Oct
(41) |
Nov
(53) |
Dec
(37) |
| 2013 |
Jan
(48) |
Feb
(66) |
Mar
|
Apr
(54) |
May
(50) |
Jun
(7) |
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(64) |
Mar
(67) |
Apr
(40) |
May
(72) |
Jun
(42) |
Jul
(99) |
Aug
(40) |
Sep
(8) |
Oct
(3) |
Nov
(16) |
Dec
(10) |
| 2015 |
Jan
(9) |
Feb
(8) |
Mar
(10) |
Apr
(14) |
May
(27) |
Jun
(12) |
Jul
(38) |
Aug
(55) |
Sep
(27) |
Oct
(43) |
Nov
(11) |
Dec
(46) |
| 2016 |
Jan
(46) |
Feb
(37) |
Mar
(24) |
Apr
(3) |
May
(16) |
Jun
(17) |
Jul
(49) |
Aug
(7) |
Sep
|
Oct
(61) |
Nov
(11) |
Dec
(17) |
| 2017 |
Jan
(13) |
Feb
(12) |
Mar
(29) |
Apr
(5) |
May
(67) |
Jun
(21) |
Jul
(61) |
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <bac...@li...> - 2004-08-09 21:29:04
|
The following bug has been SUBMITTED. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000081 ====================================================================== Reported By: Dan Langille Assigned To: ====================================================================== Project: bacula Bug ID: 81 Category: bconsole Reproducibility: always Severity: block Priority: normal Status: new ====================================================================== Date Submitted: 08-09-2004 14:29 GMT Last Modified: 08-09-2004 14:29 GMT ====================================================================== Summary: compile of console fails to find get_cmd Description: ==== Make of filed is good ==== /usr/bin/install -c -o root -g wheel -s -m 0754 bacula-fd /usr/local/sbin/bacula-fd ==> Found existing bacula-fd.conf, installing new conf file as bacula-fd.conf.new /usr/bin/install -c -o root -g wheel -m 640 bacula-fd.conf /usr/local/etc/bacula-fd.conf.new c++ -L/usr/local/lib -pthread -L../lib -L../cats -o bconsole console.o console_conf.o authenticate.o -lbac -lm -D_THREAD_SAFE -lwrap -lxpg4 console.o: In function `read_and_process_input(__sFILE *, BSOCK *)': console.o(.text+0x1c2): undefined reference to `get_cmd(__sFILE *, char *, BSOCK *, int)' console.o: In function `main': console.o(.text+0x7cc): undefined reference to `get_cmd(__sFILE *, char *, BSOCK *, int)' *** Error code 1 Stop in /usr/ports/sysutils/bacula/work/bacula-1.34.6/src/console. *** Error code 1 Stop in /usr/ports/sysutils/bacula/work/bacula-1.34.6. *** Error code 1 Stop in /usr/ports/sysutils/bacula. *** Error code 1 Stop in /usr/ports/sysutils/bacula. ====================================================================== Bug History Date Modified Username Field Change ====================================================================== 08-09-04 14:29 Dan Langille New Bug ====================================================================== |
|
From: <bac...@li...> - 2004-08-09 16:24:47
|
A BUGNOTE has been added to this bug. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000079 ====================================================================== Reported By: scoopex Assigned To: Dan Langille ====================================================================== Project: bacula Bug ID: 79 Category: PostgreSQL Reproducibility: always Severity: feature Priority: normal Status: assigned ====================================================================== Date Submitted: 08-09-2004 02:45 GMT Last Modified: 08-09-2004 03:09 GMT ====================================================================== Summary: problems while creating tables Description: all of the scripts use statements like that: -- root@backup3: # grep psql * create_postgresql_database:if $bindir/psql template1 $* -f - <<END-OF-DATA drop_postgresql_tables:if $bindir/psql $* -f - <<END-OF-DATA grant_postgresql_privileges:if $bindir/psql $* bacula -f - <<END-OF-DATA make_catalog_backup:# psql bacula <bacula.sql make_postgresql_tables:if $bindir/psql $* bacula -f - <<END-OF-DATA update_postgresql_tables:if $bindir/psql $* -f - <<END-OF-DATA -- PostgreSQL 7.4.3 doesn´t know/allow "-f -" - this is a fragment of the mysql-install-process - so the execution failed. ()as described in the install-manual of postgresql) PostgreSQL mostly uses the user "postgres" for performing database-operations - doing this operations with the "root"-user sometimes does not work. Removing "-f -" solved my problem. Maybe using "createuser" and "creatdb" would be a also a option. ====================================================================== ---------------------------------------------------------------------- scoopex - 08-09-2004 03:09 GMT ---------------------------------------------------------------------- Sorry, this is not a feature-request - it´s a bug :-) I forgot to change the report-type.... Bug History Date Modified Username Field Change ====================================================================== 08-09-04 02:45 scoopex New Bug 08-09-04 03:09 scoopex Bugnote Added: 0000154 ====================================================================== |
|
From: <bac...@li...> - 2004-08-09 16:24:47
|
The following bug has been CLOSED ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000076 ====================================================================== Reported By: kern Assigned To: ====================================================================== Project: bacula Bug ID: 76 Category: Director Reproducibility: always Severity: major Priority: normal Status: closed ====================================================================== Date Submitted: 08-09-2004 00:00 GMT Last Modified: 08-09-2004 00:01 GMT ====================================================================== Summary: New FileSet Excludes do not work Description: The new FileSet Exclude does not exclude a directory if that directory has been modified. ====================================================================== Bug History Date Modified Username Field Change ====================================================================== 08-09-04 00:00 kern New Bug 08-09-04 00:00 kern File Added: 1.34.6-find.patch 08-09-04 00:01 kern Resolution open => fixed 08-09-04 00:01 kern Status new => closed ====================================================================== |
|
From: <bac...@li...> - 2004-08-09 16:24:47
|
The following bug has been SUBMITTED. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000076 ====================================================================== Reported By: kern Assigned To: ====================================================================== Project: bacula Bug ID: 76 Category: Director Reproducibility: always Severity: major Priority: normal Status: new ====================================================================== Date Submitted: 08-09-2004 00:00 GMT Last Modified: 08-09-2004 00:00 GMT ====================================================================== Summary: New FileSet Excludes do not work Description: The new FileSet Exclude does not exclude a directory if that directory has been modified. ====================================================================== Bug History Date Modified Username Field Change ====================================================================== 08-09-04 00:00 kern New Bug 08-09-04 00:00 kern File Added: 1.34.6-find.patch ====================================================================== |
|
From: <bac...@li...> - 2004-08-09 16:24:47
|
The following bug has been CLOSED ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000077 ====================================================================== Reported By: kern Assigned To: ====================================================================== Project: bacula Bug ID: 77 Category: Director Reproducibility: always Severity: trivial Priority: normal Status: closed ====================================================================== Date Submitted: 08-09-2004 00:07 GMT Last Modified: 08-09-2004 00:08 GMT ====================================================================== Summary: Bacula prints 5000 messages on update slots Description: I am using a 10 slot tape changer (one is hidden by the hardware as that [1] I slot contains a cleaning tape). I ran update slots today. 1000 OK: backup.example.com Version: 1.34.5 (21 June 2004) Enter a period to cancel a command. *update slots Using default Catalog name=MyCatalog DB=bacula Automatically selected Storage: DDS-4 Connecting to Storage daemon DDS-4 at backup.example.com:9103 ... 3301 Issuing autochanger "loaded drive 0" command. 3302 Autochanger "loaded drive 0", result: nothing loaded. 3306 Issuing autochanger "list" command. Catalog record for Volume "A0000001" is up to date. Catalog record for Volume "A0000002" is up to date. Catalog record for Volume "A0000003" is up to date. Catalog record for Volume "A0000004" is up to date. Catalog record for Volume "A0000005" is up to date. Catalog record for Volume "A0000006" is up to date. Catalog record for Volume "A0000008" is up to date. Catalog record for Volume "A0000009" is up to date. Catalog record for Volume "A0000010" is up to date. No VolName for Slot=10 set InChanger to zero. No VolName for Slot=11 set InChanger to zero. No VolName for Slot=12 set InChanger to zero. No VolName for Slot=13 set InChanger to zero. ... No VolName for Slot=4996 set InChanger to zero. No VolName for Slot=4997 set InChanger to zero. No VolName for Slot=4998 set InChanger to zero. No VolName for Slot=4999 set InChanger to zero. * Why did it go so high? FYI: $ sudo /usr/local/sbin/mtx -f /dev/pass0 status Storage Changer /dev/pass0:1 Drives, 9 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Storage Element 1:Full :VolumeTag=A0000001 Storage Element 2:Full :VolumeTag=A0000002 Storage Element 3:Full :VolumeTag=A0000003 Storage Element 4:Full :VolumeTag=A0000004 Storage Element 5:Full :VolumeTag=A0000005 Storage Element 6:Full :VolumeTag=A0000006 Storage Element 7:Full :VolumeTag=A0000008 Storage Element 8:Full :VolumeTag=A0000009 Storage Element 9:Full :VolumeTag=A0000010 mysql> select MediaId, VolumeName, Slot, InChanger from Media; +---------+------------+------+-----------+ | MediaId | VolumeName | Slot | InChanger | +---------+------------+------+-----------+ | 1 | A0000001 | 1 | 1 | | 2 | A0000002 | 2 | 1 | | 3 | A0000003 | 3 | 1 | | 4 | A0000004 | 4 | 1 | | 5 | A0000005 | 5 | 1 | | 6 | A0000006 | 6 | 1 | | 7 | A0000008 | 7 | 1 | | 8 | A0000009 | 8 | 1 | | 9 | A0000010 | 9 | 1 | | 10 | B0000001 | 1 | 0 | | 11 | B0000002 | 2 | 0 | | 12 | B0000003 | 3 | 0 | | 13 | B0000004 | 4 | 0 | | 14 | B0000005 | 5 | 0 | | 15 | B0000006 | 6 | 0 | | 16 | B0000007 | 7 | 0 | | 17 | B0000008 | 8 | 0 | | 18 | B0000009 | 9 | 0 | +---------+------------+------+-----------+ 18 rows in set (0.00 sec) ====================================================================== ---------------------------------------------------------------------- kern - 08-09-2004 00:08 GMT ---------------------------------------------------------------------- Bug report originally submitted by Dan Langille. Bug History Date Modified Username Field Change ====================================================================== 08-09-04 00:07 kern New Bug 08-09-04 00:07 kern File Added: 1.34.6-slots.patch 08-09-04 00:08 kern Bugnote Added: 0000152 08-09-04 00:08 kern Resolution open => fixed 08-09-04 00:08 kern Status new => closed ====================================================================== |
|
From: <bac...@li...> - 2004-08-09 16:24:47
|
A BUGNOTE has been added to this bug. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000079 ====================================================================== Reported By: scoopex Assigned To: Dan Langille ====================================================================== Project: bacula Bug ID: 79 Category: PostgreSQL Reproducibility: always Severity: feature Priority: normal Status: assigned ====================================================================== Date Submitted: 08-09-2004 02:45 GMT Last Modified: 08-09-2004 06:38 GMT ====================================================================== Summary: problems while creating tables Description: all of the scripts use statements like that: -- root@backup3: # grep psql * create_postgresql_database:if $bindir/psql template1 $* -f - <<END-OF-DATA drop_postgresql_tables:if $bindir/psql $* -f - <<END-OF-DATA grant_postgresql_privileges:if $bindir/psql $* bacula -f - <<END-OF-DATA make_catalog_backup:# psql bacula <bacula.sql make_postgresql_tables:if $bindir/psql $* bacula -f - <<END-OF-DATA update_postgresql_tables:if $bindir/psql $* -f - <<END-OF-DATA -- PostgreSQL 7.4.3 doesn´t know/allow "-f -" - this is a fragment of the mysql-install-process - so the execution failed. ()as described in the install-manual of postgresql) PostgreSQL mostly uses the user "postgres" for performing database-operations - doing this operations with the "root"-user sometimes does not work. Removing "-f -" solved my problem. Maybe using "createuser" and "creatdb" would be a also a option. ====================================================================== ---------------------------------------------------------------------- scoopex - 08-09-2004 03:09 GMT ---------------------------------------------------------------------- Sorry, this is not a feature-request - it´s a bug :-) I forgot to change the report-type.... ---------------------------------------------------------------------- kern - 08-09-2004 06:36 GMT ---------------------------------------------------------------------- Can I assume that since you created the scripts, found the problem, and propose removing the -f option, that you will be submitting a patch? Concerning createuser and createdb -- maybe but if it is not *absolutely* necessary, I would prefer not as it will complicated the documentation and the scripts, especially concerning other DBs. ---------------------------------------------------------------------- kern - 08-09-2004 06:38 GMT ---------------------------------------------------------------------- Oops -- I saw Dan's name, and mistakenly assumed he was the author of the bug -- not true. Please ignore my previous comment concerning submitting a fix. The second comment still applies. Bug History Date Modified Username Field Change ====================================================================== 08-09-04 02:45 scoopex New Bug 08-09-04 03:09 scoopex Bugnote Added: 0000154 08-09-04 06:36 kern Bugnote Added: 0000155 08-09-04 06:38 kern Bugnote Added: 0000156 ====================================================================== |
|
From: <bac...@li...> - 2004-08-09 16:24:47
|
The following bug has been SUBMITTED. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000080 ====================================================================== Reported By: scoopex Assigned To: ====================================================================== Project: bacula Bug ID: 80 Category: Director Reproducibility: always Severity: feature Priority: normal Status: new ====================================================================== Date Submitted: 08-09-2004 03:07 GMT Last Modified: 08-09-2004 03:07 GMT ====================================================================== Summary: adding a index fo file:jobid Description: I saw many times in "mytop", that there are SQL-statements which use "jobid" in the where-clause for operations in the "file"-table. -- create index file_file_jobid_idx on file (jobid); -- I´m really sure that queries which reference "jobid" on the "file"-table are very widespread...so an index would be helpful ? ====================================================================== Bug History Date Modified Username Field Change ====================================================================== 08-09-04 03:07 scoopex New Bug ====================================================================== |
|
From: <bac...@li...> - 2004-08-09 16:24:47
|
A BUGNOTE has been added to this bug. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000072 ====================================================================== Reported By: jhreiche Assigned To: ====================================================================== Project: bacula Bug ID: 72 Category: Director Reproducibility: always Severity: crash Priority: normal Status: feedback ====================================================================== Date Submitted: 08-06-2004 00:47 GMT Last Modified: 08-08-2004 13:13 GMT ====================================================================== Summary: bacula-dir kabooms at run command Description: I installed Bacula on three systems: bacula-dir Version: 1.34.5 (21 June 2004) i586-pc-linux-gnu suse 9.0 bacula_ts-sd Version: 1.34.5 (21 June 2004) i586-pc-linux-gnu suse 9.0 linux2-fd Version: 1.34.2 (24 Apr 2004) i686-suse-linux-gnu suse 9.0 After setting the fileset and so on, I tried to "run" "linux2ts" wich should backup linux2 to tapes, but the director daemon crashes. You can see the traceback output in additional information. In former times I run bacula on a RedHat 9.0 Linux. Maybe the problem is the result of a different library version. It's maybe a database failure. I'll try to test it today ... ====================================================================== ---------------------------------------------------------------------- kern - 08-06-2004 12:12 GMT ---------------------------------------------------------------------- Thanks for the traceback -- it gets very close to the problem. It looks like something has gone wrong in your Catalog resource. To go further, you will need to run the director under the debugger as described in the Kaboom chapter of the manual, and when it stops, enter the following commands: print *jcr print *jcr->catalog That should help me get a bit farther. ---------------------------------------------------------------------- jhreiche - 08-08-2004 13:13 GMT ---------------------------------------------------------------------- Hi!, I will be on holiday till 18.8.2004. So it will take some time till I can report the output from the debugger. Regards, Jan He. Bug History Date Modified Username Field Change ====================================================================== 08-06-04 00:47 jhreiche New Bug 08-06-04 12:12 kern Bugnote Added: 0000148 08-06-04 12:12 kern Status new => feedback 08-06-04 12:12 kern version => 1.34.5 08-08-04 13:13 jhreiche Bugnote Added: 0000151 ====================================================================== |
|
From: <bac...@li...> - 2004-08-09 16:24:41
|
The following bug has been SUBMITTED. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000077 ====================================================================== Reported By: kern Assigned To: ====================================================================== Project: bacula Bug ID: 77 Category: Director Reproducibility: always Severity: trivial Priority: normal Status: new ====================================================================== Date Submitted: 08-09-2004 00:07 GMT Last Modified: 08-09-2004 00:07 GMT ====================================================================== Summary: Bacula prints 5000 messages on update slots Description: I am using a 10 slot tape changer (one is hidden by the hardware as that [1] I slot contains a cleaning tape). I ran update slots today. 1000 OK: backup.example.com Version: 1.34.5 (21 June 2004) Enter a period to cancel a command. *update slots Using default Catalog name=MyCatalog DB=bacula Automatically selected Storage: DDS-4 Connecting to Storage daemon DDS-4 at backup.example.com:9103 ... 3301 Issuing autochanger "loaded drive 0" command. 3302 Autochanger "loaded drive 0", result: nothing loaded. 3306 Issuing autochanger "list" command. Catalog record for Volume "A0000001" is up to date. Catalog record for Volume "A0000002" is up to date. Catalog record for Volume "A0000003" is up to date. Catalog record for Volume "A0000004" is up to date. Catalog record for Volume "A0000005" is up to date. Catalog record for Volume "A0000006" is up to date. Catalog record for Volume "A0000008" is up to date. Catalog record for Volume "A0000009" is up to date. Catalog record for Volume "A0000010" is up to date. No VolName for Slot=10 set InChanger to zero. No VolName for Slot=11 set InChanger to zero. No VolName for Slot=12 set InChanger to zero. No VolName for Slot=13 set InChanger to zero. ... No VolName for Slot=4996 set InChanger to zero. No VolName for Slot=4997 set InChanger to zero. No VolName for Slot=4998 set InChanger to zero. No VolName for Slot=4999 set InChanger to zero. * Why did it go so high? FYI: $ sudo /usr/local/sbin/mtx -f /dev/pass0 status Storage Changer /dev/pass0:1 Drives, 9 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Storage Element 1:Full :VolumeTag=A0000001 Storage Element 2:Full :VolumeTag=A0000002 Storage Element 3:Full :VolumeTag=A0000003 Storage Element 4:Full :VolumeTag=A0000004 Storage Element 5:Full :VolumeTag=A0000005 Storage Element 6:Full :VolumeTag=A0000006 Storage Element 7:Full :VolumeTag=A0000008 Storage Element 8:Full :VolumeTag=A0000009 Storage Element 9:Full :VolumeTag=A0000010 mysql> select MediaId, VolumeName, Slot, InChanger from Media; +---------+------------+------+-----------+ | MediaId | VolumeName | Slot | InChanger | +---------+------------+------+-----------+ | 1 | A0000001 | 1 | 1 | | 2 | A0000002 | 2 | 1 | | 3 | A0000003 | 3 | 1 | | 4 | A0000004 | 4 | 1 | | 5 | A0000005 | 5 | 1 | | 6 | A0000006 | 6 | 1 | | 7 | A0000008 | 7 | 1 | | 8 | A0000009 | 8 | 1 | | 9 | A0000010 | 9 | 1 | | 10 | B0000001 | 1 | 0 | | 11 | B0000002 | 2 | 0 | | 12 | B0000003 | 3 | 0 | | 13 | B0000004 | 4 | 0 | | 14 | B0000005 | 5 | 0 | | 15 | B0000006 | 6 | 0 | | 16 | B0000007 | 7 | 0 | | 17 | B0000008 | 8 | 0 | | 18 | B0000009 | 9 | 0 | +---------+------------+------+-----------+ 18 rows in set (0.00 sec) ====================================================================== Bug History Date Modified Username Field Change ====================================================================== 08-09-04 00:07 kern New Bug 08-09-04 00:07 kern File Added: 1.34.6-slots.patch ====================================================================== |
|
From: <bac...@li...> - 2004-08-09 16:24:41
|
A BUGNOTE has been added to this bug. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000079 ====================================================================== Reported By: scoopex Assigned To: Dan Langille ====================================================================== Project: bacula Bug ID: 79 Category: PostgreSQL Reproducibility: always Severity: feature Priority: normal Status: assigned ====================================================================== Date Submitted: 08-09-2004 02:45 GMT Last Modified: 08-09-2004 06:36 GMT ====================================================================== Summary: problems while creating tables Description: all of the scripts use statements like that: -- root@backup3: # grep psql * create_postgresql_database:if $bindir/psql template1 $* -f - <<END-OF-DATA drop_postgresql_tables:if $bindir/psql $* -f - <<END-OF-DATA grant_postgresql_privileges:if $bindir/psql $* bacula -f - <<END-OF-DATA make_catalog_backup:# psql bacula <bacula.sql make_postgresql_tables:if $bindir/psql $* bacula -f - <<END-OF-DATA update_postgresql_tables:if $bindir/psql $* -f - <<END-OF-DATA -- PostgreSQL 7.4.3 doesn´t know/allow "-f -" - this is a fragment of the mysql-install-process - so the execution failed. ()as described in the install-manual of postgresql) PostgreSQL mostly uses the user "postgres" for performing database-operations - doing this operations with the "root"-user sometimes does not work. Removing "-f -" solved my problem. Maybe using "createuser" and "creatdb" would be a also a option. ====================================================================== ---------------------------------------------------------------------- scoopex - 08-09-2004 03:09 GMT ---------------------------------------------------------------------- Sorry, this is not a feature-request - it´s a bug :-) I forgot to change the report-type.... ---------------------------------------------------------------------- kern - 08-09-2004 06:36 GMT ---------------------------------------------------------------------- Can I assume that since you created the scripts, found the problem, and propose removing the -f option, that you will be submitting a patch? Concerning createuser and createdb -- maybe but if it is not *absolutely* necessary, I would prefer not as it will complicated the documentation and the scripts, especially concerning other DBs. Bug History Date Modified Username Field Change ====================================================================== 08-09-04 02:45 scoopex New Bug 08-09-04 03:09 scoopex Bugnote Added: 0000154 08-09-04 06:36 kern Bugnote Added: 0000155 ====================================================================== |
|
From: <bac...@li...> - 2004-08-09 16:24:41
|
The following bug has been CLOSED ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000078 ====================================================================== Reported By: kern Assigned To: ====================================================================== Project: bacula Bug ID: 78 Category: Director Reproducibility: always Severity: feature Priority: normal Status: closed ====================================================================== Date Submitted: 08-09-2004 00:10 GMT Last Modified: 08-09-2004 00:15 GMT ====================================================================== Summary: The director deadlocks Description: Occasionally everything stops with a deadlock in the Directory. ====================================================================== ---------------------------------------------------------------------- kern - 08-09-2004 00:15 GMT ---------------------------------------------------------------------- This is caused by a mutex conflict between the job queue scheduler and the watchdog thread. The patch attached to this bug report should fix the problem. In addition, the patch corrects an improper initialization of the watchdog's queues which could cause a memory corruption. The documentation on how to apply the patch is at the top of the patch file. Bug History Date Modified Username Field Change ====================================================================== 08-09-04 00:10 kern New Bug 08-09-04 00:13 kern File Added: 1.34.6-deadlock.patch 08-09-04 00:15 kern Bugnote Added: 0000153 08-09-04 00:15 kern Resolution open => fixed 08-09-04 00:15 kern Status new => closed ====================================================================== |
|
From: <bac...@li...> - 2004-08-09 16:24:41
|
The following bug has been SUBMITTED. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000078 ====================================================================== Reported By: kern Assigned To: ====================================================================== Project: bacula Bug ID: 78 Category: Director Reproducibility: always Severity: feature Priority: normal Status: new ====================================================================== Date Submitted: 08-09-2004 00:10 GMT Last Modified: 08-09-2004 00:10 GMT ====================================================================== Summary: The director deadlocks Description: Occasionally everything stops with a deadlock in the Directory. ====================================================================== Bug History Date Modified Username Field Change ====================================================================== 08-09-04 00:10 kern New Bug ====================================================================== |
|
From: <bac...@li...> - 2004-08-09 16:24:41
|
The following bug has been SUBMITTED. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000079 ====================================================================== Reported By: scoopex Assigned To: Dan Langille ====================================================================== Project: bacula Bug ID: 79 Category: PostgreSQL Reproducibility: always Severity: feature Priority: normal Status: assigned ====================================================================== Date Submitted: 08-09-2004 02:45 GMT Last Modified: 08-09-2004 02:45 GMT ====================================================================== Summary: problems while creating tables Description: all of the scripts use statements like that: -- root@backup3: # grep psql * create_postgresql_database:if $bindir/psql template1 $* -f - <<END-OF-DATA drop_postgresql_tables:if $bindir/psql $* -f - <<END-OF-DATA grant_postgresql_privileges:if $bindir/psql $* bacula -f - <<END-OF-DATA make_catalog_backup:# psql bacula <bacula.sql make_postgresql_tables:if $bindir/psql $* bacula -f - <<END-OF-DATA update_postgresql_tables:if $bindir/psql $* -f - <<END-OF-DATA -- PostgreSQL 7.4.3 doesn´t know/allow "-f -" - this is a fragment of the mysql-install-process - so the execution failed. ()as described in the install-manual of postgresql) PostgreSQL mostly uses the user "postgres" for performing database-operations - doing this operations with the "root"-user sometimes does not work. Removing "-f -" solved my problem. Maybe using "createuser" and "creatdb" would be a also a option. ====================================================================== Bug History Date Modified Username Field Change ====================================================================== 08-09-04 02:45 scoopex New Bug ====================================================================== |
|
From: <bac...@li...> - 2004-08-07 12:00:26
|
The following bug has been CLOSED ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000075 ====================================================================== Reported By: barninger Assigned To: ====================================================================== Project: bacula Bug ID: 75 Category: configure/build process Reproducibility: always Severity: major Priority: normal Status: closed ====================================================================== Date Submitted: 08-06-2004 15:15 GMT Last Modified: 08-07-2004 05:00 GMT ====================================================================== Summary: Gnome 1.x Makefile for gnome-console is broken Description: The Makefile for the gnome-console in the released tarball for 1.34.6 is broken due to the inadvertant addition of changes intended for the gnome2 version. Attempts to build on a gnome1 system will fail. src/gnome-console/Makefile.in is broken. ====================================================================== Bug History Date Modified Username Field Change ====================================================================== 08-06-04 15:15 barninger New Bug 08-06-04 15:15 barninger File Added: gnome-console-Makefile.in.patch 08-07-04 05:00 kern Resolution open => fixed 08-07-04 05:00 kern Status new => closed ====================================================================== |
|
From: <bac...@li...> - 2004-08-06 22:14:54
|
The following bug has been SUBMITTED. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000075 ====================================================================== Reported By: barninger Assigned To: ====================================================================== Project: bacula Bug ID: 75 Category: configure/build process Reproducibility: always Severity: major Priority: normal Status: new ====================================================================== Date Submitted: 08-06-2004 15:15 GMT Last Modified: 08-06-2004 15:15 GMT ====================================================================== Summary: Gnome 1.x Makefile for gnome-console is broken Description: The Makefile for the gnome-console in the released tarball for 1.34.6 is broken due to the inadvertant addition of changes intended for the gnome2 version. Attempts to build on a gnome1 system will fail. src/gnome-console/Makefile.in is broken. ====================================================================== Bug History Date Modified Username Field Change ====================================================================== 08-06-04 15:15 barninger New Bug 08-06-04 15:15 barninger File Added: gnome-console-Makefile.in.patch ====================================================================== |
|
From: <bac...@li...> - 2004-08-06 20:13:45
|
The following bug has been CLOSED ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000073 ====================================================================== Reported By: Dan Langille Assigned To: ====================================================================== Project: bacula Bug ID: 73 Category: Director Reproducibility: always Severity: tweak Priority: low Status: closed ====================================================================== Date Submitted: 08-06-2004 06:04 GMT Last Modified: 08-06-2004 13:14 GMT ====================================================================== Summary: Job IDs with commas aren't liked by restore Description: The Directory outputs Job IDs with a comma in them. But it doesn't like to use that as input. When I copy/paste a job id, it gets rejected. If I don't use the comma, it is accepted. This is a nice-to-have, because it is convenient to copy/paste the job id. Example follows: *restore First you select one or more JobIds that contain files to be restored. You will be presented several methods of specifying the JobIds. Then you will be allowed to select which files from those JobIds are to be restored. To select the JobIds, you have the following choices: 1: List last 20 Jobs run 2: List Jobs where a given File is saved 3: Enter list of JobIds to select 4: Enter SQL list command 5: Select the most recent backup for a client 6: Select backup for a client before a specified time 7: Enter a list of files to restore 8: Enter a list of files to restore before a specified time 9: Cancel Select item: (1-9): 2 freebsddiary-announce +-------+-----------+-------------------------------------------------------------------------+---------------------+---------+----------+-------------+ | JobId | Client | Name | StartTime | JobType | JobFiles | JobBytes | +-------+-----------+-------------------------------------------------------------------------+---------------------+---------+----------+-------------+ | 4,029 | nezlok-fd | /usr/local/majordomo/lists/lists.freebsddiary.org/freebsddiary-announce | 2004-07-17 04:02:51 | B | 164 | 25,870,998 | | 4,133 | nezlok-fd | /usr/local/majordomo/lists/lists.freebsddiary.org/freebsddiary-announce | 2004-07-25 03:39:05 | B | 211 | 35,683,858 | | 4,042 | nezlok-fd | /usr/local/majordomo/lists/lists.freebsddiary.org/freebsddiary-announce | 2004-07-18 04:19:31 | B | 208 | 27,969,224 | | 4,226 | lists-fd | /usr/local/majordomo/lists/freebsddiary.org/freebsddiary-announce | 2004-08-01 12:14:07 | B | 12,055 | 127,754,251 | +-------+-----------+-------------------------------------------------------------------------+---------------------+---------+----------+-------------+ To select the JobIds, you have the following choices: 1: List last 20 Jobs run 2: List Jobs where a given File is saved 3: Enter list of JobIds to select 4: Enter SQL list command 5: Select the most recent backup for a client 6: Select backup for a client before a specified time 7: Enter a list of files to restore 8: Enter a list of files to restore before a specified time 9: Cancel Select item: (1-9): 3 Enter JobId(s), comma separated, to restore: 4,226 You have selected the following JobIds: 4,226 Unable to get Job record. ERR=sql_get.c:281 No Job found for JobId 4 *restore First you select one or more JobIds that contain files to be restored. You will be presented several methods of specifying the JobIds. Then you will be allowed to select which files from those JobIds are to be restored. To select the JobIds, you have the following choices: 1: List last 20 Jobs run 2: List Jobs where a given File is saved 3: Enter list of JobIds to select 4: Enter SQL list command 5: Select the most recent backup for a client 6: Select backup for a client before a specified time 7: Enter a list of files to restore 8: Enter a list of files to restore before a specified time 9: Cancel Select item: (1-9): 3 Enter JobId(s), comma separated, to restore: 4226 You have selected the following JobId: 4226 Building directory tree for JobId 4226 ... 1 Job inserted into the tree and marked for extraction. The defined Storage resources are: 1: ArchivePython 2: ArchivePythonRemote Select Storage resource (1-2): ====================================================================== ---------------------------------------------------------------------- Dan Langille - 08-06-2004 09:25 GMT ---------------------------------------------------------------------- This is a test of the email notification. ---------------------------------------------------------------------- Dan Langille - 08-06-2004 09:33 GMT ---------------------------------------------------------------------- I just realised this: 3: Enter list of comma separated JobIds to select If a JobID contains a comma, we can't input it above.... This bugnote is really a test of the email notification system. ---------------------------------------------------------------------- Dan Langille - 08-06-2004 09:37 GMT ---------------------------------------------------------------------- Another test of the email notification system. ---------------------------------------------------------------------- TheBossAccount - 08-06-2004 10:21 GMT ---------------------------------------------------------------------- Ignore this bugnote. Testing email again. ---------------------------------------------------------------------- TheBossAccount - 08-06-2004 10:21 GMT ---------------------------------------------------------------------- another test ---------------------------------------------------------------------- kern - 08-06-2004 13:14 GMT ---------------------------------------------------------------------- Kludged in 1.35, but only for listings made from within the restore command. Bug History Date Modified Username Field Change ====================================================================== 08-06-04 06:04 Dan Langille New Bug 08-06-04 09:25 Dan Langille Bugnote Added: 0000142 08-06-04 09:33 Dan Langille Bugnote Added: 0000143 08-06-04 09:37 Dan Langille Bugnote Added: 0000144 08-06-04 10:21 TheBossAccount Bugnote Added: 0000145 08-06-04 10:21 TheBossAccount Bugnote Added: 0000146 08-06-04 13:14 kern Bugnote Added: 0000150 08-06-04 13:14 kern Resolution open => fixed 08-06-04 13:14 kern Status new => closed ====================================================================== |
|
From: <bac...@li...> - 2004-08-06 20:03:00
|
The following bug has been CLOSED ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000074 ====================================================================== Reported By: rowens Assigned To: ====================================================================== Project: bacula Bug ID: 74 Category: Director Reproducibility: always Severity: tweak Priority: normal Status: closed ====================================================================== Date Submitted: 08-06-2004 06:40 GMT Last Modified: 08-06-2004 13:03 GMT ====================================================================== Summary: Remove verify job records from database when purging Description: Verify job records are never removed from the database. Backup jobs are removed per the configured time parameters, but verify jobs hang around forever. ====================================================================== ---------------------------------------------------------------------- kern - 08-06-2004 13:03 GMT ---------------------------------------------------------------------- When manually pruning or purging, the operation only applies to Backup jobs. In some future version, I'll add code to allow the user to choose the job type. Currently, Verify jobs are removed from the database when they have a later InitCatalog record, and this regardless of the time you set -- otherwise current data gets wiped out. I did notice that failed jobs are not pruned, and will correct this in 1.35 Bug History Date Modified Username Field Change ====================================================================== 08-06-04 06:40 rowens New Bug 08-06-04 06:40 rowens File Added: bacula-dir.conf 08-06-04 13:03 kern Bugnote Added: 0000149 08-06-04 13:03 kern Resolution open => not a bug 08-06-04 13:03 kern Status new => closed ====================================================================== |
|
From: <bac...@li...> - 2004-08-06 19:11:37
|
The following bug requires your FEEDBACK. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000072 ====================================================================== Reported By: jhreiche Assigned To: ====================================================================== Project: bacula Bug ID: 72 Category: Director Reproducibility: always Severity: crash Priority: normal Status: feedback ====================================================================== Date Submitted: 08-06-2004 00:47 GMT Last Modified: 08-06-2004 12:12 GMT ====================================================================== Summary: bacula-dir kabooms at run command Description: I installed Bacula on three systems: bacula-dir Version: 1.34.5 (21 June 2004) i586-pc-linux-gnu suse 9.0 bacula_ts-sd Version: 1.34.5 (21 June 2004) i586-pc-linux-gnu suse 9.0 linux2-fd Version: 1.34.2 (24 Apr 2004) i686-suse-linux-gnu suse 9.0 After setting the fileset and so on, I tried to "run" "linux2ts" wich should backup linux2 to tapes, but the director daemon crashes. You can see the traceback output in additional information. In former times I run bacula on a RedHat 9.0 Linux. Maybe the problem is the result of a different library version. It's maybe a database failure. I'll try to test it today ... ====================================================================== ---------------------------------------------------------------------- kern - 08-06-2004 12:12 GMT ---------------------------------------------------------------------- Thanks for the traceback -- it gets very close to the problem. It looks like something has gone wrong in your Catalog resource. To go further, you will need to run the director under the debugger as described in the Kaboom chapter of the manual, and when it stops, enter the following commands: print *jcr print *jcr->catalog That should help me get a bit farther. Bug History Date Modified Username Field Change ====================================================================== 08-06-04 00:47 jhreiche New Bug 08-06-04 12:12 kern Bugnote Added: 0000148 08-06-04 12:12 kern Status new => feedback 08-06-04 12:12 kern version => 1.34.5 ====================================================================== |
|
From: <bac...@li...> - 2004-08-06 19:05:43
|
The following bug has been CLOSED ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000071 ====================================================================== Reported By: thgr Assigned To: ====================================================================== Project: bacula Bug ID: 71 Category: bconsole Reproducibility: always Severity: trivial Priority: normal Status: closed ====================================================================== Date Submitted: 08-05-2004 04:31 GMT Last Modified: 08-06-2004 12:06 GMT ====================================================================== Summary: update volumes: setting Volume Retention Period goes wrong Description: i need to set VolRetention on 6 day, 12 hours. in seconds it means 561600 sec. if you set the value, the result is 1 year an some days. i think, the commadn line should be "Enter Volume Retention period (minutes):" the confusion comes with the value shown in the table before. the value is there given in seconds. thanx thomas ====================================================================== ---------------------------------------------------------------------- kern - 08-06-2004 12:06 GMT ---------------------------------------------------------------------- Thanks for noticing this. You can now enter values of the same form that it prints at you, and I have reduced the confusion a bit by eliminating the "seconds" from the message. You can enter "1 day 2 hours 3 sec" for example. See patch for 1.34.6 attached to this bug report. The instructions are at the top of the file. Fixed in 1.35.1 CVS Bug History Date Modified Username Field Change ====================================================================== 08-05-04 04:31 thgr New Bug 08-06-04 12:03 kern File Added: 1.34.6-duration.patch 08-06-04 12:06 kern Bugnote Added: 0000147 08-06-04 12:06 kern Resolution open => fixed 08-06-04 12:06 kern Status new => closed 08-06-04 12:06 kern version => 1.34.6 ====================================================================== |
|
From: <bac...@li...> - 2004-08-06 17:21:11
|
A BUGNOTE has been added to this bug. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000073 ====================================================================== Reported By: Dan Langille Assigned To: ====================================================================== Project: bacula Bug ID: 73 Category: Director Reproducibility: always Severity: tweak Priority: low Status: new ====================================================================== Date Submitted: 08-06-2004 06:04 GMT Last Modified: 08-06-2004 10:21 GMT ====================================================================== Summary: Job IDs with commas aren't liked by restore Description: The Directory outputs Job IDs with a comma in them. But it doesn't like to use that as input. When I copy/paste a job id, it gets rejected. If I don't use the comma, it is accepted. This is a nice-to-have, because it is convenient to copy/paste the job id. Example follows: *restore First you select one or more JobIds that contain files to be restored. You will be presented several methods of specifying the JobIds. Then you will be allowed to select which files from those JobIds are to be restored. To select the JobIds, you have the following choices: 1: List last 20 Jobs run 2: List Jobs where a given File is saved 3: Enter list of JobIds to select 4: Enter SQL list command 5: Select the most recent backup for a client 6: Select backup for a client before a specified time 7: Enter a list of files to restore 8: Enter a list of files to restore before a specified time 9: Cancel Select item: (1-9): 2 freebsddiary-announce +-------+-----------+-------------------------------------------------------------------------+---------------------+---------+----------+-------------+ | JobId | Client | Name | StartTime | JobType | JobFiles | JobBytes | +-------+-----------+-------------------------------------------------------------------------+---------------------+---------+----------+-------------+ | 4,029 | nezlok-fd | /usr/local/majordomo/lists/lists.freebsddiary.org/freebsddiary-announce | 2004-07-17 04:02:51 | B | 164 | 25,870,998 | | 4,133 | nezlok-fd | /usr/local/majordomo/lists/lists.freebsddiary.org/freebsddiary-announce | 2004-07-25 03:39:05 | B | 211 | 35,683,858 | | 4,042 | nezlok-fd | /usr/local/majordomo/lists/lists.freebsddiary.org/freebsddiary-announce | 2004-07-18 04:19:31 | B | 208 | 27,969,224 | | 4,226 | lists-fd | /usr/local/majordomo/lists/freebsddiary.org/freebsddiary-announce | 2004-08-01 12:14:07 | B | 12,055 | 127,754,251 | +-------+-----------+-------------------------------------------------------------------------+---------------------+---------+----------+-------------+ To select the JobIds, you have the following choices: 1: List last 20 Jobs run 2: List Jobs where a given File is saved 3: Enter list of JobIds to select 4: Enter SQL list command 5: Select the most recent backup for a client 6: Select backup for a client before a specified time 7: Enter a list of files to restore 8: Enter a list of files to restore before a specified time 9: Cancel Select item: (1-9): 3 Enter JobId(s), comma separated, to restore: 4,226 You have selected the following JobIds: 4,226 Unable to get Job record. ERR=sql_get.c:281 No Job found for JobId 4 *restore First you select one or more JobIds that contain files to be restored. You will be presented several methods of specifying the JobIds. Then you will be allowed to select which files from those JobIds are to be restored. To select the JobIds, you have the following choices: 1: List last 20 Jobs run 2: List Jobs where a given File is saved 3: Enter list of JobIds to select 4: Enter SQL list command 5: Select the most recent backup for a client 6: Select backup for a client before a specified time 7: Enter a list of files to restore 8: Enter a list of files to restore before a specified time 9: Cancel Select item: (1-9): 3 Enter JobId(s), comma separated, to restore: 4226 You have selected the following JobId: 4226 Building directory tree for JobId 4226 ... 1 Job inserted into the tree and marked for extraction. The defined Storage resources are: 1: ArchivePython 2: ArchivePythonRemote Select Storage resource (1-2): ====================================================================== ---------------------------------------------------------------------- Dan Langille - 08-06-2004 09:25 GMT ---------------------------------------------------------------------- This is a test of the email notification. ---------------------------------------------------------------------- Dan Langille - 08-06-2004 09:33 GMT ---------------------------------------------------------------------- I just realised this: 3: Enter list of comma separated JobIds to select If a JobID contains a comma, we can't input it above.... This bugnote is really a test of the email notification system. ---------------------------------------------------------------------- Dan Langille - 08-06-2004 09:37 GMT ---------------------------------------------------------------------- Another test of the email notification system. ---------------------------------------------------------------------- TheBossAccount - 08-06-2004 10:21 GMT ---------------------------------------------------------------------- Ignore this bugnote. Testing email again. ---------------------------------------------------------------------- TheBossAccount - 08-06-2004 10:21 GMT ---------------------------------------------------------------------- another test Bug History Date Modified Username Field Change ====================================================================== 08-06-04 06:04 Dan Langille New Bug 08-06-04 09:25 Dan Langille Bugnote Added: 0000142 08-06-04 09:33 Dan Langille Bugnote Added: 0000143 08-06-04 09:37 Dan Langille Bugnote Added: 0000144 08-06-04 10:21 TheBossAccount Bugnote Added: 0000145 08-06-04 10:21 TheBossAccount Bugnote Added: 0000146 ====================================================================== |
|
From: <bac...@li...> - 2004-08-06 17:20:49
|
A BUGNOTE has been added to this bug. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000073 ====================================================================== Reported By: Dan Langille Assigned To: ====================================================================== Project: bacula Bug ID: 73 Category: Director Reproducibility: always Severity: tweak Priority: low Status: new ====================================================================== Date Submitted: 08-06-2004 06:04 GMT Last Modified: 08-06-2004 10:21 GMT ====================================================================== Summary: Job IDs with commas aren't liked by restore Description: The Directory outputs Job IDs with a comma in them. But it doesn't like to use that as input. When I copy/paste a job id, it gets rejected. If I don't use the comma, it is accepted. This is a nice-to-have, because it is convenient to copy/paste the job id. Example follows: *restore First you select one or more JobIds that contain files to be restored. You will be presented several methods of specifying the JobIds. Then you will be allowed to select which files from those JobIds are to be restored. To select the JobIds, you have the following choices: 1: List last 20 Jobs run 2: List Jobs where a given File is saved 3: Enter list of JobIds to select 4: Enter SQL list command 5: Select the most recent backup for a client 6: Select backup for a client before a specified time 7: Enter a list of files to restore 8: Enter a list of files to restore before a specified time 9: Cancel Select item: (1-9): 2 freebsddiary-announce +-------+-----------+-------------------------------------------------------------------------+---------------------+---------+----------+-------------+ | JobId | Client | Name | StartTime | JobType | JobFiles | JobBytes | +-------+-----------+-------------------------------------------------------------------------+---------------------+---------+----------+-------------+ | 4,029 | nezlok-fd | /usr/local/majordomo/lists/lists.freebsddiary.org/freebsddiary-announce | 2004-07-17 04:02:51 | B | 164 | 25,870,998 | | 4,133 | nezlok-fd | /usr/local/majordomo/lists/lists.freebsddiary.org/freebsddiary-announce | 2004-07-25 03:39:05 | B | 211 | 35,683,858 | | 4,042 | nezlok-fd | /usr/local/majordomo/lists/lists.freebsddiary.org/freebsddiary-announce | 2004-07-18 04:19:31 | B | 208 | 27,969,224 | | 4,226 | lists-fd | /usr/local/majordomo/lists/freebsddiary.org/freebsddiary-announce | 2004-08-01 12:14:07 | B | 12,055 | 127,754,251 | +-------+-----------+-------------------------------------------------------------------------+---------------------+---------+----------+-------------+ To select the JobIds, you have the following choices: 1: List last 20 Jobs run 2: List Jobs where a given File is saved 3: Enter list of JobIds to select 4: Enter SQL list command 5: Select the most recent backup for a client 6: Select backup for a client before a specified time 7: Enter a list of files to restore 8: Enter a list of files to restore before a specified time 9: Cancel Select item: (1-9): 3 Enter JobId(s), comma separated, to restore: 4,226 You have selected the following JobIds: 4,226 Unable to get Job record. ERR=sql_get.c:281 No Job found for JobId 4 *restore First you select one or more JobIds that contain files to be restored. You will be presented several methods of specifying the JobIds. Then you will be allowed to select which files from those JobIds are to be restored. To select the JobIds, you have the following choices: 1: List last 20 Jobs run 2: List Jobs where a given File is saved 3: Enter list of JobIds to select 4: Enter SQL list command 5: Select the most recent backup for a client 6: Select backup for a client before a specified time 7: Enter a list of files to restore 8: Enter a list of files to restore before a specified time 9: Cancel Select item: (1-9): 3 Enter JobId(s), comma separated, to restore: 4226 You have selected the following JobId: 4226 Building directory tree for JobId 4226 ... 1 Job inserted into the tree and marked for extraction. The defined Storage resources are: 1: ArchivePython 2: ArchivePythonRemote Select Storage resource (1-2): ====================================================================== ---------------------------------------------------------------------- Dan Langille - 08-06-2004 09:25 GMT ---------------------------------------------------------------------- This is a test of the email notification. ---------------------------------------------------------------------- Dan Langille - 08-06-2004 09:33 GMT ---------------------------------------------------------------------- I just realised this: 3: Enter list of comma separated JobIds to select If a JobID contains a comma, we can't input it above.... This bugnote is really a test of the email notification system. ---------------------------------------------------------------------- Dan Langille - 08-06-2004 09:37 GMT ---------------------------------------------------------------------- Another test of the email notification system. ---------------------------------------------------------------------- TheBossAccount - 08-06-2004 10:21 GMT ---------------------------------------------------------------------- Ignore this bugnote. Testing email again. Bug History Date Modified Username Field Change ====================================================================== 08-06-04 06:04 Dan Langille New Bug 08-06-04 09:25 Dan Langille Bugnote Added: 0000142 08-06-04 09:33 Dan Langille Bugnote Added: 0000143 08-06-04 09:37 Dan Langille Bugnote Added: 0000144 08-06-04 10:21 TheBossAccount Bugnote Added: 0000145 ====================================================================== |
|
From: <bac...@li...> - 2004-08-06 16:36:54
|
A BUGNOTE has been added to this bug. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000073 ====================================================================== Reported By: Dan Langille Assigned To: ====================================================================== Project: bacula Bug ID: 73 Category: Director Reproducibility: always Severity: tweak Priority: low Status: new ====================================================================== Date Submitted: 08-06-2004 06:04 GMT Last Modified: 08-06-2004 09:37 GMT ====================================================================== Summary: Job IDs with commas aren't liked by restore Description: The Directory outputs Job IDs with a comma in them. But it doesn't like to use that as input. When I copy/paste a job id, it gets rejected. If I don't use the comma, it is accepted. This is a nice-to-have, because it is convenient to copy/paste the job id. Example follows: *restore First you select one or more JobIds that contain files to be restored. You will be presented several methods of specifying the JobIds. Then you will be allowed to select which files from those JobIds are to be restored. To select the JobIds, you have the following choices: 1: List last 20 Jobs run 2: List Jobs where a given File is saved 3: Enter list of JobIds to select 4: Enter SQL list command 5: Select the most recent backup for a client 6: Select backup for a client before a specified time 7: Enter a list of files to restore 8: Enter a list of files to restore before a specified time 9: Cancel Select item: (1-9): 2 freebsddiary-announce +-------+-----------+-------------------------------------------------------------------------+---------------------+---------+----------+-------------+ | JobId | Client | Name | StartTime | JobType | JobFiles | JobBytes | +-------+-----------+-------------------------------------------------------------------------+---------------------+---------+----------+-------------+ | 4,029 | nezlok-fd | /usr/local/majordomo/lists/lists.freebsddiary.org/freebsddiary-announce | 2004-07-17 04:02:51 | B | 164 | 25,870,998 | | 4,133 | nezlok-fd | /usr/local/majordomo/lists/lists.freebsddiary.org/freebsddiary-announce | 2004-07-25 03:39:05 | B | 211 | 35,683,858 | | 4,042 | nezlok-fd | /usr/local/majordomo/lists/lists.freebsddiary.org/freebsddiary-announce | 2004-07-18 04:19:31 | B | 208 | 27,969,224 | | 4,226 | lists-fd | /usr/local/majordomo/lists/freebsddiary.org/freebsddiary-announce | 2004-08-01 12:14:07 | B | 12,055 | 127,754,251 | +-------+-----------+-------------------------------------------------------------------------+---------------------+---------+----------+-------------+ To select the JobIds, you have the following choices: 1: List last 20 Jobs run 2: List Jobs where a given File is saved 3: Enter list of JobIds to select 4: Enter SQL list command 5: Select the most recent backup for a client 6: Select backup for a client before a specified time 7: Enter a list of files to restore 8: Enter a list of files to restore before a specified time 9: Cancel Select item: (1-9): 3 Enter JobId(s), comma separated, to restore: 4,226 You have selected the following JobIds: 4,226 Unable to get Job record. ERR=sql_get.c:281 No Job found for JobId 4 *restore First you select one or more JobIds that contain files to be restored. You will be presented several methods of specifying the JobIds. Then you will be allowed to select which files from those JobIds are to be restored. To select the JobIds, you have the following choices: 1: List last 20 Jobs run 2: List Jobs where a given File is saved 3: Enter list of JobIds to select 4: Enter SQL list command 5: Select the most recent backup for a client 6: Select backup for a client before a specified time 7: Enter a list of files to restore 8: Enter a list of files to restore before a specified time 9: Cancel Select item: (1-9): 3 Enter JobId(s), comma separated, to restore: 4226 You have selected the following JobId: 4226 Building directory tree for JobId 4226 ... 1 Job inserted into the tree and marked for extraction. The defined Storage resources are: 1: ArchivePython 2: ArchivePythonRemote Select Storage resource (1-2): ====================================================================== ---------------------------------------------------------------------- Dan Langille - 08-06-2004 09:25 GMT ---------------------------------------------------------------------- This is a test of the email notification. ---------------------------------------------------------------------- Dan Langille - 08-06-2004 09:33 GMT ---------------------------------------------------------------------- I just realised this: 3: Enter list of comma separated JobIds to select If a JobID contains a comma, we can't input it above.... This bugnote is really a test of the email notification system. ---------------------------------------------------------------------- Dan Langille - 08-06-2004 09:37 GMT ---------------------------------------------------------------------- Another test of the email notification system. Bug History Date Modified Username Field Change ====================================================================== 08-06-04 06:04 Dan Langille New Bug 08-06-04 09:25 Dan Langille Bugnote Added: 0000142 08-06-04 09:33 Dan Langille Bugnote Added: 0000143 08-06-04 09:37 Dan Langille Bugnote Added: 0000144 ====================================================================== |
|
From: <no...@bu...> - 2004-08-02 12:47:55
|
The following bug has been SUBMITTED. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000071 ====================================================================== Reported By: Dan Langille Assigned To: kern ====================================================================== Project: bacula Bug ID: 71 Category: Director Reproducibility: always Severity: trivial Priority: normal Status: assigned ====================================================================== Date Submitted: 02-08-2004 04:08 PDT Last Modified: 02-08-2004 04:08 PDT ====================================================================== Summary: Bacula prints 5000 messages on update slots Description: I am using a 10 slot tape changer (one is hidden by the hardware as that slot contains a cleaning tape). I ran update slots today. 1000 OK: backup.example.com Version: 1.34.5 (21 June 2004) Enter a period to cancel a command. *update slots Using default Catalog name=MyCatalog DB=bacula Automatically selected Storage: DDS-4 Connecting to Storage daemon DDS-4 at backup.example.com:9103 ... 3301 Issuing autochanger "loaded drive 0" command. 3302 Autochanger "loaded drive 0", result: nothing loaded. 3306 Issuing autochanger "list" command. Catalog record for Volume "A0000001" is up to date. Catalog record for Volume "A0000002" is up to date. Catalog record for Volume "A0000003" is up to date. Catalog record for Volume "A0000004" is up to date. Catalog record for Volume "A0000005" is up to date. Catalog record for Volume "A0000006" is up to date. Catalog record for Volume "A0000008" is up to date. Catalog record for Volume "A0000009" is up to date. Catalog record for Volume "A0000010" is up to date. No VolName for Slot=10 set InChanger to zero. No VolName for Slot=11 set InChanger to zero. No VolName for Slot=12 set InChanger to zero. No VolName for Slot=13 set InChanger to zero. ... No VolName for Slot=4996 set InChanger to zero. No VolName for Slot=4997 set InChanger to zero. No VolName for Slot=4998 set InChanger to zero. No VolName for Slot=4999 set InChanger to zero. * Why did it go so high? FYI: $ sudo /usr/local/sbin/mtx -f /dev/pass0 status Storage Changer /dev/pass0:1 Drives, 9 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Storage Element 1:Full :VolumeTag=A0000001 Storage Element 2:Full :VolumeTag=A0000002 Storage Element 3:Full :VolumeTag=A0000003 Storage Element 4:Full :VolumeTag=A0000004 Storage Element 5:Full :VolumeTag=A0000005 Storage Element 6:Full :VolumeTag=A0000006 Storage Element 7:Full :VolumeTag=A0000008 Storage Element 8:Full :VolumeTag=A0000009 Storage Element 9:Full :VolumeTag=A0000010 mysql> select MediaId, VolumeName, Slot, InChanger from Media; +---------+------------+------+-----------+ | MediaId | VolumeName | Slot | InChanger | +---------+------------+------+-----------+ | 1 | A0000001 | 1 | 1 | | 2 | A0000002 | 2 | 1 | | 3 | A0000003 | 3 | 1 | | 4 | A0000004 | 4 | 1 | | 5 | A0000005 | 5 | 1 | | 6 | A0000006 | 6 | 1 | | 7 | A0000008 | 7 | 1 | | 8 | A0000009 | 8 | 1 | | 9 | A0000010 | 9 | 1 | | 10 | B0000001 | 1 | 0 | | 11 | B0000002 | 2 | 0 | | 12 | B0000003 | 3 | 0 | | 13 | B0000004 | 4 | 0 | | 14 | B0000005 | 5 | 0 | | 15 | B0000006 | 6 | 0 | | 16 | B0000007 | 7 | 0 | | 17 | B0000008 | 8 | 0 | | 18 | B0000009 | 9 | 0 | +---------+------------+------+-----------+ 18 rows in set (0.00 sec) ====================================================================== Bug History Date Modified Username Field Change ====================================================================== 02-08-04 04:08 Dan Langille New Bug ====================================================================== |
|
From: <no...@bu...> - 2004-07-23 10:00:39
|
The following bug has been CLOSED ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000070 ====================================================================== Reported By: kern Assigned To: ====================================================================== Project: bacula Bug ID: 70 Category: Director Reproducibility: always Severity: major Priority: normal Status: closed ====================================================================== Date Submitted: 23-07-2004 02:42 PDT Last Modified: 23-07-2004 03:00 PDT ====================================================================== Summary: JobIds are out of order on restore Description: When doing a restore, the list of JobIds to be restored is sometimes out of order. This bug was reported by several users (the most recent being Mike Acar). ====================================================================== ---------------------------------------------------------------------- kern - 23-07-2004 02:46 PDT ---------------------------------------------------------------------- This bug could cause old files to be restored that were later modified and backed up. It occurs because the retrieval order of items inserted into a table is not always the same as the order they were inserted. The fix is to sort the items as they are retrieved. A patch is attached to this bug report with instructions for applying it at the top of the patch. All users are strongly recommended to apply the patch. ---------------------------------------------------------------------- kern - 23-07-2004 02:59 PDT ---------------------------------------------------------------------- Add patch for version 1.32f-5 Bug History Date Modified Username Field Change ====================================================================== 23-07-04 02:42 kern New Bug 23-07-04 02:45 kern File Added: restore_jobids.patch 23-07-04 02:46 kern Bugnote Added: 0000140 23-07-04 02:46 kern Resolution open => fixed 23-07-04 02:46 kern Status new => closed 23-07-04 02:59 kern Bugnote Added: 0000141 23-07-04 02:59 kern Resolution fixed => reopened 23-07-04 02:59 kern Status closed => feedback 23-07-04 03:00 kern File Added: 1.32f-5.restore_jobids.patch 23-07-04 03:00 kern Resolution reopened => fixed 23-07-04 03:00 kern Status feedback => closed ====================================================================== |
|
From: <no...@bu...> - 2004-07-23 09:59:40
|
The following bug has been REOPENED. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000070 ====================================================================== Reported By: kern Assigned To: ====================================================================== Project: bacula Bug ID: 70 Category: Director Reproducibility: always Severity: major Priority: normal Status: feedback ====================================================================== Date Submitted: 23-07-2004 02:42 PDT Last Modified: 23-07-2004 02:59 PDT ====================================================================== Summary: JobIds are out of order on restore Description: When doing a restore, the list of JobIds to be restored is sometimes out of order. This bug was reported by several users (the most recent being Mike Acar). ====================================================================== ---------------------------------------------------------------------- kern - 23-07-2004 02:46 PDT ---------------------------------------------------------------------- This bug could cause old files to be restored that were later modified and backed up. It occurs because the retrieval order of items inserted into a table is not always the same as the order they were inserted. The fix is to sort the items as they are retrieved. A patch is attached to this bug report with instructions for applying it at the top of the patch. All users are strongly recommended to apply the patch. ---------------------------------------------------------------------- kern - 23-07-2004 02:59 PDT ---------------------------------------------------------------------- Add patch for version 1.32f-5 Bug History Date Modified Username Field Change ====================================================================== 23-07-04 02:42 kern New Bug 23-07-04 02:45 kern File Added: restore_jobids.patch 23-07-04 02:46 kern Bugnote Added: 0000140 23-07-04 02:46 kern Resolution open => fixed 23-07-04 02:46 kern Status new => closed 23-07-04 02:59 kern Bugnote Added: 0000141 23-07-04 02:59 kern Resolution fixed => reopened 23-07-04 02:59 kern Status closed => feedback ====================================================================== |
12 messages has been excluded from this view by a project administrator.