samba - Nov 2017 - Compiling Samba 4.7 with systemd support on Fedora 26

Hi Rowland,

No I am running samba as a member, purely using it for ntlm_auth for
freeradius. If i run it manually i.e. /usr/local/samba/sbin/winbindd -D it
starts up and stays up no issues. Yes selinx is disabled

sestatus
SELinux status:                 disabled

Any pointers...?

Many Thanks
Arnab

On Thu, Nov 23, 2017 at 8:34 PM, Rowland Penny via samba <
samba at lists.samba.org> wrote:
> On Thu, 23 Nov 2017 20:21:15 +0000
> Arnab Roy via samba <samba at lists.samba.org> wrote:
>
> > Thanks Michael, after starting the service within a few secs it dies
> > in my case with this error samba winbind Got sig[15] terminate
> > (is_parent=1)
> >
> > Let me know if you need any further information.
> >
>
> How are you running Samba, as a DC ?
> If so, are you trying to start winbind manually ?
>
> Rowland
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

On Thu, 23 Nov 2017 20:58:52 +0000
Arnab Roy <arniekol at gmail.com> wrote:
> Hi Rowland,
> 
> No I am running samba as a member, purely using it for ntlm_auth for
> freeradius. If i run it manually i.e. /usr/local/samba/sbin/winbindd
> -D it starts up and stays up no issues. Yes selinx is disabled
> 
> sestatus
> SELinux status:                 disabled
> 
> Any pointers...?
> 
The fact that it does work manually sort of points to it being a
systemd problem rather than a Samba one.

Have you tried raising the Samba log level and then examining the logs.
Does systemd have its own log for when a service doesn't start ?
Sorry but I cannot help you further, I use Devuan.

Rowland

Contents of your systemd service file in question?

Am 23.11.2017 um 21:58 schrieb Arnab Roy via samba:
> No I am running samba as a member, purely using it for ntlm_auth for
> freeradius. If i run it manually i.e. /usr/local/samba/sbin/winbindd -D it
> starts up and stays up no issues. Yes selinx is disabled
> 
> sestatus
> SELinux status:                 disabled
> 
> Any pointers...?
show the systemd unit!

most likely wrong unit-type or bad pid-file config so that systemd has 
no chance to get aware it was sucessful started
> On Thu, Nov 23, 2017 at 8:34 PM, Rowland Penny via samba <
> samba at lists.samba.org> wrote:
> 
>> On Thu, 23 Nov 2017 20:21:15 +0000
>> Arnab Roy via samba <samba at lists.samba.org> wrote:
>>
>>> Thanks Michael, after starting the service within a few secs it
dies
>>> in my case with this error samba winbind Got sig[15] terminate
>>> (is_parent=1)
>>>
>>> Let me know if you need any further information.
>>>
>>
>> How are you running Samba, as a DC ?
>> If so, are you trying to start winbind manually ?

The systemd unit file looks like as follows:

[Unit]
Description=Winbindd Service
After=syslog.target network.target

[Service]
Environment=KRB5CCNAME=FILE:/run/samba/krb5cc_samba
Type=notify
NotifyAccess=all
PIDFile=/var/run/samba/
ExecStart=/usr/local/samba/sbin/winbindd -D
ExecReload=/usr/bin/kill -HUP $MAINPID
LimitCORE=infinity

[Install]


@Rowland I am not blaming samba at all, certainly is some sort of
systemd+samba issue.


I will try increasing the log verbosity and see if I see anything else.
Installing samba from rpm works fine, so it would seem fedora package
maintainers must be doing something, but currently there isnt samba 4.7 in
any of their repos and I would prefer to compile from source tbh.

Thanks everyone for your inputs.

Arnab





On Thu, Nov 23, 2017 at 9:37 PM, Sonic <sonicsmith at gmail.com> wrote:
> Contents of your systemd service file in question?
>