[Fail] on start/stop but working fine. No init controls.

Bug #1199395 reported by Skyler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Invalid
Undecided
Unassigned

Bug Description

ISSUE:
---------

 Percona on wheezy reports [FAIL] on init start ... but its still running. Reports [ OK ] to stop ... but its still running. Unable to stop/restart. Reload reports [info] MySQL (Percona Server) is stopped.. ... but its not, its still running.

STEPS PERFORMED:
----------------------------

Fresh installation of Debian Wheezy
Fresh installation of Percona from APT as per instructions on website
Once percona finalizes install, it is running
/etc/int.d/mysql stop
It stops fine.
Create a my.cnf from tools.percona.com
[copy paste] into /etc/mysql/my.cnf
rm /var/lib/mysql/ib_logfile* (due to logfile size increase)
/etc/init.d/mysql start

PROBLEM:
---------------

root@debian-wheezy:~# /etc/init.d/mysql start
[FAIL] Starting MySQL (Percona Server) database server: mysqld . . . . . . . . . . . . . . failed!

root@debian-wheezy:/etc/mysql# ps aux |grep mysql
root 18528 0.0 0.0 4176 712 pts/0 S 06:56 0:00 /bin/sh /usr/bin/mysqld_safe
mysql 19046 0.1 7.5 1410380 156384 pts/0 Sl 06:56 0:04 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql/ --plugin-dir=/usr/lib/mysql/plugin --user=mysql --log-error=/var/log/mysql/mysql.err --open-files-limit=65535 --pid-file=/var/run/mysqld/mysql.pid --socket=/var/run/mysqld/mysql.sock --port=3306
root 20106 0.0 0.0 7828 872 pts/0 S+ 07:37 0:00 grep mysql

root@debian-wheezy:/etc/mysql# mysql -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.5.32-31.0-log Percona Server (GPL), Release 31.0

Copyright (c) 2009-2013 Percona Ireland Ltd.
Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql>

LOGS:
---------

 No errors at all. Only shows that its running.

root@debian-wheezy:~# tail -f /var/log/mysql/mysql.err
130709 7:46:29 InnoDB: Initializing buffer pool, size = 1.0G
130709 7:46:29 InnoDB: Completed initialization of buffer pool
130709 7:46:29 InnoDB: highest supported file format is Barracuda.
130709 7:46:29 InnoDB: Waiting for the background threads to start
130709 7:46:30 Percona XtraDB (http://www.percona.com) 5.5.32-rel31.0 started; log sequence number 1602572
130709 7:46:31 [Warning] 'user' entry 'root@debian-wheezy' ignored in --skip-name-resolve mode.
130709 7:46:31 [Warning] 'proxies_priv' entry '@ root@debian-wheezy' ignored in --skip-name-resolve mode.
130709 7:46:31 [Note] Event Scheduler: Loaded 0 events
130709 7:46:31 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.32-31.0-log' socket: '/var/run/mysqld/mysql.sock' port: 3306 Percona Server (GPL), Release 31.0

 But

root@debian-wheezy:~# /etc/init.d/mysql status
[info] MySQL (Percona Server) is stopped..

Revision history for this message
Skyler (skchopperguy) wrote :

NOTE:
---------

 I reversed the steps to try defaults (delete ib_logfile*, mv my.cnf /tmp) and all init controls return to normal for debian.cnf

Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

Please, upload my.cnf file content.

Revision history for this message
Skyler (skchopperguy) wrote :

Please delete my email address from above. I can't seem to edit the comment. thanks

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

We cannot edit comments neither, but we can remove them, thus removed. Please re-submit with edited my.cnf. Thanks!

Revision history for this message
Skyler (skchopperguy) wrote :

# Generated by Percona Configuration Wizard (http://tools.percona.com/) version REL5-20120208
# Configuration generated 2013-07-09 11:20:04

[mysql]

# CLIENT #
port = 3306
socket = /var/run/mysqld/mysql.sock

[mysqld]

# GENERAL #
user = mysql
port = 3306
default_storage_engine = InnoDB
socket = /var/run/mysqld/mysql.sock
pid_file = /var/run/mysqld/mysql.pid

# MyISAM #
key_buffer_size = 32M
myisam_recover = FORCE,BACKUP

# SAFETY #
max_allowed_packet = 16M
max_connect_errors = 1000000
skip_name_resolve
sql_mode = STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_ZERO,NO_ENGINE_SUBSTITUTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,ONLY_FULL_GROUP_BY
sysdate_is_now = 1
innodb = FORCE
innodb_strict_mode = 1

# DATA STORAGE #
datadir = /var/lib/mysql/

# BINARY LOGGING #
log_bin = /var/lib/mysql/log-bin
expire_logs_days = 14
sync_binlog = 1

# CACHES AND LIMITS #
tmp_table_size = 32M
max_heap_table_size = 32M
query_cache_type = 0
query_cache_size = 0
max_connections = 500
thread_cache_size = 50
open_files_limit = 65535
table_definition_cache = 4096
table_open_cache = 32

# INNODB #
innodb_flush_method = O_DIRECT
innodb_log_files_in_group = 2
innodb_log_file_size = 128M
innodb_flush_log_at_trx_commit = 1
innodb_file_per_table = 1
innodb_buffer_pool_size = 1G

# LOGGING #
log_error = /var/log/mysql/mysql.err
log_queries_not_using_indexes = 1
slow_query_log = 1
slow_query_log_file = /var/log/mysql/mysql.slow

Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

Probably the problem is that in /etc/mysql/debian.cnf we have:

socket = /var/run/mysqld/mysqld.sock

(and this file is used in /etc/init.d/mysql script in the mysqladmin command that pings server to check its status, and is also used by PS for this platform as a socket to listen to by default), while in your /etc/mysql/my.cnf we see:

socket = /var/run/mysqld/mysql.sock

Please, check if change socket in my.cnf generated solves the problem. If it does, I'd say this is a bug in tools.percona.com (if at all), but not a server bug.

Changed in percona-server:
status: New → Incomplete
Revision history for this message
Skyler (skchopperguy) wrote :

Hi,

 Yes you are right. It was my mistake when changing the generated config socket. The Config wizard used

socket = /var/lib/mysql/data/mysql.sock

 I changed it to match the socket listed in debian.cnf BUT obviously I misread and did not add the 'd'. Sorry to throw a flag. I appreciate the quick response though!

 Issue is resolved.

 Regards,
Skyler

Changed in percona-server:
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Changed in percona-server:
status: Incomplete → Invalid
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2985

Revision history for this message
Kaisaab (kisan93) wrote :

More than just a website, Motors Stuff is a comprehensive and active centre for everything auto-related. https://motorsstuff.com/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.