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

mysqldump.sh issues

Discussion in 'Plesk for Linux - 8.x and Older' started by cwilkerson, Oct 26, 2006.

  1. cwilkerson

    cwilkerson Guest

    0
     
    I'm taking care of a server running Plesk 8 (which was originally migrated from Plesk 7.x, not sure exactly which version).

    The server was upgraded from Plesk 7.x ~September of this year when the last mysqldump of them was successful.

    Testing mysqldump manually with the same user name and password (password located in /etc/psa/.psa.shadow) works fine on the databases in question.

    The databases from mysqldump.sh are just ending up as a 337 gzipped file when complete, the file just contains this:

    -- MySQL dump 10.9
    --
    -- Host: localhost Database: snapstre_vbulletin2
    -- ------------------------------------------------------
    -- Server version 4.1.12

    /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
    /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
    /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
    /*!40101 SET NAMES utf8 */;
    /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
    /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
    /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
    /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;

    Any ideas?
     
  2. cwilkerson

    cwilkerson Guest

    0
     
    Close this thread...

    Nevermind on this question, I've never worked with plesk before and though the backup of other mysqldb's were being handled by it's cronjob. They were custom scripts located elsewhere. Problem solved, not a plesk issue.
     
Loading...