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

We have issued a new certificate. Now you can use HTTPS in your repository configuration.

Thank you for your feedback.

Best regards, Daniel Joven.

Other modules / Re: Webadmin error, after update.
« on: September 17, 2021, 12:57:20 pm »

This error is a bug that is reported is Github.


Best regards, Daniel Joven.

Email and Groupware / Re: Zentyal 7.0 Sogo-Sieve dont work
« on: August 23, 2021, 10:53:29 am »

This behaviour is a bug reported, below you have the ticket. Until Developers Team fix it, you can set a valid email address to the postmaster box in the Zentyal Admin Interface.


Best regards, Daniel Joven.

Hi Gilberto,

I did a few tests in my lab and I couldn't reproduce those errors, probably it was an isolated issue.

As an additional note, when you install all the modules but you skip their configuration in the wizard, it is normal to get the following messages in the log file 'syslog':

Code: [Select]
Your configuration is broken. Not reloading Apache 2
AH00526: Syntax error on line 47 of /etc/apache2/conf-enabled/SOGo.conf:
Invalid command 'ProxyRequests', perhaps misspelled or defined by a module not included in the server configuration

This is because Webmail module isn't enabled yet.

Best regards, Daniel Joven.

Hi Deslack,

The command that you used to fix the Suricata public key is defined in the script:

Code: [Select]
## Adding Suricata repositorio for zentyal-ips module
if ! grep -qR '' /etc/apt/sources.list*
    echo "deb $(lsb_release -sc) main" >> /etc/apt/sources.list
    apt-key adv --keyserver --recv-keys ${SURI_KEY}

Is it possible that you already had that repository in your Ubuntu server? How many times times did you run the script?

Best regards, Daniel Joven.

Installation and Upgrades / Re: can't log in Webadmin
« on: June 08, 2021, 01:27:40 pm »
Hi denis.robel,

Thank you for the information, we are working in the solution.

Best regards, Daniel Joven.

Installation and Upgrades / Re: Problems with Upgrading to 7
« on: June 08, 2021, 01:25:50 pm »
It's as up-to-date as it will allow me, hence the problem above using the site you sent me, some of the output of the CLI commands is posted above.

Hi arch113,

Confirm that your Zentyal Server 6.2 is using Ubuntu 18.04 Bionic (lsb_release -a) and if it does, you can compare the script located at '/usr/share/zentyal/release-upgrade' with the following:

And then, run it using the debug mode to see any error:

Code: [Select]
sudo bash -x /usr/share/zentyal/release-upgrade
Best regards, Daniel Joven.

I have two Zentyals, one upgraded fine, the other just hangs here

Code: [Select]
Setting up zentyal (7.0.0ubuntu1) ...
Setting up zentyal-firewall (7.0.0) ...
 * Restarting Zentyal module: firewall
Setting up zentyal-dns (7.0.2) ...
Installing new version of config file /etc/bind/db.root ...

Try to locate the process with the command 'lslocks | grep dns', kill it 'kill -9 id_process' and then, repair the packages using 'dpkg --configure -a'.

Installation and Upgrades / Re: Problems with Upgrading to 7
« on: May 31, 2021, 02:33:52 pm »

Is your Zentyal server up-to-date?

You can try to upgrade your Zentyal server using the CLI, below you have the link to the documentation.


Installation and Upgrades / Re: can't log in Webadmin
« on: May 28, 2021, 12:17:53 pm »
Hi guys,

We are doing tests in different environments and we couldn't reproduce this issue yet. Could you please send me a private message and provide me the following information?

* Was the Zentyal server 7.0 upgraded from 6.2?
* Which 'domains' do you have enabled in the log module?
* Which version of the Zentyal modules are you using (dpkg -l | grep 'zentyal' )?
* Can you attach me the following log files? We would like to analyze those log files in order to see any trace that help us to identify the issue.
   * /var/log/zentyal/zentyal.log
   * /var/log/zentyal/error.log
   * /var/log/zentyal/uwsgi.log
   * /var/log/syslog
   * /var/log/mysql/error.log

     NOTE1: Ensure that the log files are from the day that you got the issue.
     NOTE2: Tell us the day where you got the issue.

Thank you for your feedback.

Best regards, Daniel Joven.

Installation and Upgrades / Re: can't log in Webadmin
« on: May 21, 2021, 05:48:51 pm »
Hi Denis,

Can you please provide us more details?

* Which Zentyal version are you using?

* Is the service 'mysql' running correctly?
Code: [Select]
sudo systemctl status mysql

* Do you see any error in the following log files?
  • /var/log/mysql/error.log
  • /var/log/syslog

Best regards, Daniel Joven.


The error that you are getting is:

Code: [Select]
./ line 54: checkBrokenPackages: command not found

Basically, the function 'postUpgradeProcedure' doesn't recognize the other function 'checkBrokenPackages'. So, make sure that this last function is present in your script.

Best regards, Daniel Joven.

Hi guys,

There is an open issue in Github related to this DNS resolution issue, you can check it out here:


Solved but not quite solved.
After I made some updates that appeared after I modified the file as you said, after restarted the system, the file was re-written without the modification and I was forced to insert the parameter again.

If you set that configuration parameter in the stub located at '/usr/share/zentyal/stubs/dns' and you lost it after restarting the DNS module, it is because you have another stub located at '/etc/zentyal/stubs/dns', and this directory has more priority than the other.

Moreover, in Dashboard, at Core version, is written 7.0.3 (available).
If I check from Software Management, the messages said that no updates are available.
If I check from CLI, same messages.

Code: [Select]
:~$ sudo apt-get update
Hit:1 focal InRelease
Hit:2 focal-updates InRelease
Hit:3 focal-backports InRelease
Hit:4 7.0 InRelease
Hit:5 focal InRelease
Hit:6 focal-security InRelease
Reading package lists... Done
:~$ sudo apt-get install zentyal-core
Reading package lists... Done
Building dependency tree
Reading state information... Done
zentyal-core is already the newest version (7.0.3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
:~$ sudo apt-get install zentyal-software
Reading package lists... Done
Building dependency tree
Reading state information... Done
zentyal-software is already the newest version (7.0.0).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I will check it as soon as I can and I let you know.

Best regards, Daniel Joven.

Hi grolon (Buenas tardes :D),

Probably, you will need to load the profile before fixing the packages. Please, try the following:

1. Unlink the disabled profile:

Code: [Select]
sudo unlink /etc/apparmor.d/disable/usr.sbin.dhcpd

2. Load the DHCP profile

Code: [Select]
apparmor_parser -r /etc/apparmor.d/usr.sbin.dhcpd

3. Check that it was correctly loaded:

Code: [Select]

The output that should be displayed:

Code: [Select]
apparmor module is loaded.
4 profiles are loaded.
4 profiles are in enforce mode.

4. Try one more time to repair the broken packages.

Best regards, Daniel Joven.


The cause of the error is that the DHCP profile doesn't exist. Confirm that the profile '/etc/apparmor.d/usr.sbin.dhcpd' doesn't exists. If this is the case, do the following:

1. Create the profile '/etc/apparmor.d/usr.sbin.dhcpd' with the following content:

Code: [Select]
# vim:syntax=apparmor
# Last Modified: Mon Jan 25 11:06:45 2016
# Author: Jamie Strandboge <>

#include <tunables/global>

/usr/sbin/dhcpd {
  #include <abstractions/base>
  #include <abstractions/nameservice>
  #include <abstractions/ssl_keys>

  capability chown,
  capability net_bind_service,
  capability net_raw,
  capability setgid,
  capability setuid,

  network inet raw,
  network packet packet,
  network packet raw,

  @{PROC}/[0-9]*/net/dev r,
  @{PROC}/[0-9]*/net/{dev,if_inet6} r,
  owner @{PROC}/@{pid}/comm rw,
  owner @{PROC}/@{pid}/task/[0-9]*/comm rw,

  /etc/hosts.allow r,
  /etc/hosts.deny r,

  /etc/dhcp/ r,
  /etc/dhcp/** r,
  /etc/dhcpd{,6}.conf r,
  /etc/dhcpd{,6}_ldap.conf r,

  /usr/sbin/dhcpd mr,

  /var/lib/dhcp/dhcpd{,6}.leases* lrw,
  /var/log/ r,
  /var/log/** rw,
  /{,var/}run/{,dhcp-server/}dhcpd{,6}.pid rw,

  # isc-dhcp-server-ldap
  /etc/ldap/ldap.conf r,

  # LTSP. See:
  /etc/ltsp/ r,
  /etc/ltsp/** r,
  /etc/dhcpd{,6}-k12ltsp.conf r,
  /etc/dhcpd{,6}.leases* lrw,
  /ltsp/ r,
  /ltsp/** r,

  # Eucalyptus
  /{,var/}run/eucalyptus/net/ r,
  /{,var/}run/eucalyptus/net/** r,
  /{,var/}run/eucalyptus/net/*.pid lrw,
  /{,var/}run/eucalyptus/net/*.leases* lrw,
  /{,var/}run/eucalyptus/net/*.trace lrw,

  # wicd
  /var/lib/wicd/* r,

  # access to bind9 keys for dynamic update
  # It's expected that users will generate one key per zone and have it
  # stored in both /etc/bind9 (for bind to access) and /etc/dhcp/ddns-keys
  # (for dhcpd to access).
  /etc/dhcp/ddns-keys/** r,

  # allow packages to re-use dhcpd and provide their own specific directories
  #include <dhcpd.d>

  # Site-specific additions and overrides. See local/README for details.
  #include <local/usr.sbin.dhcpd>

2. Set the right permission to the file:

Code: [Select]
sudo chmod 0644 /etc/apparmor.d/usr.sbin.dhcpd
sudo root:root /etc/apparmor.d/usr.sbin.dhcpd

3. Unlink the disabled profile:

Code: [Select]
sudo unlink /etc/apparmor.d/disable/usr.sbin.dhcpd

3. Try to fix the broken packages again:

Code: [Select]
sudo dpkg --configure -a

Best regards, Daniel Joven.

Pages: [1] 2 3