Univention Bugzilla – Bug 41876
Rebuild 4.1-0 appbox image
Last modified: 2019-01-03 07:20:17 CET
We need a new 4.1-0 appbox image for those Docker Apps with DockerImage=4.1-0. Alternatively, we adjust all Docker Apps to DockerImage=4.1-3 (yet to be built) with AllowedImages=4.1-0. +++ This bug was initially created as a clone of Bug #41875 +++ Backport to 4.1-0 +++ This bug was initially created as a clone of Bug #39677 +++ I see the following log messages in a Docker App: root@dudle-docker-1446164292151882:/# tail -n 20 /var/log/syslog Oct 30 00:39:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-updater) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-updater) Oct 30 00:39:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-pam) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-pam) Oct 30 00:40:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*) NUMBER OF HARD LINKS > 1 (/etc/crontab) Oct 30 00:40:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-mail-postfix) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-mail-postfix) Oct 30 00:40:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-ucr-cronjobs) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-ucr-cronjobs) Oct 30 00:40:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-config-registry-backup) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-config-registry-backup) Oct 30 00:40:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-ssl) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-ssl) Oct 30 00:40:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-server-member) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-server-member) Oct 30 00:40:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-updater-check) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-updater-check) Oct 30 00:40:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-updater) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-updater) Oct 30 00:40:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-pam) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-pam) Oct 30 00:41:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*) NUMBER OF HARD LINKS > 1 (/etc/crontab) Oct 30 00:41:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-mail-postfix) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-mail-postfix) Oct 30 00:41:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-ucr-cronjobs) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-ucr-cronjobs) Oct 30 00:41:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-config-registry-backup) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-config-registry-backup) Oct 30 00:41:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-ssl) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-ssl) Oct 30 00:41:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-server-member) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-server-member) Oct 30 00:41:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-updater-check) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-updater-check) Oct 30 00:41:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-updater) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-updater) Oct 30 00:41:01 dudle-docker-1446164292151882 /usr/sbin/cron[1614]: (*system*univention-pam) NUMBER OF HARD LINKS > 1 (/etc/cron.d/univention-pam) root@dudle-docker-1446164292151882:/#
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.