Univention Bugzilla – Bug 46104
Horde docker container: Logrotate for apache2 fails
Last modified: 2020-07-03 20:52:33 CEST
root@ucs05:~# univention-app info UCS: 4.2-3 errata265 App Center compatibility: 4 Installed: 4.1/horde=5.2.7-3 Upgradable: This system regularly sends a systemmail for a failing logrotate cron job: > /etc/cron.daily/logrotate: > /usr/sbin/apache2ctl: 99: /usr/sbin/apache2ctl: www-browser: not found > 'www-browser -dump http://localhost:80/server-status' failed. > Maybe you need to install a package providing www-browser or you > need to adjust the APACHE_LYNX variable in /etc/apache2/envvars AFAICS the following happens inside the docker container: - Cron executes the daily logrotate job - Logrotate uses /etc/logrotate.d/apache2 - /etc/logrotate.d/apache2 does a "/etc/init.d/apache2 reload" - the reload fails with the error message above Not sure why this happens. The host runs an "/etc/init.d/apache2 reload" just fine, although the APACHE_LYNX variable is also not set there and 'www-browser' is not installed, either.
This is still happening and became quite annoying since we started operating an environment with horde for a customer and every cron-mail creates an issue in our issue tracker.
Also seen in Univention maintained Apps "Etherpad" and "Dudle" during logrotate: /etc/cron.daily/logrotate: /usr/sbin/apache2ctl: 99: /usr/sbin/apache2ctl: www-browser: not found 'www-browser -dump http://localhost:80/server-status' failed. Maybe you need to install a package providing www-browser or you need to adjust the APACHE_LYNX variable in /etc/apache2/envvars Host: UCS-4.3-1 Etherpad: 1.6.0 Dudle: 1.2.0-1
Here is a Workaround: # Install w3m root@ucs:~# univention-install w3m # configure Apache envvars root@ucs:~# sed -i "/^#export APACHE_LYNX='www-browser -dump'$/a export APACHE_LYNX='w3m -dump'" /etc/apache2/envvars You might check if the variable 'APACHE_LYNX' is properly set. # restart apache2 root@ucs:~# systemctrl restart apache2
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.