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 - apos

Pages: [1] 2
Installation and Upgrades / Re: Zentyal + Docker
« on: June 12, 2016, 01:31:59 pm »
Hello Docker and Zentyal fans,

I am very astonished, that there seams to be not post about docker + zentyal in the forum. It would solve a lot of problems (rolling back when updates are going wrong, providing ready to go images !!!). Therefore I will reactivate this thread.

Short answer to

ich will use it in docker too ... Can you help please?

Read and contribute ... ;-)

Short answer to the thread starter: The Ubuntu-Docker-Image of Ubuntu is not per default designed and prepared to run complex applications. BUT Zentyal requires Ubuntu! AND: to run in a docker image there have to be several things to be done to get things running ... that might be the reason because the effort of the thread starter ...

I test install Zentyal using Docker but dpkg displays an error message during the configuration of packets

... failed. He simply did not know, how docker workes (I am almost 100% shure whithout the spare informations he gave use) ;-)

A solution and long answer why just using the standard docker image in ubuntu won't work and how we will get it go running:

1.  (and other)

Zentyal is Debian-based and built on the latest Ubuntu Long Term Support (LTS) version. The current hardware requirements for Zentyal 3.5 are based on Ubuntu Trusty 14.04.1 LTS (kernel 3.5). Zentyal uses the LXDE desktop and the Openbox window manager.


Ubuntu is not designed to be run inside Docker. Its init system, Upstart, assumes that it's running on either real hardware or virtualized hardware, but not inside a Docker container. But inside a container you don't want a full system anyway, you want a minimal system. But configuring that minimal system for use within a container has many strange corner cases that are hard to get right if you are not intimately familiar with the Unix system model. This can cause a lot of strange problems.

Baseimage-docker gets everything right. The "Contents" section describes all the things that it modifies.

3.  An example how to get a LAMP stack running (Wordpress) with Docker Composer which might help getting zentyal run:

Docker Compose makes dealing with the orchestration processes of Docker containers (such as starting up, shutting down, and setting up intra-container linking and volumes) really easy.

Please READ before you procede and try to understand what docker is, works and how it behaves under Ubuntu. Take yourself the time, prepare coffee or tee BEFORE, read the articles above and THEN go on installing zentyal explained the following link should work.


I don't have time to test this in the moment. If anyone does, please post ... I will, wenn I find the time.

* _PLEASE_ post your solution in detail (not just. "it worked for me")
* post your docker yml files and what dependencies you had
* probably share youre zentyal docker image with others at docker registry
* Be prductive - don't post any: "I also have the same problem." -  posts.

Good luck

This might be solved through a hack. See:


:) I find the a Solution in a Owncloud-Forum with using an Ubuntu AD (as Zentyal is based on ubuntu) and it's working  :)

Here are my pictures

Thanks phiku for pointing out the solution:

Two remarks: in the first picture has some caveats that could lead to somemisunderstanding:

  • The IP is shown as server address: I can confirm this. Using the full qualified domain name is NOT working (server.zentyaldomain.lan).
  • Using the account "Administrator" is not necessary: any user can be used here. I simply created one.
  • The DN is not correct. "OU=Users," does not work for me. I simply had to use the settings as shown at the LDAP information page which you can easily copy from the webinterface at https://zentyal:WEB_PORT/Samba/Composite/Settings

And: Using ldaps://IP  or ldaps://FQD and Port 686 is NOT working for me.

Installation and Upgrades / Re: Can't re-provision domain
« on: January 07, 2016, 07:53:03 pm »

I am here on Zentyal 4.1 and I could not reprovison openchange also. 
I can confirm that adding "--ignore-already-exists" into "" works:

Code: [Select]
vim  /usr/share/perl5/EBox/OpenChange/Model/ +457

So we only need to find the call for openchange_provision in that bunch of perl source files - it's hidden in /usr/share/perl5/EBox/OpenChange/Model/ on line 457:
Code: [Select]
my $cmd = "openchange_provision --firstorg='$organizationName' ";
just add that command line switch:
Code: [Select]
my $cmd = "openchange_provision --ignore-already-exists --firstorg='$organizationName' ";


so I found a KISS (keep it simple an Stupid) -method doing this with an SSH tunnel.

The SSH server should be - for security reasons - configured to use certificate authenitfication only, which is in fact almost the same then a VPN connection (sshd_config: PasswordAuthentication no, UsePAM no).

On a local console do:

Code: [Select]
ssh -L 9000:IP_OF_SERVER:8443  loginname@IP_OF_SERVER
  • 8443 is the port of the zentyal web interface
  • 9000 is the local port you can access the web interface in your browser

Now you can access the Zentyal Webinterface in your local browser with:
Code: [Select]
Life can be so simple  ;)

Post scriptum:

As far as I can say, it is not possible to simply reach the natted network within the virtual machine, if you do not have access to the quemu / kvm host. Then, there exist some solutions. But this is normally not the case, if you are using a vserver. There are some interesting threads with deal with the solution and background, if you are running the kvm host by yourself, but the ssh tunnel is really, really the simplest way to do this:

I by myself make ports available in my KVM guest (in my own KVM host) with iptables - see:

For the problem with the zentyal-core package: A postinstallation script of zentyal-core ist not working, so zentyal-core is never installed:

Simply run the script standalone

Code: [Select]
> /var/lib/dpkg/info/zentyal-core.postinst
and check for errors!

Deactivate the script:

Code: [Select]
vim /var/lib/dpkg/info/zentyal-core.postinst

exit 0

set -e

re-run dpkg

Code: [Select]
dpkg --configure -a
    continue with the web interface, which should be run now!

Code: [Select]
service zentyal webadmin restart

nano /etc/network/interfaces
 auto lo
 iface lo inet loopback

Code: [Select]
dpkg-reconfigure zentyal-core
will at least give you the possibility to reset the admin port to a custom value.

Code: [Select]
* Restarting Zentyal module: webadmin                                   [ OK ]

Installation and Upgrades / Re: Radius 3.4
« on: April 18, 2014, 05:02:53 pm »
I could finally solve the problem Zentyal 3.4 / 13.10 saucy after upgrade from 3.3 / 12.04 lts):

Freeradius is installed as a service. Killing the program simple reopens a new instance ...

So the only way is removing all startup links from freeradius with:

Code: [Select]
update-rc.d -f freeradius remove
Now zentyal could restart and force-reload freeradius.

Ok, this seems not not be the whole story.

I investigated further, that the problem seems to be the "restart" command of zentyal.

If I do a

Code: [Select]
service zentyal radius stop
killall freeradius
service zentyal radius start

then things run fine.

So decided to write a little monitor script and put this in /etc/rc.local, so the monitor script will run upon startup.

I know this is far from perfect, but as long as the problem is solved, it works:

Code: [Select]
# Put this in /etc/rc.local
# Monitor zentyal radius

# Upon update, links for freeradius will be set again, so remove them
update-rc.d -f freeradius remove

restart_radius() {
      /usr/sbin/service zentyal radius stop
      sleep 2
      /usr/bin/killall freeradius
      /usr/sbin/service zentyal radius start

while (true)
        if radtest radtestuser 123-qwe localhost 1812 123-qwe
                echo "RADIUS OK"
                logger "ERROR: ZENTYAL RADIUS is DOWN ... restarting ..."
        sleep 15

I forgot to mention:

To get this work, you have to add a new radius client on within your zentyal configuration! The credentials - radiustestuser, its password and the secret - can be choosen freely but must be set correctly. Don't use your standard credentials for testing radius!

radtest ist part of the package

Code: [Select]
sudo apt-get install freeradius-utils


I have the same problems.

I tried to

Code: [Select]
apt-get remove --purge zentyal-radius freeradius*
and reinstall. No success.

The problems seems to be, that port 1812 is occupied, so freeradius won't start.

After trying a lot of things, I gave up, since the radius server is crucial for a lot of services.
I installed a new server.


Hi guys,

i have the same problem here under Ubuntu 14.04 and Zentyal 3.4.
After Upgrade to 3.4 webadmin fails to start.

The error is related to nginx.

Code: [Select]
EBox::Util::Init::moduleRestart('webadmin') called at /etc/init.d/zentyal line 58
main::main at /etc/init.d/zentyal line 79
2014/04/16 23:54:54 ERROR> EBox::Module::Service::restartService - Error restarting service: root command /sbin/start 'zentyal.webadmin-nginx' failed.
Error output: start: Job failed to start

Command output: .
Exit value: 1
2014/04/16 23:54:54 ERROR> EBox::Module::Service::restartService - root command /sbin/start 'zentyal.webadmin-nginx' failed.
Error output: start: Job failed to start

Command output: .
Exit value: 1 at root command /sbin/start 'zentyal.webadmin-nginx' failed.
Error output: start: Job failed to start

Editing soap-loc-ssl.conf and installing the zentyal-remoteservices, purging and reinstalling everything brings no success - unfortunately.

Sorry, did a lot of editing. But I am ready now ;-)
Did NOT (!) get to manage to reach the admin interface via VPN. :-(

Help would be really appreciated.

I really searched the forum for a hint, but did not get any thread showing this exact scenario with should be a very common one:
  • single nic kvm server at an hoster in the internet
  • a virtual nic
  • vpn for administration or other special ports via the virtual nic

I probably have to say, that I have several zentyal installations running. I have iptables scirpts running on other machines with firewall hooks, no  problem, but this really drives me nuts.

The machine is an KVM vserver.

For completeness ifconfig and iptables-save (attached).

Code: [Select]
eth0      Link encap:Ethernet  HWaddr 52:54:5b:5f:da:f1
          inet addr:MY.PUBLIC.IP.ETH0  Bcast:MY.PUBLIC.IP.255  Mask:
          RX packets:8573544 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1476026 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2377362228 (2.3 GB)  TX bytes:2070524147 (2.0 GB)

eth0:vpn  Link encap:Ethernet  HWaddr 52:54:5b:5f:da:f1
          inet addr:  Bcast:  Mask:

tap0      Link encap:Ethernet  HWaddr 56:a5:e5:3b:f6:75
          inet addr:  Bcast:  Mask:
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Installation and Upgrades / Re: LDAP installed but not searchable
« on: January 16, 2014, 05:45:23 pm »
You're welcome. It took me several days to figure that out by myself ;-)

Can you mark this solved, please?

Pages: [1] 2