SliTaz Forum

Installing MySQL from Generic Binaries

(3 posts) (1 voice)

• Started 11 years ago by spaesani
• Latest reply from spaesani
• This topic is not a support question

Tags:

No tags yet.

1. 

   spaesani
   

   offline

   Member

   I've installed mysql generic binaries using the installation outlined at http://dev.mysql.com/doc/refman/5.1/en/binary-installation.html

   When starting the server using
   tux@slitaz:/usr/local/mysql-5.5.25a-linux2.6-i686$ ./bin/mysqld_safe --user=mysql &
   I get a permissions error with an oddly named file: slitaz.err

   tux@slitaz:/usr/local/mysql-5.5.25a-linux2.6-i686$ 120721 01:18:59 mysqld_safe Logging to '/usr/local/mysql/data/slitaz.err'.
   sh: -: bad number
   120721 01:18:59 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
   ./bin/mysqld_safe: line 742: can't create /usr/local/mysql/data/slitaz.err: Permission denied
   ./bin/mysqld_safe: eval: line 1: can't create /usr/local/mysql/data/slitaz.err: Permission denied
   120721 01:18:59 mysqld_safe mysqld from pid file /usr/local/mysql/data/slitaz.pid ended
   ./bin/mysqld_safe: line 824: can't create /usr/local/mysql/data/slitaz.err: Permission denied

   If I can get some help to resolve the permissions err, thanks.
   But also, where does mysql get the name for a file: slitaz.err ??

   Posted 11 years ago #
2. 

   spaesani
   

   offline

   Member

   OK,
   slitaz.err is a name derived by mysql from the hostname of the system when no error log file name is given in /etc/my.cnf (if not other places such as command line, if any).

   The permissions is a caller issue. If the caller has the right permissions all is good.
   So a change to the mysql user, eg: su mysql, and the server starts, almost. (root yields the same results).

   mysql@slitaz:/usr/local/mysql-5.5.25a-linux2.6-i686$ ./bin/mysqld_safe
   120721 05:49:49 mysqld_safe Logging to '/usr/local/mysql/data/mysql-error.err'.
   sh: -: bad number
   120721 05:49:49 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
   120721 05:49:49 mysqld_safe mysqld from pid file /usr/local/mysql/data/slitaz.pid ended
   mysql@sl

   Here the server starts and then stops immediately. Not much is said in the error log
   except a repeat of the screen output (above):
   mysql@slitaz:/usr/local/mysql-5.5.25a-linux2.6-i686$ less ./data/mysql-error.err
   120721 05:49:49 mysqld_safe Starting mysqld daemon with databases from /usr/local
   /mysql/data
   120721 05:49:49 mysqld_safe mysqld from pid file /usr/local/mysql/data/slitaz.pid
   ended

   The mysql docs at http://dev.mysql.com/doc/refman/5.1/en/starting-server.html
   give some info here:

   "if no other server is running, try to execute the command telnet your_host_name tcp_ip_port_number. (The default MySQL port number is 3306.) Then press Enter a couple of times. If you do not get an error message like telnet: Unable to connect to remote host: Connection refused, some other program is using the TCP/IP port that mysqld is trying to use."

   so:
   root@slitaz:/usr/local/mysql-5.5.25a-linux2.6-i686# telnet localhost:3306
   telnet: can't connect to remote host (127.0.0.1): Connection refused

   I get the error message that clears any potentially guilty port users.

   Finally, according to the same mysql document, there is the potential that a firewall is blocking the port. I'll check this and post back.

   Posted 11 years ago #
3. 

   spaesani
   

   offline

   Member

   I disable/stop the firewall:

   root@slitaz:/usr/local/mysql-5.5.25a-linux2.6-i686# /etc/init.d/firewall stop
   Iptables rules are disabled in: /etc/firewall.conf...

   and give it another try:

   root@slitaz:/usr/local/mysql-5.5.25a-linux2.6-i686# ./bin/mysqld_safe --user=mysql
   120721 06:11:37 mysqld_safe Logging to '/usr/local/mysql/data/mysql-error.err'.
   sh: -: bad number
   120721 06:11:37 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
   120721 06:11:37 mysqld_safe mysqld from pid file /usr/local/mysql/data/slitaz.pid ended

   It is a common error that many seem to have encountered. It is usually related to an allready running mysql server (no), another process holding the port mysql wants to use (no), or a firewall blocking the port (no).

   ? hmmm ...

   Posted 11 years ago #

RSS feed for this topic

Reply

You must log in to post.