run-parts: /etc/cron.daily/univention-ssl exited with return code 2
Was läuft hier falsch?
Whats going wrong?
UCS 4.3-2 errata 257 mit Kopano, letsencrypt, nextcloud bisher ohne Probleme. Seit drei Tagen morgens diese Meldung.
Kann mir jemand helfen?
Heiko
Hi,
we prefer English. I translated your request.
run-parts: /etc/cron.daily/univention-ssl exited with return code 2
What’s wrong here?
UCS 4.3-2 errata 257 with Kopano, letsencrypt, nextcloud so far without problems. Since three days in the morning this message.
Can anyone help me?
What happens when you run the mentioned script manually?
/CV
thanks for your reply
you mean to start /etc/cron.daily/univention-ssl manually?
i get no output to the console
Well, there should be no output.
But you will get an error level after the execution. Just type “echo $?” after the above command finished.
Or use “univention-ssl || echo $?”
There has been some changes related to the univention-ssl. See Bug.
I am still investigating if this is related to the issue you reported.
I will report here to confirm.
/CV
Many thanks. I‘ll wait for the next update.
Too bad that the error was not corrected in the last update.
Hi,
sorry but fixing a bug in a product is not like hacking in a home environment. Before we can officially release a fix we have to perform some tests to verify it is ok and some other stuff.
This takes a good amount of time.
If you prefer faster and less reliable you could easily implement the patch which is shown in the last comment on your system.
/CV
Many thanks for correcting this bug in the last Update.
Heiko
Hi,
Im also getting an email now every morning since a couple of days saying (Server is running on UCS5.x):
run-parts: /etc/cron.daily/univention-ssl exited with return code 2
Running the script manually (as advised by Christian above) also gives me a return code 2.
Im not even sure what this means?
I have also already checked the certifcates manually (univention-certificate check), but it seems that there are no issues at all with the certifcates.
Any hint to solve or further troubleshoot this, would be much appreciated.
Same error only on “master” since sunday. I mean the bug was introduced with errata 330
every morning? Let me guess, 6:25?
yep, every morning at 6:25am
so thats Debian’s typical time to do daily things. Some other job is bothering.
A bug was opened for this:
https://forge.univention.org/bugzilla/show_bug.cgi?id=54932