Page 1 of 1

Issue with LFD failing

Posted: 23 Jun 2016, 19:13
by jacobc
Hi All,

We are seeing the below error on a few servers and I am wondering if it is related to the recent upgrade of csf - anyone else seeing this?

Jun 23 19:10:46 xxxxx lfd[32628]: *System Integrity* has detected modified file(s): /usr/sbin/csf /usr/sbin/lfd /sbin/csf /sbin/lfd
Jun 23 19:10:46 xxxxx lfd[32628]: Unable to send SMTP alert via [xxxxx @xxxxx ]: Invalid argument at /usr/sbin/lfd line 6381.

Jun 23 19:10:46 xxxxx lfd[32628]: daemon stopped
Jun 23 19:10:46 xxxxx lfd[32619]: *Error* pid mismatch or missing, at line 909
Jun 23 19:10:46 xxxxx lfd[32619]: daemon stopped

TIA

Jacob

Re: Issue with LFD failing

Posted: 23 Jun 2016, 20:49
by ForumAdmin
That would suggest that you have set LF_ALERT_SMTP to an email address, not the IP address of the SMTP server to use.

Re: Issue with LFD failing

Posted: 23 Jun 2016, 22:11
by jacobc
Ah ok, thanks.

Re: Issue with LFD failing

Posted: 27 Jun 2016, 02:12
by Chargin
I have this same problem but Im not sure how it can be fixed?


Jun 24 09:28:34 server1 lfd[845588]: *System Integrity* has detected modified file(s): /usr/sbin/csf /usr/sbin/lfd
Jun 24 09:28:34 server1 lfd[845588]: Unable to send SMTP alert via [1]: Invalid argument at /usr/sbin/lfd line 6381.

Jun 24 09:28:34 server1 lfd[845588]: daemon stopped
Jun 24 09:28:37 server1 lfd[845582]: *Error* pid mismatch or missing, at line 909
Jun 24 09:28:37 server1 lfd[845582]: daemon stopped
Jun 24 09:31:43 server1 lfd[846010]: daemon started on serverxxx.axxxxxxr.info - csf v9.02 (cPanel)

Re: Issue with LFD failing

Posted: 27 Jun 2016, 06:10
by Sergio
Try to update to csf v9.06 and see if the error goes away.

Re: Issue with LFD failing

Posted: 27 Jun 2016, 09:19
by Chargin
Hi Sergio, Ive just checked and its running 9.06 already.
The error pasted above was from a few days ago so maybe thats why it says 9.02?

Any other help appreciated, Im getting hundreds of emails from the server about this error...

Re: Issue with LFD failing

Posted: 04 Jul 2016, 11:25
by jacobc
The issue was the mail server was wrong for the alerts - for us.