Bug 6599

Summary:	winbindd should start after nmbd (and smbd after winbindd)
Product:	Mageia	Reporter:	Samuel Verschelde <stormi-mageia>
Component:	RPM Packages	Assignee:	Buchan Milne <bgmilne>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal
Version:	3
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	samba-3.6.5-2.mga2.src.rpm	CVE:
Status comment:

Description Samuel Verschelde 2012-06-27 15:50:03 CEST

If winbindd starts before nmbd I can't authenticate against a remote active directory.

Discussion with blingme on IRC let to this :
- winbindd should start after nmbd
- but ideally smbd should start after winbindd, so we need to split nmbd out of current smb service

Manuel Hiebel 2012-07-09 19:42:01 CEST

Assignee: bugsquad => bgmilne

Comment 1 Samuel Verschelde 2012-08-21 11:12:26 CEST

I tried to add smb in the Required-Start line for the winbind initscript, but I still can't log in without restarting winbind myself.

# Required-Start: $network smb

Comment 2 Samuel Verschelde 2012-08-21 13:20:06 CEST

I found the same error messages in samba logs than in winbind logs:

Aug 20 14:55:49 tech009 smbd[2350]: [2012/08/20 14:55:49.175562,  0] ../libcli/nbt/lmhosts.c:121(getlmhostsent)
Aug 20 14:55:49 tech009 smbd[2350]:   getlmhostsent: invalid address 127.0.0.1.

So I added $named to the # Required-Start line in the LSB header for smb, and now smb and winbind start well, and I can log in.

Comment 3 Samuel Verschelde 2012-08-21 17:44:09 CEST

Previous comment seems wrong, it worked by chance apparently. Still trying to find the correct dependencies.

Comment 4 Samuel Verschelde 2012-08-21 19:41:37 CEST

So, although it would still be good to start nmb then winbind then smb, my problem was solved by increasing the timeout so that network-up doesn't consider my network to be up before I actually get an IP from the dhcp server.

Comment 5 Manuel Hiebel 2013-10-22 12:09:43 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 Mageia version prior to Mageia 2'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 Mageia 2 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Samuel Verschelde 2013-10-22 12:13:29 CEST

Version: 2 => 3

Comment 6 Marja Van Waes 2015-03-31 16:03:09 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 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 Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

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

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD