ClearOS Bug Tracker


View Revisions: Issue #6211 All Revisions ] Back to Issue ]
Summary 0006211: Zarafa does not start on boot
Revision 2015-12-29 09:48 by user2
Description The upstream Zarafa RPMs still use the old SysV startup scripts. The boot ordering is not guaranteed and that's problematic. If the Zarafa server starts up before the MariaDB/MySQL database, the startup will fail.
Revision 2015-11-13 10:12 by bchambers
Description When you try to enable them, you get:

[root@localhost ~]# systemctl enable zarafa-server
zarafa-server.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig zarafa-server on
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).