Re: MacOS Server 5 problem after upgrade

> 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

Re: MacOS Server 5 problem after upgrade

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

Re: MacOS Server 5 problem after upgrade

> 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 >> -

Re: MacOS Server 5 problem after upgrade

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

MacOS Server 5 problem after upgrade

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

Problem with upgrade command in mysql.

Hi, I have a script which updates a mysql table. When I run this script the update in not happening. But if I stop mysql and start in safe mode as follows mysqld_safe --skip-grant-tables --user=root then the update script is running properly. Why it is not happening in the non safe mode.

Problem with upgrade

I upgraded a server from 4.0 to 4.1 and then to 5.0 but I've been running into a problem. When I was running 4.0 the passwords with the password('password') command where being created like this: 2a287c002f9773dc now after I upgraded to 4.1 when I add a new user the passwords end up being like

Re: Problem with upgrade

On 11/22/06, Tom Ray [Lists] [EMAIL PROTECTED] wrote: I upgraded a server from 4.0 to 4.1 and then to 5.0 but I've been running into a problem. When I was running 4.0 the passwords with the password('password') command where being created like this: 2a287c002f9773dc now after I upgraded to 4.1

MySQL 5 problem after upgrade

Hello, I've posted this on Gentoo forums, but I'll try here too. :) I've made upgrade of MySQL to latest 5.0.x version. Now, when I access my site MySQL CPU usage is about 100%, and site is unaccessible. :( I've checked SHOW PROCESSLIST and this query take lng time to execute: SELECT

Re: MySQL 5 problem after upgrade

Hello again, SELECT shout_avatar, shout_own, timestamp, tekst, imie, pseudo, wiek, City, Country, plec, wlosy_kol, gra_gwiazdy.id, gra_gm.gid AS gm FROM gra_shoutbox INNER JOIN (gra_gwiazdy) ON (gra_gwiazdy.id = gra_shoutbox.gid) INNER JOIN (swiat_miasta) ON (swiat_miasta.CityId =

RE: MySQL 5 problem after upgrade

problem after upgrade Hello again, SELECT shout_avatar, shout_own, timestamp, tekst, imie, pseudo, wiek, City, Country, plec, wlosy_kol, gra_gwiazdy.id, gra_gm.gid AS gm FROM gra_shoutbox INNER JOIN (gra_gwiazdy) ON (gra_gwiazdy.id = gra_shoutbox.gid) INNER JOIN (swiat_miasta

Re: My.cnf problem when upgrade from 4.01 to 4.02

Sent: Saturday, July 13, 2002 7:23 AM Subject: Re: My.cnf problem when upgrade from 4.01 to 4.02 Hello, I've experienced what seems to be the same problem on Redhat 7.2. I eventually realized that in addition to the regular 4.0.2 server RPM, I had to also install the MySql-Max 4.0.2 server RPM

Re: My.cnf problem when upgrade from 4.01 to 4.02

is that Max supports also BDB tables. Regards, Heikki - Original Message - From: Michael Ivanyo [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Saturday, July 13, 2002 7:23 AM Subject: Re: My.cnf problem when upgrade from 4.01 to 4.02 Hello, I've

Re: My.cnf problem when upgrade from 4.01 to 4.02

PROTECTED] To: Heikki Tuuri [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, July 14, 2002 1:26 AM Subject: Re: My.cnf problem when upgrade from 4.01 to 4.02 Heikki, I actually upgraded from Max-3.23.51 to the 4.0.2 server. The only way I could get it to start was to comment out all

My.cnf problem when upgrade from 4.01 to 4.02

Hi, I'm a new user of mysql, I was upgrade from mysql 4.01 to 4.02 in mandrake 8.2. The following options in current running my.cnf suddently not work: innodb_data_file_path = ibdata1:100M innodb_data_home_dir= /data/mysql/ innodb_log_group_home_dir =

Re: My.cnf problem when upgrade from 4.01 to 4.02

Hello, I've experienced what seems to be the same problem on Redhat 7.2. I eventually realized that in addition to the regular 4.0.2 server RPM, I had to also install the MySql-Max 4.0.2 server RPM. After that, everything worked fine. I was under the impression that there would only be one