Re: MySQL Platform Migration

[Matthias Schmidt]

Hello,

I’m quite new to this list and I’m surprised about the vocabulary used on this 
list by certain people, who besides that do not add any productive idea to the 
problem asked by the OT.

Besides that I upgraded just from MacOS10.6 -> 10.11 and copying just the data 
folder did the job.
As I was using also a newer version of mysql I ran mysql_upgrade -u root -p 
after starting mysql and all is now running fine.
I had to make certain adjustements to the config file thou.
imho a change from Darwin to Linux (which one) isn’t that much different.

cheers
Matthias


> Am 12.09.2016 um 22:06 schrieb Ryan Coleman :
> 
> Dear sir,
> 
> You do not realize that there aren’t always sys admins on these lists. Your 
> proven track record of asshole first, kid gloves later drives people away.
> 
> Your fight to change mailing lists is one which only you seem to share.
> 
> Goodnight.
> 
>> On Sep 12, 2016, at 7:27 AM, Reindl Harald  wrote:
>> 
>> first: get rid of "reply-all"o n mailing-lists, you break others 
>> "reply-list" button with the second copy which arrives usually faster the 
>> the list one
>> 
>> Am 12.09.2016 um 13:35 schrieb Harrie Robins:
>>> It is bad practice to do so in my eyes (and yes that is an *opinion*).
>>> When you advice people, instruct them to take the proven route, as
>>> described in the mysql documentation
>> 
>> proven route?
>> 
>> proven is that you can *test* how it works out by
>> * hot rsync
>> * shut down the old server
>> * cold rsync
>> * start the old server
>> which is scriptable to minimize downtime
>> 
>> after that (while the old machine is still in production) you figure out 
>> what needs to get adopted in the configuration
>> 
>> then you test your software, prove that everything works fine
>> 
>> in the meantime you can test as often as you want the hot-cold-rsync to 
>> refresh the mysql databases from production - and *now you have proven* that 
>> everything works
>> 
>> since you have proven that successful you can write a final script which 
>> does the sync (over ssh with certificates) a last time, restart the old 
>> servers network servioce with a prepared network address and on the new 
>> server take over the old ip adress
>> 
>> and trust me: that way you minimize downtime, have a proven *by yourself* 
>> way to go which works, is tested and when correct done nobody notices that 
>> the machine and undrlying operating system changed
>> 
>> after doing that dozens of times for thousands of mysql databases i know 
>> what i am doing and call bad practice ways which take depending on database 
>> sizes hours and beware god something goes wrong with your dump
>> 
>>> Second, mastering mysqldump should be golden standard for any DBA.
>>> Telling someone that asks for guidance to simply copy around some files
>>> is bad practice as you do not know the level of expertise involved.
>> 
>> the golden standard for any sysadmin is to know where his datafiles and 
>> configuration files are stored and how they work together - independent of 
>> the software type
>> 
>>> Regards,
>>> Harrie
>>> 
>>> On 12 September 2016 at 11:03, Reindl Harald >> > wrote:
>>> 
>>> 
>>> 
>>>   Am 12.09.2016 um 10:48 schrieb Harrie Robins:
>>> 
>>>   Ok let's drop this. Simply copying files to migrate a server is
>>>   not the
>>>   approach to take (in my humble opinion)
>>> 
>>> 
>>>   And why?
>>> 
>>>   When you start with "Get the same release-version of mysql running
>>>   on the target platform" and dump/load what's the point in playing
>>>   around with dump-files when you hava binary datafiles which can be
>>>   used on the destination
>>> 
>>>   and no - i am not talking about theory
>>> 
>>>   i migrated a hosting-infrastructure with dozens of servers from OSX
>>>   PPC to OSX Intel and later to Linux x86_64 with just rsync the
>>>   mysql-datadir
>> 
>> --
>> MySQL General Mailing List
>> For list archives: http://lists.mysql.com/mysql
>> To unsubscribe:http://lists.mysql.com/mysql
>> 
> 
> 
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/mysql
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: MacOS Server 5 problem after upgrade

[Matthias Schmidt]

> Am 04.09.2016 um 23:35 schrieb Reindl Harald :
> 
> 
> 
> Am 04.09.2016 um 16:17 schrieb Matthias Schmidt:
>>> Am 04.09.2016 um 16:29 schrieb Reindl Harald :
>>> 
>>> Am 04.09.2016 um 08:40 schrieb Matthias Schmidt:
>>>> 2016-09-04 15:25:19 85518 [ERROR] /usr/local/mysql/bin/mysqld: Can't 
>>>> create/write to file '/usr/local/mysql/data/mysqld.local.pid' (Errcode: 
>>>> 102 - Operation not supported on socket)
>>>> 2016-09-04 15:25:19 85518 [ERROR] Can't start server: can't create PID 
>>>> file: Operation not supported on socket
>>>> 
>>>> the socket is created but then something goes wrong
>>> 
>>> that sounds like socket and pid are configured for the same location
>>> what about "rm -f /usr/local/mysql/data/mysqld.local.pid" and show us your 
>>> config
>>> 
>> 
>> thanks, that did the trick and made it run, but now I just discovered that 
>> my databases are all gone …
>> Of course I have backups, but really no experience how to get the stuff back 
>> :(
> 
> just configure “datadir” to the correct location and get familar with mysql 
> basics and your operating system

there have been 2 problems:
- the last mysql update didn’t do the update and the data folder didn’t contain 
the databases :-0
- the sock file was created in the temp folder instead of the var folder, after 
setting the sock file to the var/mysql folder all works fine

besides the control panel, it “thinks" the server is not running, although it 
is, so I guess I can delete it, as it is also not anymore distributed with the 
current versions for OS10.11


so, thanks especially to Harald, much appreciated :-)
Matthias



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: MacOS Server 5 problem after upgrade

[Matthias Schmidt]

> Am 04.09.2016 um 16:29 schrieb Reindl Harald :
> 
> 
> 
> Am 04.09.2016 um 08:40 schrieb Matthias Schmidt:
>> 2016-09-04 15:25:19 85518 [ERROR] /usr/local/mysql/bin/mysqld: Can't 
>> create/write to file '/usr/local/mysql/data/mysqld.local.pid' (Errcode: 102 
>> - Operation not supported on socket)
>> 2016-09-04 15:25:19 85518 [ERROR] Can't start server: can't create PID file: 
>> Operation not supported on socket
>> 
>> the socket is created but then something goes wrong
> 
> that sounds like socket and pid are configured for the same location
> what about "rm -f /usr/local/mysql/data/mysqld.local.pid" and show us your 
> config
> 
> 

thanks, that did the trick and made it run, but now I just discovered that my 
databases are all gone …
Of course I have backups, but really no experience how to get the stuff back :(
thanks
Matthias



signature.asc
Description: Message signed with OpenPGP using GPGMail

MacOS Server 5 problem after upgrade

[Matthias Schmidt]

Hello,
sorry if this question has been asked already - at least google din’t find a 
sufficient answer :(

I have been upgrading a MacOS 10.6 server to serverv5, which is MacOS 10.11

I was running before: mysql-5.5.40-osx10.6-x86_64

upgrade has been always a no-brainer: download the dmg and run the installer

but now after upgrading to mysql-5.6.31-osx10.11-x86_64
mysql is crashing:
09-03 18:23:07 51218 [Note] IPv6 is available.
2016-09-03 18:23:07 51218 [Note]   - '::' resolves to '::';
2016-09-03 18:23:07 51218 [Note] Server socket created on IP: '::'.
2016-09-03 18:23:07 51218 [ERROR] /usr/local/mysql/bin/mysqld: Can't 
create/write to file '/usr/local/mysql/data/mysqld.local.pid' (Errcode: 102 - 
Operation not supported on socket)
2016-09-03 18:23:07 51218 [ERROR] Can't start server: can't create PID file: 
Operation not supported on socket

I set the bind to the local ip, but it doesn’t change anything

2016-09-03 19:16:08 2125 [Note]   - '192.168.2.10' resolves to '192.168.2.10';
2016-09-03 19:16:08 2125 [Note] Server socket created on IP: '192.168.2.10'.
2016-09-03 19:16:08 2125 [ERROR] /usr/local/mysql/bin/mysqld: Can't 
create/write to file '/usr/local/mysql/data/mysqld.local.pid' (Errcode: 102 - 
Operation not supported on socket)
2016-09-03 19:16:08 2125 [ERROR] Can’t start server: can't create PID file: 
Operation not supported on socket

same happens with local ip:
2016-09-04 15:25:19 85518 [Note] Server hostname (bind-address): '127.0.0.1'; 
port: 3306
2016-09-04 15:25:19 85518 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
2016-09-04 15:25:19 85518 [Note] Server socket created on IP: '127.0.0.1'.
2016-09-04 15:25:19 85518 [ERROR] /usr/local/mysql/bin/mysqld: Can't 
create/write to file '/usr/local/mysql/data/mysqld.local.pid' (Errcode: 102 - 
Operation not supported on socket)
2016-09-04 15:25:19 85518 [ERROR] Can't start server: can't create PID file: 
Operation not supported on socket

the socket is created but then something goes wrong.

as I couldn’t find anything, which really would relate to the problem, I guess 
I miss something here.

thanks for any input
Matthias


signature.asc
Description: Message signed with OpenPGP using GPGMail