Bug - Daily Cron failure (Closed)

Forum - Software
1

Hallo, for a few weeks already our installation of eramba fails to run the daily cron routine.

The cron job in crontab has always been this:

[bash]$: sudo /usr/bin/wget -q 0 /dev/null/ http://eramba.simacan-internal/cron/daily/--very-long-and-random-key--

I tried to run the job manually removing the “-q 0” to have some output of the error and I got this:

/dev/null: Scheme missing.
–2017-01-16 09:46:11-- http://eramba.simacan-internal/cron/daily/--very-long-and-random-key--
Resolving eramba.simacan-internal (eramba.simacan-internal)… 10.3.4.101
Connecting to eramba.simacan-internal (eramba.simacan-internal)|10.3.4.101|:80… connected.
HTTP request sent, awaiting response… 500 Internal Server Error
2017-01-16 09:46:14 ERROR 500: Internal Server Error.

If I run the command twice however, it seems to get through.

/dev/null: Scheme missing.
–2017-01-16 09:46:18-- http://eramba.simacan-internal/cron/daily/--very-long-and-random-key--
Resolving eramba.simacan-internal (eramba.simacan-internal)… 10.3.4.101
Connecting to eramba.simacan-internal (eramba.simacan-internal)|10.3.4.101|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 60 [text/html]
Saving to: ‘–very-long-and-random-key–.6’

–very-long-and-random-key-- 100%[================================================================================================================>] 60 --.-KB/s in 0s

2017-01-16 09:46:18 (13.1 MB/s) - ‘–very-long-and-random-key–.6’ saved [60/60]

FINISHED --2017-01-16 09:46:18–
Total wall clock time: 0.2s
Downloaded: 1 files, 60 in 0s (13.1 MB/s)

Are you familiar with this bug?

2

Similar problem here. I haven’t had time to troubleshoot, but have run it manually and it still shows up in the system health as a failure.

3

Hello!

/usr/bin/wget -q 0 /dev/null/ http://eramba.simacan-internal/cron/daily/--very-long-and-random-key--

the command is not ok, -q (quiet) , O means nothing, you need a “-” in front so output goes to /dev/null.

Just comment the cron line (put a # in front) and tomorrow run the cron from the browesr, if there is an error it will be shown there.

To know if crons run or not ok, look at System / Settings / Cron

Let us know!

4

Thanks! I’ll let you know the result.

5

We think there is an error, but is random in the sense that affects some installs and others dont, this is likely to be on the settings each use.

If you can enable debug (System / Settings / Debug) and run the cron from the browser (remember to comment the crontab entry first putting an “#” on the front of the line)

We are looking at in the meantime

6

Clear. This is what I did now.

  1. I corrected the cron command

/usr/bin/wget -qO /dev/null/ http://eramba.simacan-internal/cron/daily/--very-long-and-random-key--

  1. I ran it from the shell (and gave me status OK in Settings/Cron)

  2. I commented the command in crontab now

# /usr/bin/wget -qO /dev/null/ http://eramba.simacan-internal/cron/daily/--very-long-and-random-key--

  1. waiting for tomorrow to run cron again via browser.
7

Good, tomorrow before you call the cron on the browser enable first debug (system /settings/ debug) so we get a trace of the error (on the browser and also on app/tmp/logs/error.log)

Thanks Ruggero!!

8

You are welcome Esteban!

9

Its a bug and will be fixed by tonight (Europe time) - thanks everyone for reporting and helping!

10

We have corrected it as a new release - please update and run the cron it should now (hopefully) work.
Thanks again

11

We are putting some additional checks on crons to deal with memory shortages on some systems. This is not a fix, just an improvement on the code.