Bug 30323 - samba4: listener.log: No process in pidfile '/var/run/smbd.pid' found running; none killed
Summary: samba4: listener.log: No process in pidfile '/var/run/smbd.pid' found running...
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: Samba4
Version: UCS 3.1
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: Samba maintainers
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-06 18:14 CET by Arvid Requate
Modified: 2016-10-11 08:01 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2013-02-06 18:14:45 CET 
On a samba4 DC the following error message is logged to listener.log:

Reloading /etc/samba/smb.conf (smbd only):No process in pidfile '/var/run/smbd.pid' found running; none killed.

Probably this is triggered by the samba reload performed by some listener modules. Since the introduction of the "s3fs" model in UCS 3.0, the smbd is forked from the main samba daemon. One should check, that this relaod still works, and how to avoid the error message.
Comment 1 Stefan Gohmann univentionstaff 2016-10-11 08:01:17 CEST 
This issue has been filed against UCS 3.1.

UCS 3.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please reopen.