samba - Nov 2018 - Kodi crashes when trying to browse network

On 11/2/18 5:43 AM, L.P.H. van Belle via samba wrote:
> Its a headless server so in this case im unable to test from within kodi,
atm.
> But Michael count try to to adjust the maxprotocol from within kodi and see
if that helps.
Kodi is a GUI app. There is no "shell" or "exit to shell"
feature. It calls library
functions and does not call the "smbclient" command-line tool.

Any changes to guisettings.xml requires entering the GUI and toggling the
settings.
I've tried setting Min Protocol to None, SMBv1, SMBv2. I've tried
setting Max
Protocol to None, SMBv1, SMBv2. No combination of settings works. Kodi crashes
the
same way (in libgenrand-samba4.so, opening /dev/urandom) each time.

This looks like a Samba bug so I'll file it.

Thanks,
Michael

On Fri, 2 Nov 2018 09:45:44 -0500
Michael Cronenworth via samba <samba at lists.samba.org> wrote:
> On 11/2/18 5:43 AM, L.P.H. van Belle via samba wrote:
> > Its a headless server so in this case im unable to test from within
> > kodi, atm. But Michael count try to to adjust the maxprotocol from
> > within kodi and see if that helps.
> 
> Kodi is a GUI app. There is no "shell" or "exit to
shell" feature. It
> calls library functions and does not call the "smbclient"
> command-line tool.
Yes I know now ;-)
There is a 'shell', it is called 'ssh' 
> 
> Any changes to guisettings.xml requires entering the GUI and toggling
> the settings. I've tried setting Min Protocol to None, SMBv1, SMBv2.
> I've tried setting Max Protocol to None, SMBv1, SMBv2. No combination
> of settings works. Kodi crashes the same way (in
> libgenrand-samba4.so, opening /dev/urandom) each time.
I cannot make it crash (I have fixed my 'cannot connect' problem, I
didn't have libsmbclient installed)
> 
> This looks like a Samba bug so I'll file it.
If it is a Samba bug, it seems to be localised to Fedora, it works on
Devuan, which means it works on Debian, Louis seems to have it working
on Ubuntu 18.04 
Using smbclient is very much like using the Kodi interface, the both
use libsmbclient

Rowland

Hai, 

Can you check the following, a few things that where bit buggy lately. 

Disable nmbd   ( systemctl stop nmbd )  And Try again.
And what is in /etc/nsswitch.conf 
And is SeLinux or Apparmor installed/enabled? 


Greetz, 

Louis

 
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Rowland Penny via samba
> Verzonden: vrijdag 2 november 2018 16:01
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] Kodi crashes when trying to browse network
> 
> On Fri, 2 Nov 2018 09:45:44 -0500
> Michael Cronenworth via samba <samba at lists.samba.org> wrote:
> 
> > On 11/2/18 5:43 AM, L.P.H. van Belle via samba wrote:
> > > Its a headless server so in this case im unable to test 
> from within
> > > kodi, atm. But Michael count try to to adjust the maxprotocol
from
> > > within kodi and see if that helps.
> > 
> > Kodi is a GUI app. There is no "shell" or "exit to
shell"
> feature. It
> > calls library functions and does not call the "smbclient"
> > command-line tool.
> 
> Yes I know now ;-)
> There is a 'shell', it is called 'ssh' 
> 
> > 
> > Any changes to guisettings.xml requires entering the GUI 
> and toggling
> > the settings. I've tried setting Min Protocol to None, SMBv1,
SMBv2.
> > I've tried setting Max Protocol to None, SMBv1, SMBv2. No 
> combination
> > of settings works. Kodi crashes the same way (in
> > libgenrand-samba4.so, opening /dev/urandom) each time.
> 
> I cannot make it crash (I have fixed my 'cannot connect' problem, I
> didn't have libsmbclient installed)
> > 
> > This looks like a Samba bug so I'll file it.
> 
> If it is a Samba bug, it seems to be localised to Fedora, it works on
> Devuan, which means it works on Debian, Louis seems to have it working
> on Ubuntu 18.04 
> Using smbclient is very much like using the Kodi interface, the both
> use libsmbclient
> 
> Rowland
>  
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
>

On 11/2/18 10:08 AM, L.P.H. van Belle via samba wrote:
> Disable nmbd   ( systemctl stop nmbd )  And Try again.
nmb is not running (and has never been run)
> And what is in /etc/nsswitch.conf
passwd:      files sss systemd
shadow:     files sss
group:       files sss systemd
hosts:      files mdns4_minimal [NOTFOUND=return] dns myhostname
bootparams: nisplus [NOTFOUND=return] files
ethers:     files
netmasks:   files
networks:   files
protocols:  files
rpc:        files
services:   files sss
netgroup:   files sss
publickey:  nisplus
automount:  files
aliases:    files nisplus

(sssd is not running)
> And is SeLinux or Apparmor installed/enabled?
SELinux is disabled.

On Fri, 2 Nov 2018 16:08:47 +0100
"L.P.H. van Belle via samba" <samba at lists.samba.org> wrote:
> Hai, 
>
If that was aimed at me:
 
> Can you check the following, a few things that where bit buggy
> lately. 
> 
> Disable nmbd   ( systemctl stop nmbd )  And Try again.
Bit hard to disable something that isn't running ;-)
> And what is in /etc/nsswitch.conf
It is standard, no mention of winbind etc
 
> And is SeLinux or Apparmor installed/enabled? 
Neither are installed.

Rowland

Hai, 

No, this one is more Michael.
We know it works for us. 

I suspect one of the following. 

/dev/random gets access denied. 
Nmbd browsing crashes. 

If we can exclude that latest.. 

Nmbd broadcast storm bug.
The nsswitch.conf resolv order might be wrong.

And these 2 might also be affected with SeLinux or Apparmor. 

Thats why im asking, but .. .RH/Centos..  
So that bit harder for me, i dont track the specific bug in RH/centos. 
For debian i track a lot of bug/problems. 


Greetz, 

Louis

 
> -----Oorspronkelijk bericht-----
> Van: Rowland Penny [mailto:rpenny at samba.org] 
> Verzonden: vrijdag 2 november 2018 16:18
> Aan: samba at lists.samba.org
> CC: L.P.H. van Belle
> Onderwerp: Re: [Samba] Kodi crashes when trying to browse network
> 
> On Fri, 2 Nov 2018 16:08:47 +0100
> "L.P.H. van Belle via samba" <samba at lists.samba.org>
wrote:
> 
> > Hai, 
> >
> 
> If that was aimed at me:
>  
> > Can you check the following, a few things that where bit buggy
> > lately. 
> > 
> > Disable nmbd   ( systemctl stop nmbd )  And Try again.
> 
> Bit hard to disable something that isn't running ;-)
> 
> > And what is in /etc/nsswitch.conf
> 
> It is standard, no mention of winbind etc
>  
> > And is SeLinux or Apparmor installed/enabled? 
> 
> Neither are installed.
> 
> Rowland
>  
> 
>

Hai, 


Ok, we have 2 last things to try.

Change in : /etc/nsswitch.conf
Only this line.
hosts:      files dns myhostname mdns4_minimal [NOTFOUND=return] 

There are know problems with the search orders. 
A guess, but worth a try. 

Last, what if you run kodi as root? 
I did run it as a normal user.


Greetz, 

Louis



> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Michael Cronenworth via samba
> Verzonden: vrijdag 2 november 2018 16:14
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] Kodi crashes when trying to browse network
> 
> On 11/2/18 10:08 AM, L.P.H. van Belle via samba wrote:
> > Disable nmbd   ( systemctl stop nmbd )  And Try again.
> 
> nmb is not running (and has never been run)
> 
> > And what is in /etc/nsswitch.conf
> 
> passwd:      files sss systemd
> shadow:     files sss
> group:       files sss systemd
> hosts:      files mdns4_minimal [NOTFOUND=return] dns myhostname
> bootparams: nisplus [NOTFOUND=return] files
> ethers:     files
> netmasks:   files
> networks:   files
> protocols:  files
> rpc:        files
> services:   files sss
> netgroup:   files sss
> publickey:  nisplus
> automount:  files
> aliases:    files nisplus
> 
> (sssd is not running)
> 
> > And is SeLinux or Apparmor installed/enabled?
> 
> SELinux is disabled.
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
>