Ftp connection problem after update
04-02-2020, 09:45 PM
(This post was last modified: 04-02-2020, 10:59 PM by BatuhanK.)
Hi everyone, everything was working normal but after kernel update, proftpd problem started
When i tried to start proftpd service, it gave this error
unable to load 'mod_sql_mysql.c'; check to see if '/usr/libexec/proftpd/mod_sql_mysql.la' exists
After that i deleted theĀ
LoadModule mod_sql_mysql.c
line from /etc/proftpd.conf and proftpd service started to work but when i tried ftp connection, error was server not accepted
then changed the name of proftpd.conf and i did yum reinstall proftpd and yum reinstall proftpd-mysql
after that proftpd service can start normally but when i try to ftp connection, ftp client gives 530 login incorrect and proftpd service gives ftp session opened, no such user error
Can't open PID file /run/proftpd/proftpd.pid (yet?) after start: No such file or directory
ProFTPD 1.3.5e (maint) standalone mode STARTUP
Started ProFTPD FTP Server.
I can reach sentora_proftpd database and can see the users, i can add ftp users from sentora panel
Centos 7.0 Sentora 1.0.3
How can i solve this problem?
When i tried to start proftpd service, it gave this error
unable to load 'mod_sql_mysql.c'; check to see if '/usr/libexec/proftpd/mod_sql_mysql.la' exists
After that i deleted theĀ
LoadModule mod_sql_mysql.c
line from /etc/proftpd.conf and proftpd service started to work but when i tried ftp connection, error was server not accepted
then changed the name of proftpd.conf and i did yum reinstall proftpd and yum reinstall proftpd-mysql
after that proftpd service can start normally but when i try to ftp connection, ftp client gives 530 login incorrect and proftpd service gives ftp session opened, no such user error
Can't open PID file /run/proftpd/proftpd.pid (yet?) after start: No such file or directory
ProFTPD 1.3.5e (maint) standalone mode STARTUP
Started ProFTPD FTP Server.
I can reach sentora_proftpd database and can see the users, i can add ftp users from sentora panel
Centos 7.0 Sentora 1.0.3
How can i solve this problem?