Yesterday, I installed MySql 4.0.13. Everything works fine. All existing domains can now access new version of MySql and do not seem to have problems with it. Plesk also accepted it; however, there is one problem.

I cannot add new domains in Plesk. It turns out that MySql 4.0.x has "ssl" as a restrictied word, but Plesk uses it as a column name. Therefore, I get MySql error messege when I try to add new domains. The problem can be fixed by replacing ssl with `ssl`. However, all Plesk files are encrypted.

I'm thinking of two solutions: get Plesk to use `ssl` instead of ssl or get MySql to remove ssl from rescricted words. Does anybody have any ideas about my two solutions or something else that might help?

Thanks.

I would just like to let everybody know that MySQL 4.0.13 is incompatible with Plesk and you shouldn't install it. The problem is that "ssl" become a restricted word in MySQL 4.0.x but Plesk uses in one of its tables. Moreover, after the upgrade, Apache stopped working. However, I was able to get it back up.

I unstalled MySQL 4.0.13 and downgraded back to MySQL 3.23 that I had before. The only problem that remains is that ASP stopped working when I went back to 3.23. However, this is just a minor one.


DO NOT INSTALL MYSQL 4.0.13 ON PLESK UNLESS YOU HAVE LOTS OF SPARE TIME TO FIRST CONFIGURE IT AND THEN REMOVE IT

Look here: http://www.atomicrocketturtle.com/modules....&artid=8&page=1

this is an solution for mysql4 and psa5.x

If it were that easy, I would be running MySQL 4.0.13 on all my boxes.

I tried the solution you mentioned during my countless attempts to get MySQL 4.0.13 to work with Plesk 5. Unfortunately, nothing helped. I even contacted the person who wrote it. Thank you, scott@atomicrocketturtle.com, for responding within 20 minutes. He said that he didn't figure out a way to solve all incompatibilities of Plesk and MySQL 4.0.x.

I already uninstalled MySQL 4.0.13 and installed 3.23. Everything seems to be working fine. In my opinion, it's all bs that you cannot go back a version. I did and everythying works ok.

We tried mysql 4 a whiles back and it worked great until Apache restarted and then...BANG.....the server exploded into a million pieces and caused that transformer fire.

So there is no solution available? I've been waiting for the speed up of MySQL query caching so long. Hmm, might consider uninstalling Plesk


Just curious, what happened to Apache after restarting??? Is there a fix? Or Plesk uses a mod version of Apache (I doubt so)

The problem is that Plesk uses SSL as a field name while MySql 4.0 doesn't allow it. When Plesk tries to re-write httpd.include file, it cannot read domain information from MySql database "psa" properly. Therefore, httpd.include is created broken and Apache cannot start.

Modifying httpd.conf manually and getting rid of httpd.include completely might be the solution. This is practically equivalent to uninistalling Plesk because this effectively makes Plesk useless in modifying domain properties.

I have MySQL 4.0.13 working fine on my Plesk server.

The catch: I left MySQL 3 installed, and installed MySQL 4 to use different port/socket/etc. settings. This means Plesk can't do anything to manage MySQL 4, but I can use it manually on my busy sites.

Just a thought, at least this way doesn't break Plesk completely. Instructions here:

http://www.mysql.com/documentation/mysql/b...ultiple_servers

Doesn't it slow down the server to have two MySql 's running?

This is an cool idea

Can you write an quick howto?

You installed mysql from source or binary-pack?
Can you post how to start mysql4 and your my-cnf

I think you should use the source since it's more flexible in configuration. I installed MySQL4 and remove 3.23.x and I'll believe there'll be a full hack/support for MySQL4 for Plesk.

I intalled now mysql 4.0.14 from binary on different port/locations.
It´s working very good, my busy sites run on mysql4 , the others on mysql3.

I just put together a new mysql 4.0.14 rpm that should resolve the previous issues with the ssl reserved keyword. I'm looking for testers now, its available here:

www.atomicrocketturtle.com
or
www.atomicrocketturtle.com/psa/SRPMS/

Please note that you will have to recompile php and perl-DBI to work with the newer mysql libaries.

Did anybody test atomicturtle's RPM. I screwed up one of my servers with regular rpms (not from atomicturtle) like I said and eventually had to get a restore. Therefore, I'm not attemptin anything until somebody says that it's OK.

Anyways, did anybody test the RPMs yet?

Plesk should really release a patch for this.

I dont know, frankly I've seen the ssl reserved keyword break applications other than plesk. Rather than fix all of them, I just fixed mysql. I'm lazy I guess

Currently I'm testing this on 7.3/6.0.1. So anyone with a different platform or version of PSA that could test this out would be great.

I might be up to the challenge. I run 9.0/6.01 on a non-production server. But I'm afraid I'll break it if the installation procedure is too complicated.

How much modifications have you made to the source code of MySQL?

I have successfully installed both PHP 4.3.2 and Spamassasin with the help from your guides, so I must be doing something right .

I changed one line in lex.h I think, basically making the SSL keyword no longer reserved. This may or may not wreck havok with mysql if you use SSL-mysql. But my RPM (and the mysql.com one that this is based on) disables ssl by default anyway, so its not like it would have worked before I modified it either. Longterm I'll probably make that conditional, and fire off a patch to mysql.

You'll definitely have to recompile php (just a --rebuild, no other changes needed) or the mysql.so module will fail out. Theres probably a shortcut to just rebuild that shared object now that I think about it, but the path of least resistance right now is just to rebuild the whole RPM.

Wow! We have the amazing AtomicRocketTurtle in my little corner of the internet......no wonder they didn't miss me....hehe ...welcome to the nuthouse! Let me know if you need anything.