proftped auto killed?

2014-06-29 00:31:45,643 servername proftpd[28486] servername ([ip]): Preparing to chroot to directory ‘/home/xxxxxx’
2014-06-29 00:31:45,644 servername proftpd[28486] servername ([ip]): USER xxxxx: Login successful.
2014-06-29 06:56:47,099 servername proftpd[2286] servername: ProFTPD killed (signal 15)
2014-06-29 06:56:47,100 servername proftpd[2286] servername: ProFTPD 1.3.5rc3 standalone mode SHUTDOWN
2014-06-29 08:09:27,068 servername proftpd[26460] servername: ProFTPD 1.3.5rc3 (devel) (built Fri Dec 20 2013 18:05:41 UTC) standalone mode STARTUP

i have faced this problem 2 times.
i didnt change anything. i only know that lots of ppl trying to bruce to my ftp server.
any hints for me? thanks!


Are you using a dedicated server, or a VPS? If it’s a VPS, are you by chance using OpenVZ? If so, can you paste in the contents of your /proc/user_beancounters file?


thansk for your reply.
we are using hyper-v to running ubuntu 14.04 linux


What is the output of these two commands on your server:

free -m dmesg | tail -30


any can help?


I don’t see any obvious signs of resource problems, such as low RAM or oom-killer messages.

However, the services that run on Linux are reliable, they don’t tend to die on their own… so I suspect there’s something unusual going on there either with the VPS setup, or the hardware.

You may want to review your hyper-v setup, and the hyper-v logs, to see if there’s any kind of information about resource availability/usage, to make sure that it’s not restricting the RAM or other resources that are available.



I just stumbled across this (admittedly a bit old) post.

If you are on Debian/Ubuntu or derived OS, this might be related to a logrotate/restart issue. See: