Author Topic: [Solved] Problems saving network data  (Read 610 times)

mkugler

  • Zen Apprentice
  • *
  • Posts: 16
  • Karma: +0/-0
    • View Profile
[Solved] Problems saving network data
« on: April 10, 2022, 11:42:59 am »
ZENTYAL Version: 6.1.6

Hello, I need your help when I want to save changes e.g. of the following data:

VPN
HTTP-Proxy
Firewall
IPsec

then I get the following message:

Einige Module meldeten ein Fehler beim Sichern der Änderungen. Weitere Informationen finden Sie in den Logs in /var/log/zentyal/
The following modules failed while saving their changes, their state is unknown: network

and in the Zentral.log I then find the following message:

2022/04/09 19:16:25 INFO> DHCP.pm:1168 EBox::DHCP::_setDHCPConf - Checking by config of DDNS for dhcp dns and samba
2022/04/09 19:16:25 INFO> DHCP.pm:1193 EBox::DHCP::_createUserDhcpdUser - Creating dhcpduser for dynamic dns DON'T NEED, ignore step.
2022/04/09 19:16:27 ERROR> GlobalImpl.pm:727 EBox::GlobalImpl::saveAllModules - The following modules failed while saving their changes, their state is unknown: network  at The following modules failed while saving their changes, their state is unknown: network  at /usr/share/perl5/EBox/GlobalImpl.pm line 727
EBox::GlobalImpl::saveAllModules('EBox::GlobalImpl=HASH(0x560af8b61e78)', 'progress', 'EBox::ProgressIndicator=HASH(0x560af497d698)') called at /usr/share/perl5/EBox/Global.pm line 95
EBox::Global::AUTOLOAD('EBox::Global=HASH(0x560af49a0060)', 'progress', 'EBox::ProgressIndicator=HASH(0x560af497d698)') called at /usr/share/zentyal/global-action line 32
eval {...} at /usr/share/zentyal/global-action line 30
2022/04/09 19:16:46 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2022/04/09 19:17:15 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2022/04/09 19:17:45 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2022/04/09 19:18:15 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2022/04/09 19:18:45 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2022/04/09 19:19:12 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2022/04/09 19:19:16 INFO> Index.pm:187 EBox::Dashboard::CGI::Index::masonParameters - dashboard1

I can unfortunately do nothing with this, can someone help me. Thanks in advance.
« Last Edit: May 25, 2022, 08:23:09 pm by mkugler »

turalyon

  • Zen Monk
  • **
  • Posts: 94
  • Karma: +12/-0
    • View Profile
Re: Problems saving network data
« Reply #1 on: April 11, 2022, 01:32:50 pm »
Hi,

You can do 2 things:

1. Enable the debug mode in Zentyal in order to identify the network error in the log file '/var/log/zentyal/zentyal.log'.
2. Disable all the modules, and enable one by one. NOTE: This option is risky because there is a chance that the modules cannot start again due the error.

In case you want to try the first option, do the following:

1. Modify the option 'debug' to 'yes' in the configuration file '/etc/zentyal/zentyal.conf'
2. Restart the webadmin module:

Code: [Select]
sudo zs webadmin restart

--
“This world is ours, and by the Holy Light we will keep it safe, now and forever".

mkugler

  • Zen Apprentice
  • *
  • Posts: 16
  • Karma: +0/-0
    • View Profile
Re: Problems saving network data
« Reply #2 on: April 16, 2022, 10:36:00 am »
Hi turayon.

I have changed the LOG to Debut, I get the following message when I save:

Einige Module meldeten ein Fehler beim Sichern der Änderungen. Weitere Informationen finden Sie in den Logs in /var/log/zentyal/

The following modules failed while saving their changes, their state is unknown: network The following modules failed while saving their changes, their state is unknown: network at The following modules failed while saving their changes, their state is unknown: network at /usr/share/perl5/EBox/GlobalImpl.pm line 727 EBox::GlobalImpl::saveAllModules('EBox::GlobalImpl=HASH(0x56353cfcaa40)', 'progress', 'EBox::ProgressIndicator=HASH(0x563538de5698)') called at /usr/share/perl5/EBox/Global.pm line 95 EBox::Global::AUTOLOAD('EBox::Global=HASH(0x56353cec6c40)', 'progress', 'EBox::ProgressIndicator=HASH(0x563538de5698)') called at /usr/share/zentyal/global-action line 32 eval {...} at /usr/share/zentyal/global-action line 30

The following can be seen in the zentyal.log:

2022/04/16 10:24:03 ERROR> GlobalImpl.pm:727 EBox::GlobalImpl::saveAllModules - The following modules failed while saving their changes, their state is unknown: network  at The following modules failed while saving their changes, their state is unknown: network  at /usr/share/perl5/EBox/GlobalImpl.pm line 727
EBox::GlobalImpl::saveAllModules('EBox::GlobalImpl=HASH(0x56353cfcaa40)', 'progress', 'EBox::ProgressIndicator=HASH(0x563538de5698)') called at /usr/share/perl5/EBox/Global.pm line 95
EBox::Global::AUTOLOAD('EBox::Global=HASH(0x56353cec6c40)', 'progress', 'EBox::ProgressIndicator=HASH(0x563538de5698)') called at /usr/share/zentyal/global-action line 32
eval {...} at /usr/share/zentyal/global-action line 30

2022/04/16 10:24:51 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.
2022/04/16 10:25:21 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command LANG=C /usr/sbin/ejabberdctl status failed.

Jabber is not turned on for me, I tried to turn it on, this did not work. I do not get anywhere here.

Thanks in advance

turalyon

  • Zen Monk
  • **
  • Posts: 94
  • Karma: +12/-0
    • View Profile
Re: Problems saving network data
« Reply #3 on: April 20, 2022, 10:00:46 am »
Hi,

Unfortunately that information is not helpful. Did you analyse the log file '/var/log/syslog'?

If you can't find anything useful in the log files, you will need to disable all of them, and start enable one by one.

--
“This world is ours, and by the Holy Light we will keep it safe, now and forever".

mkugler

  • Zen Apprentice
  • *
  • Posts: 16
  • Karma: +0/-0
    • View Profile
Re: Problems saving network data
« Reply #4 on: April 24, 2022, 10:15:34 am »
I have now checked the syslog, there I found the following errors:

Apr 24 10:00:45 srvdc01 systemd[11870]: zentyal.antivirus-clamonacc.service: Failed to execute command: No such file or directory
Apr 24 10:00:45 srvdc01 systemd[11870]: zentyal.antivirus-clamonacc.service: Failed at step EXEC spawning /usr/bin/clamonacc: No such file or directory
Apr 24 10:00:45 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Main process exited, code=exited, status=203/EXEC
Apr 24 10:00:45 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Failed with result 'exit-code'.
Apr 24 10:00:50 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Service hold-off time over, scheduling restart.
Apr 24 10:00:50 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Scheduled restart job, restart counter is at 47.
Apr 24 10:00:50 srvdc01 systemd[1]: Stopped Executable for On-Access scans.
Apr 24 10:00:50 srvdc01 systemd[1]: Started Executable for On-Access scans.
Apr 24 10:00:50 srvdc01 systemd[11926]: zentyal.antivirus-clamonacc.service: Failed to execute command: No such file or directory
Apr 24 10:00:50 srvdc01 systemd[11926]: zentyal.antivirus-clamonacc.service: Failed at step EXEC spawning /usr/bin/clamonacc: No such file or directory
Apr 24 10:00:50 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Main process exited, code=exited, status=203/EXEC
Apr 24 10:00:50 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Failed with result 'exit-code'.
Apr 24 10:00:53 srvdc01 dhcpd[5585]: Commit: IP: 192.168.1.20 DHCID: 48:e1:e9:71:21:1d Name: Meross_Smart_Plug
Apr 24 10:00:53 srvdc01 kernel: [  612.267609] audit: type=1400 audit(1650787253.510:24): apparmor="DENIED" operation="exec" profile="/usr/sbin/dhcpd" name="/usr/share/zentyal-dhcp/dhcp-dyndns.sh" pid=11955 comm="dhcpd" requested_mask="x" denied_mask="x" fsuid=118 ouid=0
Apr 24 10:00:53 srvdc01 dhcpd[5585]: execute_statement argv[0] = /usr/share/zentyal-dhcp/dhcp-dyndns.sh
Apr 24 10:00:53 srvdc01 dhcpd[5585]: execute_statement argv[1] = add
Apr 24 10:00:53 srvdc01 dhcpd[5585]: execute_statement argv[2] = 192.168.1.20
Apr 24 10:00:53 srvdc01 dhcpd[5585]: execute_statement argv[3] = 48:e1:e9:71:21:1d
Apr 24 10:00:53 srvdc01 dhcpd[5585]: execute_statement argv[4] = Meross_Smart_Plug
Apr 24 10:00:53 srvdc01 dhcpd[11955]: Unable to execute /usr/share/zentyal-dhcp/dhcp-dyndns.sh: Permission denied
Apr 24 10:00:53 srvdc01 dhcpd[5585]: execute: /usr/share/zentyal-dhcp/dhcp-dyndns.sh exit status 32512
Apr 24 10:00:53 srvdc01 dhcpd[5585]: DHCPREQUEST for 192.168.1.20 from 48:e1:e9:71:21:1d (Meross_Smart_Plug) via eth0
Apr 24 10:00:53 srvdc01 dhcpd[5585]: DHCPACK on 192.168.1.20 to 48:e1:e9:71:21:1d (Meross_Smart_Plug) via eth0
Apr 24 10:00:55 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Service hold-off time over, scheduling restart.
Apr 24 10:00:55 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Scheduled restart job, restart counter is at 48.
Apr 24 10:00:55 srvdc01 systemd[1]: Stopped Executable for On-Access scans.
Apr 24 10:00:55 srvdc01 systemd[1]: Started Executable for On-Access scans.
Apr 24 10:00:55 srvdc01 systemd[12088]: zentyal.antivirus-clamonacc.service: Failed to execute command: No such file or directory
Apr 24 10:00:55 srvdc01 systemd[12088]: zentyal.antivirus-clamonacc.service: Failed at step EXEC spawning /usr/bin/clamonacc: No such file or directory
Apr 24 10:00:55 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Main process exited, code=exited, status=203/EXEC
Apr 24 10:00:55 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Failed with result 'exit-code'.
Apr 24 10:00:56 srvdc01 systemd[1]: Started Session c3 of user ejabberd.
Apr 24 10:00:57 srvdc01 dhcpd[5585]: Commit: IP: 192.168.1.40 DHCID: 48:e1:e9:71:0e:cf Name: Meross_Smart_Plug
Apr 24 10:00:57 srvdc01 dhcpd[5585]: execute_statement argv[0] = /usr/share/zentyal-dhcp/dhcp-dyndns.sh
Apr 24 10:00:57 srvdc01 dhcpd[5585]: execute_statement argv[1] = add
Apr 24 10:00:57 srvdc01 dhcpd[5585]: execute_statement argv[2] = 192.168.1.40
Apr 24 10:00:57 srvdc01 dhcpd[5585]: execute_statement argv[3] = 48:e1:e9:71:0e:cf
Apr 24 10:00:57 srvdc01 dhcpd[5585]: execute_statement argv[4] = Meross_Smart_Plug
Apr 24 10:00:57 srvdc01 dhcpd[12272]: Unable to execute /usr/share/zentyal-dhcp/dhcp-dyndns.sh: Permission denied
Apr 24 10:00:57 srvdc01 dhcpd[5585]: execute: /usr/share/zentyal-dhcp/dhcp-dyndns.sh exit status 32512
Apr 24 10:00:57 srvdc01 kernel: [  616.354148] audit: type=1400 audit(1650787257.598:25): apparmor="DENIED" operation="exec" profile="/usr/sbin/dhcpd" name="/usr/share/zentyal-dhcp/dhcp-dyndns.sh" pid=12272 comm="dhcpd" requested_mask="x" denied_mask="x" fsuid=118 ouid=0
Apr 24 10:00:57 srvdc01 dhcpd[5585]: DHCPREQUEST for 192.168.1.40 from 48:e1:e9:71:0e:cf (Meross_Smart_Plug) via eth0
Apr 24 10:00:57 srvdc01 dhcpd[5585]: DHCPACK on 192.168.1.40 to 48:e1:e9:71:0e:cf (Meross_Smart_Plug) via eth0

regarding DHCP I have executed the following command:
/usr/share/zentyal-dhcp/dhcp-dyndns.sh

Message:
Required keytab /etc/dhcp/samba-keys/dhcpduser.keytab not found, it needs to be created.
Use the following commands as root
samba-tool domain exportkeytab --principal=dhcpduser@ZENTYAL-DOMAIN.LAN /etc/dhcp/samba-keys/dhcpduser.keytab
chown XXXX:XXXX /etc/dhcp/samba-keys/dhcpduser.keytab
Replace 'XXXX:XXXX' with the user & group that dhcpd runs as on your distro
chmod 400 /etc/dhcp/samba-keys/dhcpduser.keytab

Executed the following command:
sudo samba-tool domain exportkeytab --principal=dhcpduser@ZENTYAL-DOMAIN.LAN /etc/dhcp/samba-keys/dhcpduser.keytab
sudo chown root:dhcpd /etc/dhcp/samba-keys/dhcpduser.keytab

But unfortunately the problem remains



turalyon

  • Zen Monk
  • **
  • Posts: 94
  • Karma: +12/-0
    • View Profile
Re: Problems saving network data
« Reply #5 on: April 25, 2022, 04:56:13 pm »
I have now checked the syslog, there I found the following errors:

Apr 24 10:00:45 srvdc01 systemd[11870]: zentyal.antivirus-clamonacc.service: Failed to execute command: No such file or directory
Apr 24 10:00:45 srvdc01 systemd[11870]: zentyal.antivirus-clamonacc.service: Failed at step EXEC spawning /usr/bin/clamonacc: No such file or directory
Apr 24 10:00:45 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Main process exited, code=exited, status=203/EXEC
Apr 24 10:00:45 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Failed with result 'exit-code'.
Apr 24 10:00:50 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Service hold-off time over, scheduling restart.
Apr 24 10:00:50 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Scheduled restart job, restart counter is at 47.
Apr 24 10:00:50 srvdc01 systemd[1]: Stopped Executable for On-Access scans.
Apr 24 10:00:50 srvdc01 systemd[1]: Started Executable for On-Access scans.
Apr 24 10:00:50 srvdc01 systemd[11926]: zentyal.antivirus-clamonacc.service: Failed to execute command: No such file or directory
Apr 24 10:00:50 srvdc01 systemd[11926]: zentyal.antivirus-clamonacc.service: Failed at step EXEC spawning /usr/bin/clamonacc: No such file or directory
Apr 24 10:00:50 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Main process exited, code=exited, status=203/EXEC
Apr 24 10:00:50 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Failed with result 'exit-code'.
Apr 24 10:00:53 srvdc01 dhcpd[5585]: Commit: IP: 192.168.1.20 DHCID: 48:e1:e9:71:21:1d Name: Meross_Smart_Plug
Apr 24 10:00:53 srvdc01 kernel: [  612.267609] audit: type=1400 audit(1650787253.510:24): apparmor="DENIED" operation="exec" profile="/usr/sbin/dhcpd" name="/usr/share/zentyal-dhcp/dhcp-dyndns.sh" pid=11955 comm="dhcpd" requested_mask="x" denied_mask="x" fsuid=118 ouid=0
Apr 24 10:00:53 srvdc01 dhcpd[5585]: execute_statement argv[0] = /usr/share/zentyal-dhcp/dhcp-dyndns.sh
Apr 24 10:00:53 srvdc01 dhcpd[5585]: execute_statement argv[1] = add
Apr 24 10:00:53 srvdc01 dhcpd[5585]: execute_statement argv[2] = 192.168.1.20
Apr 24 10:00:53 srvdc01 dhcpd[5585]: execute_statement argv[3] = 48:e1:e9:71:21:1d
Apr 24 10:00:53 srvdc01 dhcpd[5585]: execute_statement argv[4] = Meross_Smart_Plug
Apr 24 10:00:53 srvdc01 dhcpd[11955]: Unable to execute /usr/share/zentyal-dhcp/dhcp-dyndns.sh: Permission denied
Apr 24 10:00:53 srvdc01 dhcpd[5585]: execute: /usr/share/zentyal-dhcp/dhcp-dyndns.sh exit status 32512
Apr 24 10:00:53 srvdc01 dhcpd[5585]: DHCPREQUEST for 192.168.1.20 from 48:e1:e9:71:21:1d (Meross_Smart_Plug) via eth0
Apr 24 10:00:53 srvdc01 dhcpd[5585]: DHCPACK on 192.168.1.20 to 48:e1:e9:71:21:1d (Meross_Smart_Plug) via eth0
Apr 24 10:00:55 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Service hold-off time over, scheduling restart.
Apr 24 10:00:55 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Scheduled restart job, restart counter is at 48.
Apr 24 10:00:55 srvdc01 systemd[1]: Stopped Executable for On-Access scans.
Apr 24 10:00:55 srvdc01 systemd[1]: Started Executable for On-Access scans.
Apr 24 10:00:55 srvdc01 systemd[12088]: zentyal.antivirus-clamonacc.service: Failed to execute command: No such file or directory
Apr 24 10:00:55 srvdc01 systemd[12088]: zentyal.antivirus-clamonacc.service: Failed at step EXEC spawning /usr/bin/clamonacc: No such file or directory
Apr 24 10:00:55 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Main process exited, code=exited, status=203/EXEC
Apr 24 10:00:55 srvdc01 systemd[1]: zentyal.antivirus-clamonacc.service: Failed with result 'exit-code'.
Apr 24 10:00:56 srvdc01 systemd[1]: Started Session c3 of user ejabberd.
Apr 24 10:00:57 srvdc01 dhcpd[5585]: Commit: IP: 192.168.1.40 DHCID: 48:e1:e9:71:0e:cf Name: Meross_Smart_Plug
Apr 24 10:00:57 srvdc01 dhcpd[5585]: execute_statement argv[0] = /usr/share/zentyal-dhcp/dhcp-dyndns.sh
Apr 24 10:00:57 srvdc01 dhcpd[5585]: execute_statement argv[1] = add
Apr 24 10:00:57 srvdc01 dhcpd[5585]: execute_statement argv[2] = 192.168.1.40
Apr 24 10:00:57 srvdc01 dhcpd[5585]: execute_statement argv[3] = 48:e1:e9:71:0e:cf
Apr 24 10:00:57 srvdc01 dhcpd[5585]: execute_statement argv[4] = Meross_Smart_Plug
Apr 24 10:00:57 srvdc01 dhcpd[12272]: Unable to execute /usr/share/zentyal-dhcp/dhcp-dyndns.sh: Permission denied
Apr 24 10:00:57 srvdc01 dhcpd[5585]: execute: /usr/share/zentyal-dhcp/dhcp-dyndns.sh exit status 32512
Apr 24 10:00:57 srvdc01 kernel: [  616.354148] audit: type=1400 audit(1650787257.598:25): apparmor="DENIED" operation="exec" profile="/usr/sbin/dhcpd" name="/usr/share/zentyal-dhcp/dhcp-dyndns.sh" pid=12272 comm="dhcpd" requested_mask="x" denied_mask="x" fsuid=118 ouid=0
Apr 24 10:00:57 srvdc01 dhcpd[5585]: DHCPREQUEST for 192.168.1.40 from 48:e1:e9:71:0e:cf (Meross_Smart_Plug) via eth0
Apr 24 10:00:57 srvdc01 dhcpd[5585]: DHCPACK on 192.168.1.40 to 48:e1:e9:71:0e:cf (Meross_Smart_Plug) via eth0

regarding DHCP I have executed the following command:
/usr/share/zentyal-dhcp/dhcp-dyndns.sh

Message:
Required keytab /etc/dhcp/samba-keys/dhcpduser.keytab not found, it needs to be created.
Use the following commands as root
samba-tool domain exportkeytab --principal=dhcpduser@ZENTYAL-DOMAIN.LAN /etc/dhcp/samba-keys/dhcpduser.keytab
chown XXXX:XXXX /etc/dhcp/samba-keys/dhcpduser.keytab
Replace 'XXXX:XXXX' with the user & group that dhcpd runs as on your distro
chmod 400 /etc/dhcp/samba-keys/dhcpduser.keytab

Executed the following command:
sudo samba-tool domain exportkeytab --principal=dhcpduser@ZENTYAL-DOMAIN.LAN /etc/dhcp/samba-keys/dhcpduser.keytab
sudo chown root:dhcpd /etc/dhcp/samba-keys/dhcpduser.keytab

But unfortunately the problem remains

Hi,

Well, you're facing 2 bugs:

1. With the antivirus module:

Code: [Select]
/usr/bin/clamonacc: No such file or directory

The binary 'clamonacc' has changed. Now I thing is '/usr/sbin/' instead of '/usr/bin/'. You need to change the daemon located at '/lib/systemd/system/zentyal.antivirus-clamonacc.service'. Remember to reload the Systemd configuration before restart the antivirus module.

Code: [Select]
sudo systemctl daemon-reload
sudo zs antivirus restart

2. Apparmor is blocking the usage of DDNS script.

Code: [Select]
Apr 24 10:00:57 srvdc01 kernel: [  616.354148] audit: type=1400 audit(1650787257.598:25): apparmor="DENIED" operation="exec" profile="/usr/sbin/dhcpd" name="/usr/share/zentyal-dhcp/dhcp-dyndns.sh" pid=12272 comm="dhcpd" requested_mask="x" denied_mask="x" fsuid=118 ouid=0

The link with the fix below:

* https://github.com/zentyal/zentyal/issues/1930

--
“This world is ours, and by the Holy Light we will keep it safe, now and forever".

mkugler

  • Zen Apprentice
  • *
  • Posts: 16
  • Karma: +0/-0
    • View Profile
Re: Problems saving network data
« Reply #6 on: May 14, 2022, 11:23:09 am »
Hi, first of all thank you very much for your help, I was on vacation for 2 weeks now so I couldn't get back to you. The problem with the antivirus I could solve by changing the path, the 2nd part I unfortunately do not understand exactly, how was the file called, must this be linked, can you help me here please again. Thanks in advance.

Antivirus changes: at '/lib/systemd/system/zentyal.antivirus-clamonacc.service' - Path to '/usr/sbin/'

sudo systemctl daemon-reload
sudo zs antivirus restart
---------------------
Regarding the memory problem, I created a file named "dhcpd" and stored the information from the link.
This is probably not correct, since the problem persists and I have not found any other solution on the Internet. Would you have another idea.

Many Thanks in advanced

Mathias

turalyon

  • Zen Monk
  • **
  • Posts: 94
  • Karma: +12/-0
    • View Profile
Re: Problems saving network data
« Reply #7 on: May 18, 2022, 11:21:35 am »
Hi,

Well, basically Apparmor is blocking the script that manages the DDNS feature. So, as the link explains, you have 2 alternatives:

1. Disable apparmor.
2. Tune the dhcpd profile of Apparmor.

Once you have applied one of those 2 solutions, I recommend you enable the debug in the script, so you can analyze each step until you confirm that it worked correctly. To do this, just add 'set -x' in the second line of the script located at '/usr/share/zentyal-dhcp/dhcp-dyndns.sh'.

Once you did all the above, try again to get a DHCP IP from a computer while you monitor the log file '/var/log/syslog'.

Code: [Select]
sudo tail -f /var/log/syslog

I hope it helps you.

mkugler

  • Zen Apprentice
  • *
  • Posts: 16
  • Karma: +0/-0
    • View Profile
Re: Problems saving network data
« Reply #8 on: May 19, 2022, 11:05:00 am »
Hi, thanks for your help, unfortunately this also did not lead to success. The main problem is still when I alone changes to the network e.g. assignment of a fixed IP address, then this is not saved, the process is not completed at all. In the syslog I have searched after a restart times for "error" and found some errors. I share these errors here again in the forum.

May 19 10:04:59 srvdc01 kernel: [    0.641692] RAS: Correctable Errors collector initialized.
May 19 10:04:59 srvdc01 kernel: [    8.173739] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,usrquota,grpquota,acl
May 19 10:05:03 srvdc01 networkd-dispatcher[1013]: ERROR:Unknown state for interface NetworkctlListState(idx=1, name='lo', type='loopback', operational='n/a', administrative='unmanaged'): n/a
May 19 10:05:03 srvdc01 networkd-dispatcher[1013]: ERROR:Unknown state for interface NetworkctlListState(idx=2, name='eth0', type='ether', operational='n/a', administrative='unmanaged'): n/a
May 19 10:05:03 srvdc01 networkd-dispatcher[1013]: ERROR:Unknown state for interface NetworkctlListState(idx=3, name='eth1', type='ether', operational='n/a', administrative='unmanaged'): n/a
May 19 10:05:03 srvdc01 networkd-dispatcher[1013]: ERROR:Unknown state for interface NetworkctlListState(idx=4, name='bond0', type='ether', operational='n/a', administrative='unmanaged'): n/a
May 19 10:10:01 srvdc01 amavis[4424]: ...45, in getaddrinfo\\n for res in _socket.getaddrinfo(host, port, family, type, proto, flags):\\nsocket.gaierror: [Errno -3] Temporary failure in name resolution\\nError in sys.excepthook:\\nTraceback (most recent call last):\\n File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 154, in apport_excepthook\\n os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f:\\nFileNotFoundError: [Errno 2] No such file or directory: '/var/crash/_usr_bin
or: [Errno -3] Temporary failure in name resolution\\nError in sys.excepthook:\\nTraceback (most recent call last):\\n File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 154, in apport_excepthook\\n os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f:\\nFileNotFoundError: [Errno 2] No such file or directory: '/var/crash/_usr_bin_pyzor.125.crash'\\n\\nOriginal exception was:\\nTraceback (most recent call last):\\n File "/usr/bin/pyzor", line 408, in <module>\\n main()\\n File
kages/apport_python_hook.py", line 154, in apport_excepthook\\n os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f:\\nFileNotFoundError: [Errno 2] No such file or directory: '/var/crash/_usr_bin_pyzor.125.crash'\\n\\nOriginal exception was:\\nTraceback (most recent call last):\\n File "/usr/bin/pyzor", line 408, in <module>\\n main()\\n File "/usr/bin/pyzor", line 152, in main\\n if not dispatch(client, servers, config):\\n File "/usr/bin/pyzor", line 241, in check\\n send_digest(digested,
, proto, flags):\\nsocket.gaierror: [Errno -3] Temporary failure in name resolution
May 19 10:10:01 srvdc01 amavis[4424]: _WARN: internal error, python traceback seen in response
May 19 10:10:02 srvdc01 amavis[4424]: SA dbg: pyzor: failure to parse response "socket.gaierror: [Errno -3] Temporary failure in name resolution"
May 19 10:10:02 srvdc01 amavis[4424]: SA dbg: pyzor: failure to parse response "Error in sys.excepthook:"
May 19 10:10:02 srvdc01 amavis[4424]: SA dbg: pyzor: failure to parse response "FileNotFoundError: [Errno 2] No such file or directory: '/var/crash/_usr_bin_pyzor.125.crash'"
May 19 10:10:02 srvdc01 amavis[4424]: SA dbg: pyzor: failure to parse response "socket.gaierror: [Errno -3] Temporary failure in name resolution"
May 19 10:10:02 srvdc01 amavis[4424]: _WARN: razor2: razor2 check failed:  razor2: razor2 had unknown error during get_server_info at /usr/share/perl5/Mail/SpamAssassin/Plugin/Razor2.pm line 186. at /usr/share/perl5/Mail/SpamAssassin/Plugin/Razor2.pm line 329.
May 19 10:10:21 srvdc01 clamonacc[5152]: ERROR: ClamClient: Could not connect to clamd, Couldn't connect to server
May 19 10:10:21 srvdc01 clamonacc[5152]: ERROR: Clamonacc: daemon is local, but a connection could not be established
May 19 10:10:27 srvdc01 clamonacc[5353]: ERROR: ClamClient: Could not connect to clamd, Couldn't connect to server
May 19 10:10:27 srvdc01 clamonacc[5353]: ERROR: Clamonacc: daemon is local, but a connection could not be established
May 19 10:10:32 srvdc01 clamonacc[5429]: ERROR: ClamClient: Could not connect to clamd, Couldn't connect to server
May 19 10:10:32 srvdc01 clamonacc[5429]: ERROR: Clamonacc: daemon is local, but a connection could not be established
May 19 10:10:37 srvdc01 clamonacc[5522]: ERROR: ClamClient: Could not connect to clamd, Couldn't connect to server
May 19 10:10:37 srvdc01 clamonacc[5522]: ERROR: Clamonacc: daemon is local, but a connection could not be established
May 19 10:10:42 srvdc01 clamonacc[5684]: ERROR: ClamClient: Could not connect to clamd, Couldn't connect to server
May 19 10:10:42 srvdc01 clamonacc[5684]: ERROR: Clamonacc: daemon is local, but a connection could not be established
May 19 10:10:43 srvdc01 sh[5657]: Error looking up domain users
May 19 10:10:47 srvdc01 clamonacc[5913]: ERROR: ClamClient: Could not connect to clamd, Couldn't connect to server
May 19 10:10:47 srvdc01 clamonacc[5913]: ERROR: Clamonacc: daemon is local, but a connection could not be established
May 19 10:10:51 srvdc01 sh[5657]: Error looking up domain users
May 19 10:10:53 srvdc01 sh[5657]: Error looking up domain users
May 19 10:10:54 srvdc01 sh[5657]: Error looking up domain users
r-strong -Wformat -Werror=format-security -fno-strict-aliasing -fno-delete-null-pointer-checks -DNO_VERSION_DATE -DDIG_SIGCHASE' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'
May 19 10:10:56 srvdc01 sh[5657]: Error looking up domain users
May 19 10:11:01 srvdc01 sh[5657]: Error looking up domain users
May 19 10:11:04 srvdc01 sh[5657]: Error looking up domain users
May 19 10:11:09 srvdc01 sh[5657]: Error looking up domain users
May 19 10:11:11 srvdc01 sh[5657]: Error looking up domain users
May 19 10:11:16 srvdc01 named[6184]: dispatch 0x7fe120513d20: shutting down due to TCP receive error: 204.61.216.126#53: connection reset
May 19 10:11:16 srvdc01 sh[5657]: Error looking up domain users
May 19 10:11:17 srvdc01 sh[5657]: Error looking up domain users
May 19 10:11:28 srvdc01 sh[5657]: Error looking up domain users
May 19 10:11:37 srvdc01 sh[5657]: Error looking up domain users
May 19 10:11:42 srvdc01 sh[5657]: Error looking up domain users
May 19 10:11:46 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:  37518
May 19 10:11:46 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:  44311
May 19 10:11:46 srvdc01 sh[5657]: 1877464019.sig-srvdc01.zentyal-domain.lan. 0 ANY TKEY gss-tsig. 1652947906 1652947906 3 NOERROR 1418 YIIFhgYJKoZIhvcSAQICAQBuggV1MIIFcaADAgEFoQMCAQ6iBwMFACAA AACjggRiYYIEXjCCBFqgAwIBBaEUGxJaRU5UWUFMLURPTUFJTi5MQU6i LDAqoAMCAQGhIzAhGwNETlMbGnNydmRjMDEuemVudHlhbC1kb21haW4u bGFuo4IEDTCCBAmgAwIBF6EDAgEBooID+wSCA/c9ModzNMPVreOIo1zB FBk9049cffqBwi46JS2krcN+4AOOVWcKerf4GKIKijiqdqGU3RFqUAbt j0kFkX4B4ODFX0Bnp4yJhrpNv2R9+O82hjpiiFiDFWNVsBxn1uGyG6YZ 1WFjVhpb6YQffQgmRBOWlKU
May 19 10:11:46 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:  44311
May 19 10:11:46 srvdc01 sh[5657]: 1877464019.sig-srvdc01.zentyal-domain.lan. 0 ANY TKEY gss-tsig. 1652947906 1652951506 3 NOERROR 152 YIGVBgkqhkiG9xIBAgICAG+BhTCBgqADAgEFoQMCAQ+idjB0oAMCARei bQRrxD5PfHLQJG2wKRMBoEpSY6MMlxjILrIwSTu9ZkK1aG5LWJJgz5d9 ehQCP8sBB58pA1PTEqRDsBkUif6NmQaHwhx8kftn1RwtU4VrORcsd/96 26gi/Afz0BSUOD2I+lnfTUQjQDmX8yETrNw= 0
May 19 10:11:46 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id:  54140
May 19 10:11:46 srvdc01 sh[5657]: 1877464019.sig-srvdc01.zentyal-domain.lan. 0 ANY TSIG gss-tsig. 1652947906 300 28 BAQE//////8AAAAAAADbiNr94+svENwTLbzrxw== 54140 NOERROR 0
May 19 10:11:46 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id:  54140
May 19 10:11:46 srvdc01 sh[5657]: 1877464019.sig-srvdc01.zentyal-domain.lan. 0 ANY TSIG gss-tsig. 1652947906 300 28 BAQF//////8AAAAAJMHucbUnhPQWKyrtyVd28g== 54140 NOERROR 0
May 19 10:11:46 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id:  48155
May 19 10:11:47 srvdc01 sh[5657]: zentyal-domain.lan.#0110#011ANY#011TSIG#011hmac-md5.sig-alg.reg.int. 1652947906 300 16 sAIlsIK2XDYtmFM/576m9g== 48155 NOERROR 0
May 19 10:11:47 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id:  48155
May 19 10:11:47 srvdc01 sh[5657]: zentyal-domain.lan.#0110#011ANY#011TSIG#011hmac-md5.sig-alg.reg.int. 1652947906 300 16 mvsvI7ZrP0YRTDP44TTS3g== 48155 NOERROR 0
May 19 10:12:26 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:  22997
May 19 10:12:26 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:  15265
May 19 10:12:26 srvdc01 sh[5657]: 3489801607.sig-srvdc01.zentyal-domain.lan. 0 ANY TKEY gss-tsig. 1652947946 1652947946 3 NOERROR 1419 YIIFhwYJKoZIhvcSAQICAQBuggV2MIIFcqADAgEFoQMCAQ6iBwMFACAA AACjggRiYYIEXjCCBFqgAwIBBaEUGxJaRU5UWUFMLURPTUFJTi5MQU6i LDAqoAMCAQGhIzAhGwNETlMbGnNydmRjMDEuemVudHlhbC1kb21haW4u bGFuo4IEDTCCBAmgAwIBF6EDAgEBooID+wSCA/c9ModzNMPVreOIo1zB FBk9049cffqBwi46JS2krcN+4AOOVWcKerf4GKIKijiqdqGU3RFqUAbt j0kFkX4B4ODFX0Bnp4yJhrpNv2R9+O82hjpiiFiDFWNVsBxn1uGyG6YZ 1WFjVhpb6YQffQgmRBOWlKU
May 19 10:12:26 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:  15265
May 19 10:12:26 srvdc01 sh[5657]: 3489801607.sig-srvdc01.zentyal-domain.lan. 0 ANY TKEY gss-tsig. 1652947946 1652951546 3 NOERROR 152 YIGVBgkqhkiG9xIBAgICAG+BhTCBgqADAgEFoQMCAQ+idjB0oAMCARei bQRrj65M8+ZQuNJAyWJ4it1jwYGpAHLuM7kT8HmuZ5l1IyASzOmy681X wCPv7PAY0EEuooQdzIgRg5XB0jq0NmjXMINeMd+H9d3Ic8aqBoNCxGzn jawpnkpvwFmQhmaTizV3km1nlPIwZvpvxQU= 0
May 19 10:12:26 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id:  43490
May 19 10:12:26 srvdc01 sh[5657]: 3489801607.sig-srvdc01.zentyal-domain.lan. 0 ANY TSIG gss-tsig. 1652947946 300 28 BAQE//////8AAAAAMBuJWIswtbC37iQxs+Jw4g== 43490 NOERROR 0
May 19 10:12:26 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id:  43490
May 19 10:12:26 srvdc01 sh[5657]: 3489801607.sig-srvdc01.zentyal-domain.lan. 0 ANY TSIG gss-tsig. 1652947946 300 28 BAQF//////8AAAAACZ0OOIpokVeavk9BuG2ZCA== 43490 NOERROR 0
May 19 10:12:26 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id:  27009
May 19 10:12:26 srvdc01 sh[5657]: zentyal-domain.lan.#0110#011ANY#011TSIG#011hmac-md5.sig-alg.reg.int. 1652947946 300 16 Zztq8NbDngiW+tNNWfBTUg== 27009 NOERROR 0
May 19 10:12:26 srvdc01 sh[5657]: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id:  27009
May 19 10:12:26 srvdc01 sh[5657]: zentyal-domain.lan.#0110#011ANY#011TSIG#011hmac-md5.sig-alg.reg.int. 1652947946 300 16 8enTLELU39BO3z2Acgu3kg== 27009 NOERROR 0
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: async: query 30710/IN/A/linkedin.com.dbl.spamhaus.org already underway, adding no.3 URIBL_DBL_ERROR
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: dns: URIBL_DBL_ERROR lookup start
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: async: query 45237/IN/A/en25.com.dbl.spamhaus.org already underway, adding no.3 URIBL_DBL_ERROR
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: dns: URIBL_DBL_ERROR lookup start
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: async: query 49301/IN/A/sophos.com.dbl.spamhaus.org already underway, adding no.3 URIBL_DBL_ERROR
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: dns: URIBL_DBL_ERROR lookup start
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: async: query 49301/IN/A/sophos.com.dbl.spamhaus.org already underway, adding no.13 URIBL_DBL_ERROR
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: dns: URIBL_DBL_ERROR lookup start
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: async: query 9287/IN/A/sophos.de.dbl.spamhaus.org already underway, adding no.3 URIBL_DBL_ERROR
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: dns: URIBL_DBL_ERROR lookup start
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: async: query 48110/IN/A/kuglerm.de.dbl.spamhaus.org already underway, adding no.3 URIBL_DBL_ERROR
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: dns: URIBL_DBL_ERROR lookup start
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: async: query 49301/IN/A/sophos.com.dbl.spamhaus.org already underway, adding no.23 URIBL_DBL_ERROR
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: dns: URIBL_DBL_ERROR lookup start
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: async: query 49301/IN/A/sophos.com.dbl.spamhaus.org already underway, adding no.33 URIBL_DBL_ERROR
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: dns: URIBL_DBL_ERROR lookup start
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: async: query 49301/IN/A/sophos.com.dbl.spamhaus.org already underway, adding no.43 URIBL_DBL_ERROR
May 19 10:12:31 srvdc01 amavis[4655]: (04655-01) SA dbg: dns: URIBL_DBL_ERROR lookup start
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: async: calling callback on key DNSBL:linkedin.com:dbl.spamhaus.org, rule URIBL_DBL_ERROR
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: uridnsbl: complete_dnsbl_lookup URIBL_DBL_ERROR DNSBL:linkedin.com:dbl.spamhaus.org
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: async: calling callback on key DNSBL:en25.com:dbl.spamhaus.org, rule URIBL_DBL_ERROR
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: uridnsbl: complete_dnsbl_lookup URIBL_DBL_ERROR DNSBL:en25.com:dbl.spamhaus.org
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: async: calling callback on key DNSBL:kuglerm.de:dbl.spamhaus.org, rule URIBL_DBL_ERROR
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: uridnsbl: complete_dnsbl_lookup URIBL_DBL_ERROR DNSBL:kuglerm.de:dbl.spamhaus.org
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: async: calling callback on key DNSBL:sophos.de:dbl.spamhaus.org, rule URIBL_DBL_ERROR
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: uridnsbl: complete_dnsbl_lookup URIBL_DBL_ERROR DNSBL:sophos.de:dbl.spamhaus.org
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: async: calling callback on key DNSBL:sophos.com:dbl.spamhaus.org, rule URIBL_DBL_ERROR
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: uridnsbl: complete_dnsbl_lookup URIBL_DBL_ERROR DNSBL:sophos.com:dbl.spamhaus.org
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: async: calling callback on key DNSBL:sophos.com:dbl.spamhaus.org, rule URIBL_DBL_ERROR
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: uridnsbl: complete_dnsbl_lookup URIBL_DBL_ERROR DNSBL:sophos.com:dbl.spamhaus.org
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: async: calling callback on key DNSBL:sophos.com:dbl.spamhaus.org, rule URIBL_DBL_ERROR
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: uridnsbl: complete_dnsbl_lookup URIBL_DBL_ERROR DNSBL:sophos.com:dbl.spamhaus.org
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: async: calling callback on key DNSBL:sophos.com:dbl.spamhaus.org, rule URIBL_DBL_ERROR
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: uridnsbl: complete_dnsbl_lookup URIBL_DBL_ERROR DNSBL:sophos.com:dbl.spamhaus.org
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: async: calling callback on key DNSBL:sophos.com:dbl.spamhaus.org, rule URIBL_DBL_ERROR
May 19 10:12:33 srvdc01 amavis[4655]: (04655-01) SA dbg: uridnsbl: complete_dnsbl_lookup URIBL_DBL_ERROR DNSBL:sophos.com:dbl.spamhaus.org

turalyon

  • Zen Monk
  • **
  • Posts: 94
  • Karma: +12/-0
    • View Profile
Re: Problems saving network data
« Reply #9 on: May 19, 2022, 03:47:50 pm »
Hi,

If I were you, I would disable the Antivirus and Mailfilter modules temporarily so the log files (syslog and zentyal.log) could be easier to read while debugging the issue.

--
“This world is ours, and by the Holy Light we will keep it safe, now and forever".

mkugler

  • Zen Apprentice
  • *
  • Posts: 16
  • Karma: +0/-0
    • View Profile
Re: Problems saving network data
« Reply #10 on: May 20, 2022, 11:41:46 am »
I turned off antivirus and mail filter, the following errors remained:

May 20 10:45:48 srvdc01 networkd-dispatcher[935]: ERROR:Unknown state for interface NetworkctlListState(idx=1, name='lo', type='loopback', operational='n/a', administrative='unmanaged'): n/a
May 20 10:45:48 srvdc01 networkd-dispatcher[935]: ERROR:Unknown state for interface NetworkctlListState(idx=2, name='eth0', type='ether', operational='n/a', administrative='unmanaged'): n/a
May 20 10:45:48 srvdc01 networkd-dispatcher[935]: ERROR:Unknown state for interface NetworkctlListState(idx=3, name='eth1', type='ether', operational='n/a', administrative='unmanaged'): n/a
May 20 10:45:48 srvdc01 networkd-dispatcher[935]: ERROR:Unknown state for interface NetworkctlListState(idx=4, name='bond0', type='ether', operational='n/a', administrative='unmanaged'): n/a

For this I found a troubleshooting on the Internet, but it did not solve the problem, after I renamed the path, the whole network stopped working, the system was no longer pingable, etc.. I have then undone this again, so that the system at least works again.

https://forums.debian.net/viewtopic.php?t=135550

turalyon

  • Zen Monk
  • **
  • Posts: 94
  • Karma: +12/-0
    • View Profile
Re: Problems saving network data
« Reply #11 on: May 23, 2022, 10:53:13 am »
I didn't see that error before. Perhaps it is time to contact sales so they can inform you about getting a support ticket.

--
“This world is ours, and by the Holy Light we will keep it safe, now and forever".

mkugler

  • Zen Apprentice
  • *
  • Posts: 16
  • Karma: +0/-0
    • View Profile
Re: Problems saving network data
« Reply #12 on: May 25, 2022, 10:32:45 am »
Hello everyone, first of all I would like to thank you for the help here, I have looked at everything again over the last few days and sometimes the problem is right in front of my eyes. First of all the problem is solved, but what was it?
After my last post I looked at the file Interfaces under /etc/network/ and there I found the entry for network card bundling, but since I haven't set up any bundling it can't work. Under the Zentyal VM I deactivated the second interface completely - it was activated but not configured - after I restarted the server twice, all errors and problems were gone. I don't know why Zentyal tried to create a bundle, as I didn't have it configured myself. I am just glad that this solved the problem. Thanks again for the help here.