MySQL breaks after upgrading (Sid)

From: Mailing List (deb_milist_at_yahoo.com.sg)
Date: 09/30/04

  • Next message: James Miller: "Re: unicode input in X apps: how to?" 
    Date: Thu, 30 Sep 2004 19:23:25 +0700
To: debian mailing list <debian-user@lists.debian.org>

    After upgrading last night, I realized that MySQL server has stop.
    After checking what's going on from /var/log/syslog, I decided to
    uncomment line max_allowed_packet=16M on my.cf
    Then restart mysql server and it run well.
    Wonder if anyone experienced this.

    ---me---

    syslog:

    Sep 30 19:15:25 mslinuz mysqld_safe[27711]:
    Sep 30 19:15:26 mslinuz mysqld_safe[27779]: started
    Sep 30 19:15:26 mslinuz mysqld[27782]: /usr/sbin/mysqld: ready for
    connections.
    Sep 30 19:15:26 mslinuz mysqld[27782]: Version: '4.0.21-log' socket:
    '/var/run/mysqld/mysqld.sock' port: 3306 Source distribution
    Sep 30 19:15:32 mslinuz /etc/init.d/mysql[27827]: 4 processes alive and
    '/usr/bin/mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf ping'
    resulted in
    Sep 30 19:15:32 mslinuz /etc/init.d/mysql[27827]: /usr/bin/mysqladmin:
    unknown variable 'max_allowed_packet=16M'
    Sep 30 19:15:32 mslinuz /etc/init.d/mysql[27827]: 

    


    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: James Miller: "Re: unicode input in X apps: how to?"

    Relevant Pages