1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

MySQL upgrade

Discussion in 'Plesk for Linux - 8.x and Older' started by dano@, Jun 16, 2005.

  1. dano@

    dano@ Guest

    0
     
    I have recently obtained a Red Hat dedicated server using PLESK 7,5. I never worked with red hat and plesk...

    I have deinstalled mysql:
    # rpm –e –nodeps mysql-server-3.23.58-16.RHEL3.1
    # rpm –e –nodeps mysql-devel-3.23.58-15.RHEL3.1
    # rpm –e –nodeps mysql-3.23.58-15.RHEL3.1

    Installed new version:
    # rpm –i MySQL-server-standard-4.1.12-0.rhel3.i386.rpm
    # rpm –i MySQL-client-standard-4.1.12-0.rhel3.i386.rpm
    # rpm –i MySQL-devel-standard-4.1.12-0.rhel3.i386.rpm

    MySQL server is running and PLESK also, but the "Component Info" page: mysql - Component was not installed

    how can I make PLESK understand that mysql server is running?

    Please point me in the right direction how to solve this problem! Unfortunately it is very urgent... :(

    thx

    G
     
  2. fusionhosting

    fusionhosting Guest

    0
     
    Sorry, I don't have an answer since I haven't made the upgrade myself either.

    I just wanted to ask as well if there's any issues to watch out for when upgrading to mysql4 with plesk 7.5 (besides breaking the plesk gui status readout)?
     
  3. Cranky

    Cranky Guest

    0
     
    MySQL 4.1 seems to work fine on Plesk 7.5.3 ... older versions you'll need to use ART's mysql rpm's.
     
  4. atomicturtle

    atomicturtle Golden Pleskian

    29
     
    Joined:
    Nov 20, 2002
    Messages:
    2,110
    Likes Received:
    7
    Location:
    Washington, DC
    the mysql 4.1 rpms in my [atomic-testing] channel are designed to integrate correctly with PSA 7.5.3.
     
  5. Traged1

    Traged1 Guest

    0
     
    I recently upgraded MySQL3.28.xx to 4.0.24-2.rhel3.art via up2date with atomic yum channel for RHEL3 ES, with the PHP upgraded to 4.3.11-8.rhel3.art. I have run /usr/bin/mysql_fix_privilege_tables --user=admin --password=`cat /etc/psa/.psa.shadow` and edited my.cnf to look like:

    Here is what I get on /etc/init.d/psa restart:

    I think I may have to edit the init script but not sure, anyone have any idea's?
     
  6. Traged1

    Traged1 Guest

    0
     
    Ok, I am too tired, I just realized that I did not recompile perl-DBI
     
  7. Traged1

    Traged1 Guest

    0
     
    Well, I re-compiled the following packages from source:

    rpmbuild --rebuild perl-DBI-1.32-9.src.rpm
    rpm -Uvh /usr/src/redhat/RPMS/i386/perl-DBI-1.32-9.i386.rpm
    rpmbuild --rebuild perl-DBD-MySQL-2.1021-3.src.rpm
    rpm -Uvh /usr/src/redhat/RPMS/i386/perl-DBD-MySQL-2.1021-3.i386.rpm
    rpmbuild --rebuild perl-DBD-Pg-1.21-2.src.rpm
    rpm -Uvh /usr/src/redhat/RPMS/i386/perl-DBD-Pg-1.21-2.i386.rpm

    Still I get the cannot connect errors?

    Anyone hvae any other ideas?
     
  8. EvolutionCrazy

    EvolutionCrazy Basic Pleskian

    23
    90%
    Joined:
    Jun 4, 2005
    Messages:
    65
    Likes Received:
    0
    is you /tmp directory correctly chmodded to 1777?

    i've seen a similar problem (not with plesk, but with plain servers) that for some unknow nreason changed the chmod of /tmp...

    try to look at it and then restart mysql ;)
     
  9. Traged1

    Traged1 Guest

    0
     
    Yep chmod is 1777 on /tmp

    I managed to get rid of the spamassassin error, as I updated it to 3.x on Atomic's channel.

    So now I got this left:

     
  10. Traged1

    Traged1 Guest

    0
     
    It is wierd because the location of the mysql.sock file doesn't appear to have been changed, so I don't see why DBI is freaking out?
     
  11. atomicturtle

    atomicturtle Golden Pleskian

    29
     
    Joined:
    Nov 20, 2002
    Messages:
    2,110
    Likes Received:
    7
    Location:
    Washington, DC
    Is mysql actually running? The set syntax in your my.cnf was discontinued in mysql 4. I suspect whats happening is that mysql isnt even starting because of it.
     
  12. Traged1

    Traged1 Guest

    0
     
    Yep, but to be sure I have removed any of the set- directives.

    Here is what is in mysqld log upon restart:

     
  13. Traged1

    Traged1 Guest

    0
     
    Ok, maybe I have done something wrong back in the adding of the your yum channels, one of my pages is showing :

    CentOS-3 Test Page

    Yes we are on RHEL3ES,
     
  14. atomicturtle

    atomicturtle Golden Pleskian

    29
     
    Joined:
    Nov 20, 2002
    Messages:
    2,110
    Likes Received:
    7
    Location:
    Washington, DC
    my base/updates channels are from CentOS, that could be doing it.
     
  15. Traged1

    Traged1 Guest

    0
     
    That's prolly it,

    What do you think is the best way to resolve it now? Do a rmp --force on all the rmps?
     
  16. EvolutionCrazy

    EvolutionCrazy Basic Pleskian

    23
    90%
    Joined:
    Jun 4, 2005
    Messages:
    65
    Likes Received:
    0
    could be a problem related to old password hashing method?

    http://dev.mysql.com/doc/mysql/en/ignoring-user.html

    that happen when you update apache using ART repo (centOS based)

    if you want to mantain your redhat apache update it only with up2date and the offiacial "red hat network" ;)
     
  17. fusionhosting

    fusionhosting Guest

    0
     
    I've got a number of those mysql user password errors in my logs and I've only done Plesk 7.x updates and RH ES3 updates. So I doubt it has anything to do with the mysql update you did recently.
     
  18. Traged1

    Traged1 Guest

    0
     
    I'm not worried about apache, cuase I can easily re-build it from the redhat source. But I am a lillte concerned with MySQL, I guess I can just to a force, I hoe it doesn't break anything else.
     
  19. Traged1

    Traged1 Guest

    0
     
    Well recompiled apache from the redhat source, and rpm -e --nodeps perl-DBI and reinstalled perl-DBI and I still got the same error:

    DBI connect('mailmon:localhost:3306','mailmon1',...) failed: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) at /usr/sbin/sendmail line 85
    Unable to connect to MySQL database!

    Does anyone have any other idea's?
     
  20. Traged1

    Traged1 Guest

    0
     
    Well, I guess the last thing to do is force the rpm install of the correct MySQL version?
     
Loading...