Recent Posts

Pages: [1] 2 3 ... 10
1
I had some issues after upgrading too, with both the Antivirus and MySQL, resolved with the help of steps provided by Daniel - thank you!

Hi,

We are debugging the antivirus issue, we believe three things should be analyzed:

1. The server was not rebooted after the upgrade, so the directory /var/run/clamav does not belong to the owner clamav.


 Ensure the directory /var/run/clamav belongs to clamav as chapderprinz suggested.
   
    sudo chown -R clamav /var/run/clamav/
   

4. Restart the module through the CLI:
   
    sudo zs antivirus restart
   


... <snip> ..

Best regards, Daniel Joven.


That fixed the same antivirus issue for us.

And the MySQL error on trying to login:

Code: [Select]
2024/04/26 11:04:02 ERROR> MyDBEngine.pm:200 EBox::MyDBEngine::_connect - Connection DB Error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
 at Connection DB Error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
 at /usr/share/perl5/EBox/MyDBEngine.pm line 200

The following fixed that issue (copied from another post by Daniel and edited down a bit):
Quote
check mysql running status:

   
Code: [Select]
sudo systemctl status mysql   
Status, inactive:

Code: [Select]
○ mysql.service - MySQL Community Server
     Loaded: loaded (/lib/systemd/system/mysql.service; disabled; vendor preset: enabled)
     Active: inactive (dead)
   
If it is stopped (inactive), run the following commands:
   
Code: [Select]
mkdir /var/log/mysql/
    chown -R mysql:adm /var/log/mysql
    chmod -R 0770 /var/log/mysql
    systemctl restart mysql
   

Status Update on 29/04/2024 - issues returned
Issues continue:  We have been getting intermittent network connectivity issues since the upgrade, with users on DHCP leased IP's.  Static IP systems (couple of users and various printers and servers) seem unaffected.

The AntiVirus and MySql issues returned on our PDC (which also runs the DHCP service), with the antivirus stopping and not restarting.
Tried to reset the permission on the clamav folder, but result was the directory not found:
Code: [Select]
sudo chown -R clamav /var/run/clamav/
chown: cannot access '/var/run/clamav/': No such file or directory

So as per the upgrade guidance instructions on https://doc.zentyal.org/en/upgrade.html#antivirus-module re-ran the dpkg command for clamav:

Code: [Select]
sudo dpkg-reconfigure clamav-daemon
Service still failed to start.  Result in the error log showed:

Code: [Select]
Mon Apr 29 11:48:30 2024 -> ERROR: LOCAL: Could not create socket directory: /var/run/clamav: Permission denied
47 Mon Apr 29 11:48:30 2024 -> ERROR: LOCAL: Socket file /var/run/clamav/clamd.ctl could not be bound: No such file or directory

I re-ran the clamav config

Code: [Select]
sudo dpkg-reconfigure clamav-daemon
This time,  I selected YES to handling the configuration file automatically - the opposite to the upgrade guidance.  Went through that accepting the defaults - it recreated the missing /var/run/clamav/ folder for us, and added the missing clamd.ctl file.
This seems to have sorted it, the service has remained running for the last 15 minutes...

MySQL
The mysql error occurred again when trying to check the DHCP module from the web admin (though the dashboard was displaying OK).

Checked the mysql status in CLI:
Code: [Select]
~$ sudo systemctl status mysql
[sudo] password for copeadmin:
○ mysql.service - MySQL Community Server
     Loaded: loaded (/lib/systemd/system/mysql.service; disabled; vendor preset: enabled)
     Active: [b]inactive[/b] (dead)

Checked the current permissions in the mysql log directory:
Code: [Select]
~$ sudo ls -lh /var/log/mysql
total 12K
-rw-r----- 1 mysql adm     0 Apr 29 00:00 error.log
-rw-r----- 1 mysql adm    20 Apr 28 00:00 error.log.1.gz
-rw-r----- 1 mysql adm    20 Apr 27 00:00 error.log.2.gz
-rw-r----- 1 mysql mysql 942 Apr 26 19:05 error.log.3.gz
Note the difference in owner for file dated 26/04, when it ought to match the other 3 files (mysql:adm).  This had previously been corrected on 26/04 in the morning.  I had rebooted the server after office hours, but afraid I can't recall exact time - I don't think it was as late as 19:00 though.

So reapplied the permission chown commands:
Code: [Select]
sudo chown -R mysql:adm /var/log/mysql
sudo chmod -R 0770 /var/log/mysql

Result:
Code: [Select]
~$ sudo ls -lh /var/log/mysql
total 12K
-rwxrwx--- 1 mysql adm   0 Apr 29 00:00 error.log
-rwxrwx--- 1 mysql adm  20 Apr 28 00:00 error.log.1.gz
-rwxrwx--- 1 mysql adm  20 Apr 27 00:00 error.log.2.gz
-rwxrwx--- 1 mysql adm 942 Apr 26 19:05 error.log.3.gz

And then restarted mysql again.

sudo systemctl restart mysql

And check status again - OK:

Code: [Select]
~$ sudo systemctl status mysql
● mysql.service - MySQL Community Server
     Loaded: loaded (/lib/systemd/system/mysql.service; disabled; vendor preset: enabled)
     Active: active (running) since Mon 2024-04-29 10:24:57 BST; 4s ago
    Process: 3236229 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
   Main PID: 3236248 (mysqld)
     Status: "Server is operational"
      Tasks: 39 (limit: 7071)
     Memory: 437.9M
        CPU: 1.527s
     CGroup: /system.slice/mysql.service
             └─3236248 /usr/sbin/mysqld

So it's OK again for now - but worrying I had to re-apply the permission changes on the log directory again.  I don't want to be having to re-apply this every day!

2
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

3
I had some issues after upgrading too, with both the Antivirus and MySQL, resolved with the help of steps provided by Daniel - thank you!

Hi,

We are debugging the antivirus issue, we believe three things should be analyzed:

1. The server was not rebooted after the upgrade, so the directory /var/run/clamav does not belong to the owner clamav.


 Ensure the directory /var/run/clamav belongs to clamav as chapderprinz suggested.
   
    sudo chown -R clamav /var/run/clamav/
   

4. Restart the module through the CLI:
   
    sudo zs antivirus restart
   


... <snip> ..

Best regards, Daniel Joven.


That fixed the same antivirus issue for us.

And the MySQL error on trying to login:

Code: [Select]
2024/04/26 11:04:02 ERROR> MyDBEngine.pm:200 EBox::MyDBEngine::_connect - Connection DB Error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
 at Connection DB Error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
 at /usr/share/perl5/EBox/MyDBEngine.pm line 200

The following fixed that issue (copied from another post by Daniel and edited down a bit):
Quote
check mysql running status:

   
Code: [Select]
sudo systemctl status mysql   
Status, inactive:

Code: [Select]
○ mysql.service - MySQL Community Server
     Loaded: loaded (/lib/systemd/system/mysql.service; disabled; vendor preset: enabled)
     Active: inactive (dead)
   
If it is stopped (inactive), run the following commands:
   
Code: [Select]
mkdir /var/log/mysql/
    chown -R mysql:adm /var/log/mysql
    chmod -R 0770 /var/log/mysql
    systemctl restart mysql
   
4
Installation and Upgrades / Problems for install Zentyal on Ubuntu ARM
« Last post by dgalvarro on April 25, 2024, 05:46:09 pm »
Hello guys i tried to install zentyal on Ubuntu ARM. Is possible install?

All packages are up to date.
- Installing Zentyal...
Reading package lists... Done Building dependency tree... Done Reading state information... Done
E: Unable to locate package zentyal
E: Unable to locate package zenbuntu-core

Hit:7 https://packages.zentyal.org/zentyal 8.0 InRelease
Reading package lists... Done Building dependency tree... Done Reading state information... Done
All packages are up to date.
Skipping acquire of configured file 'main/binary-arm64/Packages' as repositor y 'https://packages.zentyal.org/zentyal 8.0 InRelease' doesn't support architect ure 'arm64'
N: Skipping acquire of configured file 'extra/binary-arm64/Packages' as reposito ry 'https://packages.zentyal.org/zentyal 8.0 InRelease' doesn't support architec ture 'arm64'
5
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
6
Installation and Upgrades / Re: SMTP Connection time out
« Last post by veerababu0724 on April 25, 2024, 09:16:02 am »
is your problem is resolved ?
if it is resolved can you help me i have also same problem
my mail id veerababu0724@gmail.com
7
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.
8
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
9
Hi,

We have updated the official documentation with the mentioned steps in my previous answer about the Antivirus module. Below you have the links.

* https://doc.zentyal.org/en/upgrade.html#antivirus-module
* https://doc.zentyal.org/es/upgrade.html#modulo-de-antivirus

Again, thank you for reporting the issues.

Best regards, Daniel Joven.
10
News and Announcements / Upgrade from Zentyal 7.1 to 8.0 is now available
« Last post by blorente on April 16, 2024, 08:41:13 pm »
Hi all,

The upgrade path from Zentyal Server Development 7.1 to 8.0 has been published now. When you upgrade the 'zentyal-core' package to its latest version, "Upgrade button" will appear on the Dashboard.

We would recommend you to follow this checklist to avoid issues:

* Make sure you don't have pending updates
* Back up your server and data before upgrading
* Make sure that there are no errors in the /var/log/zentyal/zentyal.log file
* Make sure that there is space available on the disk
* Make sure that the server is updated
* Make sure that there are no broken packages
* Make sure that there are no errors in the internal Samba database or in the MySQL databases
* Make sure that you have Internet connectivity
* Click on the Upgrade button on the Dashboard
* Make sure that the packages have been updated

The official documentation for Zentyal Server 8.0 will include more detailed instructions.

Looking forward to receiving your feedback and comments.
Pages: [1] 2 3 ... 10