New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cron Issues? #164
Comments
@waja any idea on this one, I am not seeing this myself but this is the second such report |
@theonlydaleking what distribution are you running maldet on, including OS release # please? Thanks |
I can confirm this too, Debian 8 here. |
I'll have a look in my Debian 8 docker container. |
Oh, I forgot that I'm running this script on a Vesta system. For what that's worth. As in, the control panel. |
@theonlydaleking can you please have a look into: |
After lot of testing, I'm also not able to reproduce this (in my clean Debian 8 docker env). Anyway ... shellcheck has some warnings:
|
@rfxn running this on Centos 6.8 with a cpanel distribution (WHM 56.0 (build 24)) if that helps Ran the script with -x but I'm not sure what i'm looking for. do you need the output? |
@theonlydaleking yes pleae, output of |
@theonlydaleking can you also md5sum the /etc/cron.daily/maldet file please |
|
and the md5sum bddfc2f11ec5413a964b3c22de7ba833 /etc/cron.daily/maldet Is that what you need? @rfxn |
@theonlydaleking this |
@waja ah yup my mistake, updated my comment above after sleep finished |
Hmm ... cool! In your output there is no nothing about your origin reported error. |
@theonlydaleking did this error happen only once or is it happening every day? |
/etc/cron.daily/maldet updates itself while it's running. If a new version is available /etc/cron.daily/maldet fail:
Update running script has unpredictable results. |
It didn't happen last night so it looks like it might have been a once off thing, i'll keep an eye on it and keep you posted |
We can probably fix this by, on version updates, detect if the LMD_CRON variable is set, if so then break/exit out of the existing cron and re-execute it cleanly. |
This issue is fixed by latest release. If there are further reports of similar issues in the future, I will more aggressively check for / exit on updates during cron execution. |
Hi, /etc/cron.daily/maldet:
/etc/cron.daily/maldet: line 56: n: command not found
/etc/cron.daily/maldet: line 59: syntax error near unexpected token `fi'
/etc/cron.daily/maldet: line 59: `fi' Then I ran the script again and I had no errors. Linux Malware Detect v1.6.1
(C) 2002-2017, R-fx Networks <proj@rfxn.com>
(C) 2017, Ryan MacDonald <ryan@rfxn.com>
This program may be freely redistributed under the terms of the GNU GPL v2 |
I must confirm this issue. Had it yesterday while updating from 1.6 to 1.6.1. OS Debian Jessie. |
I also had the problem to version 1.6.1. etc/cron.daily/maldet: Is the problem resolved? |
getting this:
alert on email. Checked the cron for syntax and it looks fine. could this be caused by a source script error?
The text was updated successfully, but these errors were encountered: