Monit says: Proftpd "Execution failed"

[Hans]

Since a quiet long time i use Monit as my system monitor.
Since yetserday Monit says that the status for Proftpd is "Execution failed".

I wonder how this is possible, because uploading/downloading files via ProFTP is no problem at all and is going quiet fast.
What could be the reason for this?

I have restarted Proftpd and monit as well, but this makes no difference.

[falko]

Can you post the Proftpd part of your monitrc file?

[Hans]

Within the attachement you find the output of the file.

[falko]

What are the outputs of

ls -la /var/run/proftpd.pid

and

netstat -tap

?

[Hans]

Falko,

I think the problem is that the pid-file can not be found, because the output of ls -la /var/run/proftpd.pid is: no such file or directory



How can this be solved?

netstat -tap has a line like this:

tcp 0 0 *:2812 *:* LISTEN 18237/monit

[falko]

If you are absolutely sure that Proftpd is running, run

updatedb
locate proftpd.pid

What's the output?

Also, check /etc/init.d/proftpd. Maybe the pid file is named differently.

[Hans]

The strange thing was that i had no pid file.
I do not know if i made a good decision;
i supercopied (scp) the backup of this file from my backup-server via SSH to the /var/run/ directory again on the production server.

The output of ls -la /var/run/proftpd.pid now is:

-rw-r--r-- 1 root root 5 2006-12-21 11:29 /var/run/proftpd.pid


Monit still gives the failure.
What can i do now?

[Hans]

When i do an: ps aux | grep ftp
The result is:

nobody 7923 0.0 0.7 4772 2292 ? Ss Dec18 0:00 proftpd: (accepting connections)
root 3141 0.0 0.2 3112 600 pts/0 S+ 19:57 0:00 grep ftp

And using FTP goes fast indeed.
However monit still now that the process Proftpd "does not excists".
I guess this is because Proftpd is not creating any pid files when the process is started again.

I really do not understand this , any one knows a solution?

[falko]

What's in /etc/init.d/proftpd, and what's the output of

ls -la /var/run

?

[Hans]

Falko,

within the attachment you find the proftpd file.

The output of ls -la /var/run is:

server1:/home/admin# ls -la /var/run
total 108
drwxr-xr-x 15 root root 4096 2006-12-21 19:51 .
drwxr-xr-x 16 root root 4096 2006-06-07 20:14 ..
drwxr-xr-x 2 root root 4096 2006-12-21 12:47 apache2
-rw-r--r-- 1 root root 6 2006-12-21 12:47 apache2.pid
-rw-r--r-- 1 root root 5 2006-12-12 21:57 atd.pid
drwxr-xr-x 3 root root 4096 2006-03-31 11:14 bind
drwxr-xr-x 3 daemon daemon 4096 2006-12-12 21:57 courier
-rw-r--r-- 1 root root 6 2006-12-18 20:48 crond.pid
---------- 1 root root 0 2006-12-12 21:57 crond.reboot
drwxr-xr-x 2 dcc dcc 4096 2006-12-12 22:49 dcc
drwxr-x--- 2 Debian-exim Debian-exim 4096 2006-03-31 11:26 exim4
drwx------ 2 fetchmail nogroup 4096 2006-03-31 11:08 fetchmail
drwxr-xr-x 2 identd nogroup 4096 2006-03-31 10:02 identd
-rw-r--r-- 1 root root 5 2006-12-12 21:57 inetd.pid
-rw-r--r-- 1 root root 5 2006-12-12 21:57 klogd.pid
-rw-r--r-- 1 root root 5 2006-12-12 21:57 mdadm.pid
-rw-r--r-- 1 root root 5 2006-12-21 19:51 monit.pid
drwxr-xr-x 2 munin root 4096 2006-12-23 00:35 munin
drwxr-xr-x 2 mysql root 4096 2006-12-18 20:36 mysqld
drwxr-xr-x 2 root root 4096 2006-12-23 00:37 proftpd
drwx--x--- 2 root sasl 4096 2006-09-28 00:01 saslauthd
-rw-r--r-- 1 root root 6 2006-12-12 23:03 spamd.pid
drwxr-xr-x 2 root root 4096 2004-11-29 13:51 sshd
-rw-r--r-- 1 root root 5 2006-12-12 21:57 sshd.pid
-rw-r--r-- 1 root root 5 2006-12-12 21:57 syslogd.pid
drwxr-xr-x 2 root root 4096 2005-04-07 18:37 usb
-rw-rw-r-- 1 root utmp 7680 2006-12-23 00:29 utmp

You see, there is no proftpd.pid file