Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #172625 > unrolled thread

mysql broken after jessie upgrade

Started byTony van der Hoff <tony@vanderhoff.org>
First post2016-09-22 12:50 +0200
Last post2016-09-23 06:10 +0200
Articles 10 — 5 participants

Back to article view | Back to linux.debian.user

Contents

  mysql broken after jessie upgrade Tony van der Hoff <tony@vanderhoff.org> - 2016-09-22 12:50 +0200
    Re: mysql broken after jessie upgrade <tomas@tuxteam.de> - 2016-09-22 13:00 +0200
      Re: mysql broken after jessie upgrade Tony van der Hoff <tony@vanderhoff.org> - 2016-09-22 13:10 +0200
        Re: mysql broken after jessie upgrade <tomas@tuxteam.de> - 2016-09-22 14:10 +0200
          SOLVED Re: mysql broken after jessie upgrade Tony van der Hoff <tony@vanderhoff.org> - 2016-09-22 16:10 +0200
            Re: SOLVED Re: mysql broken after jessie upgrade <tomas@tuxteam.de> - 2016-09-22 16:40 +0200
            Re: SOLVED Re: mysql broken after jessie upgrade Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-22 17:10 +0200
              Re: SOLVED Re: mysql broken after jessie upgrade Tony van der Hoff <tony@vanderhoff.org> - 2016-09-22 19:50 +0200
                Re: SOLVED Re: mysql broken after jessie upgrade Liam O'Toole <liam.p.otoole@gmail.com> - 2016-09-22 21:20 +0200
    Re: mysql broken after jessie upgrade Cindy-Sue Causey <butterflybytes@gmail.com> - 2016-09-23 06:10 +0200

#172625 — mysql broken after jessie upgrade

FromTony van der Hoff <tony@vanderhoff.org>
Date2016-09-22 12:50 +0200
Subjectmysql broken after jessie upgrade
Message-ID<sk9JM-5c6-19@gated-at.bofh.it>
Hi,

Running Jessie here. Performed apt-get upgrade yesterday, which included
a new version of mysql.

I now cannot connect to mysql:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)

Any suggestions on how to fix, please?

-- 
Tony van der Hoff  | mailto:tony@vanderhoff.org
Ariège, France     |

[toc] | [next] | [standalone]

#172626

From<tomas@tuxteam.de>
Date2016-09-22 13:00 +0200
Message-ID<sk9Tr-5fL-7@gated-at.bofh.it>
In reply to#172625
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Sep 22, 2016 at 12:43:18PM +0200, Tony van der Hoff wrote:
> Hi,
> 
> Running Jessie here. Performed apt-get upgrade yesterday, which included
> a new version of mysql.
> 
> I now cannot connect to mysql:
> ERROR 2002 (HY000): Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2)
> 
> Any suggestions on how to fix, please?

Is the mysql daemon running? Try "service mysqld status" or however
that's named in the brave new systemd world (I'm still in the messy
old sysv world, mind you ;-)

- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlfjuPEACgkQBcgs9XrR2kaQBgCfaFNu2FMDGtPoplcujHEq0kaZ
8d4AnRqPpIvIj7OFP33/LqdyMoLD3WOx
=U9gc
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#172628

FromTony van der Hoff <tony@vanderhoff.org>
Date2016-09-22 13:10 +0200
Message-ID<ska38-5ym-27@gated-at.bofh.it>
In reply to#172626
On 22/09/16 12:56, tomas@tuxteam.de wrote:
> On Thu, Sep 22, 2016 at 12:43:18PM +0200, Tony van der Hoff wrote:
>> Hi,
> 
>> Running Jessie here. Performed apt-get upgrade yesterday, which included
>> a new version of mysql.
> 
>> I now cannot connect to mysql:
>> ERROR 2002 (HY000): Can't connect to local MySQL server through socket
>> '/var/run/mysqld/mysqld.sock' (2)
> 
>> Any suggestions on how to fix, please?
> 
> Is the mysql daemon running? Try "service mysqld status" or however
> that's named in the brave new systemd world (I'm still in the messy
> old sysv world, mind you ;-)
> 
Thanks tomas;

No, it's not:
13:03:23 tony@tony-fr:~$ sudo service mysqld status
Failed to dump process list, ignoring: Unit mysqld.service not found.
● mysqld.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

But:
13:03:36 tony@tony-fr:~$ sudo service mysql status
● mysql.service - LSB: Start and stop the mysql database server daemon
   Loaded: loaded (/etc/init.d/mysql; generated; vendor preset: enabled)
   Active: active (exited) since Thu 2016-09-22 12:32:43 CEST; 32min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 21125 ExecStart=/etc/init.d/mysql start (code=exited,
status=0/SUCCESS)

-- 
Tony van der Hoff  | mailto:tony@vanderhoff.org
Ariège, France     |

[toc] | [prev] | [next] | [standalone]

#172632

From<tomas@tuxteam.de>
Date2016-09-22 14:10 +0200
Message-ID<skaZb-68M-15@gated-at.bofh.it>
In reply to#172628
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Sep 22, 2016 at 01:07:49PM +0200, Tony van der Hoff wrote:
> On 22/09/16 12:56, tomas@tuxteam.de wrote:
> > On Thu, Sep 22, 2016 at 12:43:18PM +0200, Tony van der Hoff wrote:
> >> Hi,
> > 
> >> Running Jessie here. Performed apt-get upgrade yesterday, which included
> >> a new version of mysql.
> > 
> >> I now cannot connect to mysql:
> >> ERROR 2002 (HY000): Can't connect to local MySQL server through socket
> >> '/var/run/mysqld/mysqld.sock' (2)
> > 
> >> Any suggestions on how to fix, please?
> > 
> > Is the mysql daemon running? Try "service mysqld status" or however
> > that's named in the brave new systemd world (I'm still in the messy
> > old sysv world, mind you ;-)
> > 
> Thanks tomas;
> 
> No, it's not:
> 13:03:23 tony@tony-fr:~$ sudo service mysqld status
> Failed to dump process list, ignoring: Unit mysqld.service not found.
> ● mysqld.service
>    Loaded: not-found (Reason: No such file or directory)
>    Active: inactive (dead)
> 
> But:
> 13:03:36 tony@tony-fr:~$ sudo service mysql status
> ● mysql.service - LSB: Start and stop the mysql database server daemon
>    Loaded: loaded (/etc/init.d/mysql; generated; vendor preset: enabled)
>    Active: active (exited) since Thu 2016-09-22 12:32:43 CEST; 32min ago
>      Docs: man:systemd-sysv-generator(8)
>   Process: 21125 ExecStart=/etc/init.d/mysql start (code=exited,
> status=0/SUCCESS)

Actually that looks good -- that just means that the service is called
'mysql', not 'mysqld'. If I read this systemd runes correctly that means
that systemd is just calling the 'classical' init script for mysql and
that all seems OK.

You might check whether there's a process called (more or less) mysql
around:

  ps wwwaux | grep mysql

you might have a look into wherever mysql places its log files (unless
they've been kidnapped by systemd, in which case I'd have to defer to
smarter people; but I don't believe that). Look somewhere in /var/log/mysql.

Then you might try to invoke (gasp!) "/etc/init.d/mysql start" (as root)
yourself and see whether it spews any error messages giving any clues.

Then you could issue an "netstat -antp" as root, to see whether the
mysql daemon is listening on some other (non-default) port.

> Ariège, France     |

Wonderful region, btw. I've got warm and sweet memories from summer
2015...

regards
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlfjx58ACgkQBcgs9XrR2kbL2ACbB0ny3LrO79nGkS7lGuNKxjiW
ULoAn3Hi4FQUI5p5k6xLwHWK2cXeMkd4
=Knj1
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#172642 — SOLVED Re: mysql broken after jessie upgrade

FromTony van der Hoff <tony@vanderhoff.org>
Date2016-09-22 16:10 +0200
SubjectSOLVED Re: mysql broken after jessie upgrade
Message-ID<skcRj-7nx-7@gated-at.bofh.it>
In reply to#172632
On 22/09/16 13:59, tomas@tuxteam.de wrote:
> On Thu, Sep 22, 2016 at 01:07:49PM +0200, Tony van der Hoff wrote:
>> On 22/09/16 12:56, tomas@tuxteam.de wrote:
>>> On Thu, Sep 22, 2016 at 12:43:18PM +0200, Tony van der Hoff wrote:
>>>> Hi,
>>>
>>>> Running Jessie here. Performed apt-get upgrade yesterday, which included
>>>> a new version of mysql.
>>>
>>>> I now cannot connect to mysql:
>>>> ERROR 2002 (HY000): Can't connect to local MySQL server through socket
>>>> '/var/run/mysqld/mysqld.sock' (2)
>>>
>>>> Any suggestions on how to fix, please?
>>>
>>> Is the mysql daemon running? Try "service mysqld status" or however
>>> that's named in the brave new systemd world (I'm still in the messy
>>> old sysv world, mind you ;-)
>>>
>> Thanks tomas;
> 
> You might check whether there's a process called (more or less) mysql
> around:
> 
>   ps wwwaux | grep mysql
> 
Ther was...

> you might have a look into wherever mysql places its log files (unless
> they've been kidnapped by systemd, in which case I'd have to defer to
> smarter people; but I don't believe that). Look somewhere in /var/log/mysql.
> 
No all the log files were there, but empty...

> Then you might try to invoke (gasp!) "/etc/init.d/mysql start" (as root)
> yourself and see whether it spews any error messages giving any clues.
> 
Nothing...

> Then you could issue an "netstat -antp" as root, to see whether the
> mysql daemon is listening on some other (non-default) port.
> 
No...

It turns out that the recent upgrade took mysql from 5.5 to 5.6. It
uninstalled mysql-server-5.5, but failed to install mysql-server-5.6,
due to an unmet dependency on mysql-server-core-5.6.

I manually installed mysql-server-core-5.6, after which mysql-server-5.6
installed fine.

Mysql now starts correctly.

Thanks for your help,

tony

>> Ariège, France     |
> 
> Wonderful region, btw. I've got warm and sweet memories from summer
> 2015...

Very warm and sunny right now. The trees are just starting to change colour.

-- 
Tony van der Hoff  | mailto:tony@vanderhoff.org
Ariège, France     |

[toc] | [prev] | [next] | [standalone]

#172645 — Re: SOLVED Re: mysql broken after jessie upgrade

From<tomas@tuxteam.de>
Date2016-09-22 16:40 +0200
SubjectRe: SOLVED Re: mysql broken after jessie upgrade
Message-ID<skdkl-7zs-5@gated-at.bofh.it>
In reply to#172642
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Sep 22, 2016 at 04:02:37PM +0200, Tony van der Hoff wrote:

[...]

> It turns out that the recent upgrade took mysql from 5.5 to 5.6. It
> uninstalled mysql-server-5.5, but failed to install mysql-server-5.6,
> due to an unmet dependency on mysql-server-core-5.6.

Ouch.

> Mysql now starts correctly.

Glad you solved it.

> Thanks for your help,

Wasn't much, but glad if it helped a bit :-)

> tony
> 
> >> Ariège, France     |
> > 
> > Wonderful region, btw. I've got warm and sweet memories from summer
> > 2015...
> 
> Very warm and sunny right now. The trees are just starting to change colour.

Berlin here. Usually grey, but we've been treated to an uncommonly warm
and sunny autumn this year. I won't complain :-)

Regards
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlfj65UACgkQBcgs9XrR2ka39gCePY/TzPQx5eJFIUnJNwBQsXfB
6J4AnRSNEiQ03RiHHJBkrCB4JNS7OXTl
=iRYf
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#172647 — Re: SOLVED Re: mysql broken after jessie upgrade

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2016-09-22 17:10 +0200
SubjectRe: SOLVED Re: mysql broken after jessie upgrade
Message-ID<skdNo-7ZV-35@gated-at.bofh.it>
In reply to#172642
On Thu, Sep 22, 2016 at 04:02:37PM +0200, Tony van der Hoff wrote:
> >>>> Running Jessie here. Performed apt-get upgrade yesterday, which included
> >>>> a new version of mysql.

> It turns out that the recent upgrade took mysql from 5.5 to 5.6. It
> uninstalled mysql-server-5.5, but failed to install mysql-server-5.6,
> due to an unmet dependency on mysql-server-core-5.6.

Sounds like you're getting mysql-server from jessie-backports instead
of jessie.  On a pure jessie system, it is still 5.5.

[toc] | [prev] | [next] | [standalone]

#172677 — Re: SOLVED Re: mysql broken after jessie upgrade

FromTony van der Hoff <tony@vanderhoff.org>
Date2016-09-22 19:50 +0200
SubjectRe: SOLVED Re: mysql broken after jessie upgrade
Message-ID<skgig-VW-109@gated-at.bofh.it>
In reply to#172647
On 22/09/16 16:59, Greg Wooledge wrote:
> On Thu, Sep 22, 2016 at 04:02:37PM +0200, Tony van der Hoff wrote:
>>>>>> Running Jessie here. Performed apt-get upgrade yesterday, which included
>>>>>> a new version of mysql.
> 
>> It turns out that the recent upgrade took mysql from 5.5 to 5.6. It
>> uninstalled mysql-server-5.5, but failed to install mysql-server-5.6,
>> due to an unmet dependency on mysql-server-core-5.6.
> 
> Sounds like you're getting mysql-server from jessie-backports instead
> of jessie.  On a pure jessie system, it is still 5.5.
> 

Yes, I am.
-- 
Tony van der Hoff        | mailto:tony@vanderhoff.org
Buckinghamshire, England |

[toc] | [prev] | [next] | [standalone]

#172687 — Re: SOLVED Re: mysql broken after jessie upgrade

FromLiam O'Toole <liam.p.otoole@gmail.com>
Date2016-09-22 21:20 +0200
SubjectRe: SOLVED Re: mysql broken after jessie upgrade
Message-ID<skhHk-1Xw-11@gated-at.bofh.it>
In reply to#172677
On 2016-09-22, Tony van der Hoff <tony@vanderhoff.org> wrote:
> On 22/09/16 16:59, Greg Wooledge wrote:
>> On Thu, Sep 22, 2016 at 04:02:37PM +0200, Tony van der Hoff wrote:
>>>>>>> Running Jessie here. Performed apt-get upgrade yesterday, which included
>>>>>>> a new version of mysql.
>> 
>>> It turns out that the recent upgrade took mysql from 5.5 to 5.6. It
>>> uninstalled mysql-server-5.5, but failed to install mysql-server-5.6,
>>> due to an unmet dependency on mysql-server-core-5.6.
>> 
>> Sounds like you're getting mysql-server from jessie-backports instead
>> of jessie.  On a pure jessie system, it is still 5.5.
>> 
>
> Yes, I am.

If you install the mysql-server metapackage from backports then the
server upgrade will be handled correctly in future.

-- 

Liam

[toc] | [prev] | [next] | [standalone]

#172697

FromCindy-Sue Causey <butterflybytes@gmail.com>
Date2016-09-23 06:10 +0200
Message-ID<skpYd-7dc-3@gated-at.bofh.it>
In reply to#172625
On 9/22/16, Tony van der Hoff <tony@vanderhoff.org> wrote:
>
> Running Jessie here. Performed apt-get upgrade yesterday, which included
> a new version of mysql.
>
> I now cannot connect to mysql:
> ERROR 2002 (HY000): Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2)
>
> Any suggestions on how to fix, please?


Well, I've got a slightly weird one that yours brings to mind. I've
wanted to write it up for Debian-User but haven't had the brain power.
Short version is that, for no particular reason, I decided to see what
"apt-get upgrade" would try to do the other day. I don't normally go
that route. Also for no particular reason, I go the "apt-get install"
route instead.

So... How did your upgrade go? Was anything held back?

I'm asking because if I specifically "apt-get install libreoffice"
right now, it says, "Sure, let's do it." If I  try a generic "apt-get
upgrade" instead, all kinds of Libreoffice packages get held back,
including libreoffice itself, while unrelated packages are queued up
to be successfully upgraded.

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web