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.

Topics - c.monty

Pages: [1]

I have a question regarding the configuration of a solution where the Zentyal DB is running on a dedicated DB host.
Is this feasible?
If yes, how should I modify the configuration?

(The idea is to run a single DB host with MariaDB/MySQL and several DBs for the different applications (Zentyal, Owncloud, etc.)



Wie kann ich mittels CLI das Zentyal Module webadmin starten / stoppen, ohne dabei gleichzeitig alle anderen Module zu steuern?

Wenn ich
Code: [Select]
/etc/init.d/zentyal restartverwende werden alle installierten Module neu gestartet.
Code: [Select]
admin@vm-zentyal64:~⟫ sudo /etc/init.d/zentyal restart
 * Stopping Zentyal module: logs
 * Stopping Zentyal module: ca
 * Stopping Zentyal module: audit
 * Stopping Zentyal module: antivirus
 * Stopping Zentyal module: firewall
 * Stopping Zentyal module: network
 * Stopping Zentyal module: webadmin
 * Starting Zentyal module: network
 * Starting Zentyal module: firewall
 * Starting Zentyal module: antivirus
 * Starting Zentyal module: audit
 * Starting Zentyal module: ca
 * Starting Zentyal module: logs
 * Starting Zentyal module: webadmin

German / [Solved] Customizing von Nginx Webserver in Zentyal 4.0
« on: January 21, 2015, 10:31:47 am »

Was ist zu tun, um den Nginx Webserver in Zentyal 4.0 zu customizen?
Ich möchte
  • a) diverse Subdomains nutzen
  • b) die Nginx-Konfigurationsdatei nginx.conf modifizieren

Die Nginx-Konfigdatei wird mittels eines Templates nach Restart immer neu in /var/lib/zentyal/conf/nginx.conf geschrieben, d.h. jede Änderung in dieser Datei ist nach einem Restart verloren.
Ohne Modifikation dieser Datei ist es aber unmöglich, ein Subdomain zu definieren.

Aus meiner Sicht wäre es ausreichend, Zentyal so zu modifizieren, dass der Webserver Nginx nicht automatisch mit der Konfig-Datei /var/lib/zentyal/conf/nginx.conf gestartet wird, sondern stattdessen Nginx ganz normal durch den Systemstart aufgerufen wird und dann die default Konfig-Datei /etc/nginx/nginx.conf verwendet.

Deshalb meine Frage:
Wie kann ich unterbinden, dass Zentyal den Webserver Nginx startet?



I want to enhance the webservices of the Zentyal 4.0 server installation, e.g. Adminer (, Owncloud, ...

After upgrading to Nginx 1.6.2 there are now 2 configuration files:
Code: [Select]
root@vm4-zentyal64:~# find / -type f -name "nginx.conf"

Of course this makes no sense and I must ensure that only one nginx.conf is used.
The problem here is that /var/lib/zentyal/conf/nginx.conf is overwritten after each start of server zentyal, means any modification in this file will be overwritten.

I think it should be best to disable Zentyal overruling the standard Nginx configuration in /etc/nginx/nginx.conf.
How can I modify Zentyal in order to use /etc/nginx/nginx.conf?
Then I don't care if /var/lib/zentyal/conf/nginx.conf is overwritten by a template.

What is the preferred location for storing files belonging to Adminer and Owncloud?


Installation and Upgrades / Migration to MariaDB 10.0 fails
« on: January 08, 2015, 12:34:59 am »

I want to migrate to MariaDB 10.0 and follow the best practice guide from MariaDB.
In detail I executed the following steps:
- Start Zentyal 4 in recovery mode
- Stop service mysql
- Start installation of mariadb-server

The installation will automatically remove mysql-server-5.5 and all depending packages.

However, the configuration of package mariadb-server-10.0 fails with this error:
trying to overwrite '/usr/share/mysql/mysql_system_tables.sql, which is also in package mysql-server-core-5.5
(All details in attached screenshot).

How can I fix this problem?



I have migrated successfully from MySQL to MariaDB.
Unfortunately the deinstallation of MySQL forced uninstallation of packages
zentyal zentyal-core zentyal-software

After the DB migration I started re-installation of these zentyal packages.
However, the config of package zentyal-core (4.0.5) fails in step "Restarting module webadmin":
Code: [Select]
Trigger für zentyal-core (4.0.5) werden verarbeitet ...
 * Restarting Zentyal module: webadmin!
 * Restarting Zentyal module: logs

In the errorlog /var/log/zentyal/zentyal.log the following error is written:
Code: [Select]
2015/01/06 13:09:49 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

Command output: .
Exit value: 1 at /usr/share/perl5/EBox/Module/ line 1003
EBox::Module::Service::restartService('EBox::WebAdmin=HASH(0x3a7fd48)', 'restartModules', 1) called at /usr/share/perl5/EBox/Util/ line 127
eval {...} at /usr/share/perl5/EBox/Util/ line 125
EBox::Util::Init::moduleAction('webadmin', 'restartService', 'restart') called at /usr/share/perl5/EBox/Util/ line 253
EBox::Util::Init::moduleRestart('webadmin') called at /usr/share/zentyal/restart-trigger line 35

What's the root cause of this error?
How can I fix the failed startup of webadmin?
Would it make sense to apply the solution provided here,23964.0.html?


Pages: [1]