After the most recent webmin/virtual update through webmin my proftp server stopped working, error posted below, please help.
Oct 18 00:27:39 ns proftpd[24404]: ProFTPD terminating (signal 11)
Oct 18 00:27:39 ns proftpd[24404]: FTP session closed.
Oct 18 00:30:39 ns proftpd[24638]: ProFTPD terminating (signal 11)
Oct 18 00:30:39 ns proftpd[24638]: FTP session closed.
Oct 18 00:32:39 ns proftpd[24816]: ProFTPD terminating (signal 11)
Oct 18 00:32:39 ns proftpd[24816]: FTP session closed.
Howdy,
A Virtualmin update shouldn’t cause any trouble with ProFTPd (or any other daemon)… it’s possible something else was changed at the same time, or that something else is going on.
The errors you’re seeing above actually look like a normal shutdown, but no restart. What happens if you attempt to start up the ProFTPd daemon?
How to do that depends on what distro you’re using, but it’d be something like this:
/etc/init.d/proftpd start
You can type that on the command line as root. Let us know how that works!
-Eric
Hi Eric, I know no other updates were done, but virtualmin/webmin updates through the application so it would have to be some other issue, but it worked fine for months and months until the night of that update, below is the info, proftpd says started on command line but does not start, i attempted to stop it but it fails as shown below, let me know, I can get any information available I can for assistance
[root@ns ~]# /etc/init.d/proftpd start
Starting proftpd: [ OK ]
[root@ns ~]# /etc/init.d/proftpd stop
Shutting down proftpd: [FAILED]
[root@ns ~]# /etc/init.d/proftpd stop
Shutting down proftpd: [FAILED]
[root@ns ~]# /etc/init.d/proftpd start
Starting proftpd: [ OK ]
[root@ns ~]# /etc/init.d/proftpd start
Starting proftpd: [ OK ]
[root@ns ~]#
What happens if you attempt to launch the ProFTPd binary from the command line – “/usr/sbin/proftpd”?
Do you get an error of some sort?
I’ve occasionally seen issues where the daemon was erroring out, but the errors were hidden when using the init script.
-Eric
Hi Eric, i do, seems maybe a bind issue
Howdy,
That can happen if the name of your server isn’t in /etc/hosts… which could have occurred if the hostname of your server changed, but the /etc/hosts entry weren’t kept in sync with the new hostname.
The fix would be to edit /etc/hosts, and make sure that “ns.atozstoresonline.info” is listed in there next to your IP address.
After updating /etc/hosts, ProFTPd should then start up without generating an error.
-Eric
Hi eric, thanks that was the issue, for some reason only local-host was in there and another name server we se, thanks again, if you need any free hosting please don’t hesitate to contact me, thanks Jay