It looks like we found the recurrent issue of disappearing cron jobs on Helos.
I read that crontab -e is the safer option, less prone to unintended consequences than directly editing the file is.
Christian Düben
Doctoral Candidate
Chair of Macroeconomics
Hamburg University
Germany
christian.dueben(a)uni-hamburg.de
https://www.christian-dueben.com
-----Original Message-----
From: Thomas Krichel <krichel(a)openlib.org>
Sent: Sonntag, 30. Juli 2023 17:08
To: Düben, Christian <christian.dueben(a)uni-hamburg.de>
Subject: Re: [CollEc] helos overload
Düben, Christian writes
> All my cron jobs have been deleted from the cron tab, including the daily updating job.
dear.
>
> Is that due to the fact that we edit the crontab differently? I use "EDITOR=nano crontab -e".
Colud be. I use the file /root/etc/crontab ; crontab /root/etc/crontab
--
Written by Thomas Krichel http://openlib.org/home/krichel on his 21240th day.
it's back.
I have stopped nginx and stopped docker.socket. That seems
to work but leaves CollEc not running.
--
Written by Thomas Krichel http://openlib.org/home/krichel on his 21240th day.
I get mails like these as root. I am adding Christian to the
root email recipients, temporarily.
----- Forwarded message from Cron Daemon <root(a)openlib.org> -----
Return-path: <root(a)openlib.org>
Envelope-to: root(a)openlib.org
Delivery-date: Sun, 30 Jul 2023 13:30:06 +0000
Received: from root by helos.openlib.org with local (Exim 4.95)
(envelope-from <root(a)openlib.org>)
id 1qQ6Uo-0023YW-0c
for root(a)openlib.org;
Sun, 30 Jul 2023 13:30:06 +0000
From: Cron Daemon <root(a)openlib.org>
To: root(a)openlib.org
Subject: Cron <root@helos> docker ps --filter "ancestor=collec_app" --filter "status=created" |
xargs --no-run-if-empty docker rm
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
Message-Id: <E1qQ6Uo-0023YW-0c(a)helos.openlib.org>
Date: Sun, 30 Jul 2023 13:30:06 +0000
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: root(a)openlib.org
X-SA-Exim-Scanned: No (on helos.openlib.org) SAEximRunCond expanded to false
9753fa54c274
Error response from daemon: No such container: CONTAINER
Error response from daemon: No such container: ID
Error response from daemon: No such container: IMAGE
Error response from daemon: No such container: COMMAND
Error response from daemon: No such container: CREATED
Error response from daemon: No such container: STATUS
Error response from daemon: No such container: PORTS
Error response from daemon: No such container: NAMES
Error response from daemon: You cannot remove a running container 2c03291b3e0024540d110b7ece2086c511da6a48ba02cb55766506b18296f34a. Stop the container before attempting removal or force remove
Error response from daemon: No such container: collec_app
Error response from daemon: No such container: R -e shiny::runApp(…
Error response from daemon: multiple IDs found with provided prefix: 3
Error response from daemon: No such container: seconds
Error response from daemon: No such container: ago
Error response from daemon: No such container: Created
Error response from daemon: You cannot remove a running container 2c03291b3e0024540d110b7ece2086c511da6a48ba02cb55766506b18296f34a. Stop the container before attempting removal or force remove
Error response from daemon: You cannot remove a running container d4c6aff38b37f7b74a8423e096e2768c393ca30a1ecb14c48737b796b608924e. Stop the container before attempting removal or force remove
Error response from daemon: No such container: collec_app
Error response from daemon: No such container: R -e shiny::runApp(…
Error response from daemon: multiple IDs found with provided prefix: 3
Error response from daemon: No such container: seconds
Error response from daemon: No such container: ago
Error response from daemon: No such container: Created
Error response from daemon: You cannot remove a running container d4c6aff38b37f7b74a8423e096e2768c393ca30a1ecb14c48737b796b608924e. Stop the container before attempting removal or force remove
Error response from daemon: You cannot remove a running container 70b9c3e1b04adbc6e7f332a0061f95cad27dd81d5a6c2621c64bb3eb7ec532a8. Stop the container before attempting removal or force remove
Error response from daemon: No such container: collec_app
Error response from daemon: No such container: R -e shiny::runApp(…
Error response from daemon: multiple IDs found with provided prefix: 4
Error response from daemon: No such container: seconds
Error response from daemon: No such container: ago
Error response from daemon: No such container: Created
Error response from daemon: You cannot remove a running container 70b9c3e1b04adbc6e7f332a0061f95cad27dd81d5a6c2621c64bb3eb7ec532a8. Stop the container before attempting removal or force remove
Error response from daemon: You cannot remove a running container c571fb87462380846189e6cf23ef7fe965ad217da46f26316190bdca0020f370. Stop the container before attempting removal or force remove
Error response from daemon: No such container: collec_app
Error response from daemon: No such container: R -e shiny::runApp(…
Error response from daemon: multiple IDs found with provided prefix: 5
Error response from daemon: No such container: seconds
Error response from daemon: No such container: ago
Error response from daemon: No such container: Created
Error response from daemon: You cannot remove a running container c571fb87462380846189e6cf23ef7fe965ad217da46f26316190bdca0020f370. Stop the container before attempting removal or force remove
Error response from daemon: You cannot remove a running container 5bfdfbe665a40b5d284d4777bcae45fd33fd8c18fc2ae54c8ff001dbf8e2a956. Stop the container before attempting removal or force remove
Error response from daemon: No such container: collec_app
Error response from daemon: No such container: R -e shiny::runApp(…
Error response from daemon: multiple IDs found with provided prefix: 5
Error response from daemon: No such container: seconds
Error response from daemon: No such container: ago
Error response from daemon: No such container: Created
Error response from daemon: You cannot remove a running container 5bfdfbe665a40b5d284d4777bcae45fd33fd8c18fc2ae54c8ff001dbf8e2a956. Stop the container before attempting removal or force remove
Error response from daemon: You cannot remove a running container 03dcafd59ee5be69acb2e860d1f381ea8b0e2c7497c07ae8b477925c33d8f8a0. Stop the container before attempting removal or force remove
Error response from daemon: No such container: collec_app
Error response from daemon: No such container: R -e shiny::runApp(…
Error response from daemon: multiple IDs found with provided prefix: 5
Error response from daemon: No such container: seconds
Error response from daemon: No such container: ago
Error response from daemon: No such container: Created
Error response from daemon: You cannot remove a running container 03dcafd59ee5be69acb2e860d1f381ea8b0e2c7497c07ae8b477925c33d8f8a0. Stop the container before attempting removal or force remove
Error response from daemon: No such container: collec_app
Error response from daemon: No such container: R -e shiny::runApp(…
Error response from daemon: multiple IDs found with provided prefix: 6
Error response from daemon: No such container: minutes
Error response from daemon: No such container: ago
Error response from daemon: No such container: Created
Error response from daemon: removal of container focused_turing is already in progress
----- End forwarded message -----
--
Written by Thomas Krichel http://openlib.org/home/krichel on his 21240th day.
helos is oveloaded again.
I killed nginx, now trying to kill docker. It needs
work forme CD.
--
Written by Thomas Krichel http://openlib.org/home/krichel on his 21240th day.