I added a new directory to my FTP server configuration, but it is not displaying when I log in even though the permissions are set properly. I thought I might be able to fix this by stopping and restarting the proftpd service, but I seem to have a strange issue with being unable to actually stop the service. When I disable FTP through the web UI, I can still log in to the FTP server. I also tried service proftpd stop but was still able to log in. What can I do about this?
Cannot Restart FTP Server
-
- OMV 4.x
- David B
-
-
I'm just going to poke @ryecoaaron since he's a master at fixing things like this.
-
While I don't use ftp, I know proftp it is still using an init script instead of systemd unit file. Try: sudo /etc/init.d/proftpd force-stop
-
-
While I don't use ftp, I know proftp it is still using an init script instead of systemd unit file. Try: sudo /etc/init.d/proftpd force-stop
This does not seem to work either. After running this, the FTP server remains up.
-
If you are determining that it is still running by the services green indicator then that is deceiving. /etc/init.d/proftpd status is the most accurate method or grep the output of ps.
-
If you are determining that it is still running by the services green indicator then that is deceiving. /etc/init.d/proftpd status is the most accurate method or grep the output of ps.
It still shows as running using these two commands as well. It's the unkillable service.
-
-
It still shows as running using these two commands as well. It's the unkillable service.
I can't replicate this at all. I am able to start and stop it with systemctl and /etc/init.d/
aaron@omv4dev:~$ ps aux | grep ftpd
proftpd 22044 0.0 0.0 124756 3844 ? Ss 19:28 0:00 proftpd: (accepting connections)
aaron 22260 0.0 0.0 12784 932 pts/0 S+ 19:29 0:00 grep ftpdaaron@omv4dev:~$ sudo /etc/init.d/proftpd stop
[ ok ] Stopping proftpd (via systemctl): proftpd.service.
aaron@omv4dev:~$ ps aux | grep ftpd
aaron 22509 0.0 0.0 12784 936 pts/0 S+ 19:29 0:00 grep ftpdaaron@omv4dev:~$ sudo /etc/init.d/proftpd start
[ ok ] Starting proftpd (via systemctl): proftpd.service.
aaron@omv4dev:~$ ps aux | grep ftpd
proftpd 22596 0.0 0.0 124756 3828 ? Ss 19:29 0:00 proftpd: (accepting connections)
aaron 22693 0.0 0.0 12784 964 pts/0 S+ 19:29 0:00 grep ftpdaaron@omv4dev:~$ sudo systemctl stop proftpd
aaron@omv4dev:~$ ps aux | grep ftpd
aaron 23118 0.0 0.0 12784 932 pts/0 S+ 19:30 0:00 grep ftpdaaron@omv4dev:~$ sudo systemctl start proftpd
aaron@omv4dev:~$ ps aux | grep ftpd
proftpd 23298 0.0 0.0 124756 3848 ? Ss 19:30 0:00 proftpd: (accepting connections)
aaron 23305 0.0 0.0 12784 928 pts/0 S+ 19:30 0:00 grep ftpd -
I can't replicate this at all. I am able to start and stop it with systemctl and /etc/init.d/
Here's what I see:
Code
Alles anzeigenroot@OpenMediaVault:~# ps aux | grep ftpd proftpd 1207 0.0 0.1 34144 9992 ? SLs 2019 6:28 proftpd: (accepting connections) root 9977 0.0 0.0 7800 888 pts/0 S+ 20:50 0:00 grep ftpd root@OpenMediaVault:~# sudo /etc/init.d/proftpd stop [ ok ] Stopping proftpd (via systemctl): proftpd.service. root@OpenMediaVault:~# ps aux | grep ftpd proftpd 1207 0.0 0.1 34144 9992 ? SLs 2019 6:28 proftpd: (accepting connections) root 10034 0.0 0.0 7800 892 pts/0 S+ 20:51 0:00 grep ftpd root@OpenMediaVault:~# sudo /etc/init.d/proftpd start [ ok ] Starting proftpd (via systemctl): proftpd.service. root@OpenMediaVault:~# ps aux | grep ftpd proftpd 1207 0.0 0.1 34144 9992 ? SLs 2019 6:28 proftpd: (accepting connections) root 10085 0.0 0.0 7800 888 pts/0 S+ 20:51 0:00 grep ftpd root@OpenMediaVault:~# sudo /etc/init.d/proftpd stop [ ok ] Stopping proftpd (via systemctl): proftpd.service. root@OpenMediaVault:~# ps aux | grep ftpd proftpd 1207 0.0 0.1 34144 9992 ? SLs 2019 6:28 proftpd: (accepting connections) root 10140 0.0 0.0 7800 828 pts/0 R+ 20:51 0:00 grep ftpd root@OpenMediaVault:~# sudo /etc/init.d/proftpd start [ ok ] Starting proftpd (via systemctl): proftpd.service. root@OpenMediaVault:~# ps aux | grep ftpd proftpd 1207 0.0 0.1 34144 9992 ? SLs 2019 6:28 proftpd: (accepting connections) root 10183 0.0 0.0 7800 892 pts/0 S+ 20:51 0:00 grep ftpd
I'm not really sure what to do at this point. I'm considering doing a good old kill -KILL <pid>, but at the same time, I am not sure that's a good idea.
Update: I decided to give it a shot and used `kill` as I mentioned above. It worked.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!