samba - Feb 2020 - smbd fails to start after upgrade to version 4.11.6

Hi Louis,
> Hai Roy,
> 
> Thanks for verifing it all. Im still amazed with this one.
> It all looks good to me, exept the missing PTR records then..  ;-)
> 
> Ok last question here to both, now i have Raspbian and Debian Buster amhf
on the repo.
> Rowland and Roy your both running Raspbian Buster correct?
> Its so strange Rowland his pi is running correct and Roy not.
> There has to be a different.
> 
> Im rulling out samba, of db corruptions.. Etc.
> Only thing is samba should not crash, we might like to have a loglevel 10
of that.
> And a bug report. Its a consistant crash of smbd so, reporting it would be
nice yes..
> 
> It im 100% sure its something withing the pi and the nic in combination off
raspbian or debian buster?
> So, If you guys can confirm the os once again, who runs which one exactly.
> 
> 
> If your on Raspbian.
> Run : sudo raspi-config
> Check what the state is of : Wait for Network at Boot.
It is set to "No"
> 
> Is someone using something like this to reduce boot time?
> /etc/systemd/system/networking.service.d/reduce-timeout.conf
> [Service]
> TimeoutStartSec=1
I'm not.
> Roy, can you reboot the pi and send me the dmesg log and syslog I found
some reports about "faulty" Pi mainboards also.
> Or can  you check it and look flipping networks..
> 
> Something like this:
> [ 182.553342] bcmgenet fd580000.genet eth0: Link is Down
> [ 182.553465] br0: port 1(eth0) entered disabled state
> [ 185.673598] bcmgenet fd580000.genet eth0: Link is Up - 1Gbps/Full - flow
control rx/tx
> 
Yes the first and third lines appear in both dmesg and syslog files - attached
for you only if you need to look deeper (not the
list) - but not the middle line.
> (source:
https://github.com/raspberrypi/linux/issues/3034#issuecomment-509709135 )
> 
> You can try to enable the network speed for the nic..
> 
> 
> Greetz,
> 
> Louis
> 
Cheers,
Roy
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dmesg.txt
URL:
<http://lists.samba.org/pipermail/samba/attachments/20200205/3a57c11b/dmesg.txt>

On 05/02/2020 09:00, Roy Eastwood via samba wrote:
> Hi Louis,
>> If your on Raspbian.
>> Run : sudo raspi-config
>> Check what the state is of : Wait for Network at Boot.
> It is set to "No"
And on mine
> Is someone using something like this to reduce boot time?
> /etc/systemd/system/networking.service.d/reduce-timeout.conf
> [Service]
> TimeoutStartSec=1
> I'm not.
Nor me
>> Roy, can you reboot the pi and send me the dmesg log and syslog I found
some reports about "faulty" Pi mainboards also.
>> Or can  you check it and look flipping networks..
>>
>> Something like this:
>> [ 182.553342] bcmgenet fd580000.genet eth0: Link is Down
>> [ 182.553465] br0: port 1(eth0) entered disabled state
>> [ 185.673598] bcmgenet fd580000.genet eth0: Link is Up - 1Gbps/Full -
flow control rx/tx
I didn't bother checking, I can cause the panic just by editing 
smb.conf, adding the two lines in question and then restarting Samba. I 
do this over SSH, so presumably the network is up on eth0 ;-)

Rowland

> 
> I didn't bother checking, I can cause the panic just by editing 
> smb.conf, adding the two lines in question and then 
> restarting Samba. I 
> do this over SSH, so presumably the network is up on eth0 ;-)
Ah, ok, so we clearly have bug in samba???
But i dont see this one on Debian Buster (amd64).. 
I just checked one of my production servers and it work fine.. 

Rowland, can you check the pi with the Debian Buster armhf packages? 
Or Dirk, can you test this on Debian Buster. 

Its only about these 2 lines. 

    interfaces = lo eth0
    bind interfaces only = yes

( if needed correct eth0 to your interface name ) 

I want to know if this is only on Raspbian buster or also on Debian Buster armhf
.


Greetz, 

Louis

Hello Louis,

Am 05.02.20 um 11:33 schrieb L.P.H. van Belle via samba:
>  
>> I didn't bother checking, I can cause the panic just by editing 
>> smb.conf, adding the two lines in question and then 
>> restarting Samba. I 
>> do this over SSH, so presumably the network is up on eth0 ;-)
> Ah, ok, so we clearly have bug in samba???
> But i dont see this one on Debian Buster (amd64).. 
> I just checked one of my production servers and it work fine.. 
>
> Rowland, can you check the pi with the Debian Buster armhf packages? 
> Or Dirk, can you test this on Debian Buster. 
>
> Its only about these 2 lines. 
>
>     interfaces = lo eth0
>     bind interfaces only = yes
>
> ( if needed correct eth0 to your interface name ) 
>
> I want to know if this is only on Raspbian buster or also on Debian Buster
armhf .
yes, i can check this. I will let you know the Results this evening :)


Regards

Dirk

On 05/02/2020 10:33, L.P.H. van Belle via samba wrote:
>   
>> I didn't bother checking, I can cause the panic just by editing
>> smb.conf, adding the two lines in question and then
>> restarting Samba. I
>> do this over SSH, so presumably the network is up on eth0 ;-)
> Ah, ok, so we clearly have bug in samba???
> But i dont see this one on Debian Buster (amd64)..
> I just checked one of my production servers and it work fine..
Neither do I, I am typing this on a Devuan boewulf (you know this as 
buster) using your 4.11.6 packages. It also has an eth0 and wlan0 
packages (I am using wlan0) and this works
>
> Rowland, can you check the pi with the Debian Buster armhf packages?
> Or Dirk, can you test this on Debian Buster.
>
> Its only about these 2 lines.
>
>      interfaces = lo eth0
>      bind interfaces only = yes
>
> ( if needed correct eth0 to your interface name )
>
> I want to know if this is only on Raspbian buster or also on Debian Buster
armhf .
What I can fairly easily do is, dig out my very long ethernet cable and 
use eth0 instead of wlan0. I could then try using the lines and see if 
this works.

Rowland