The following issue has been UPDATED.
======================================================================
http://bugs.bacula.org/view.php?id=1832
======================================================================
Reported By: macx
Assigned To:
======================================================================
Project: bacula
Issue ID: 1832
Category: bat
Reproducibility: always
Severity: minor
Priority: normal
Status: confirmed
======================================================================
Date Submitted: 2012-02-14 14:16 GMT
Last Modified: 2012-04-29 08:44 BST
======================================================================
Summary: Windows bat hangs if there is pending console output
but works after it's stopped and restarted
Description:
- version 5.2.5 (I don't see a 'build' field anywhere).
- the same thing happened with 5.2.3
The first time I run Bat it connects to the director and hangs. When I stop it I
get the Windows 'End Process' dialog. Bat works when I start it the second time.
This happens every time I start Bat after a certain period of time.
Steps to Reproduce:
Start Bat after a long period of time (unknown), kill the process and then
restart.
Additional Information:
I'm running the Bacula director on Arch Linux, but the version and set up on
that end doesn't seem to matter.
======================================================================
----------------------------------------------------------------------
(0006188) macx (reporter) - 2012-02-23 14:08
http://bugs.bacula.org/view.php?id=1832#c6188
----------------------------------------------------------------------
It looks like this only happens when a Job has been run since the last time Bat
was opened. Otherwise it runs properly the first time.
----------------------------------------------------------------------
(0006199) guenterg (reporter) - 2012-02-29 15:06
http://bugs.bacula.org/view.php?id=1832#c6199
----------------------------------------------------------------------
Same on Windows 7. For me it also looks like this problem happens if there are
messages to be displayed in the console window.
----------------------------------------------------------------------
(0006200) macx (reporter) - 2012-02-29 15:14
http://bugs.bacula.org/view.php?id=1832#c6200
----------------------------------------------------------------------
I agree. I only happens when unread messages are present.
----------------------------------------------------------------------
(0006218) aryder (reporter) - 2012-03-21 22:17
http://bugs.bacula.org/view.php?id=1832#c6218
----------------------------------------------------------------------
I have the same on Windows SBS 2008 x64 for only when unread messages are
present when BAT is opened. Forcing a close and re-starting works.
----------------------------------------------------------------------
(0006262) kern (administrator) - 2012-03-30 19:46
http://bugs.bacula.org/view.php?id=1832#c6262
----------------------------------------------------------------------
Well, the version of the Director does matter. It must be identical to that of
bat.
That said, I have reproduced the problem. As far as I can see, it happens, as
was noted, only when messages are pending.
I will look at it in more detail next week ... These kinds of Windows problems
have been *very* difficult to resolve in the past.
Issue History
Date Modified Username Field Change
======================================================================
2012-02-14 14:16 macx New Issue
2012-02-23 14:08 macx Note Added: 0006188
2012-02-29 15:06 guenterg Note Added: 0006199
2012-02-29 15:14 macx Note Added: 0006200
2012-03-21 22:17 aryder Note Added: 0006218
2012-03-30 19:46 kern Note Added: 0006262
2012-03-30 19:46 kern Status new => confirmed
2012-04-29 08:44 kern Summary bat hangs the first
time it's run but works after it's stopped and restarted => Windows bat hangs if
there is pending console output but works after it's stopped and restarted
======================================================================

The following issue has been ASSIGNED.
======================================================================
http://bugs.bacula.org/view.php?id=1862
======================================================================
Reported By: Bastian Friedrich
Assigned To: kern
======================================================================
Project: bacula
Issue ID: 1862
Category: Director
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
======================================================================
Date Submitted: 2012-04-27 15:21 BST
Last Modified: 2012-04-29 08:43 BST
======================================================================
Summary: Multi-job-restores can fail or lack files
Description:
Restores of backup jobs that span multiple volumes may fail when multiple job
ids are selected for restore. In one case, one file of a given job was not
restored at all (and no error message was issued); in another case (re-testing
that issue), the file was restored, but was incomplete.
Restore of the respective files is possible if only one job id is selected.
The issue arose with rather special setup concerning partially filled tapes:
First, write to one volume, then run a second backup that fills a second volume
and then appends to the first volume.
As said, in the initial case, the error remained unnoticed (by bacula; it came
up during some software tests, so in fact I noticed the problem). In the second
case, the error was this:
27-Apr 16:17 dev55-fd JobId 338: Error: attribs.c:485 File size of restored file
/data/bacula-restores/export/__shares__/backuptest/testfile.tar not correct.
Original 166707200, restored 98828288.
Steps to Reproduce:
1) Run a ("small") job to Volume 1
2) Mark Volume 1 as "Full"
3) Run a (larger) job to Volume 2 that fills Vol.2
4) During that run, mark Vol.1 as "Append" again, so that the second half of the
second job writes on Vol.1 again
5) restore (e.g., via bconsole; bvfs disabled!) all files of these jobs
("restore" -> 3 -> id1,id2, "mark *", done, ...).
Additional Information:
The created bsr file of the two-job restore contains the exact same data of the
first and the second job, so the problem is not in the creation of the bsr or
the restore UI, but in the restore of that bsr.
I can offer a catalog and if really required backup data, but I hope the problem
is reproducable without.
======================================================================
----------------------------------------------------------------------
(0006307) kern (administrator) - 2012-04-29 08:43
http://bugs.bacula.org/view.php?id=1862#c6307
----------------------------------------------------------------------
Thanks for bringing this up. It is an unusual and interesting restriction on how
Bacula functions.
>From what I see (very good explanation) you are trying to do something outside
the design envelope of Bacula. The problem is quite simple, if you restore from
two Volumes, Bacula mounts each Volume once and reads all files from that
Volume. That is in fact what one wants to do in 99.9999% of all cases. In the
case you have created, to do a correct restore, Bacula would need to mount Vol1,
read only the first Job, then mount Vol2 and read files then remount Vol1 and
read the rest of the Job.
Bacula does not do that.
There are two possible solutions:
1. Document the limitation.
2. Implement some new code that detects this situation during the restore
bsr generation, which then fails the job.
I will be happy to do http://bugs.bacula.org/view.php?id=1, but
http://bugs.bacula.org/view.php?id=2 will need a contributed implementation.
=======
Note, I am assuming that you can properly restore all the files from Job1 or
from Job2 as long as each Job is done by a separate restore. If this is not the
case, please let me know.
Issue History
Date Modified Username Field Change
======================================================================
2012-04-27 15:21 Bastian FriedrichNew Issue
2012-04-29 08:43 kern Note Added: 0006307
2012-04-29 08:43 kern Assigned To => kern
2012-04-29 08:43 kern Status new => feedback
======================================================================

The following issue has been SUBMITTED.
======================================================================
http://bugs.bacula.org/view.php?id=1863
======================================================================
Reported By: Bastian Friedrich
Assigned To:
======================================================================
Project: bacula
Issue ID: 1863
Category: scheduling
Reproducibility: always
Severity: tweak
Priority: low
Status: new
======================================================================
Date Submitted: 2012-04-27 15:34 BST
Last Modified: 2012-04-27 15:34 BST
======================================================================
Summary: "Reload" at schedule time duplicates jobs
Description:
When a "reload" (via bconsole, or via SIGHUP) is sent to the bacula-dir in a
minute where a job is executed, the job gets queued a second time.
E.g.:
A schedule contains a "Run" statement for 10:00h. The respective job is queued
at 10:00:00h. Then, a reload is executed at 10:00:15h; bacula sees a "new" job
scheduled for 10:00, and queues it another time.
Steps to Reproduce:
1) Create a schedule with a run "soon"
2) Create a job for any fileset using the schedule
3) Wait for the minute where the schedule runs the job
4) killall -HUP bacula-dir
5) See the configured job being executed twice
Additional Information:
I'm not 100% sure whether this can be regarded a bug. Depending on how a
"reload" is understood, and given the job states -- queued, or running -- the
behavior is correct. However, When the schedule is not modified, I expect a job
to be executed once, when it is configure once only.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2012-04-27 15:34 Bastian FriedrichNew Issue
======================================================================

The following issue has been SUBMITTED.
======================================================================
http://bugs.bacula.org/view.php?id=1862
======================================================================
Reported By: Bastian Friedrich
Assigned To:
======================================================================
Project: bacula
Issue ID: 1862
Category: Director
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 2012-04-27 15:21 BST
Last Modified: 2012-04-27 15:21 BST
======================================================================
Summary: Multi-job-restores can fail or lack files
Description:
Restores of backup jobs that span multiple volumes may fail when multiple job
ids are selected for restore. In one case, one file of a given job was not
restored at all (and no error message was issued); in another case (re-testing
that issue), the file was restored, but was incomplete.
Restore of the respective files is possible if only one job id is selected.
The issue arose with rather special setup concerning partially filled tapes:
First, write to one volume, then run a second backup that fills a second volume
and then appends to the first volume.
As said, in the initial case, the error remained unnoticed (by bacula; it came
up during some software tests, so in fact I noticed the problem). In the second
case, the error was this:
27-Apr 16:17 dev55-fd JobId 338: Error: attribs.c:485 File size of restored file
/data/bacula-restores/export/__shares__/backuptest/testfile.tar not correct.
Original 166707200, restored 98828288.
Steps to Reproduce:
1) Run a ("small") job to Volume 1
2) Mark Volume 1 as "Full"
3) Run a (larger) job to Volume 2 that fills Vol.2
4) During that run, mark Vol.1 as "Append" again, so that the second half of the
second job writes on Vol.1 again
5) restore (e.g., via bconsole; bvfs disabled!) all files of these jobs
("restore" -> 3 -> id1,id2, "mark *", done, ...).
Additional Information:
The created bsr file of the two-job restore contains the exact same data of the
first and the second job, so the problem is not in the creation of the bsr or
the restore UI, but in the restore of that bsr.
I can offer a catalog and if really required backup data, but I hope the problem
is reproducable without.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2012-04-27 15:21 Bastian FriedrichNew Issue
======================================================================

A NOTE has been added to this issue.
======================================================================
http://bugs.bacula.org/view.php?id=1861
======================================================================
Reported By: macx
Assigned To: kern
======================================================================
Project: bacula
Issue ID: 1861
Category: fd-plugin
Reproducibility: random
Severity: crash
Priority: low
Status: assigned
======================================================================
Date Submitted: 2012-04-19 13:39 BST
Last Modified: 2012-04-24 19:06 BST
======================================================================
Summary: local fd crashes with 'Segmentation violation'
Description:
The bacula-fd process ends with a 'Segmentation violation' about once/wk. I
haven't been able to establish a pattern yet.
Apr 18 13:07:31 localhost bacula-fd: Bacula interrupted by signal 11:
Segmentation violation
is the complete message from the most recent instance.
Otherwise bacula works just fine.
Steps to Reproduce:
Leave bacula running for a week.
Additional Information:
Please let me know what information you need.
======================================================================
----------------------------------------------------------------------
(0006299) macx (reporter) - 2012-04-19 13:58
http://bugs.bacula.org/view.php?id=1861#c6299
----------------------------------------------------------------------
The last time it happened was:
Apr 5 15:00:04 localhost bacula-fd: Bacula interrupted by signal 11:
Segmentation violation
----------------------------------------------------------------------
(0006300) kern (administrator) - 2012-04-19 15:18
http://bugs.bacula.org/view.php?id=1861#c6300
----------------------------------------------------------------------
Please get us a traceback. If the FD were installed correctly, it would be
emailed to you, and it will be in your FD's working directory. It will have an
extension .traceback and a second file will have extension .bactrace.
The first is the most important, the second can often be useful too.
The manual documents how to setup the traceback file capture. If you are unable
to get that working, then please read the Kaboom chapter of the manual and
obtain a traceback manually.
----------------------------------------------------------------------
(0006301) macx (reporter) - 2012-04-19 16:12
http://bugs.bacula.org/view.php?id=1861#c6301
----------------------------------------------------------------------
I've installed gdb - sorry, it wasn't installed before.
I'll have to wait until it crashes again (I'm assuming that I can't get debug
info. after the fact).
----------------------------------------------------------------------
(0006302) kern (administrator) - 2012-04-19 19:28
http://bugs.bacula.org/view.php?id=1861#c6302
----------------------------------------------------------------------
No, you cannot get the traceback after the fact.
However, when your FD is idle sometime, I would recommend testing that
you get a proper dump by forcing it to crash, otherwise you may wait a
week only to find it still doesn't dump.
To force it to crash, you must find its PID with something like:
ps -fax | grep bacula-fd
the do:
kill -SEGV <pid>
where <pid> is the process id found with the ps fax.
If it doesn't at least write the .traceback file, there is a
problem.
----------------------------------------------------------------------
(0006303) kern (administrator) - 2012-04-19 19:30
http://bugs.bacula.org/view.php?id=1861#c6303
----------------------------------------------------------------------
Oh, please don't forget to restart the FD if you kill it.
----------------------------------------------------------------------
(0006304) macx (reporter) - 2012-04-24 18:38
http://bugs.bacula.org/view.php?id=1861#c6304
----------------------------------------------------------------------
OK. More info. I don't seem to be able to get a traceback. I've installed gdb.
Is there anything else I need to do?
Where should I be looking for a .traceback file. I can't find one anywhere.
I've noticed that when the fd crashes, it does so after a certain job every time
and then the rest of the jobs fail.
I'm not sure, but I think that maybe this only happens the night after I get
status info. from the fd in BAT.
----------------------------------------------------------------------
(0006305) macx (reporter) - 2012-04-24 19:06
http://bugs.bacula.org/view.php?id=1861#c6305
----------------------------------------------------------------------
OK. I got postfix set up now. I'd never bothered before. Now I get this:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[New Thread 0xb7018b40 (LWP 822)]
0xb77a8416 in __kernel_vsyscall ()
$1 = 1768121699
$2 = 147488840
$3 = 147488880
/etc/bacula/scripts/btraceback.gdb:4: Error in sourced command file:
No symbol table is loaded. Use the "file" command.
Issue History
Date Modified Username Field Change
======================================================================
2012-04-19 13:39 macx New Issue
2012-04-19 13:58 macx Note Added: 0006299
2012-04-19 15:18 kern Note Added: 0006300
2012-04-19 15:18 kern Assigned To => kern
2012-04-19 15:18 kern Priority high => low
2012-04-19 15:18 kern Status new => feedback
2012-04-19 16:12 macx Note Added: 0006301
2012-04-19 16:12 macx Status feedback => assigned
2012-04-19 19:28 kern Note Added: 0006302
2012-04-19 19:29 kern Status assigned => feedback
2012-04-19 19:30 kern Note Added: 0006303
2012-04-24 18:38 macx Note Added: 0006304
2012-04-24 18:38 macx Status feedback => assigned
2012-04-24 19:06 macx Note Added: 0006305
======================================================================

A NOTE has been added to this issue.
======================================================================
http://bugs.bacula.org/view.php?id=1861
======================================================================
Reported By: macx
Assigned To: kern
======================================================================
Project: bacula
Issue ID: 1861
Category: fd-plugin
Reproducibility: random
Severity: crash
Priority: low
Status: assigned
======================================================================
Date Submitted: 2012-04-19 13:39 BST
Last Modified: 2012-04-24 18:38 BST
======================================================================
Summary: local fd crashes with 'Segmentation violation'
Description:
The bacula-fd process ends with a 'Segmentation violation' about once/wk. I
haven't been able to establish a pattern yet.
Apr 18 13:07:31 localhost bacula-fd: Bacula interrupted by signal 11:
Segmentation violation
is the complete message from the most recent instance.
Otherwise bacula works just fine.
Steps to Reproduce:
Leave bacula running for a week.
Additional Information:
Please let me know what information you need.
======================================================================
----------------------------------------------------------------------
(0006299) macx (reporter) - 2012-04-19 13:58
http://bugs.bacula.org/view.php?id=1861#c6299
----------------------------------------------------------------------
The last time it happened was:
Apr 5 15:00:04 localhost bacula-fd: Bacula interrupted by signal 11:
Segmentation violation
----------------------------------------------------------------------
(0006300) kern (administrator) - 2012-04-19 15:18
http://bugs.bacula.org/view.php?id=1861#c6300
----------------------------------------------------------------------
Please get us a traceback. If the FD were installed correctly, it would be
emailed to you, and it will be in your FD's working directory. It will have an
extension .traceback and a second file will have extension .bactrace.
The first is the most important, the second can often be useful too.
The manual documents how to setup the traceback file capture. If you are unable
to get that working, then please read the Kaboom chapter of the manual and
obtain a traceback manually.
----------------------------------------------------------------------
(0006301) macx (reporter) - 2012-04-19 16:12
http://bugs.bacula.org/view.php?id=1861#c6301
----------------------------------------------------------------------
I've installed gdb - sorry, it wasn't installed before.
I'll have to wait until it crashes again (I'm assuming that I can't get debug
info. after the fact).
----------------------------------------------------------------------
(0006302) kern (administrator) - 2012-04-19 19:28
http://bugs.bacula.org/view.php?id=1861#c6302
----------------------------------------------------------------------
No, you cannot get the traceback after the fact.
However, when your FD is idle sometime, I would recommend testing that
you get a proper dump by forcing it to crash, otherwise you may wait a
week only to find it still doesn't dump.
To force it to crash, you must find its PID with something like:
ps -fax | grep bacula-fd
the do:
kill -SEGV <pid>
where <pid> is the process id found with the ps fax.
If it doesn't at least write the .traceback file, there is a
problem.
----------------------------------------------------------------------
(0006303) kern (administrator) - 2012-04-19 19:30
http://bugs.bacula.org/view.php?id=1861#c6303
----------------------------------------------------------------------
Oh, please don't forget to restart the FD if you kill it.
----------------------------------------------------------------------
(0006304) macx (reporter) - 2012-04-24 18:38
http://bugs.bacula.org/view.php?id=1861#c6304
----------------------------------------------------------------------
OK. More info. I don't seem to be able to get a traceback. I've installed gdb.
Is there anything else I need to do?
Where should I be looking for a .traceback file. I can't find one anywhere.
I've noticed that when the fd crashes, it does so after a certain job every time
and then the rest of the jobs fail.
I'm not sure, but I think that maybe this only happens the night after I get
status info. from the fd in BAT.
Issue History
Date Modified Username Field Change
======================================================================
2012-04-19 13:39 macx New Issue
2012-04-19 13:58 macx Note Added: 0006299
2012-04-19 15:18 kern Note Added: 0006300
2012-04-19 15:18 kern Assigned To => kern
2012-04-19 15:18 kern Priority high => low
2012-04-19 15:18 kern Status new => feedback
2012-04-19 16:12 macx Note Added: 0006301
2012-04-19 16:12 macx Status feedback => assigned
2012-04-19 19:28 kern Note Added: 0006302
2012-04-19 19:29 kern Status assigned => feedback
2012-04-19 19:30 kern Note Added: 0006303
2012-04-24 18:38 macx Note Added: 0006304
2012-04-24 18:38 macx Status feedback => assigned
======================================================================

The following issue requires your FEEDBACK.
======================================================================
http://bugs.bacula.org/view.php?id=1861
======================================================================
Reported By: macx
Assigned To: kern
======================================================================
Project: bacula
Issue ID: 1861
Category: fd-plugin
Reproducibility: random
Severity: crash
Priority: low
Status: feedback
======================================================================
Date Submitted: 2012-04-19 13:39 BST
Last Modified: 2012-04-19 19:29 BST
======================================================================
Summary: local fd crashes with 'Segmentation violation'
Description:
The bacula-fd process ends with a 'Segmentation violation' about once/wk. I
haven't been able to establish a pattern yet.
Apr 18 13:07:31 localhost bacula-fd: Bacula interrupted by signal 11:
Segmentation violation
is the complete message from the most recent instance.
Otherwise bacula works just fine.
Steps to Reproduce:
Leave bacula running for a week.
Additional Information:
Please let me know what information you need.
======================================================================
----------------------------------------------------------------------
(0006299) macx (reporter) - 2012-04-19 13:58
http://bugs.bacula.org/view.php?id=1861#c6299
----------------------------------------------------------------------
The last time it happened was:
Apr 5 15:00:04 localhost bacula-fd: Bacula interrupted by signal 11:
Segmentation violation
----------------------------------------------------------------------
(0006300) kern (administrator) - 2012-04-19 15:18
http://bugs.bacula.org/view.php?id=1861#c6300
----------------------------------------------------------------------
Please get us a traceback. If the FD were installed correctly, it would be
emailed to you, and it will be in your FD's working directory. It will have an
extension .traceback and a second file will have extension .bactrace.
The first is the most important, the second can often be useful too.
The manual documents how to setup the traceback file capture. If you are unable
to get that working, then please read the Kaboom chapter of the manual and
obtain a traceback manually.
----------------------------------------------------------------------
(0006301) macx (reporter) - 2012-04-19 16:12
http://bugs.bacula.org/view.php?id=1861#c6301
----------------------------------------------------------------------
I've installed gdb - sorry, it wasn't installed before.
I'll have to wait until it crashes again (I'm assuming that I can't get debug
info. after the fact).
----------------------------------------------------------------------
(0006302) kern (administrator) - 2012-04-19 19:28
http://bugs.bacula.org/view.php?id=1861#c6302
----------------------------------------------------------------------
No, you cannot get the traceback after the fact.
However, when your FD is idle sometime, I would recommend testing that
you get a proper dump by forcing it to crash, otherwise you may wait a
week only to find it still doesn't dump.
To force it to crash, you must find its PID with something like:
ps -fax | grep bacula-fd
the do:
kill -SEGV <pid>
where <pid> is the process id found with the ps fax.
If it doesn't at least write the .traceback file, there is a
problem.
Issue History
Date Modified Username Field Change
======================================================================
2012-04-19 13:39 macx New Issue
2012-04-19 13:58 macx Note Added: 0006299
2012-04-19 15:18 kern Note Added: 0006300
2012-04-19 15:18 kern Assigned To => kern
2012-04-19 15:18 kern Priority high => low
2012-04-19 15:18 kern Status new => feedback
2012-04-19 16:12 macx Note Added: 0006301
2012-04-19 16:12 macx Status feedback => assigned
2012-04-19 19:28 kern Note Added: 0006302
2012-04-19 19:29 kern Status assigned => feedback
======================================================================

A NOTE has been added to this issue.
======================================================================
http://bugs.bacula.org/view.php?id=1861
======================================================================
Reported By: macx
Assigned To: kern
======================================================================
Project: bacula
Issue ID: 1861
Category: fd-plugin
Reproducibility: random
Severity: crash
Priority: low
Status: assigned
======================================================================
Date Submitted: 2012-04-19 13:39 BST
Last Modified: 2012-04-19 19:28 BST
======================================================================
Summary: local fd crashes with 'Segmentation violation'
Description:
The bacula-fd process ends with a 'Segmentation violation' about once/wk. I
haven't been able to establish a pattern yet.
Apr 18 13:07:31 localhost bacula-fd: Bacula interrupted by signal 11:
Segmentation violation
is the complete message from the most recent instance.
Otherwise bacula works just fine.
Steps to Reproduce:
Leave bacula running for a week.
Additional Information:
Please let me know what information you need.
======================================================================
----------------------------------------------------------------------
(0006299) macx (reporter) - 2012-04-19 13:58
http://bugs.bacula.org/view.php?id=1861#c6299
----------------------------------------------------------------------
The last time it happened was:
Apr 5 15:00:04 localhost bacula-fd: Bacula interrupted by signal 11:
Segmentation violation
----------------------------------------------------------------------
(0006300) kern (administrator) - 2012-04-19 15:18
http://bugs.bacula.org/view.php?id=1861#c6300
----------------------------------------------------------------------
Please get us a traceback. If the FD were installed correctly, it would be
emailed to you, and it will be in your FD's working directory. It will have an
extension .traceback and a second file will have extension .bactrace.
The first is the most important, the second can often be useful too.
The manual documents how to setup the traceback file capture. If you are unable
to get that working, then please read the Kaboom chapter of the manual and
obtain a traceback manually.
----------------------------------------------------------------------
(0006301) macx (reporter) - 2012-04-19 16:12
http://bugs.bacula.org/view.php?id=1861#c6301
----------------------------------------------------------------------
I've installed gdb - sorry, it wasn't installed before.
I'll have to wait until it crashes again (I'm assuming that I can't get debug
info. after the fact).
----------------------------------------------------------------------
(0006302) kern (administrator) - 2012-04-19 19:28
http://bugs.bacula.org/view.php?id=1861#c6302
----------------------------------------------------------------------
No, you cannot get the traceback after the fact.
However, when your FD is idle sometime, I would recommend testing that
you get a proper dump by forcing it to crash, otherwise you may wait a
week only to find it still doesn't dump.
To force it to crash, you must find its PID with something like:
ps -fax | grep bacula-fd
the do:
kill -SEGV <pid>
where <pid> is the process id found with the ps fax.
If it doesn't at least write the .traceback file, there is a
problem.
Issue History
Date Modified Username Field Change
======================================================================
2012-04-19 13:39 macx New Issue
2012-04-19 13:58 macx Note Added: 0006299
2012-04-19 15:18 kern Note Added: 0006300
2012-04-19 15:18 kern Assigned To => kern
2012-04-19 15:18 kern Priority high => low
2012-04-19 15:18 kern Status new => feedback
2012-04-19 16:12 macx Note Added: 0006301
2012-04-19 16:12 macx Status feedback => assigned
2012-04-19 19:28 kern Note Added: 0006302
======================================================================

The following issue has been ASSIGNED.
======================================================================
http://bugs.bacula.org/view.php?id=1861
======================================================================
Reported By: macx
Assigned To: kern
======================================================================
Project: bacula
Issue ID: 1861
Category: fd-plugin
Reproducibility: random
Severity: crash
Priority: low
Status: feedback
======================================================================
Date Submitted: 2012-04-19 13:39 BST
Last Modified: 2012-04-19 15:18 BST
======================================================================
Summary: local fd crashes with 'Segmentation violation'
Description:
The bacula-fd process ends with a 'Segmentation violation' about once/wk. I
haven't been able to establish a pattern yet.
Apr 18 13:07:31 localhost bacula-fd: Bacula interrupted by signal 11:
Segmentation violation
is the complete message from the most recent instance.
Otherwise bacula works just fine.
Steps to Reproduce:
Leave bacula running for a week.
Additional Information:
Please let me know what information you need.
======================================================================
----------------------------------------------------------------------
(0006299) macx (reporter) - 2012-04-19 13:58
http://bugs.bacula.org/view.php?id=1861#c6299
----------------------------------------------------------------------
The last time it happened was:
Apr 5 15:00:04 localhost bacula-fd: Bacula interrupted by signal 11:
Segmentation violation
----------------------------------------------------------------------
(0006300) kern (administrator) - 2012-04-19 15:18
http://bugs.bacula.org/view.php?id=1861#c6300
----------------------------------------------------------------------
Please get us a traceback. If the FD were installed correctly, it would be
emailed to you, and it will be in your FD's working directory. It will have an
extension .traceback and a second file will have extension .bactrace.
The first is the most important, the second can often be useful too.
The manual documents how to setup the traceback file capture. If you are unable
to get that working, then please read the Kaboom chapter of the manual and
obtain a traceback manually.
Issue History
Date Modified Username Field Change
======================================================================
2012-04-19 13:39 macx New Issue
2012-04-19 13:58 macx Note Added: 0006299
2012-04-19 15:18 kern Note Added: 0006300
2012-04-19 15:18 kern Assigned To => kern
2012-04-19 15:18 kern Priority high => low
2012-04-19 15:18 kern Status new => feedback
======================================================================

The following issue has been ASSIGNED.
======================================================================
http://bugs.bacula.org/view.php?id=1846
======================================================================
Reported By: linuxaos
Assigned To: ebollengier
======================================================================
Project: bacula
Issue ID: 1846
Category: bat
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 2012-03-19 21:20 GMT
Last Modified: 2012-04-19 10:29 BST
======================================================================
Summary: [Patch] This is a list of 3 enhancements that I have
added to BAT.
Description:
After using BAT for a while, I have noticed 3 annoyances which I have fixed.
None of these represent bugs per-se. These fixes represent my own preferences.
Use them if you like. They are released as freeware. Well, Here I go:
1. The current directory text field is tiny and is all the way to the upper
right. It would be nice to have a line that takes up the whole window width.
2. File filter is not filtering directories. Try it for directories. It won't
work.
3. Once the filter is applied, it should go away. Subsequent directories need
different filters. Let me explain:
Let's say I have 3 files: "AA", "BB", "CC". If I filter by "AA" and I click on a
directory, I don't want to filter just yet. I want to see the contents first,
and then filter. get it?
Steps to Reproduce:
Fixed:
1. I used Qt to modify brestore.ui and give the current directory a nice long
line.
2+3. I modified brestore.cpp to filter files AND directories. Also the filter
goes away once you move to a new directory.
Additional Information:
In the tar file, included, I have the 2 files: brestore.ui and brestore.cpp
Again, These fixes represent my own way of doing things. If you like them, use
them and enjoy!
======================================================================
----------------------------------------------------------------------
(0006214) linuxaos (reporter) - 2012-03-19 21:28
http://bugs.bacula.org/view.php?id=1846#c6214
----------------------------------------------------------------------
This is for bacula 5.2.6
----------------------------------------------------------------------
(0006263) kern (administrator) - 2012-03-30 19:48
http://bugs.bacula.org/view.php?id=1846#c6263
----------------------------------------------------------------------
This is a good place to send a patch. Thanks. :-)
We will take a look at it.
Issue History
Date Modified Username Field Change
======================================================================
2012-03-19 21:20 linuxaos New Issue
2012-03-19 21:20 linuxaos File Added: linuxaos.tgz
2012-03-19 21:28 linuxaos Note Added: 0006214
2012-03-30 19:48 kern Note Added: 0006263
2012-03-30 19:48 kern Status new => acknowledged
2012-03-30 19:48 kern Summary This is a list of 3
enhancements that I have added to BAT. Please forgive me if I am posting in the
wrong place. => [Patch] This is a list of 3 enhancements that I have added to
BAT.
2012-04-19 10:29 kern Assigned To => ebollengier
2012-04-19 10:29 kern Status acknowledged =>
assigned
======================================================================

Community

Help

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

CountryState

JavaScript is required for this form.

I agree to receive quotes, newsletters and other information from sourceforge.net and its partners regarding IT services and products. I understand that I can withdraw my consent at any time. Please refer to our Privacy Policy or Contact Us for more details