I have installed OMV 6. Everything appears to be fine but when I try to enable the FTP Service I get a '500 Internal Server Error'.
Thanks.
I have installed OMV 6. Everything appears to be fine but when I try to enable the FTP Service I get a '500 Internal Server Error'.
Thanks.
I installed OMV 5 and have the same error message.
Here is a log I hope can help to detect the cause:
tail -f /var/log/syslog
Jul 4 01:11:38 nas monit[736]: 'proftpd' process is not running
Jul 4 01:11:38 nas monit[736]: 'proftpd' trying to restart
Jul 4 01:11:38 nas monit[736]: 'proftpd' start: '/etc/init.d/proftpd restart'
Jul 4 01:11:38 nas systemd[1]: Starting ProFTPD FTP Server...
Jul 4 01:11:38 nas proftpd[64191]: Checking syntax of configuration file
Jul 4 01:11:38 nas proftpd[64191]: 2021-07-04 01:11:38,197 nas proftpd[64191]: fatal: unknown configuration directive 'IdentLookups' on line 23 of '/etc/proftpd/proftpd.conf'
Jul 4 01:11:38 nas systemd[1]: proftpd.service: Control process exited, code=exited, status=1/FAILURE
Jul 4 01:11:38 nas systemd[1]: proftpd.service: Failed with result 'exit-code'.
Jul 4 01:11:38 nas systemd[1]: Failed to start ProFTPD FTP Server.
Jul 4 01:11:46 nas systemd[1]: Started /bin/systemctl mask avahi-daemon.service.
Jul 4 01:11:46 nas systemd[1]: Reloading.
Jul 4 01:11:46 nas systemd[1]: avahi-daemon.service: Current command vanished from the unit file, execution of the command list won't be resumed.
Jul 4 01:11:46 nas systemd[1]: run-rf525d6fd26e848e98c78388ca6e22ee5.scope: Succeeded.
Jul 4 01:11:46 nas systemd[1]: Started /bin/systemctl stop avahi-daemon.socket.
Jul 4 01:11:46 nas systemd[1]: avahi-daemon.socket: Succeeded.
Jul 4 01:11:46 nas systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
Jul 4 01:11:46 nas systemd[1]: run-r969a3dbdc9494762a114728643cfbda7.scope: Succeeded.
Jul 4 01:11:46 nas systemd[1]: Started /bin/systemctl disable avahi-daemon.socket.
Jul 4 01:11:46 nas systemd[1]: Reloading.
Jul 4 01:11:47 nas systemd[1]: run-ra0fa5aa8bb4a461a9e833a8ad1f00dd0.scope: Succeeded.
Jul 4 01:11:47 nas systemd[1]: Started /bin/systemctl stop avahi-daemon.service.
Jul 4 01:11:47 nas avahi-daemon[50849]: Got SIGTERM, quitting.
Jul 4 01:11:47 nas avahi-daemon[50849]: Leaving mDNS multicast group on interface enp5s0.IPv4 with address 192.168.1.41.
Jul 4 01:11:47 nas avahi-daemon[50849]: Leaving mDNS multicast group on interface lo.IPv6 with address ::1.
Jul 4 01:11:47 nas avahi-daemon[50849]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Jul 4 01:11:47 nas systemd[1]: Stopping avahi-daemon.service...
Jul 4 01:11:47 nas avahi-daemon[50849]: avahi-daemon 0.8 exiting.
Jul 4 01:11:47 nas systemd[1]: avahi-daemon.service: Succeeded.
Jul 4 01:11:47 nas systemd[1]: Stopped avahi-daemon.service.
Jul 4 01:11:47 nas systemd[1]: run-r55514fd8df4c44bda3f9de38f429542c.scope: Succeeded.
Jul 4 01:11:47 nas systemd[1]: Started /bin/systemctl unmask avahi-daemon.service.
Jul 4 01:11:47 nas systemd[1]: Reloading.
Jul 4 01:11:48 nas systemd[1]: run-r20499c990adb4b7f8677bd944b0a9246.scope: Succeeded.
Jul 4 01:11:48 nas systemd[1]: Started /bin/systemctl start avahi-daemon.socket.
Jul 4 01:11:48 nas systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Jul 4 01:11:48 nas systemd[1]: run-r1fdba22e3d674da693ae021ba7b5835f.scope: Succeeded.
Jul 4 01:11:48 nas systemd[1]: Started /bin/systemctl enable avahi-daemon.socket.
Jul 4 01:11:48 nas systemd[1]: Reloading.
Jul 4 01:11:48 nas systemd[1]: run-r40d9132fcab04817806121029cf20c00.scope: Succeeded.
Jul 4 01:11:48 nas systemd[1]: Started /bin/systemctl start avahi-daemon.service.
Jul 4 01:11:48 nas systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Jul 4 01:11:48 nas avahi-daemon[64526]: Process 50849 died: No such process; trying to remove PID file. (/run/avahi-daemon//pid)
Jul 4 01:11:48 nas avahi-daemon[64526]: Found user 'avahi' (UID 112) and group 'avahi' (GID 116).
Jul 4 01:11:48 nas avahi-daemon[64526]: Successfully dropped root privileges.
Jul 4 01:11:48 nas avahi-daemon[64526]: avahi-daemon 0.8 starting up.
Jul 4 01:11:48 nas systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Jul 4 01:11:48 nas systemd[1]: run-r3cfbce812ba048bda886174c06587ba8.scope: Succeeded.
Jul 4 01:11:48 nas avahi-daemon[64526]: Successfully called chroot().
Jul 4 01:11:48 nas avahi-daemon[64526]: Successfully dropped remaining capabilities.
Jul 4 01:11:48 nas avahi-daemon[64526]: Loading service file /services/ftp.service.
Jul 4 01:11:48 nas avahi-daemon[64526]: Loading service file /services/nfs-global_folder.service.
Jul 4 01:11:48 nas avahi-daemon[64526]: Loading service file /services/smb.service.
Jul 4 01:11:48 nas avahi-daemon[64526]: Loading service file /services/ssh.service.
Jul 4 01:11:48 nas avahi-daemon[64526]: Loading service file /services/website.service.
Jul 4 01:11:48 nas avahi-daemon[64526]: Joining mDNS multicast group on interface enp5s0.IPv4 with address 192.168.1.41.
Jul 4 01:11:48 nas avahi-daemon[64526]: New relevant interface enp5s0.IPv4 for mDNS.
Jul 4 01:11:48 nas avahi-daemon[64526]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
Jul 4 01:11:48 nas avahi-daemon[64526]: New relevant interface lo.IPv6 for mDNS.
Jul 4 01:11:48 nas avahi-daemon[64526]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Jul 4 01:11:48 nas avahi-daemon[64526]: New relevant interface lo.IPv4 for mDNS.
Jul 4 01:11:48 nas avahi-daemon[64526]: Network interface enumeration completed.
Jul 4 01:11:48 nas avahi-daemon[64526]: Registering new address record for 192.168.1.41 on enp5s0.IPv4.
Jul 4 01:11:48 nas avahi-daemon[64526]: Registering new address record for ::1 on lo.*.
Jul 4 01:11:48 nas avahi-daemon[64526]: Registering new address record for 127.0.0.1 on lo.IPv4.
Jul 4 01:11:49 nas avahi-daemon[64526]: Server startup complete. Host name is nas.local. Local service cookie is 1007010703.
Jul 4 01:11:50 nas avahi-daemon[64526]: Service "nas - Web control panel" (/services/website.service) successfully established.
Jul 4 01:11:50 nas avahi-daemon[64526]: Service "nas - SSH" (/services/ssh.service) successfully established.
Jul 4 01:11:50 nas avahi-daemon[64526]: Service "nas - SMB/CIFS" (/services/smb.service) successfully established.
Jul 4 01:11:50 nas avahi-daemon[64526]: Service "nas - NFS [global_folder]" (/services/nfs-global_folder.service) successfully established.
Jul 4 01:11:50 nas avahi-daemon[64526]: Service "nas - FTP" (/services/ftp.service) successfully established.
Jul 4 01:12:08 nas monit[736]: 'proftpd' failed to start (exit status 1) -- '/etc/init.d/proftpd restart': Job for proftpd.service failed because the control process exited with error code.#012See "systemctl status proftpd.service" and "journalctl -xe" for details.#012
Jul 4 01:12:38 nas monit[736]: 'proftpd' process is not running
Jul 4 01:12:38 nas monit[736]: 'proftpd' trying to restart
Jul 4 01:12:38 nas monit[736]: 'proftpd' start: '/etc/init.d/proftpd restart'
Jul 4 01:12:38 nas systemd[1]: Starting ProFTPD FTP Server...
Jul 4 01:12:38 nas proftpd[66284]: Checking syntax of configuration file
Jul 4 01:12:38 nas proftpd[66284]: 2021-07-04 01:12:38,472 nas proftpd[66284]: fatal: unknown configuration directive 'IdentLookups' on line 23 of '/etc/proftpd/proftpd.conf'
Jul 4 01:12:38 nas systemd[1]: proftpd.service: Control process exited, code=exited, status=1/FAILURE
Jul 4 01:12:38 nas systemd[1]: proftpd.service: Failed with result 'exit-code'.
Jul 4 01:12:38 nas systemd[1]: Failed to start ProFTPD FTP Server.
Alles anzeigen
I don't know if there are any problem, but the folder I have associated to the ftp service is already associated to SMB service that is working well.
Thanks any help
Yes. Mine is associated with the SMB service and working very well also. It's not like I use FTP a lot anymore, but I do use from time to time. It worked fine on my OMV5 install.
Here is my output, looks like there might be a configuration issue.
tail -f /var/log/syslog
Jul 4 18:05:18 OMV monit[752]: 'proftpd' failed to start (exit status 1) -- '/etc/init.d/proftpd restart': Job for proftpd.service failed because the control process exited with error code.#012See "systemctl status proftpd.service" and "journalctl -xe" for details.#012
Jul 4 18:05:48 OMV monit[752]: 'proftpd' process is not running
Jul 4 18:05:48 OMV monit[752]: 'proftpd' trying to restart
Jul 4 18:05:48 OMV monit[752]: 'proftpd' start: '/etc/init.d/proftpd restart'
Jul 4 18:05:48 OMV systemd[1]: Starting ProFTPD FTP Server...
Jul 4 18:05:48 OMV proftpd[40344]: Checking syntax of configuration file
Jul 4 18:05:48 OMV proftpd[40344]: 2021-07-04 18:05:48,334 OMV proftpd[40344]: fatal: unknown configuration directive 'IdentLookups' on line 22 of '/etc/proftpd/proftpd.conf'
Jul 4 18:05:48 OMV systemd[1]: proftpd.service: Control process exited, code=exited, status=1/FAILURE
Jul 4 18:05:48 OMV systemd[1]: proftpd.service: Failed with result 'exit-code'.
Jul 4 18:05:48 OMV systemd[1]: Failed to start ProFTPD FTP Server.
Jul 4 18:06:18 OMV monit[752]: 'proftpd' failed to start (exit status 1) -- '/etc/init.d/proftpd restart': Job for proftpd.service failed because the control process exited with error code.#012See "systemctl status proftpd.service" and "journalctl -xe" for details.#012
It's because the ident-Module is not loaded by default. Just remove the leading # in /etc/proftpd/modules.conf
#This is required only if you need to set IdentLookups on
#LoadModule mod_ident.c
Alles anzeigenI installed OMV 5 and have the same error message.
Here is a log I hope can help to detect the cause:
CodeAlles anzeigentail -f /var/log/syslog Jul 4 01:11:38 nas monit[736]: 'proftpd' process is not running Jul 4 01:11:38 nas monit[736]: 'proftpd' trying to restart Jul 4 01:11:38 nas monit[736]: 'proftpd' start: '/etc/init.d/proftpd restart' Jul 4 01:11:38 nas systemd[1]: Starting ProFTPD FTP Server... Jul 4 01:11:38 nas proftpd[64191]: Checking syntax of configuration file Jul 4 01:11:38 nas proftpd[64191]: 2021-07-04 01:11:38,197 nas proftpd[64191]: fatal: unknown configuration directive 'IdentLookups' on line 23 of '/etc/proftpd/proftpd.conf' Jul 4 01:11:38 nas systemd[1]: proftpd.service: Control process exited, code=exited, status=1/FAILURE Jul 4 01:11:38 nas systemd[1]: proftpd.service: Failed with result 'exit-code'. Jul 4 01:11:38 nas systemd[1]: Failed to start ProFTPD FTP Server. Jul 4 01:11:46 nas systemd[1]: Started /bin/systemctl mask avahi-daemon.service. Jul 4 01:11:46 nas systemd[1]: Reloading. Jul 4 01:11:46 nas systemd[1]: avahi-daemon.service: Current command vanished from the unit file, execution of the command list won't be resumed. Jul 4 01:11:46 nas systemd[1]: run-rf525d6fd26e848e98c78388ca6e22ee5.scope: Succeeded. Jul 4 01:11:46 nas systemd[1]: Started /bin/systemctl stop avahi-daemon.socket. Jul 4 01:11:46 nas systemd[1]: avahi-daemon.socket: Succeeded. Jul 4 01:11:46 nas systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket. Jul 4 01:11:46 nas systemd[1]: run-r969a3dbdc9494762a114728643cfbda7.scope: Succeeded. Jul 4 01:11:46 nas systemd[1]: Started /bin/systemctl disable avahi-daemon.socket. Jul 4 01:11:46 nas systemd[1]: Reloading. Jul 4 01:11:47 nas systemd[1]: run-ra0fa5aa8bb4a461a9e833a8ad1f00dd0.scope: Succeeded. Jul 4 01:11:47 nas systemd[1]: Started /bin/systemctl stop avahi-daemon.service. Jul 4 01:11:47 nas avahi-daemon[50849]: Got SIGTERM, quitting. Jul 4 01:11:47 nas avahi-daemon[50849]: Leaving mDNS multicast group on interface enp5s0.IPv4 with address 192.168.1.41. Jul 4 01:11:47 nas avahi-daemon[50849]: Leaving mDNS multicast group on interface lo.IPv6 with address ::1. Jul 4 01:11:47 nas avahi-daemon[50849]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Jul 4 01:11:47 nas systemd[1]: Stopping avahi-daemon.service... Jul 4 01:11:47 nas avahi-daemon[50849]: avahi-daemon 0.8 exiting. Jul 4 01:11:47 nas systemd[1]: avahi-daemon.service: Succeeded. Jul 4 01:11:47 nas systemd[1]: Stopped avahi-daemon.service. Jul 4 01:11:47 nas systemd[1]: run-r55514fd8df4c44bda3f9de38f429542c.scope: Succeeded. Jul 4 01:11:47 nas systemd[1]: Started /bin/systemctl unmask avahi-daemon.service. Jul 4 01:11:47 nas systemd[1]: Reloading. Jul 4 01:11:48 nas systemd[1]: run-r20499c990adb4b7f8677bd944b0a9246.scope: Succeeded. Jul 4 01:11:48 nas systemd[1]: Started /bin/systemctl start avahi-daemon.socket. Jul 4 01:11:48 nas systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket. Jul 4 01:11:48 nas systemd[1]: run-r1fdba22e3d674da693ae021ba7b5835f.scope: Succeeded. Jul 4 01:11:48 nas systemd[1]: Started /bin/systemctl enable avahi-daemon.socket. Jul 4 01:11:48 nas systemd[1]: Reloading. Jul 4 01:11:48 nas systemd[1]: run-r40d9132fcab04817806121029cf20c00.scope: Succeeded. Jul 4 01:11:48 nas systemd[1]: Started /bin/systemctl start avahi-daemon.service. Jul 4 01:11:48 nas systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Jul 4 01:11:48 nas avahi-daemon[64526]: Process 50849 died: No such process; trying to remove PID file. (/run/avahi-daemon//pid) Jul 4 01:11:48 nas avahi-daemon[64526]: Found user 'avahi' (UID 112) and group 'avahi' (GID 116). Jul 4 01:11:48 nas avahi-daemon[64526]: Successfully dropped root privileges. Jul 4 01:11:48 nas avahi-daemon[64526]: avahi-daemon 0.8 starting up. Jul 4 01:11:48 nas systemd[1]: Started Avahi mDNS/DNS-SD Stack. Jul 4 01:11:48 nas systemd[1]: run-r3cfbce812ba048bda886174c06587ba8.scope: Succeeded. Jul 4 01:11:48 nas avahi-daemon[64526]: Successfully called chroot(). Jul 4 01:11:48 nas avahi-daemon[64526]: Successfully dropped remaining capabilities. Jul 4 01:11:48 nas avahi-daemon[64526]: Loading service file /services/ftp.service. Jul 4 01:11:48 nas avahi-daemon[64526]: Loading service file /services/nfs-global_folder.service. Jul 4 01:11:48 nas avahi-daemon[64526]: Loading service file /services/smb.service. Jul 4 01:11:48 nas avahi-daemon[64526]: Loading service file /services/ssh.service. Jul 4 01:11:48 nas avahi-daemon[64526]: Loading service file /services/website.service. Jul 4 01:11:48 nas avahi-daemon[64526]: Joining mDNS multicast group on interface enp5s0.IPv4 with address 192.168.1.41. Jul 4 01:11:48 nas avahi-daemon[64526]: New relevant interface enp5s0.IPv4 for mDNS. Jul 4 01:11:48 nas avahi-daemon[64526]: Joining mDNS multicast group on interface lo.IPv6 with address ::1. Jul 4 01:11:48 nas avahi-daemon[64526]: New relevant interface lo.IPv6 for mDNS. Jul 4 01:11:48 nas avahi-daemon[64526]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Jul 4 01:11:48 nas avahi-daemon[64526]: New relevant interface lo.IPv4 for mDNS. Jul 4 01:11:48 nas avahi-daemon[64526]: Network interface enumeration completed. Jul 4 01:11:48 nas avahi-daemon[64526]: Registering new address record for 192.168.1.41 on enp5s0.IPv4. Jul 4 01:11:48 nas avahi-daemon[64526]: Registering new address record for ::1 on lo.*. Jul 4 01:11:48 nas avahi-daemon[64526]: Registering new address record for 127.0.0.1 on lo.IPv4. Jul 4 01:11:49 nas avahi-daemon[64526]: Server startup complete. Host name is nas.local. Local service cookie is 1007010703. Jul 4 01:11:50 nas avahi-daemon[64526]: Service "nas - Web control panel" (/services/website.service) successfully established. Jul 4 01:11:50 nas avahi-daemon[64526]: Service "nas - SSH" (/services/ssh.service) successfully established. Jul 4 01:11:50 nas avahi-daemon[64526]: Service "nas - SMB/CIFS" (/services/smb.service) successfully established. Jul 4 01:11:50 nas avahi-daemon[64526]: Service "nas - NFS [global_folder]" (/services/nfs-global_folder.service) successfully established. Jul 4 01:11:50 nas avahi-daemon[64526]: Service "nas - FTP" (/services/ftp.service) successfully established. Jul 4 01:12:08 nas monit[736]: 'proftpd' failed to start (exit status 1) -- '/etc/init.d/proftpd restart': Job for proftpd.service failed because the control process exited with error code.#012See "systemctl status proftpd.service" and "journalctl -xe" for details.#012 Jul 4 01:12:38 nas monit[736]: 'proftpd' process is not running Jul 4 01:12:38 nas monit[736]: 'proftpd' trying to restart Jul 4 01:12:38 nas monit[736]: 'proftpd' start: '/etc/init.d/proftpd restart' Jul 4 01:12:38 nas systemd[1]: Starting ProFTPD FTP Server... Jul 4 01:12:38 nas proftpd[66284]: Checking syntax of configuration file Jul 4 01:12:38 nas proftpd[66284]: 2021-07-04 01:12:38,472 nas proftpd[66284]: fatal: unknown configuration directive 'IdentLookups' on line 23 of '/etc/proftpd/proftpd.conf' Jul 4 01:12:38 nas systemd[1]: proftpd.service: Control process exited, code=exited, status=1/FAILURE Jul 4 01:12:38 nas systemd[1]: proftpd.service: Failed with result 'exit-code'. Jul 4 01:12:38 nas systemd[1]: Failed to start ProFTPD FTP Server.
I don't know if there are any problem, but the folder I have associated to the ftp service is already associated to SMB service that is working well.
Thanks any help
fabiopaolini How is this possible? OMV5 is based on Debian Buster which uses ProFTPd 1.3.6. In this version the mod_ident is compiled by default and not as an external module that needs to be enabled. Are you using a backport from Debian Bullseye? Using backports is not supported in OMV because of exactly the problem you are facing now, backports break existing configurations and introduce new features that are not reflected by the deployment scripts.
Fixed in OMV 6.0-13, see https://github.com/openmediava…89e681730dfdac7cb2897b9cd.
fabiopaolini How is this possible? OMV5 is based on Debian Buster which uses ProFTPd 1.3.6. In this version the mod_ident is compiled by default and not as an external module that needs to be enabled. Are you using a backport from Debian Bullseye? Using backports is not supported in OMV because of exactly the problem you are facing now, backports break existing configurations and introduce new features that are not reflected by the deployment scripts.
Sorry, probably I made a mistake. I have downloaded the two isos and I thought that I had installed the 5. Now I have changed my instalation where I have installed the Debian and then installing the OMV. My actual install is really the "6.0-12 (Shaitan)". I have the other in a pendrive to confirm soon, but good chance it be a version 6. I will also soon try the suggestions about the fix. Thanks
It's because the ident-Module is not loaded by default. Just remove the leading # in /etc/proftpd/modules.conf
#This is required only if you need to set IdentLookups on
#LoadModule mod_ident.c
Thanks Burgermeister It works
Thanks. It is working now.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!