Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Daniel Joven

Pages: [1] 2 3 ... 5
1
Manually deleting entries does not solve the problem. File /etc/netplan/netplan.yaml is created from information stored somewhere else and that is where it needs to be removed.

Hi,

To fix this issue, please, go to the following link:

* https://github.com/zentyal/zentyal/issues/2167#issuecomment-2208417078

2
Hi ggallo,

First of all, thank you for the detailed explanation of your upgrade process from the very old Zentyal 5 version.

About the MySQL issue, we thought it was fixed with the below function in the script but apparently, it does not cover all the cases. Do you remember if this issue caused the upgrade to fail?

* https://github.com/zentyal/zentyal/blob/7.1/main/core/src/scripts/release-upgrade#L352

Regarding ClamAV and Sogo, as you found out, it looks like it is an issue caused by the version of Zentyal you upgraded from. However, we are going to do some tests in our internal lab and if it is necessary, we will update the script, the documentation, or both.

Again, thank you for sharing.

Best regards, Daniel Joven.

3
Other modules / Re: DHCP Leases file garbage?
« on: June 28, 2024, 10:07:28 am »
Zentyal version 8.0.3.  We have been using Zentyal for many years.

We have recently started having issues with our DHCP causing loss of client device connectivity.  Clients devices seem to be losing IP addresses for a period of time before re-establishing new ones.

We are a moderately small office and have just one range of DHCP IP's available (currently 10.0.0.59 - 10.0.0.254), the rest being reserved for servers, some Dev PC's and other network devices such as printers, switches etc.

Looking at the content of our leases file (/var/lib/dhcp/dhcpd.leases), we see a mix of some very old expired leases (from November 2023), current leases (3rd June 2024) and some leases (current) with some sort of scripting for "on expiry" and "on release".

I don't know if the two script blocks are legitimate entries, since not all entries have this format.

Our leases file is also getting very long, with over eight TEN thousand lines (increased during time of writing this post) of lease entries (lines bulked by the coded outputs as exampled below), almost all of them dated for today.

Example of the scripting:

Code: [Select]
on expiry {
    set ClientIP =
       binary-to-ascii (10, 8, ".", leased-address) ;
    log (debug,
        concat ("Expired: IP: ", ClientIP));
    execute ("/usr/share/zentyal-dhcp/dhcp-dyndns.sh", "delete", ClientIP, "", "0");
  }
  on release {
    set ClientIP =
       binary-to-ascii (10, 8, ".", leased-address) ;
    set ClientDHCID =
       concat (concat (concat (concat (concat (concat (concat (concat (concat (
                                                                               concat
                                                                              (
                                                                             suffix
                                                                              (
                                                                             concat
                                                                              (
                                                                             "0",
                                                                             
                                                                             
                                                                             binary-to-ascii
                                                                              (16
                                                                             ,
                                                                             8,
                                                                             ""
                                                                             ,
                                                                             
                                                                             substring
                                                                              (
                                                                             hardware,
                                                                             1,
                                                                             1)
                                                                             ))
                                                                             ,
                                                                             2)
                                                                             ,
                                                                               ":")
                                                                               ,
                                                                               
                                                                               suffix
                                                                              (
                                                                             concat
                                                                              (
                                                                             "0",
                                                                             
                                                                             
                                                                             binary-to-ascii
                                                                              (16
                                                                             ,
                                                                             8,
                                                                             ""
                                                                             ,
                                                                             
                                                                             substring
                                                                              (
                                                                             hardware,
                                                                             2,
                                                                             1)
                                                                             ))
                                                                             ,
                                                                             2)
                                                                       ), ":"),
                                                               
                                                               suffix (concat (
                                                                               "0",
                                                                               
                                                                               
                                                                               binary-to-ascii
                                                                              (16
                                                                             ,
                                                                             8,
                                                                             ""
                                                                             ,
                                                                             
                                                                             substring
                                                                              (
                                                                             hardware,
                                                                             3,
                                                                             1)
                                                                               ))
                                                                       , 2)),
                                                       ":"),
                                               suffix (concat ("0",
                                                               binary-to-ascii
                                                               (16, 8, "",
                                                                substring (
                                                                           hardware,
                                                                4, 1))), 2)),
                                       ":"),
                               suffix (concat ("0",
                                               binary-to-ascii (16, 8, "",
                                                                substring (
                                                                           hardware,
                                                                5, 1))), 2)),
                       ":"),
               suffix (concat ("0",
                               binary-to-ascii (16, 8, "",
                                                substring (hardware, 6, 1))), 2
               )) ;
    log (debug,
        concat ("Release: IP: ", ClientIP));
    execute ("/usr/share/zentyal-dhcp/dhcp-dyndns.sh", "delete", ClientIP, ClientDHCID);
  }


Can anyone enlighten me as to whether we have a buggy DHCP service (if so, what should I do to remedy), and whether I should try deleting the old or oddly-formed lease entries from the file in an effort to resolve it?

(I have made a backup copy of the file already.)

Thanks in advance,
Alec

=============== UPDATE (4th June 24) ================
Applying some basic troubleshooting/elimination processes on our network devices, I turned off our new WiFi AP (an Ubiquiti U7 Pro) and the address loss/reclaiming seems to have stabilised.  Perhaps a bit early to tell after only a couple of hours, as we had seen things stabilise after the morning anyway - so tomorrow morning should provide the real test of whether that device had been doing something rogue on the LAN.  It had applied an update back on 9th May (to v. 7.0.47), and we think that date is around when we started seeing the connectivity issues, but not sure why it had become increasingly worse during the last couple of weeks.

Have ordered a pair of NetGear AP's to test/replace the Ubiqiti stuff...
==============================================


Hi AlecM,

We have checked the DHCP behavior you reported in our internal lab and we have confirmed that this is a bug, concretely, with the managing of the reverse zone. We have added it to our roadmap.

In order to let people know about this, we strongly recommend you create a new issue in GitHub and hopefully, someone can contribute.

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

Thank you for sharing the issue.

Best regards, Daniel Joven.

4
Where is this info stored so that I can remove the virtual interfaces???

The network configuration is in /etc/netplan/netplan.yaml. The virtual interfaces entries are like this:

Code: [Select]
eth0.eth02:
      dhcp4: false
      dhcp6: false
      match:
        name: eth0.eth02
      set-name: eth0.eth02
      addresses:
        - 10.1.10.1/24
#            label: "eth0:eth02"

Those kinds of entries must be removed manually. After that, you must restart the network module:

Code: [Select]
sudo zs network restart

5
Hi,

What repositories do you have configured? Perhaps you have some Ubuntu repository for previous versions that is causing this issue. Additionally, you can run the following commands to see from what repository is trying to fetch the packages:


Code: [Select]

sudo apt update

sudo apt policy zentyal-samba samba zentyal-openvpn openvpn frr zentyal-ips suricata


Finally, what errors do you get when you try to install those packages?

Best regards, Daniel Joven.

6
Hi,

If the webadmin module is running and the server does not have any lock file or load issues, the 504 error might be related to the bug we have fixed and released today in the package zentyal-core 8.0.3, below you have the commit.

- https://github.com/zentyal/zentyal/commit/da6fcd411e3a3acea43d8581eb972f3ba901556d#diff-f2da1cfc0ddd16974080efa028f11a9c2c83db2d36b364d89fabc8f70e797da0

Basically, the webadmin module does a HTTP query to the certain public web page, and if the server that manages that page has load issues, the webadmin module might thrown an error. With this fix, that issue should be solved.

Best regards, Daniel Joven.

7
Hi,

We have added the following section in the upgrade documentation regarding this deprecated feature in Zentyal 8.0.

* https://doc.zentyal.org/en/upgrade.html#virtual-interfaces
* https://doc.zentyal.org/es/upgrade.html#intefaces-virtuales

Thank you again for reporting this behavior.

8
Hi David,

Here is the output:

root@mail:/home/strama_admin# sudo apt policy zentyal-sogo
zentyal-sogo:
  Telepítve: (nincs)
  Jelölt:    8.0.0
  Verziótáblázat:
     8.0.0 500
        500 https://packages.zentyal.org/zentyal 8.0/main amd64 Packages
        500 https://packages.zentyal.org/zentyal 8.0/main i386 Packages
     7.0.0 500
        500 file:/var/tmp/zentyal-packages ./ Packages

root@mail:/home/strama_admin# sudo apt policy sogo
sogo:
  Telepítve: (nincs)
  Jelölt:    5.5.1-1
  Verziótáblázat:
     5.5.1-1 500
        500 http://hu.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
     5.0.1.20201214-1 500
        500 file:/var/tmp/zentyal-packages ./ Packages
root@mail:/home/strama_admin#

root@mail:/home/strama_admin# sudo apt policy gnustep-base-common
gnustep-base-common:
  Telepítve: (nincs)
  Jelölt:    1.28.0-4build1
  Verziótáblázat:
     1.28.0-4build1 500
        500 http://hu.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
        500 http://hu.archive.ubuntu.com/ubuntu jammy/universe i386 Packages
     1.26.0-7 500
        500 file:/var/tmp/zentyal-packages ./ Packages
root@mail:/home/strama_admin#

Please let me know if you needm ore information.

BR,
GáborS

Hi GáborS,

The initial local repository of Zentyal that is set when Zentyal is installed through the ISO file is still active and because of that, the behavior you get. You must search for the following repository and remove it:

Code: [Select]
deb [trusted=yes] file://file:/var/tmp/zentyal-packages ./

It might be located at /etc/apt/sources.list.d/zentyal-temporal.list , /etc/apt/sources.list or in a similar location.

Once you find it, remove it and then, run the following command:

Code: [Select]
sudo apt update

After that, you should be able to install zentyal-sogo package.

9
Hi,

Thank you for reporting this behavior. Could you please tell us where the configuration remained after the upgrade? We have identified that certain configuration remains in the configuration file /etc/netplan/netplan.yaml

Best regards, Daniel Joven.

10
Hi David,

You mean this command:
sudo apt policy zentyal-sogo
sudo apt policy sogo
sudo apt policy gnustep-base-common

It is not solve the issue, but produce same error message:

The following packages have unmet dependencies:
libgnustep-base1.26 : Depends: gnustep-base-common (= 1.26.0-7) but 1.28.0-4build1 is to be installed
Depends: libicu66 (>= 66.1-1~) but it is not installable


BR,
GáborS

The goal of those commands is to get more information about your Zentyal, concretely, for your repositories.

11
Hi Daniel,

Here is the requested logs...
https://nextcloud.bemutatjuk.eu/index.php/s/s83n9s4oc8rGLH2

Please let me know if you need more information in this case.

Hi,

I cannot determine why the module is being removed. According to the log files, the package 'zentyal-sogo 8.0.0' is installed but for some reason, it is uninstalled later. What about the results of the commands I mentioned to you?


12
Thanks Daniel!
You were quite correct, our mysql was not set to start with the system.
Code: [Select]
~$ sudo systemctl is-enabled mysql
disabled
So enabled as you indicated:
Code: [Select]
~$ sudo systemctl enable mysql
Synchronizing state of mysql.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable mysql
Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → /lib/systemd/system/mysql.service.

Checked the permissions on the log folder - I think it's correct? (mysql:adm)
Code: [Select]
~$ sudo ls -ld /var/log/mysql/
drwxrwx--- 2 mysql adm 4096 Apr 30 00:00 /var/log/mysql/

Thanks again Daniel.  I have just checked the service status after 24 hours, to allow for log rotation, and happy to report that it is still "enabled" at this point:

Code: [Select]
~$ sudo systemctl is-enabled mysql
enabled

Hi,

Please, can you confirm that the Mysql log rotations are not breaking the service and everything is working as expected once you have enabled the service?

13
Hi AlecM,

About the mysql issue, a few things I saw in your output:

1. The service is not enabled, so when the server is rebooted, it does not start.
   
Code: [Select]
    # To confirm that it is disabled
    sudo systemctl is-enabled mysql
   
    # To enable
    sudo systemctl enable mysql
   
   
2. The permission behavior is probably caused by logrotate, you can check this out by analyzing the configuration file /etc/logrotate.d/mysql-server

NOTE: You should check the permissions of the folder as well (sudo ls -ld /var/log/mysql/)

If it is possible, just fix step 1 and only check step 2 but do not make any changes, let’s see tomorrow when the system rotates the logs if the issue is fixed or if a change must be done in the mentioned configuration file.

14
Hi Daniel,

I appreciate your help,

Before i started the upgrade I did all of the check steps and I didn't see any error

Yes, the proper and up-to-date repository data will be used.

The first time when I wrote I used a live server clone this server contains the webmail module and this module is actively used. But today I created an empty 7.0 server, during the upgrade from 7.0 to 8.0 I didn't experience any issues but when I tried to deploy the webmail module it showed same  error


BR,
GáborS

Hi,

The script uninstalls temporarily the zentyal-webmail package and installs it later. Also, it does a database backup and restores it, just to avoid any issues during this process. Unfortunately, without the required information, we cannot know what might happen in your upgrade. You must schedule another upgrade and in case you get the same error, you must run the mentioned commands and also, analyze the following log files:
  • /var/log/zentyal/upgrade.log
  • /var/log/zentyal/zentyal.log
  • /var/log/dpkg.log


15
Hi,

I made a upgrade by the web page official guide but the webmail module is disappeared after the upgrade, and when i try to reinstall it in that case i got the following error message:
The following packages have unmet dependencies:
libgnustep-base1.26 : Depends: gnustep-base-common (= 1.26.0-7) but 1.28.0-4build1 is to be installed
Depends: libicu66 (>= 66.1-1~) but it is not installable

Somebody can help in this case.

BR,
GáborS

Hi Gábor,

Below you have a few questions that might help you to find the issue with the Webmail module:

1. Did you confirm that all the Zentyal packages are correctly installed and there is anything broken or removed?

Code: [Select]
dpkg -l | egrep ‘zen(buntu|tyal)-’
dpkg -l | egrep -v ‘^ii’
lsb_release -a

2. Did you ensure that you are using the right repositories? Perhaps you have an old Zentyal repository that is causing the issue.

Code: [Select]
sudo apt update

3. Did you check where the webmail module and its main dependency is going to be installed?

Code: [Select]
sudo apt policy zentyal-sogo
sudo apt policy sogo
sudo apt policy gnustep-base-common

Hope the above helps you.

Best regards, Daniel Joven.

Pages: [1] 2 3 ... 5