Lost my users and cant restore from backup

Support
1

NethServer Version: NethServer release 7.6.1810 (final)

Somehow I’ve managed to loose my Users and Groups. I already tryed to restore from the backup but I always end with some errors.
I’ll get the error: Account provider generic error: SSSD exit code 1

trying to uninstall the account provider. would end with some errors.
When trying to restore the network would always stop and not come up again.
I found this in the logfiles:

91670 May 23 00:13:49 home2 systemd: Stopped Shorewall IPv4 firewall.
91671 May 23 00:13:49 home2 systemd: Reloading.
91672 May 23 00:13:50 home2 systemd: Stopping LSB: Bring up/down networking…
91673 May 23 00:13:51 home2 kernel: br0: port 1(ens32) entered disabled state
91674 May 23 00:13:51 home2 kernel: device ens32 left promiscuous mode
91675 May 23 00:13:51 home2 kernel: br0: port 1(ens32) entered disabled state
91676 May 23 00:13:51 home2 network: Schnittstelle ens32 beenden: bridge br0 is still up; can’t delete it
91677 May 23 00:13:51 home2 network: [ OK ]
91678 May 23 00:13:51 home2 network: Schnittstelle ens34 beenden: [ OK ]
91679 May 23 00:13:51 home2 network: Loopback-Schnittstelle beenden: Verwendung: ifdown <Gerätename>
91680 May 23 00:13:51 home2 network: [FEHLGESCHLAGEN]
91681 May 23 00:13:51 home2 systemd: Stopped LSB: Bring up/down networking.
91682 May 23 00:13:51 home2 su: (to apache) root on none
91683 May 23 00:14:01 home2 systemd: Started Session 7 of user root.
91684 May 23 00:14:10 home2 kernel: nfs: server xxxx.lan not responding, timed out

Please can someone help me?

2

@support_team Can somebody help here?

3

Hi

In the last line of the log I can see a timed out NFS connection.

91684 May 23 00:14:10 home2 kernel: nfs: server xxxx.lan not responding, timed out

What is this?
Is this a NAS or something?

I think a hanging NFS connection is blocking the NIC from starting/stopping as required…

Andy

4

yes it’s a nas. but its working fine. the problem is the network is’nt coming up.
I think I miss the lo adaper in the network config?

db networks show
192.168.0.0=network
Description=Schwimu Net
Mask=255.255.255.0
br0=bridge
FwInBandwidth=
FwOutBandwidth=
bootproto=none
gateway=
ipaddr=192.168.178.4
netmask=255.255.255.0
role=green
br0:0=alias
ipaddr=192.168.178.17
netmask=255.255.255.0
role=alias
ens32=ethernet
FwInBandwidth=
FwOutBandwidth=
bridge=br0
role=bridged
ens34=ethernet
FwInBandwidth=
FwOutBandwidth=
bootproto=none
gateway=192.168.1.3
ipaddr=192.168.1.4
netmask=255.255.255.0
role=red
ppp0=xdsl-disabled
AuthType=auto
FwInBandwidth=
FwOutBandwidth=
Password=
name=PPPoE
provider=xDSL provider
role=red
user=
red1=provider
interface=ens34
weight=1

its also not to find with ifconfig

ifconfig

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.178.4 netmask 255.255.255.0 broadcast 192.168.178.255
inet6 fe80::20c:29ff:fe24:4a60 prefixlen 64 scopeid 0x20
ether 00:0c:29:24:4a:60 txqueuelen 1000 (Ethernet)
RX packets 20180 bytes 3701284 (3.5 MiB)
RX errors 0 dropped 39 overruns 0 frame 0
TX packets 22179 bytes 33024722 (31.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br0:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.178.17 netmask 255.255.255.0 broadcast 192.168.178.255
ether 00:0c:29:24:4a:60 txqueuelen 1000 (Ethernet)

ens32: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::20c:29ff:fe24:4a60 prefixlen 64 scopeid 0x20
ether 00:0c:29:24:4a:60 txqueuelen 1000 (Ethernet)
RX packets 92995 bytes 38339241 (36.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 30644 bytes 44672813 (42.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ens34: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.4 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::20c:29ff:fe24:4a6a prefixlen 64 scopeid 0x20
ether 00:0c:29:24:4a:6a txqueuelen 1000 (Ethernet)
RX packets 31830 bytes 34793229 (33.1 MiB)
RX errors 0 dropped 8 overruns 0 frame 0
TX packets 20743 bytes 4209296 (4.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Lokale Schleife)
RX packets 542 bytes 61330 (59.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 542 bytes 61330 (59.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

tunrallen: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 192.168.4.1 netmask 255.255.255.0 destination 192.168.4.1
inet6 fe80::8780:9bc7:4792:2847 prefixlen 64 scopeid 0x20
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 19 bytes 1104 (1.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

tunrw: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 192.168.177.1 netmask 255.255.255.255 destination 192.168.177.2
inet6 fe80::68c1:324:1f3a:91b8 prefixlen 64 scopeid 0x20
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3 bytes 144 (144.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vb-nsdc: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::5cb3:d8ff:fe9d:d281 prefixlen 64 scopeid 0x20
ether 5e:b3:d8:9d:d2:81 txqueuelen 1000 (Ethernet)
RX packets 41 bytes 4058 (3.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1522 bytes 220692 (215.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

I removed the NFS connection from the fstab, didnt change anything

5

on the dashboard I have this error Message:
Account provider generic error: SSSD exit code 1

6

Does removing the IP Alias to BR0 help? (Testing)?

2 Likes
7

yes this helps a lot. Users are back, Mailserver is working again.
but I my clients can’t connect to any server outside my LAN.

8

That’s the next problem, but not one which can’t be fixed.

I suspected the IP-Alias, as the Nextserver AD is running under a virtualization (Container).
That means there’s already some sort of IP aliasing running under the hood, combining that with firewall / routing is never a great idea, but it can be done!

My 2 cents
Andy

9

the strange thins is its worked until yesterday morning.

Do you know what I have to do so it will work again?

10

I think its working again. a final reboot did it :smile:
Thank yo uverry much for your great Help!
Peter

1 Like