Bug #2174 After installation mysql "ends" running ./bin/mysql_safe &
Submitted: 19 Dec 2003 19:56 Modified: 22 Dec 2003 9:13
Reporter: Craig Wynn Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.0-0 OS:Linux (Linux RH 9)
Assigned to: Dean Ellis CPU Architecture:Any

[19 Dec 2003 19:56] Craig Wynn
Description:
I am following the steps as documented in the manual for installing and running a binary mysql

I ran "mysqlbug" but I do not see how to include it with this submission

When I run ./bin/mysqld_safe & it like this:
[root@localhost mysql]# ./bin/mysqld_safe &
[1] 2192
[root@localhost mysql]# Starting mysqld daemon with databases from /usr/local/mysql/data
031219 21:00:19  mysqld ended

as you see it ends (stops) the question is why?

I trying to get to the point where I run mysqladmin so I can assign users and start using the database. I've been at this for over a month thinking I could get past this point on my own.

I have been able to execute mysqld and keep in running if I use the option to skip the grant tables. Is this any good to me?

this is the contents of "mysqlbug" report

SEND-PR: -*- send-pr -*-
SEND-PR: Lines stSarting with `SEND-PR' will be removed automatically, as
SEND-PR: will all comments (text enclosed in `<' and `>').
SEND-PR:
From: craig
To: mysql@lists.mysql.com
Subject: [50 character or so descriptive subject here (for reference)]

>Description:
	<precise description of the problem (multiple lines)>
>How-To-Repeat:
	<code/input/activities to reproduce the problem (multiple lines)>
>Fix:
	<how to correct or work around the problem, if known (multiple lines)>

>Submitter-Id:	<submitter ID>
>Originator:	
>Organization:
 <organization of PR author (multiple lines)>
>MySQL support: [none | licence | email support | extended email support ]
>Synopsis:	<synopsis of the problem (one line)>
>Severity:	<[ non-critical | serious | critical ] (one line)>
>Priority:	<[ low | medium | high ] (one line)>
>Category:	mysql
>Class:		<[ sw-bug | doc-bug | change-request | support ] (one line)>
>Release:	mysql-4.0.15-standard (Official MySQL-standard binary)

>C compiler:    2.95.3
>C++ compiler:  2.95.3
>Environment:
	<machine, os, target, libraries (multiple lines)>
System: Linux localhost.localdomain 2.4.20-24.9 #1 Mon Dec 1 11:35:51 EST 2003 i686 i686 i386 GNU/Linux
Architecture: i686

Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc /usr/bin/cc
GCC: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux
Thread model: posix
gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
Compilation info: CC='gcc'  CFLAGS='-O2 -mcpu=pentiumpro'  CXX='gcc'  CXXFLAGS='-O2 -mcpu=pentiumpro -felide-constructors'  LDFLAGS=''  ASFLAGS=''
LIBC: 
lrwxrwxrwx    1 root     root           13 Nov 14 13:20 /lib/libc.so.6 -> libc-2.3.2.so
-rwxr-xr-x    1 root     root      1561228 Nov 12 18:56 /lib/libc-2.3.2.so
-rw-r--r--    1 root     root      2332200 Nov 12 18:18 /usr/lib/libc.a
-rw-r--r--    1 root     root          204 Nov 12 17:49 /usr/lib/libc.so
Configure command: ./configure '--prefix=/usr/local/mysql' '--localstatedir=/usr/local/mysql/data' '--libexecdir=/usr/local/mysql/bin' '--with-comment=Official MySQL-standard binary' '--with-extra-charsets=complex' '--with-server-suffix=-standard' '--enable-thread-safe-client' '--enable-local-infile' '--enable-assembler' '--disable-shared' '--with-client-ldflags=-all-static' '--with-mysqld-ldflags=-all-static' '--with-embedded-server' '--with-innodb' 'CFLAGS=-O2 -mcpu=pentiumpro' 'CXXFLAGS=-O2 -mcpu=pentiumpro -felide-constructors' 'CXX=gcc'

thank you
craig

How to repeat:
./bin/mysqld_safe &
[22 Dec 2003 9:13] Dean Ellis
You need to read your mysqld error log and find out which step of the install process you have not completed.  You almost certainly have either not run mysql_install_db or did not chown the data directory properly (or have some other permission-related issue).

Thank you.