Room for Jason Salaz and Burning the Codeigniter

21:00

okay, my response of mysql --help was:

auto-rehash                       TRUE
auto-vertical-output              FALSE
character-sets-dir                (No default value)
column-type-info                  FALSE
comments                          FALSE
compress                          FALSE
debug-check                       FALSE
debug-info                        FALSE
database                          (No default value)
default-character-set             auto
delimiter                         ;
vertical                          FALSE

Jason Salaz

that's it?

there should be like, 3 screens full of a ~50 row terminal

Burning the Codeigniter

oh my bad

Jason Salaz

wait

Burning the Codeigniter

i didn't scroll up

Jason Salaz

I forgot SE collapses stuff

I think I have what I need

Burning the Codeigniter

21:02

mysql Ver 14.14 Distrib 5.5.20, for osx10.7 (i386) using readline 5.1
Copyright (c) 2000, 2011, 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.

Usage: mysql [OPTIONS] [database]
-?, --help Display this help and exit.
-I, --help Synonym for -?
--auto-rehash Enable automatic rehashing. One doesn't need to use
'rehash' to get table and field completion, but startup

Jason Salaz

`socket (No default value)`
pfft...

Burning the Codeigniter

D:

Jason Salaz

mysql is the client binary, btw. not the server binary, and with the server not running...

speaking of...

try running mysqld_safe

Burning the Codeigniter

120502 22:03:39 mysqld_safe Logging to '/usr/local/var/mysql/Wayne-Purton-Smiths-MacBook.local.err'.
120502 22:03:39 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
120502 22:03:43 mysqld_safe mysqld from pid file /usr/local/var/mysql/Wayne-Purton-Smiths-MacBook.local.pid ended

Jason Salaz

And there's nothing in /usr/local/var/mysql/Wayne-Purton-Smiths-MacBook.local.err ?

Burning the Codeigniter

21:04

full of error logs

Jason Salaz

grab a handful

tail -n 20 /usr/local/var/mysql/Wayne-Purton-Smiths-MacBook.local.err |pbcopy

then paste here

Burning the Codeigniter

120502 22:06:33 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
> 120502 22:06:33 [ERROR] Do you already have another mysqld server running on port: 3306 ?
> 120502 22:06:33 [ERROR] Aborting
>
> 120502 22:06:33  InnoDB: Starting shutdown...
> 120502 22:06:34  InnoDB: Shutdown completed; log sequence number 1595675
> 120502 22:06:34 [Note] /usr/local/Cellar/mysql/5.5.20/bin/mysqld: Shutdown complete
>
> 120502 22:06:34 mysqld_safe mysqld from pid file /usr/local/var/mysql/Wayne-Purton-Smiths-MacBook.local.pid ended

Jason Salaz

I think I've found your issue?

Burning the Codeigniter

but i don't have another mysqld running?

Jason Salaz

you have something running on 3306

trying to remember how to put the application name into netstat

well, let's at least confirm it

netstat -an |grep LISTEN |pbcopy

Burning the Codeigniter

21:10

I did netstat | grep mysql

ffffff800ded73f0 stream 0 0 ffffff8011bc3d10 0 0 0 /tmp/mysql.sock

Jason Salaz

(yes, I love pbcopy)

Burning the Codeigniter

:P

I got nothing returned

Jason Salaz

right

because you put it in the pasteboard

paste it here

I do things with pbcopy so you don't have to highlight/select it all. Just paste it right into chat.

Burning the Codeigniter

tcp4       0      0  *.587                  *.*                    LISTEN
tcp4       0      0  *.25                   *.*                    LISTEN
tcp4       0      0  *.55194                *.*                    LISTEN
tcp4       0      0  *.55191                *.*                    LISTEN
tcp4       0      0  *.55177                *.*                    LISTEN
tcp4       0      0  *.55175                *.*                    LISTEN
tcp4       0      0  *.55174                *.*                    LISTEN

Jason Salaz

tcp4 0 0 .3306 *. LISTEN

Burning the Codeigniter

21:13

ah yes

Jason Salaz

you have something listening on 3306.

if it isn't mysql, then it's blocking mysql

ps axuww |grep -i sql |pbcopy

Burning the Codeigniter

root           80454   0.0  0.2  2475256   7520 s000  T    12:35pm   0:00.05 sudo ./bin/mysqld_safe
root           80441   0.0  0.2  2475256   7520 s000  T    12:35pm   0:00.05 sudo ./bin/mysqld_safe
root           80422   0.0  0.2  2475256   7520 s000  T    12:34pm   0:00.06 sudo ./bin/mysqld_safe
_mysql         79759   0.0  1.1  2692168  47852   ??  Ss   12:24pm   0:15.41 --user=_mysql
RudeBoiiDevil   8755   0.0  0.0  2438316   1328 s000  S+   10:14pm   0:00.01 grep -i sql

Jason Salaz

well... there's your problem?

_mysql? are you running Lion Server?

Burning the Codeigniter

nope

lion os x

Jason Salaz

you have something else running mysql

that's the long and the short of it.

Burning the Codeigniter

21:15

how do i terminate it?

Jason Salaz

you could kill it the old fashioned way

let's try a few more things

which mysql |pbcopy

Burning the Codeigniter

/usr/local/bin/mysql

Jason Salaz

hmm, whereis is dumb on OSX, what a shame

Burning the Codeigniter

locate

instead of whereis

Jason Salaz

mdfind instead of locate

mdfind -name mysql |grep bin |pbcopy

Burning the Codeigniter

21:16

heh :P

/usr/local/Cellar/mysql/5.5.20/share/man/man1/mysqlbinlog.1
/usr/local/Cellar/mysql/5.5.20/mysql-test/t/mysqldump-no-binlog.test
/usr/local/Cellar/mysql/5.5.20/mysql-test/t/mysqldump-no-binlog-master.opt
/usr/local/Cellar/mysql/5.5.20/mysql-test/t/mysqlbinlog_row_trans.test
/usr/local/Cellar/mysql/5.5.20/mysql-test/t/mysqlbinlog_row_myisam.test
/usr/local/Cellar/mysql/5.5.20/mysql-test/t/mysqlbinlog_row_innodb.test
/usr/local/Cellar/mysql/5.5.20/mysql-test/t/mysqlbinlog_row_big.test
/usr/local/Cellar/mysql/5.5.20/mysql-test/t/mysqlbinlog_row.test

Jason Salaz

uhh... huh....

and OSX also doesn't have the proc fs

Old fashioned way it is.

ps axuww |grep -i sql |awk '{ print $2 }' |xargs -I{} sudo kill {}

keep checking the process list to see if it's running ( ps axuww |grep -i sql )

if it is, change kill {} to kill -9 {}

get the list clean and then try starting mysqld up from homebrew again

for all we know, that is the homebrew mysqld, and something's just causing a weird startup loop or something

Burning the Codeigniter

when i executed

it said

kill: 10095: No such process

Jason Salaz

don't worry about it

probably trying to kill the grep that already went away

Burning the Codeigniter

RudeBoiiDevil  10162   0.0  0.0  2439020    864 s000  R+   10:21pm   0:00.00 grep -i sql
RudeBoiiDevil  10150   0.0  1.1  2690484  44052   ??  S    10:20pm   0:00.14 /usr/local/Cellar/mysql/5.5.20/bin/mysqld --basedir=/usr/local/Cellar/mysql/5.5.20 --datadir=/usr/local/var/mysql --plugin-dir=/usr/local/Cellar/mysql/5.5.20/lib/plugin --log-error=/usr/local/var/mysql/Wayne-Purton-Smiths-MacBook.local.err --pid-file=/usr/local/var/mysql/Wayne-Purton-Smiths-MacBook.local.pid
RudeBoiiDevil  10105   0.0  0.0  2439016   1728   ??  S    10:20pm   0:00.02 /bin/sh /usr/local/bin/mysqld_safe

(ps axuww |grep -i sql)

Jason Salaz

did it start back up automatically? of is that you starting it back up?

Burning the Codeigniter

21:22

i didn't enter any other command

or started up anything

Jason Salaz

huh

well, that's definitely mysql from homebrew

... try connecting to it? :)

Burning the Codeigniter

aha :D

it's working now

thank you so much

you may answer my question here

and i'll accept your answer

Woops, my bad

0

Q: Starting MySQL produces "The server quit without updating PID file"

I've literally looked all over Stack Overflow, Superuser, I cannot find a solution to my problem that I'm experiencing right now, when I want to start MySQL, it produces this error: ERROR! The server quit without updating PID file (/usr/local/var/mysql/My-Username.local.pid). with the sudo ...

Jason Salaz

0

A: Starting MySQL produces "The server quit without updating PID file"

We (myself and Mr. Burning) did some diagnosis in chat, and I will detail what we did find: The root of his problem was that MySQLd was already running in some capacity. This could have been a previous version of MySQL installed from Homebrew, still running after upgrading the binaries/libraries...

glad I could get you running.

Burning the Codeigniter

cheers :)

Stack Exchange

22:33

Jason Salaz has frozen this room.

Transcript for

Room for Jason Salaz and Burning the …