Bug 512118 (samba_messaging)

Summary: samba fails to initialise messages database
Product: [Fedora] Fedora Reporter: Nenad Mikša <DoDoEntertainment>
Component: sambaAssignee: Simo Sorce <ssorce>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 11CC: azelinka, gdeschner, ssorce
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-28 13:39:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 516996    
Attachments:
Description Flags
log.smbd
none
log.nmbd none

Description Nenad Mikša 2009-07-16 12:51:29 UTC
Created attachment 353976 [details]
log.smbd

Description of problem: Samba can't start on a clean installation of fedora 11. Running '/etc/init.d/smb start' shows a failure message, and log.smbd says that initializing of messages database was failed. 


Version-Release number of selected component (if applicable): 3.3.2

List of installed packages:
[root@2nd-of-12 samba]# rpm -q --all | grep samba
samba-client-3.3.2-0.33.fc11.i586
samba-winbind-3.3.2-0.33.fc11.i586
samba-doc-3.3.2-0.33.fc11.i586
samba-common-3.3.2-0.33.fc11.i586
samba-domainjoin-gui-3.3.2-0.33.fc11.i586
samba-3.3.2-0.33.fc11.i586


Steps to Reproduce:
1. Install Fedora 11 and install samba
2. Run /etc/init.d/smb start
3. See /var/log/samba/log.smbd
  
Actual results:
Samba failes to start.

Expected results:
Samba should start.

Additional info:
Same happens if trying to start nmbd.

I'm providing a log.smbd and log.nmbd in an attachment.

Comment 1 Nenad Mikša 2009-07-16 12:51:54 UTC
Created attachment 353977 [details]
log.nmbd

Comment 2 Bug Zapper 2010-04-27 15:43:25 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2010-06-28 13:39:53 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.