1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice

Can't get plesk up trying to go from 7.1 to 7.5

Discussion in 'Plesk for Linux - 8.x and Older' started by fuzzball, Jan 3, 2005.

  1. fuzzball

    fuzzball Guest

    0
     
    I had problems going from 7.1.4 to 7.1.6, couldn't get the autoupdater to run correctly, so I downloaded the patch from the web site and did it manually through the shell. Everything seemed to go fine and plesk and the server came back up.

    When I tried to go to 7.5 the autoupdater again wouldn't work so I figured I would take the same route and download the patch and do it from the shell. My server is running, and the 1 site I've installed so far seems to be operational, but plesk will not come back up. I've tried re-installing RPM's, rebooting, using force on the rpm's and no luck. Following is the complete output I get from command entry to failure....Can anyone help me out so I can get this thing functional again?

    [root@srv1 base]# rpm --force -Uhv courier-imap-3.0.8-rhel3.build75041216.14.i586.rpm libidn-0.4.2-rhel3.build75041216.14.i586.rpm Mambo-4.5.1-1.noarch.rpm osCommerce-2.2ms2-3.noarch.rpm psa-7.5.1-rhel3.build75041216.14.i586.rpm psa-api-cli-7.5.1-rhel3.build75041216.14.i586.rpm psa-api-common-7.5.1-rhel3.build75041216.14.i586.rpm psa-courier-imap-add-7.5.1-rhel3.build75041216.14.i586.rpm psa-key-7.5-rhel3.build75041216.14.noarch.rpm psa-locale-base-en-US-7.5.1-rhel3.build75041216.14.noarch.rpm psa-logrotate-3.7-rhel3.build75041216.14.i586.rpm psa-pre-keyupdate-7.5.1-rhel3.build75041216.14.i586.rpm psa-proftpd-1.2.10-rhel3.build75041216.14.i586.rpm psa-proftpd-xinetd-1.2.10-rhel3.build75041216.14.i586.rpm psa-qmail-1.03-rhel3.build75041216.14.i586.rpm ../opt/bu/perl-Compress-Zlib-1.33-rhel3.build75041216.14.i586.rpm ../opt/bu/perl-IO-Ftp-0.05-rhel3.build75041216.14.noarch.rpm ../opt/bu/perl-IO-Zlib-1.01-rhel3.build75041216.14.noarch.rpm ../opt/bu/perl-MIME-Lite-2.117-rhel3.build75041216.14.noarch.rpm ../opt/bu/psa-bu-7.5.1-rhel3.build75041216.14.i586.rpm ../opt/api/psa-api-rpc-1.3.2-3.1.i586.rpm ../opt/api/psa-api-rpc-doc-1.3.2-3.1.i586.rpm ../opt/api/psa-api-rpc-protocol-1.3.2-3.1.i586.rpm ../opt/fp/frontpage-5.0-70psa.rhel3.i586.rpm ../opt/perl/perl-Apache-ASP-2.57-rhel3.build75041216.14.noarch.rpm ../opt/perl/perl-Font-AFM-1.18-60psa.noarch.rpm ../opt/perl/perl-FreezeThaw-0.43-60psa.noarch.rpm ../opt/perl/perl-HTML-Format-1.23-50psa.noarch.rpm ../opt/perl/perl-HTML-Tree-3.16-60psa.noarch.rpm ../opt/perl/perl-MLDBM-2.01-60psa.noarch.rpm ../opt/perl/perl-MLDBM-Sync-0.30-60psa.noarch.rpm ../opt/PPWSE/PPWSE-1.1-rhel3.build75041216.14.i586.rpm ../opt/sshterm/SSHTerm-0.2.2-rhel3.build75041216.14.noarch.rpm ../opt/drweb/drweb-4.32.2-rh2_psa.i586.rpm ../opt/drweb/drweb-qmail-4.32-rhel3.build75041216.14.i586.rpm
    Preparing... ########################################### [100%]
    1:psa-pre-keyupdate ########################################### [ 3%]
    mysqld is stopped
    Starting MySQL: [ OK ]
    mysqld (pid 10889) is running...
    Stopping MySQL: [ OK ]
    No errors on key upgrade

    2:perl-HTML-Tree ########################################### [ 6%]
    3:perl-FreezeThaw ########################################### [ 9%]
    4:perl-MLDBM ########################################### [ 11%]
    5:perl-Compress-Zlib ########################################### [ 14%]
    6:libidn ########################################### [ 17%]
    7:psa-qmail ########################################### [ 20%]
    ===> Reading /etc/psa/psa.conf ...
    Trying to set up default qmail permissions... done

    ===> Installing Qmail server
    Trying to set maillog file to /usr/local/psa/var/log/maillog... done
    Configuring Qmail...
    Trying to generate SSL certificates for TLS sessions... done
    Trying to start Qmail services... done
    8:perl-IO-Zlib ########################################### [ 23%]
    9:perl-MLDBM-Sync ########################################### [ 26%]
    10:perl-HTML-Format ########################################### [ 29%]
    11:courier-imap ########################################### [ 31%]
    Stopping Courier-IMAP server:
    Stopping imap [ OK ]
    Stopping imap-ssl [ OK ]
    Stopping pop3 [ OK ]
    Stopping pop3-ssl [ OK ]

    Starting Courier-IMAP server:
    Starting imapd [ OK ]
    Starting imap-ssl [ OK ]
    Starting pop3 [ OK ]
    Starting pop3-ssl [ OK ]

    12:psa-courier-imap-add ########################################### [ 34%]
    Stopping Courier-IMAP server:
    Stopping imap [ OK ]
    Stopping imap-ssl [ OK ]
    Stopping pop3 [ OK ]
    Stopping pop3-ssl [ OK ]

    Starting Courier-IMAP server:
    Starting imapd [ OK ]
    Starting imap-ssl [ OK ]
    Starting pop3 [ OK ]
    Starting pop3-ssl [ OK ]

    13:psa-key ########################################### [ 37%]
    14:psa-locale-base-en-US ########################################### [ 40%]
    15:psa-proftpd ########################################### [ 43%]
    16:psa-proftpd-xinetd ########################################### [ 46%]
    xinetd: no process killed
    17:drweb ########################################### [ 49%]
    ===> Removing bases from other versions ...
    ===> An update task already exists in the drweb crontab ...


    Please inspect /etc/drweb/drweb32.ini.rpmnew and /opt/drweb/doc/ChangeLog
    for changes in a configuration file

    18:perl-Font-AFM ########################################### [ 51%]
    19:perl-MIME-Lite ########################################### [ 54%]
    20:perl-IO-Ftp ########################################### [ 57%]
    21:psa-logrotate ########################################### [ 60%]
    22:perl-Apache-ASP ########################################### [ 63%]
    23:drweb-qmail ########################################### [ 66%]
    ===> Reading /etc/psa/psa.conf ...

    Trying to set up default drweb permissions... Checking for the system groups and users necessary for DrWeb...
    Checking for the group 'drweb'...
    Group 'drweb' already exists

    Checking for the user 'drweb'...
    User 'drweb' already exists

    Checking for the group 'nofiles'...
    Trying to add supplementary group 'nofiles' for user 'drweb'... already there
    Making chown and chmod under drweb stuff
    Trying to set up default drweb permissions... Making changes in drweb config files
    Trying to stop DrWeb services... Trying to start DrWeb services...
    WARNING!
    During the start found some small problems(see log file: /tmp/psa_7.5.1_RedHat_el3_build75041216.14_upgrade.log)

    Continue...

    24:SSHTerm ########################################### [ 69%]
    25:frontpage ########################################### [ 71%]
    Upgrading FrontPage extension...
    All existing servers will now be upgraded.
    grep: /usr/local/frontpage/version5.0/upgrade_results.txt: No such file or directory
    grep: /usr/local/frontpage/*.cnf: No such file or directory
    grep: /usr/local/frontpage/*.cnf: No such file or directory
    dirname: too few arguments
    Try `dirname --help' for more information.
    grep: /usr/local/frontpage/*.cnf: No such file or directory
    Preparing to chown webs...
    Processing /usr/local/frontpage/*.cnf
    Look at /tmp/fp_5.0_upgrade.log for details.
    Do parse ... done. frontpage_module already installed.
    26:psa-api-rpc-protocol ########################################### [ 74%]
    27:psa-api-rpc-doc ########################################### [ 77%]
    28:eek:sCommerce ########################################### [ 80%]
    29:Mambo ########################################### [ 83%]
    30:psa-api-common ########################################### [ 86%]

    Trying to define super-server internet daemon type... xinetd
    Trying to check if xinetd daemon is running... WARNING: no running xinetd found, will try to start
    Trying to restart xinetd daemon... done
    done
    ===> Reading /etc/psa/psa.conf ...


    ...Continued...
     
  2. fuzzball

    fuzzball Guest

    0
     
    ===> Checking for "/usr/local/psa" directory ... found.
    Making some checks before upgrading
    Trying to start BIND server... done

    BIND server starts Ok.


    Now BIND server shutting down...

    Trying to stop BIND server... done
    Trying to start MySQL server... done
    Trying to establish test connection... connected
    Trying to stop MySQL server... done

    ===> Checking for the necessary system accounts
    Checking for the system groups and users necessary for Qmail...
    Checking for the group 'nofiles'...
    Group 'nofiles' already exists

    Checking for the user 'alias'...
    User 'alias' already exists

    Checking for the user 'qmaild'...
    User 'qmaild' already exists

    Checking for the user 'qmaill'...
    User 'qmaill' already exists

    Checking for the user 'qmailp'...
    User 'qmailp' already exists

    Checking for the group 'qmail'...
    Group 'qmail' already exists

    Checking for the user 'qmailq'...
    User 'qmailq' already exists

    Checking for the user 'qmailr'...
    User 'qmailr' already exists

    Checking for the user 'qmails'...
    User 'qmails' already exists

    Checking for the group 'popuser'...
    Group 'popuser' already exists

    Checking for the user 'popuser'...
    User 'popuser' already exists

    Checking for the system groups and users necessary for named (bind)...
    Checking for the group 'named'...
    Group 'named' already exists

    Checking for the user 'named'...
    User 'named' already exists

    Checking for the system groups and users necessary for MySQL...
    Checking for the group 'mysql'...
    Group 'mysql' already exists

    Checking for the user 'mysql'...
    User 'mysql' already exists

    Checking for the system groups and users necessary for admin server...
    Checking for the group 'psaadm'...
    Group 'psaadm' already exists

    Checking for the user 'psaadm'...
    User 'psaadm' already exists

    Checking for the system groups and users necessary for Apache...
    Checking for the group 'apache'...
    Group 'apache' already exists

    Checking for the user 'apache'...
    User 'apache' already exists

    Checking that /bin/false registered as login shell...
    /bin/false is already registered as login shell

    /usr/local/psa/bin/chrootsh already registered as a login shell
    Checking for the group 'psaftp'...
    Group 'psaftp' already exists

    Checking for the user 'psaftp'...
    User 'psaftp' already exists

    Checking for ftp home directory for 'clients' group...
    '@psacln' is already in the /etc/ftpchroot

    Checking for the group 'psaserv'...
    Group 'psaserv' already exists

    Checking for the group 'psaserv'...
    Trying to add supplementary group 'psaserv' for user 'apache'... already there
    Checking for the group 'psaserv'...
    Trying to add supplementary group 'psaserv' for user 'psaftp'... already there
    Checking for the group 'psaserv'...
    Trying to add supplementary group 'psaserv' for user 'psaadm'... already there
    group psacln already exists
    Standard build detected. Upgrading canceled, because only
    5.0.x versions supported for upgrading from Standard to RPM
    builds.

    error: %pre(psa-7.5.1-rhel3.build75041216.14) scriptlet failed, exit status 1
    error: install: %pre scriptlet failed (2), skipping psa-7.5.1-rhel3.build75041216.14
    31:psa-api-cli ########################################### [ 89%]
    32:psa-bu ########################################### [ 91%]
    Generate public/private keys pair for server ...
    domain_bu: db_connect: failed to connect to database: Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    domain_bu: db_connect: failed to connect to database: Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    Can't connect to MySQL database: No such file or directory
    domain_bu: db_connect: failed to connect to database: Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    domain_bu: db_connect: failed to connect to database: Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    Can't connect to MySQL database: No such file or directory
    Server keys generating done
    33:psa-api-rpc ########################################### [ 94%]
    ===> Reading /etc/psa/psa.conf ...

    ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    db_connect: failed to connect to database: Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    db_connect: failed to connect to database: Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    Key register failed
    /var/tmp/rpm-tmp.89833: line 18922: 12063 Terminated /usr/local/psa/admin/bin/php /usr/local/psa/installer/api/install_db.php
    error: %post(psa-api-rpc-1.3.2-3.1) scriptlet failed, exit status 143
    34:pPWSE ########################################### [ 97%]
    [root@srv1 base]#

    -------
    So that's it. Anyone got any ideas? It looks to me like mysql is not coming back up properly, but when I manually stop and start it, it works fine.
     
  3. Cranky

    Cranky Guest

    0
     
    Are you running mysql4? If so, downgrade to mysql3 and retry.
     
  4. fuzzball

    fuzzball Guest

    0
     
    No, not running anything out of the ordinary. This is a brand new server I just got from Ev1. Everything is standard. All I did was set up the DNS, add 1 domain to the system and try to update plesk to the latest version. Nothing has been modified from the standard plesk installation.
     
  5. Cranky

    Cranky Guest

    0
     
    Check /var/log/mysqld.log
     
  6. fuzzball

    fuzzball Guest

    0
     
    050103 16:56:46 mysqld started
    Cannot initialize InnoDB as 'innodb_data_file_path' is not set.
    If you do not want to use transactional InnoDB tables, add a line
    skip-innodb
    to the [mysqld] section of init parameters in your my.cnf
    or my.ini. If you want to use InnoDB tables, add to the [mysqld]
    section, for example,
    innodb_data_file_path = ibdata1:10M:autoextend
    But to get good performance you should adjust for your hardware
    the InnoDB startup options listed in section 2 at
    http://www.innodb.com/ibman.html
    /usr/libexec/mysqld: ready for connections
    050103 17:51:00 /usr/libexec/mysqld: Normal shutdown

    050103 17:51:00 /usr/libexec/mysqld: Shutdown Complete

    050103 17:51:00 mysqld ended

    050103 17:51:05 mysqld started
    Cannot initialize InnoDB as 'innodb_data_file_path' is not set.
    If you do not want to use transactional InnoDB tables, add a line
    skip-innodb
    to the [mysqld] section of init parameters in your my.cnf
    or my.ini. If you want to use InnoDB tables, add to the [mysqld]
    section, for example,
    innodb_data_file_path = ibdata1:10M:autoextend
    But to get good performance you should adjust for your hardware
    the InnoDB startup options listed in section 2 at
    http://www.innodb.com/ibman.html
    /usr/libexec/mysqld: ready for connections
    050103 17:51:08 /usr/libexec/mysqld: Normal shutdown

    050103 17:51:08 /usr/libexec/mysqld: Shutdown Complete

    050103 17:51:08 mysqld ended

    ------
    That's all I have, over and over in the mysqld.log
     
  7. fuzzball

    fuzzball Guest

    0
     
    Tried running the update using only the "base" rpm's with no optional stuff and get the following:

    Checking for the group 'psaserv'...
    Trying to add supplementary group 'psaserv' for user 'apache'... already there
    Checking for the group 'psaserv'...
    Trying to add supplementary group 'psaserv' for user 'psaftp'... already there
    Checking for the group 'psaserv'...
    Trying to add supplementary group 'psaserv' for user 'psaadm'... already there
    group psacln already exists
    Standard build detected. Upgrading canceled, because only
    5.0.x versions supported for upgrading from Standard to RPM
    builds.

    error: %pre(psa-7.5.1-rhel3.build75041216.14) scriptlet failed, exit status 1
    error: install: %pre scriptlet failed (2), skipping psa-7.5.1-rhel3.build75041216.14

    That seems to be the showstopper. I don't understand what the error means, "Standard build detected". I hadn't modifed anything, or even done anything on the server other than try to upgrade plesk before I started putting sites on the machine. Anyone know how to get around this error?

    I can understand things not working when parts have been modified and configurations changed, but this is nuts to have the updates not work right "out of the box". EXTREMELY frustrating.
     
  8. Cranky

    Cranky Guest

    0
     
    Sorry I misread ... do a rpm -q psa and tell me what it says.
     
  9. fuzzball

    fuzzball Guest

    0
     
    Thanks a lot for trying to help me with this. I really appreciate it.

    Here's what I get...

    [admin@srv1 admin]$ rpm -q psa
    package psa is not installed
    [admin@srv1 admin]$ rpm -q psa*
    package psa-7.1.6-rhel3.build71041118.17.i586.rpm.tar.gz is not installed
    package psa-7.5.1-rhel3.build75041216.14.i586.rpm.tar.gz is not installed
     
  10. fuzzball

    fuzzball Guest

    0
     
    Just realized I probably did that in the wrong place. Here's what I get if I run the command in the "base" directory created by untarring the original archive:

    [admin@srv1 base]$ rpm -q psa*
    package psa-7.5.1-rhel3.build75041216.14.i586.rpm is not installed
    package psa-api-cli-7.5.1-rhel3.build75041216.14.i586.rpm is not installed
    package psa-api-common-7.5.1-rhel3.build75041216.14.i586.rpm is not installed
    package psa-courier-imap-add-7.5.1-rhel3.build75041216.14.i586.rpm is not installed
    package psa-key-7.5-rhel3.build75041216.14.noarch.rpm is not installed
    package psa-locale-base-en-US-7.5.1-rhel3.build75041216.14.noarch.rpm is not installed
    package psa-logrotate-3.7-rhel3.build75041216.14.i586.rpm is not installed
    package psa-pre-keyupdate-7.5.1-rhel3.build75041216.14.i586.rpm is not installed
    package psa-proftpd-1.2.10-rhel3.build75041216.14.i586.rpm is not installed
    package psa-proftpd-xinetd-1.2.10-rhel3.build75041216.14.i586.rpm is not installed
    package psa-qmail-1.03-rhel3.build75041216.14.i586.rpm is not installed
     
  11. Cranky

    Cranky Guest

    0
     
    That's all you needed to run. Was this server ever Plesk 5?
     
  12. fuzzball

    fuzzball Guest

    0
     
    As far as I know, no. I ordered the server from Ev1 a few days ago. When I got my login stuff it was running 7.1.4. I tried the autoupdate for 7.1.6 and it wouldn't update, so I downloaded the patch off SW-Soft's site and installed it from the shell. That seemed to work ok, plesk came back up, but autoupdate would not work again when I tried to go up to 7.5. So I tried to do that one manually as well, and here I am. :)
     
  13. littlefrog

    littlefrog Regular Pleskian

    25
     
    Joined:
    Jul 30, 2008
    Messages:
    176
    Likes Received:
    0
    I got my server from EV1 on Dec 23rd and it was also running 7.1.4 - on mine i did upgrade to 7.1.6 through upgrade patches on website.

    From there I did upgrade right to 7.5.1 with no errors except having to install the perl packages.. so then did full install on all RPMS except VPN and PostgreSQL

    My server is running "Red Hat Enterprise Linux ES release 3 (Taroon)"

    Here is the patch I installed to get to 7.1.6
    http://download1.sw-soft.com/Plesk/Plesk7.1/RHEL3.0/psa-7.1.6-rhel3.build71041118.17.i586.rpm.tar.gz

    This is URL I used to upgrade to 7.5.1
    http://download1.sw-soft.com/Plesk/...-7.5.1-rhel3.build75041216.14.i586.rpm.tar.gz

    You can download right to the server without having to FTP it up by typing

    wget http://download1.sw-soft.com/Plesk/...-7.5.1-rhel3.build75041216.14.i586.rpm.tar.gz

    Hope that info helped...
     
  14. fuzzball

    fuzzball Guest

    0
     
    I appreciate the help, but unfortunately that file doesn't help me. That's the same archive I have on my server now that I'm trying to use to upgrade.
     
Loading...