proftped auto killed?

8 posts / 0 new
Last post
#1 Sat, 06/28/2014 - 20:16
devmark

proftped auto killed?

... 2014-06-29 00:31:45,643 servername proftpd[28486] servername (ctinets.com[ip]): Preparing to chroot to directory '/home/xxxxxx' 2014-06-29 00:31:45,644 servername proftpd[28486] servername (ctinets.com[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!

Sat, 06/28/2014 - 22:49
andreychek

Howdy,

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?

-Eric

Sat, 06/28/2014 - 23:36
devmark

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

Sun, 06/29/2014 - 00:33
andreychek

Howdy,

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

free -m
dmesg | tail -30
Sun, 06/29/2014 - 00:43
devmark

here. thanks

Mon, 07/07/2014 - 06:51
devmark

any can help?

Mon, 07/07/2014 - 08:26
andreychek

Howdy,

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.

-Eric

Sat, 01/17/2015 - 17:18
bdabelow

Hi,

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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675081 https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1246245

Benjamin

Topic locked