Rowland Penny
2023-Jun-08 09:53 UTC
[Samba] After upgrade samba 4.16 -> 4.18, unable to access cifs-shares exported from a netapp-server
On 08/06/2023 10:36, gizmo via samba wrote:> > Hallo, > yesterday we made an upgrade from samba 4.16 to 4.18 (ubuntu 22.04 + sernet). > After the upgrade, all CIFS-Shares exported from our NetApp couldn't be accessed anymore neither from windows > nor from linux.Your NetApp doesn't 'export' anything, it (like every other NAS) just supplies shares that other clients can connect to, it is a server> > The NetApp-Server reported the following errors: > > secd.netlogon.noServers: None of the Netlogon servers configured for Vserver (svm) are currently accessible via the network > secd.ldap.noServers: None of the LDAP servers configured for Vserver (svm) are currently accessible via the network > secd.lsa.noServers: None of the LSA servers configured for Vserver (svm) are currently accessible via the network > > It's like the NetApp-server were not able anymore to connect to the samba4-serverIt certainly looks that way.> > Because the CIFS-shares are essential, we had to act fast and went back to samba 4.16 from the backup. > Then everything worked fine again.It certainly looks like the upgrade changed something that your NetApp didn't like.> > Is there any change in samba 4.17 or 4.18 that can cause this behave ? > I read the changelog, but couldn't find anything (with my minimal understanding)Like you, I cannot see anything relevant. Does your NetApp run vanilla Samba or its own version ? What is the smb.conf on the upgraded machine, which I presume wasn't changed during the upgrade. Rowland
Rowland Penny
2023-Jun-08 09:59 UTC
[Samba] After upgrade samba 4.16 -> 4.18, unable to access cifs-shares exported from a netapp-server
On 08/06/2023 10:53, Rowland Penny via samba wrote:> > > On 08/06/2023 10:36, gizmo via samba wrote: >> >> Hallo, >> yesterday we made an upgrade from samba 4.16 to 4.18 (ubuntu 22.04 + >> sernet). >> After the upgrade, all CIFS-Shares exported from our NetApp couldn't >> be accessed anymore neither from windows >> nor from linux. > > Your NetApp doesn't 'export' anything, it (like every other NAS) just > supplies shares that other clients can connect to, it is a server >> >> The NetApp-Server reported the following errors: >> >> secd.netlogon.noServers: None of the Netlogon servers configured for >> Vserver (svm) are currently accessible via the network >> secd.ldap.noServers: None of the LDAP servers configured for Vserver >> (svm) are currently accessible via the network >> secd.lsa.noServers: None of the LSA servers configured for Vserver >> (svm) are currently accessible via the network >> >> It's like the NetApp-server were not able anymore to connect to the >> samba4-server > > It certainly looks that way. > >> >> Because the CIFS-shares are essential, we had to act fast and went >> back to samba 4.16 from the backup. >> Then everything worked fine again. > > It certainly looks like the upgrade changed something that your NetApp > didn't like. > >> >> Is there any change in samba 4.17 or 4.18 that can cause this behave ? >> I read the changelog, but couldn't find anything (with my minimal >> understanding) > > Like you, I cannot see anything relevant. > > Does your NetApp run vanilla Samba or its own version ? > What is the smb.conf on the upgraded machine, which I presume wasn't > changed during the upgrade. > > Rowland > >I take it back, read this: https://bugzilla.samba.org/show_bug.cgi?id=15240 Rowland
Jeremy Allison
2023-Jun-08 15:17 UTC
[Samba] After upgrade samba 4.16 -> 4.18, unable to access cifs-shares exported from a netapp-server
On Thu, Jun 08, 2023 at 10:53:58AM +0100, Rowland Penny via samba wrote:> > >On 08/06/2023 10:36, gizmo via samba wrote: >> >>Hallo, >>yesterday we made an upgrade from samba 4.16 to 4.18 (ubuntu 22.04 + sernet). >>After the upgrade, all CIFS-Shares exported from our NetApp couldn't be accessed anymore neither from windows >>nor from linux. > >Your NetApp doesn't 'export' anything, it (like every other NAS) just >supplies shares that other clients can connect to, it is a server >> >>The NetApp-Server reported the following errors: >> >>secd.netlogon.noServers: None of the Netlogon servers configured for Vserver (svm) are currently accessible via the network >>secd.ldap.noServers: None of the LDAP servers configured for Vserver (svm) are currently accessible via the network >>secd.lsa.noServers: None of the LSA servers configured for Vserver (svm) are currently accessible via the network >> >>It's like the NetApp-server were not able anymore to connect to the samba4-server > >It certainly looks that way. > >> >>Because the CIFS-shares are essential, we had to act fast and went back to samba 4.16 from the backup. >>Then everything worked fine again. > >It certainly looks like the upgrade changed something that your NetApp >didn't like. > >> >>Is there any change in samba 4.17 or 4.18 that can cause this behave ? >>I read the changelog, but couldn't find anything (with my minimal understanding) > >Like you, I cannot see anything relevant. > >Does your NetApp run vanilla Samba or its own version ? >What is the smb.conf on the upgraded machine, which I presume wasn't >changed during the upgrade.NetApp runs their own custom proprietary code. We often have problems with them as they don't (as far as I can tell) do regression CI testing against anything other than stock Windows.