[Kolab-devel] [issue3951] During kolab_bootstrap services are started and result in erros

[Richard Bos]

New submission from Richard Bos <ml at radoeka.nl>:

When kolab_bootstrap -b is executed, services are unnecessary started and as
their configuration files are not ready yet, they fail. This results in error
messages that are confusing.  It even looks like bootstrapping has failed.  Have
a loot at the following snippet:

Create initial config files for postfix, apache, cyrus imap, saslauthd
running /usr/sbin/kolabconf -n                                        
DEBUG: Executing command:/usr/sbin/kolabsrv rc postfix reload         
Reload mail service (Postfix)                                                                      
failed
ERROR: /etc/init.d/postfix reload failed                                                                  
Run: kolabsrv rc all stop                                                                                 
to stop all services                                                                                      
DEBUG: Executing command:/usr/sbin/kolabsrv rc imapd restart                                              
Shutting down IMAP/POP3 service (cyrus-imapd)                                                      
done  
Starting IMAP/POP3 service (cyrus-imapd)                                                           
done  
DEBUG: Executing command:/usr/sbin/kolabsrv rc apache reload                                              
Reload httpd2 (graceful restart)                                                                          

Syntax error on line 13 of /etc/apache2/vhosts.d/ssl.conf:
SSLCertificateFile: file '/etc/kolab/cert.pem' does not exist or is empty

The command line was:
/usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
                                                                                                   
unused
ERROR: /etc/init.d/apache2 reload failed                                                                  
Run: kolabsrv rc all stop                                                                                 
to stop all services                                                                                      

kill temporary slapd

Shutting down ldap-server                                                                          
done
============================

I assume that this nowadays happens as the RUNONCHANGE directive in the template
files is now working correctly.  However during bootstrapping the RUNONCHANGE
directive should be neglected...

RUNONCHANGE is interpreted by kolabconf. The latter is called twice in
kolab_bootstrap with the -n option.  This option means:

# kolabconf -h
kolabconf - Version @VERSION@

Usage: kolabconf [-d] [-n] [-h]

    Option d (debug) to print out the current config.
    Option n (noreload) to skip reloading services after changing configuration.
    Option h (help) to get this text.

If I interpret this help message correctly the services shouldn't be reloaded at
all by kolabconf in case the -n option is given....  The attached patch
(do_not_reload.patch) takes care of this.

Let me know if it is okay to commit this patch to cvs.

If do_not_reload.patch is okay, the variable $Kolab::config{"reload"} can be
replaced with the variable: $Kolab::reload, if that is better liked.  This
prevents that there will be 2 variables used for the same function...

----------
keyword: server
messages: 22406
nosy: bernhard, martin, rbos, thomas, wilde, wrobel
priority: urgent
status: unread
title: During kolab_bootstrap services are started and result in erros

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3951>
______________________________________