mysql error
Hi all, I am new with FreeBSD and I have a problem with mysql. I have 6.2Release i386 I am running mysql 5.0.27 and It worked perfectly until the time that I formated /tmp (for some other reason) and now when I am trying to connect on mysql *I get this:* *[r...@leonidas:/]$ mysql ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock2' (38)* *and when I edit /var/db/mysql/leonidas.MSHOME.err I see this:* *090628 14:49:19 mysqld started 090628 14:49:19 [Warning] Ignoring user change to 'ser=mysql' because the user was set to 'mysql' e 090628 14:49:20 InnoDB: Started; log sequence number 0 43655 090628 14:49:20 [ERROR] Can't start server : Bind on unix socket: Permission denied 090628 14:49:20 [ERROR] Do you already have another mysqld server running on socket: /tmp/mysql.soc 090628 14:49:20 [ERROR] Aborting 090628 14:49:20 InnoDB: Starting shutdown... 090628 14:49:22 InnoDB: Shutdown completed; log sequence number 0 43655 090628 14:49:22 [Note] /usr/local/libexec/mysqld: Shutdown complete 090628 14:49:22 mysqld ended *I have checked /tmp and there is no mysql.sock file. (because I formated /tmp immagine) I wouldn't like to loose my database, and I have no idea What I have to do? Thanx! :D ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mysql error
thanos trompoukis wrote: Hi all, I am new with FreeBSD and I have a problem with mysql. I have 6.2Release i386 I am running mysql 5.0.27 and It worked perfectly until the time that I formated /tmp (for some other reason) and now when I am trying to connect on mysql *I get this:* *[r...@leonidas:/]$ mysql ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock2' (38)* *and when I edit /var/db/mysql/leonidas.MSHOME.err I see this:* *090628 14:49:19 mysqld started 090628 14:49:19 [Warning] Ignoring user change to 'ser=mysql' because the user was set to 'mysql' e 090628 14:49:20 InnoDB: Started; log sequence number 0 43655 090628 14:49:20 [ERROR] Can't start server : Bind on unix socket: Permission denied 090628 14:49:20 [ERROR] Do you already have another mysqld server running on socket: /tmp/mysql.soc 090628 14:49:20 [ERROR] Aborting 090628 14:49:20 InnoDB: Starting shutdown... 090628 14:49:22 InnoDB: Shutdown completed; log sequence number 0 43655 090628 14:49:22 [Note] /usr/local/libexec/mysqld: Shutdown complete 090628 14:49:22 mysqld ended *I have checked /tmp and there is no mysql.sock file. (because I formated /tmp immagine) I wouldn't like to loose my database, and I have no idea What I have to do? Thanx! :D Don't forget to chmod 1777 /tmp /Morgan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mysql error
thanos trompoukis wrote: Hi all, I am new with FreeBSD and I have a problem with mysql. I have 6.2Release i386 I am running mysql 5.0.27 and It worked perfectly until the time that I formated /tmp (for some other reason) and now when I am trying to connect on mysql *I get this:* *[r...@leonidas:/]$ mysql ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock2' (38)* Ha, I know this, it happened to me once I messed with tmp, and its pretty simple: /tmp has the sticky bit set. If you forget it, some programs fail mysteriously. So just do a chown -R root:wheel /tmp (just to be safe) and chmod -R 1777 /tmp and all will be fine ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mysql error
thanos trompoukis wrote: Hi all, I am new with FreeBSD and I have a problem with mysql. I have 6.2Release i386 I am running mysql 5.0.27 and It worked perfectly until the time that I formated /tmp (for some other reason) and now when I am trying to connect on mysql *I get this:* *[r...@leonidas:/]$ mysql ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock2' (38)* *and when I edit /var/db/mysql/leonidas.MSHOME.err I see this:* *090628 14:49:19 mysqld started 090628 14:49:19 [Warning] Ignoring user change to 'ser=mysql' because the user was set to 'mysql' e 090628 14:49:20 InnoDB: Started; log sequence number 0 43655 090628 14:49:20 [ERROR] Can't start server : Bind on unix socket: Permission denied 090628 14:49:20 [ERROR] Do you already have another mysqld server running on socket: /tmp/mysql.soc 090628 14:49:20 [ERROR] Aborting 090628 14:49:20 InnoDB: Starting shutdown... 090628 14:49:22 InnoDB: Shutdown completed; log sequence number 0 43655 090628 14:49:22 [Note] /usr/local/libexec/mysqld: Shutdown complete 090628 14:49:22 mysqld ended *I have checked /tmp and there is no mysql.sock file. (because I formated /tmp immagine) I wouldn't like to loose my database, and I have no idea What I have to do? Thanx! :D You've apparently got a copy of mysql still running, despite trashing everything in /tmp. You can confirm that by: % sockstat | grep mysql Now, if sockstat shows that mysql is listening on a network interface, then you may just be able to log into it over a network connection and shut it down cleanly. If not, then you have no alternative by to signal the process to death and then let it repair the datafiles as it restarts. * If you have to kill mysql by signalling it: At first, try: # kill -15 `ps -ax | grep mysqld | cut -d ' ' -f 2` If it doesn't work immediately, leave mysql for 5 minutes, and see if it has shut down yet. Try again if not, possibly several times. Failing that, use: # kill -9 `ps -ax | grep mysqld | cut -d ' ' -f 2` But this last really should be avoided, as it causes the process to crash without any opportunity to close itself down nicely. * If mysql is listening on a network interface -- preferably any of 127.0.0.1:3306, [::1]:3306 or *:3306 Try using mysqladmin to shut it down cleanly. Note that mysql does special shortcut things when hostname is localhost and tries to use the socket in /tmp/mysql.sock -- which doesn't help you at all. You can force it to make a *network* connection to localhost by: # mysqladmin -h localhost -P 3306 --protocol=TCP -u root -p shutdown This will prompt you for the mysql root password. If mysqladmin doesn't work, then try using kill as above. Your data *should* survive MySQL being forcibly restarted in either of these ways. MySQL takes very great pains to ensure data is written to persistent media (ie. disk) in order to provide proper ACID compliance. However, if mysql does get killed, it will need to do some repair work on data structures when it next starts up, and that can take a while. Because writing out its PID file is one of the last things mysql does in the startup sequence '/usr/local/etc/rc.d/mysql-server status' will report 'not running' during this repair work, so be a bit patient if you see that. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: mysql error
2009/6/28 Matthew Seaman m.sea...@infracaninophile.co.uk thanos trompoukis wrote: Hi all, I am new with FreeBSD and I have a problem with mysql. I have 6.2Release i386 I am running mysql 5.0.27 and It worked perfectly until the time that I formated /tmp (for some other reason) and now when I am trying to connect on mysql *I get this:* *[r...@leonidas:/]$ mysql ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock2' (38)* *and when I edit /var/db/mysql/leonidas.MSHOME.err I see this:* *090628 14:49:19 mysqld started 090628 14:49:19 [Warning] Ignoring user change to 'ser=mysql' because the user was set to 'mysql' e 090628 14:49:20 InnoDB: Started; log sequence number 0 43655 090628 14:49:20 [ERROR] Can't start server : Bind on unix socket: Permission denied 090628 14:49:20 [ERROR] Do you already have another mysqld server running on socket: /tmp/mysql.soc 090628 14:49:20 [ERROR] Aborting 090628 14:49:20 InnoDB: Starting shutdown... 090628 14:49:22 InnoDB: Shutdown completed; log sequence number 0 43655 090628 14:49:22 [Note] /usr/local/libexec/mysqld: Shutdown complete 090628 14:49:22 mysqld ended *I have checked /tmp and there is no mysql.sock file. (because I formated /tmp immagine) I wouldn't like to loose my database, and I have no idea What I have to do? Thanx! :D You've apparently got a copy of mysql still running, despite trashing everything in /tmp. You can confirm that by: % sockstat | grep mysql Now, if sockstat shows that mysql is listening on a network interface, then you may just be able to log into it over a network connection and shut it down cleanly. If not, then you have no alternative by to signal the process to death and then let it repair the datafiles as it restarts. * If you have to kill mysql by signalling it: At first, try: # kill -15 `ps -ax | grep mysqld | cut -d ' ' -f 2` If it doesn't work immediately, leave mysql for 5 minutes, and see if it has shut down yet. Try again if not, possibly several times. Failing that, use: # kill -9 `ps -ax | grep mysqld | cut -d ' ' -f 2` But this last really should be avoided, as it causes the process to crash without any opportunity to close itself down nicely. * If mysql is listening on a network interface -- preferably any of 127.0.0.1:3306, [::1]:3306 or *:3306 Try using mysqladmin to shut it down cleanly. Note that mysql does special shortcut things when hostname is localhost and tries to use the socket in /tmp/mysql.sock -- which doesn't help you at all. You can force it to make a *network* connection to localhost by: # mysqladmin -h localhost -P 3306 --protocol=TCP -u root -p shutdown This will prompt you for the mysql root password. If mysqladmin doesn't work, then try using kill as above. Your data *should* survive MySQL being forcibly restarted in either of these ways. MySQL takes very great pains to ensure data is written to persistent media (ie. disk) in order to provide proper ACID compliance. However, if mysql does get killed, it will need to do some repair work on data structures when it next starts up, and that can take a while. Because writing out its PID file is one of the last things mysql does in the startup sequence '/usr/local/etc/rc.d/mysql-server status' will report 'not running' during this repair work, so be a bit patient if you see that. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW Thanx! thank you very much guys..! Finaly it was so simple!!! aaa, god bless you!! Thanx again.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
MySQL Error: Can't create a new thread (errno 35); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug
Hello, The error message: Can't create a new thread (errno 35); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug Our website started getting this error several weeks ago (when we increased the number of application server machines connecting to the database from 5 to 7. It seems to happen anywhere from every 2 days to once a week, there does not seem to be a consistent pattern. Our CPU utilization, memory utilization, and number of HTTP Requests seem to be at normal (they are no where closed to being maxed out). When this error happens we CAN log onto the server with the MySQL database, but I CAN NOT use the mysql client to connect to the mysql database (localhost connection as root) - it reports the error mentioned above. The way we temporarily solve the problem is to restart one of our web servers. Here is our technology stack: Web Servers: 7, Each server has: 4 Gb of Memory on each server FreeBSD 6.2-RELEASE-p9 2.4 GHz CPU Apache 2.2 Webware for Python Python 2.5 DB Servers: One Master, Two Read Only (replication) 4 GB of Memory on each server FreeBSD 6.3-RELEASE-p3 FreeBSD 6.3-RELEASE-p3 MySQL 5.0.1 We have tried bumping up our number of max allowed connections (up to 1000) on MySQL and kern.ssize to 512Mb for FreeBSD. That did not help. The max connections usually hovers ~300, so it does not even get close to the 1000 we have set. Finally the last place that we have looked is the openfiles, it is set at 20,000 for the whole system, with 14K per process on the FreeBSD operating system. Here are some relevent items from my.cnf: - set-variable = max_connections=1000 - set-variable = key_buffer_size=384M - set-variable = read_buffer_size=64M - set-variable = read_rnd_buffer_size=32M - set-variable = thread_cache_size=20 Any help would be much appreciated. Thanks - Sam Nilsson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MySQL Error: Can't create a new thread (errno 35); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug
Sam Nilsson wrote: Hello, The error message: Can't create a new thread (errno 35); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug Our website started getting this error several weeks ago (when we increased the number of application server machines connecting to the database from 5 to 7. It seems to happen anywhere from every 2 days to once a week, there does not seem to be a consistent pattern. Our CPU utilization, memory utilization, and number of HTTP Requests seem to be at normal (they are no where closed to being maxed out). When this error happens we CAN log onto the server with the MySQL database, but I CAN NOT use the mysql client to connect to the mysql database (localhost connection as root) - it reports the error mentioned above. The way we temporarily solve the problem is to restart one of our web servers. Here is our technology stack: Web Servers: 7, Each server has: 4 Gb of Memory on each server FreeBSD 6.2-RELEASE-p9 2.4 GHz CPU Apache 2.2 Webware for Python Python 2.5 DB Servers: One Master, Two Read Only (replication) 4 GB of Memory on each server FreeBSD 6.3-RELEASE-p3 FreeBSD 6.3-RELEASE-p3 MySQL 5.0.1 We have tried bumping up our number of max allowed connections (up to 1000) on MySQL and kern.ssize to 512Mb for FreeBSD. That did not help. The max connections usually hovers ~300, so it does not even get close to the 1000 we have set. Finally the last place that we have looked is the openfiles, it is set at 20,000 for the whole system, with 14K per process on the FreeBSD operating system. Here are some relevent items from my.cnf: - set-variable = max_connections=1000 - set-variable = key_buffer_size=384M - set-variable = read_buffer_size=64M - set-variable = read_rnd_buffer_size=32M - set-variable = thread_cache_size=20 Any help would be much appreciated. Thanks - Sam Nilsson If you havent already, you could try increasing the per process memory limit as per examples in http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2008-05/msg00258.html (man tuning also says a bit about these tuneables but doesnt have the examples that post does) Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MySQL Error: Can't create a new thread (errno 35); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug
On Tuesday 23 September 2008 12:13:58 Sam Nilsson wrote: DB Servers: One Master, Two Read Only (replication) 4 GB of Memory on each server FreeBSD 6.3-RELEASE-p3 FreeBSD 6.3-RELEASE-p3 MySQL 5.0.1 Here are some relevent items from my.cnf: - set-variable = max_connections=1000 - set-variable = key_buffer_size=384M - set-variable = read_buffer_size=64M - set-variable = read_rnd_buffer_size=32M - set-variable = thread_cache_size=20 You're shooting yourself in the foot: 1000*2MB=2G for thread stack + 384M + 1000 * (sort_buffer_size+64M+binlog_cache_size_innodb) You don't have that much memory. http://dev.mysql.com/doc/refman/5.0/en/innodb-configuration.html There's a similar formula for MyISAM, but can't seem to find it at the moment. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MySQL Error: Can't create a new thread (errno 35); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug
Vincent Hoffman wrote: If you havent already, you could try increasing the per process memory limit as per examples in http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2008-05/msg00258.html (man tuning also says a bit about these tuneables but doesnt have the examples that post does) Vince Hi Vince, Thanks for the advice. We have already raised the memory limits: kern.maxdsiz=1843M # 1.8GB kern.dfldsiz=1843M # 1.8GB Any other ideas? - Sam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mysql Error 1135
Akhthar Parvez. K [EMAIL PROTECTED] writes: I am getting following error message while accessing mysql. ERROR 1135: Can't create a new thread (errno 35). If you are not out of available memory, you can consult the manual for a possible OS-dependent bug What could be the problem? I know that the problem is due to resources are temporarily unavaliable. But how can I fix this issue so that it won't come back. Well, first you need to figure out if you have run out of system memory or not. If so, then add a swap file. If not, then see if there are process limits affecting you. NOTHING IS IMPOSSIBLE Because Impossible itself says I'M POSSIBLE Let me know when you have FreeBSD running on an abacus. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Mysql Error 1135
Hi All, I am getting following error message while accessing mysql. ERROR 1135: Can't create a new thread (errno 35). If you are not out of available memory, you can consult the manual for a possible OS-dependent bug What could be the problem? I know that the problem is due to resources are temporarily unavaliable. But how can I fix this issue so that it won't come back. -- With Regards, Akhthar Parvez.K - NOTHING IS IMPOSSIBLE Because Impossible itself says I'M POSSIBLE ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MySQL error 2013
Hi Derrick Ryalls, you wrote. DR I have even tried firing up mysqld with --skip-grant-tables to no avail. DR Googling around, I see lots of reference to glibc issues, but I thought DR that only applied to Linux. I have tried mysql41-server port (fresh DR cvsup), mysql40, and a package mysql323, and they all have the same DR issue. That leads me to believe that the o/s has the issue, not mysql. DR Does anyone have a clue on what I need to check/upgrade? DR Current system: FreeBSD 4.9-RC #0: Tue Oct 7 Does your MySQL daemon crash (look at /var/db/mysql/*err) ? Because I'm currently seeing this on CURRENT, but STABLE works perfectly for me... Regards, Gabriel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MySQL error 2013
On Sat, Feb 21, 2004 at 11:38:11PM -0800, Derrick Ryalls wrote: snip Googling around, I see lots of reference to glibc issues, but I thought that only applied to Linux. I have tried mysql41-server port (fresh cvsup), mysql40, and a package mysql323, and they all have the same issue. That leads me to believe that the o/s has the issue, not mysql. Does anyone have a clue on what I need to check/upgrade? Current system: FreeBSD 4.9-RC #0: Tue Oct 7 yeah, glibc would be linux only... but there're a couple pr's for this issue on freebsd right now. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/62845 http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/63213 (currently, there is no fix.. the workaround is to connect via a local socket/pipe). Mind if I ask what cpu/mb you're operating on? -- -Erik [EMAIL PROTECTED] [http://math.smsu.edu/~erik] The opinions expressed by me are not necessarily opinions. In all probability, they are random rambling, and to be ignored. Failure to ignore may result in severe boredom or confusion. Shake well before opening. Keep Refrigerated. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
MySQL error 2013
I have been trying to get a working mysql daemon that allows connections from remote hosts. I can connect via local host just fine, but any time I try from my XP desktop via command center (or another remote client), I get this error immediately: ERROR 2013: Lost connection to MySQL server during query I have even tried firing up mysqld with --skip-grant-tables to no avail. Googling around, I see lots of reference to glibc issues, but I thought that only applied to Linux. I have tried mysql41-server port (fresh cvsup), mysql40, and a package mysql323, and they all have the same issue. That leads me to believe that the o/s has the issue, not mysql. Does anyone have a clue on what I need to check/upgrade? Current system: FreeBSD 4.9-RC #0: Tue Oct 7 Thanks in advance. -Derrick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mysql error and phpmyadmin how-to
get the following error when trying to log in to mysql as root like so .. # mysql -u root -p Enter password: ERROR 1045: Access denied for user: '[EMAIL PROTECTED]' (Using password: YES) I'm issuing this command as root. Also as root I have attempted to change the passwd.. # mysqladmin -u root password newpassword mysqladmin: connect to server at 'localhost' failed mysql version -- mysql-server-3.23.55 Multithreaded SQL database (server) Also Looking for a good how-to on phpmyadmin.. I installed from the ports collection (phpMyAdmin-2.3.2) Just not sure what direction to head in now.. Thanks for your time.. Shawn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mysql error and phpmyadmin how-to
# mysql -u root -px (xxx=password) That is how I got around the same error Hope it helps. ROb On Thu, 2003-09-18 at 22:57, Shawn Guillemette wrote: get the following error when trying to log in to mysql as root like so .. # mysql -u root -p Enter password: ERROR 1045: Access denied for user: '[EMAIL PROTECTED]' (Using password: YES) I'm issuing this command as root. Also as root I have attempted to change the passwd.. # mysqladmin -u root password newpassword mysqladmin: connect to server at 'localhost' failed mysql version -- mysql-server-3.23.55 Multithreaded SQL database (server) Also Looking for a good how-to on phpmyadmin.. I installed from the ports collection (phpMyAdmin-2.3.2) Just not sure what direction to head in now.. Thanks for your time.. Shawn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mysql error and phpmyadmin how-to
On Thursday, Sep 18, 2003, at 23:57 US/Eastern, Shawn Guillemette wrote: get the following error when trying to log in to mysql as root like so .. # mysql -u root -p Enter password: ERROR 1045: Access denied for user: '[EMAIL PROTECTED]' (Using password: YES) I'm issuing this command as root. Also as root I have attempted to change the passwd.. # mysqladmin -u root password newpassword mysqladmin: connect to server at 'localhost' failed mysql version -- mysql-server-3.23.55 Multithreaded SQL database (server) Also Looking for a good how-to on phpmyadmin.. I installed from the ports collection (phpMyAdmin-2.3.2) Just not sure what direction to head in now.. Thanks for your time.. Shawn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Shawn, The user named root in MySQL is completely separate from your root user for your BSD installation. It initially has no password, so mysql -u root without the -p should work for you. I have always installed from source code builds, so I am not sure as to whether or not the port does this for you. Have you run the mysql_install_db script to initialize the databases in MySQL? If not, you could potentially be seeing a situation where the permission tables for the daemon are not available, so you are being rejected out-of-hand. I would try the mysql -u root first, if you have run the script (or if the port runs the script for you; regrettably I do not know if it does). Regards, -- Barry C. Hawkins All Things Computed site: www.allthingscomputed.com/ weblog: www.allthingscomputed.com/blog/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mysql error and phpmyadmin how-to
this was part of the howto that I followed.. mysqladmin -u root password newpassword I had also created a database already.. however 24 hours later I cant seem to get it to work...I know it something stupid..,.,. :-)- Original Message - From: Barry Hawkins [EMAIL PROTECTED] To: Shawn Guillemette [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, September 18, 2003 6:41 PM Subject: Re: mysql error and phpmyadmin how-to On Thursday, Sep 18, 2003, at 23:57 US/Eastern, Shawn Guillemette wrote: get the following error when trying to log in to mysql as root like so .. # mysql -u root -p Enter password: ERROR 1045: Access denied for user: '[EMAIL PROTECTED]' (Using password: YES) I'm issuing this command as root. Also as root I have attempted to change the passwd.. # mysqladmin -u root password newpassword mysqladmin: connect to server at 'localhost' failed mysql version -- mysql-server-3.23.55 Multithreaded SQL database (server) Also Looking for a good how-to on phpmyadmin.. I installed from the ports collection (phpMyAdmin-2.3.2) Just not sure what direction to head in now.. Thanks for your time.. Shawn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Shawn, The user named root in MySQL is completely separate from your root user for your BSD installation. It initially has no password, so mysql -u root without the -p should work for you. I have always installed from source code builds, so I am not sure as to whether or not the port does this for you. Have you run the mysql_install_db script to initialize the databases in MySQL? If not, you could potentially be seeing a situation where the permission tables for the daemon are not available, so you are being rejected out-of-hand. I would try the mysql -u root first, if you have run the script (or if the port runs the script for you; regrettably I do not know if it does). Regards, -- Barry C. Hawkins All Things Computed site: www.allthingscomputed.com/ weblog: www.allthingscomputed.com/blog/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mysql error and phpmyadmin how-to
Just noticed this.,. I'm really green to mysql so this might not be anything that will help me figure out what had happened.. I can get to mysql with out a passwd mysql Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 7 to server version: 3.23.55 Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql - Original Message - From: Barry Hawkins [EMAIL PROTECTED] To: Shawn Guillemette [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, September 18, 2003 6:41 PM Subject: Re: mysql error and phpmyadmin how-to On Thursday, Sep 18, 2003, at 23:57 US/Eastern, Shawn Guillemette wrote: get the following error when trying to log in to mysql as root like so .. # mysql -u root -p Enter password: ERROR 1045: Access denied for user: '[EMAIL PROTECTED]' (Using password: YES) I'm issuing this command as root. Also as root I have attempted to change the passwd.. # mysqladmin -u root password newpassword mysqladmin: connect to server at 'localhost' failed mysql version -- mysql-server-3.23.55 Multithreaded SQL database (server) Also Looking for a good how-to on phpmyadmin.. I installed from the ports collection (phpMyAdmin-2.3.2) Just not sure what direction to head in now.. Thanks for your time.. Shawn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Shawn, The user named root in MySQL is completely separate from your root user for your BSD installation. It initially has no password, so mysql -u root without the -p should work for you. I have always installed from source code builds, so I am not sure as to whether or not the port does this for you. Have you run the mysql_install_db script to initialize the databases in MySQL? If not, you could potentially be seeing a situation where the permission tables for the daemon are not available, so you are being rejected out-of-hand. I would try the mysql -u root first, if you have run the script (or if the port runs the script for you; regrettably I do not know if it does). Regards, -- Barry C. Hawkins All Things Computed site: www.allthingscomputed.com/ weblog: www.allthingscomputed.com/blog/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
