RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 657297 - [abrt] crash in bacula-traymonitor-3.0.3-5.fc12: __strlen_sse2: Process /usr/sbin/bacula-tray-monitor was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in bacula-traymonitor-3.0.3-5.fc12: __strlen_sse2: Process /usr/...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: bacula
Version: 6.1
Hardware: i686
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Jan Görig
QA Contact: qe-baseos-daemons
URL:
Whiteboard: abrt_hash:afc9288dd6bae7b381f1f1fedc3...
Depends On: 626490
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-25 12:02 UTC by Jan Görig
Modified: 2011-08-31 09:17 UTC (History)
14 users (show)

Fixed In Version: bacula-5.0.0-8.el6
Doc Type: Bug Fix
Doc Text:
Prior to this update, Bacula's default configuration missed a required option. As a result, the Bacula tray monitor component terminated unexpectedly. The problem has been fixed by adding the "Address" option to the "Director" section in the Bacula tray monitor configuration file so that the Bacula tray monitor now works as expected with the default configuration file. Note that this bug fix does not alter any existing Bacula tray monitor configuration file. As a consequence, the Bacula tray monitor can terminate unexpectedly if the existing Bacula tray monitor configuration is incorrect.
Clone Of: 626490
Environment:
Last Closed: 2011-08-31 09:17:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1232 0 normal SHIPPED_LIVE bacula bug fix update 2011-08-31 09:16:01 UTC

Comment 3 Suzanne Logcher 2011-02-15 21:45:32 UTC 
This issue was proposed for RHEL 6.1 FasTrack but did not get resolved in time.
It has been moved to RHEL 6.2 FasTrack.
Comment 7 Jan Görig 2011-06-08 14:59:24 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause
 - missing required option in default config
Consequence
 - bacula tray monitor was crashing immediately 
Fix
 - added 'Address' option to tray monitor config file
Result
 - tray monitor is not crashing with default config file
Comment 8 Jan Görig 2011-06-08 15:16:45 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -3,6 +3,6 @@
 Consequence
  - bacula tray monitor was crashing immediately 
 Fix
- - added 'Address' option to tray monitor config file
+ - added 'Address' option in 'Director' section to tray monitor config file
 Result
  - tray monitor is not crashing with default config file
Comment 10 Jan Görig 2011-06-09 07:39:59 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -5,4 +5,5 @@
 Fix
  - added 'Address' option in 'Director' section to tray monitor config file
 Result
- - tray monitor is not crashing with default config file+ - tray monitor is not crashing with default config file 
+(this change doesn't alter existing config so tray monitor will crash with existing incorrect configuration)
Comment 11 Petr Kovar 2011-06-15 16:07:09 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,9 +1 @@
-Cause
+Prior to this update, Bacula's default configuration missed a required option. As a result, the Bacula tray monitor component terminated unexpectedly. The problem has been fixed by adding the "Address" option to the "Director" section in the Bacula tray monitor configuration file so that the Bacula tray monitor now works as expected with the default configuration file. Note that this bug fix does not alter any existing Bacula tray monitor configuration file. As a consequence, the Bacula tray monitor can terminate unexpectedly if the existing Bacula tray monitor configuration is incorrect.- - missing required option in default config
-Consequence
- - bacula tray monitor was crashing immediately 
-Fix
- - added 'Address' option in 'Director' section to tray monitor config file
-Result
- - tray monitor is not crashing with default config file 
-(this change doesn't alter existing config so tray monitor will crash with existing incorrect configuration)
Comment 14 errata-xmlrpc 2011-08-31 09:17:06 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-1232.html
Note You need to log in before you can comment on or make changes to this bug.