[Samba] smbd fails to start after upgrade to version 4.11.6

[L.P.H. van Belle]

Hai Roy, 

I had a good look and most look ok, not much exiting going on but still a few points. 

>From teh logs. 


Feb  5 08:41:48 pi4b ifup[303]: ifup: couldn't open interfaces file "/etc/network/interfaces": No such file or directory
So re-create the file with the folling content, : /etc/network/interfaces   And add : 
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

( these are only the defaults )..


Feb  5 08:41:48 pi4b systemd-udevd[157]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1. 
- Possible fix(es) read :  https://bbs.archlinux.org/viewtopic.php?id=220315 


systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket. 
- So make sure nsswitch.conf the mDNS part is at the end of the line. 


Feb  5 08:41:48 pi4b systemd-networkd[155]: eth0: Gained carrier
Feb  5 08:41:48 pi4b systemd-networkd[155]: eth0: Configured
Feb  5 08:41:48 pi4b systemd-networkd-wait-online[181]: ignoring: lo
- Ok, to network configures ok. And i notice  
Feb  5 08:41:48 pi4b systemd-udevd[178]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
- Setting it might speed up the boot process a bit but as shown network works fine. 


Failed to open /etc/resolv.conf: Invalid argument  ( typo somewhere? ) 
Check the content. 

Feb  5 08:41:48 pi4b avahi-daemon[340]: Failed to open /etc/resolv.conf: Invalid argument
Feb  5 08:41:48 pi4b avahi-daemon[340]: socket() failed: Address family not supported by protocol
Need something, i dont know but reduce the resolv.conf to
search some.dom.tld 
nameserver ip_ad_dc1  
nameserver ip_ad_dc2
nameserver ip_internet_DNS

Feb  5 08:41:48 pi4b rpc.svcgssd[320]: unable to obtain root (machine) credentials
Feb  5 08:41:48 pi4b rpc.svcgssd[320]: do you have a keytab entry for nfs/<your.host>@<YOUR.REALM> in /etc/krb5.keytab?
Your missing the nfs SPNs in the keytab file but, i dont know if you use it. 

So above point are or might not  problem related, but i would fix them. 
Why i like clean server boots without errors, it just helps.. 

I see HEVC support in the Pi4 thats nice, anyone running kodi on raspbian, if so.. :-) 
I would like to know the experiance with it. 
If its good, i'll get myself a pi4 also, since i need to replace my old player with ani915GMA GPU .
:-) 

Greetz, 

Louis



> -----Oorspronkelijk bericht-----
> Van: Roy Eastwood [mailto:spindles7 at gmail.com] 
> Verzonden: woensdag 5 februari 2020 10:00
> Aan: 'L.P.H. van Belle'; samba at lists.samba.org
> Onderwerp: RE: [Samba] 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
>