proftp no authentification after mysql update [solved]

[semen]

Did yesterday the mysql update to version mysql-5.0.54,

and after words there is no ftp connection possible.

I am using proftp and mysql for authentification.


the messages says:

Jan 31 08:43:07 ajax proftpd[6595]: server (xx.xx.xx.xx[xx.xx.xx.xx]) - FTP session opened.
Jan 31 08:43:07 ajax proftpd[6595]: server (xx.xx.xx.xx[xx.xx.xx.xx]) - USER username (Login failed): No such user found.
Jan 31 08:43:07 ajax proftpd[6595]: server (xx.xx.xx.xx[xx.xx.xx.xx]) - FTP session closed.

the username and connection to mysql is ok, did test it.
And I did not change anything before and after mysql update.

I am using syscp. http://syscp.org/ for domain, email and ftp configuration.

my configuration in proftd.conf is:

MaxInstances 30

# Set the user and group under which the server will run.
#User proftpd
#Group proftpd
User nobody
Group nogroup

# Normally, we want files to be overwriteable.
<Directory />
AllowOverwrite on
</Directory>

<Global>
# CH-Root all users
DefaultRoot ~
# Reject rootlogin (just for security)
RootLogin off
# Noo need to require valid shell, because user is virtual
RequireValidShell off
</Global>

#SQLAuthTypes Crypt Plaintext
SQLAuthTypes Plaintext
SQLAuthenticate users* groups*
SQLConnectInfo syscp@localhost syscp "xxxxx"
SQLUserInfo ftp_users username password uid gid homedir shell
SQLGroupInfo ftp_groups groupname gid members
SQLUserWhereClause "login_enabled = 'Y'"

SQLLog PASS login
SQLNamedQuery login UPDATE "last_login=now(), login_count=login_count+1 where username='%u'" ftp_users

SQLLog RETR download
SQLNamedQuery download UPDATE "down_count=down_count+1, down_bytes=down_bytes+%b where username='%u'" ftp_users

SQLLog STOR upload
SQLNamedQuery upload update "up_count=up_count+1, up_bytes=up_bytes+%b where username='%u'" ftp_users

so what is wrong?
and how to fix.

As I see there the problem seams to be in the authentication to mysql.
So what was changed by the mysql update?

Please help

[-Craig-]

You might have to recompile proftpd. And about the changes in MySQL: Why not read the changelog?

[semen]

did solved the problem by switching to pure-ftp.

see
http://www.syscp.de/wiki/contrib/Pureftp

BTW pure-ftp is more stable in holding the ftp connection and perfomance.