[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Installing mysqldump

On 8/13/2013 6:33 PM, Bob Proulx wrote:

Ethan Rosenberg, PhD wrote:

Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.


Those two are problems that need to be fixed.


After this operation, 0 B of additional disk space will be used.
Setting up mysql-server-5.5 (5.5.31+dfsg-0+wheezy1) ...



[?1049h[?25l(B


And people wonder why I don't like the happy colors in the interface! :-)
Let me clean that up a little bit for the archive.


Package configuration
Configuring mysql-server-5.5
While not mandatory, it is highly recommended that you set a password for the MySQL administrative "root" user.
If this field is left blank, the password will not be changed.
New password for the MySQL "root" user:
<Ok>
[....] Stopping MySQL database server: ok
[....] Starting MySQL database server: mysqld . . . . . . . . . . . . .y .FAIL
failed!
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing mysql-server-5.5 (--configure):
  subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mysql-server:
  mysql-server depends on mysql-server-5.5; however:
   Package mysql-server-5.5 is not configured yet.


Failure reported.  The package is not configured yet.  It is not ready
for use.  It is broken.  It won't work right until it is fixed.
Something went wrong.  It reported the error.  These errors cannot be
ignored and just hoping for the best sometime later.


dpkg: error processing mysql-server (--configure):
  dependency problems - leaving unconfigured
Errors were encountered while processing:
  mysql-server-5.5
  mysql-server


As to what the problem is, I do not know.  I have personally often had
problems with mysql upgrades.  But I always had a full database
backup.  Therefore it when things have not worked it was always very
easy to purge all of the packages and then re-install them and then
restore from backup.  But if you don't have a backup then purging the
data would be a very bad thing.

Does anyone else on the list have any suggestions at this point?


Bob,
The best thing to do would be for Ethan to look at the MySQL log to see what the failure was. He was asked to do this before but never responded with the messages in his log.
A clean install may or may not fix the problem - it all depends. For instance, if he changed some of the server settings so they are no longer compatible with the Debian defaults, then the server won't start (unless ALL MySQL data is deleted). 

The MySQL log will show the problem.
For the record, I've had problems with MySQL upgrades in the past - but all were caused by parameters I changed. The MySQL log always showed the problem, and resetting the defaults from the upgrade to the values I use fixed the problems. 

===================

Dear List -

I am sorry - the mysql log did not have any entries.

I remember changing the local host definition to 127.0.0.1 in my.cnf
I am going to erase my.cnf and see what happens. I have backed up the data files. 

I'll keep you posted.

Ethan
Reply to: