Cameron,
Did you run the recommended configuration script manually?
mysql_install_db
This is run once after install to put the "stuff" in your datadir= location
which I pointed out may be missing (and was "empty" upon your inspection).
Thanks,
Robert
Mike,
check the datadir (usually /var/lib/mysql). If it's empty, manually execute
mysql_install_db. This will place an initial db in place and mysql will start
from then on
On 02/18/2015 03:11 PM, mike wrote:
> Cameron Mann cybera.ca> writes:
>
>> Hi all,
>>
>> I've encountered a problem w
Dammit, that should've come from the other account with that
work-signature...
Have you looked at the possible errors in
http://man7.org/linux/man-pages/man3/pthread_create.3.html ?
Seems like either a resource / ulimit thing, or perhaps limited by SELinux
in some way?
On Thu, Feb 19, 2015 at 12:11 AM, mike wrote:
> Cameron Mann cybera.ca> writes:
>
> >
> > Hi all,
> >
>
Cameron Mann cybera.ca> writes:
>
> Hi all,
>
> I've encountered a problem with MySQL 5.6.23 on CentOS 7.0 and would
> greatly appreciate any advice on what to do next.
>
> Synopsis:
>
> 1. Fresh install of CentOS 7.0 using minimal install ISO
> 2. yum update -y
> 3. rpm -i http://dev.mysql.c
It worked before, when you manually had to execute the script... It worked when
the script was auto invoked. Now it's silently busted, causing problems for
people you think
that's OK.
Whatever.
Moving on
On 02/12/2015 03:45 PM, Reindl Harald wrote:
>
> Am 13.02.2015 um 00:35 schrieb Bruce F
Am 13.02.2015 um 00:35 schrieb Bruce Ferrell:
Well Mr Harald, I admit... It's not an "out of the box" behaviour put there by
Oracle/MySQL. But it IS a behaviour introduced by distribution packagers and and it's
only invoked
the first time the db is start is attempted AND there is no basic db
Well Mr Harald, I admit... It's not an "out of the box" behaviour put there by
Oracle/MySQL. But it IS a behaviour introduced by distribution packagers and
and it's only invoked
the first time the db is start is attempted AND there is no basic db in place.
mysql_install_db actually won't run w
Am 13.02.2015 um 00:03 schrieb Bruce Ferrell:
If the datadir is empty. you have to execute a different utility
mysql_install_db. This will create a correct initial database.
Jesus! I HATE systemd. The sysV init script handled this correctly.
tell me *one* reason why it is the job of the
If the datadir is empty. you have to execute a different utility
mysql_install_db. This will create a correct initial database.
Jesus! I HATE systemd. The sysV init script handled this correctly.
On 02/12/2015 02:06 PM, Cameron Mann wrote:
> Hi Robert,
>
> The value in my.cnf is datadir=/var
Hi Robert,
The value in my.cnf is datadir=/var/lib/mysql. The directory is
initially empty, which I believe is normal; there shouldn't be
anything in there until mysqld is started for the first time (at least
that's the behaviour of 5.6.22, which works fine). After mysqld fails
to start, an empty
Hi Cameron,
I've seen a similar error running on windows 7.
When you look in your datadir= specified in my.ini what is there exactly
(hopefully not empty)? Do you have a mysql folder containing plugin.*
files at this location? (say .MYI etc)
It sounds like your data folders were either not copi
The mysql_upgrade errors look like the mysql command line client can't be
located by the script... some kind of path error induced by a security "fix"
I'm thinking
On 02/12/2015 12:37 PM, Cameron Mann wrote:
> Hi all,
>
> I've encountered a problem with MySQL 5.6.23 on CentOS 7.0 and would
>
Hi all,
I've encountered a problem with MySQL 5.6.23 on CentOS 7.0 and would
greatly appreciate any advice on what to do next.
Synopsis:
1. Fresh install of CentOS 7.0 using minimal install ISO
2. yum update -y
3. rpm -i http://dev.mysql.com/get/mysql-community-release-el7-5.noarch.rpm
4. yum in
14 matches
Mail list logo
