Mysql Error 146
Forums Hosting Security and Technology ERROR 2002: Can't connect to local MySQL server (146) If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 12 of 12 Thread: ERROR 2002: Can't connect to local MySQL server (146) Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 10-21-2001,09:02 AM #1 jsmit View Profile View Forum Posts View Forum Threads Visit Homepage Newbie Join Date Oct 2001 Posts 10 ERROR 2002: Can't connect to local MySQL server (146) Somebody has shutdown the cobalt server without shutdown of the mysql server. How is it possible to restart the Mysql server ? Reply With Quote 0 10-23-2001,04:41 AM #2 niekas View Profile View Forum Posts View Forum Threads Newbie Join Date Sep 2001 Posts 23 Its better to configure Mysql to start with boot of your server. If you using webmin go to System > Bootup and Shutdown > mysqld and select radio button Start at boot time? yes. Reply With Quote 0 10-23-2001,06:30 PM #3 jks View Profile View Forum Posts View Forum Threads Visit Homepage Web Hosting Master Join Date Apr 2001 Location Denmark, Europe Posts 614 Re: ERROR 2002: Can't connect to local MySQL server (146) Originally posted by jsmit Somebody has shutdown the cobalt server without shutdown of the mysql server. How is it possible to restart the Mysql server ? The most common way on Cobalts is: 1. Log in as root. 2. Execute this command: /etc/rc.d/init.d/mysql start That should start up mysql. Jens Kristian Søgaard, Mermaid Consulting ApS, [emailprotected], http://www.mermaidconsulting.com/ Reply With Quote 0 10-24-2001,01:09 AM #4 jsmit View Profile View Forum Posts View Forum Threads Visit Homepage Newbie Join Date Oct 2001 Posts 10 It gives the following result: [root users]# /etc/rc.d/init
you need a good reference, and this is one of those times. MySQL's perror command returns many error codes, and I've provided a listing here. To find errors individually, just run: XHTML # perror 28 OS error code 28: No space left on device 12 # perror 28OS error code28:No space left on device Here's the list: XHTML OS error code 1: Operation not permitted OS error code 2: No such file or directory OS error code 3: No such process OS error code 4: Interrupted system call OS http://www.webhostingtalk.com/showthread.php?t=23982 error code 5: Input/output error OS error code 6: No such device or address OS error code 7: Argument list too long OS error code 8: Exec format error OS error code 9: Bad file descriptor OS error code 10: No child processes OS error code 11: Resource temporarily unavailable OS error code 12: Cannot allocate memory OS error code 13: Permission denied OS https://major.io/2007/08/09/mysql-error-codes/ error code 14: Bad address OS error code 15: Block device required OS error code 16: Device or resource busy OS error code 17: File exists OS error code 18: Invalid cross-device link OS error code 19: No such device OS error code 20: Not a directory OS error code 21: Is a directory OS error code 22: Invalid argument OS error code 23: Too many open files in system OS error code 24: Too many open files OS error code 25: Inappropriate ioctl for device OS error code 26: Text file busy OS error code 27: File too large OS error code 28: No space left on device OS error code 30: Read-only file system OS error code 31: Too many links OS error code 32: Broken pipe OS error code 33: Numerical argument out of domain OS error code 34: Numerical result out of range OS error code 35: Resource deadlock avoided OS error code 36: File name too long OS error code 37: No locks available OS error code 38: Function not implemented OS error code 39: Directory not empty OS error code 40: Too man
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings http://dba.stackexchange.com/questions/46180/rare-error-lasts-only-a-second-cant-connect-to-local-mysql-server-through-sock and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in mysql error the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Rare error lasts only a second “Can't connect to local MySQL server through socket '/tmp/mysql.sock' (146)” 146=ECONNREFUSED up vote 3 down vote favorite 1 This is a mysql error 146 rare error that occurs on Solaris 10, have seen it from Perl, where this line DBI->connect(...) or die "Whoops! $DBI::errstr" outputs Whoops! Can't connect to local MySQL server through socket '/tmp/mysql.sock' (146) at something.pl line ... I determined that on my system, 146=ECONNREFUSED It is very rare for this error to occur, but it happens on an ongoing basis. It always a temporary problem on this setup—lasting only a second or two. The global variable max_connections has been ruled out as a problem. This does not occur on TCP/IP based connections. I am using the [mysqld_safe] log-error option in my.cnf. The log outputs the following at startup: mysqld started InnoDB: Started; log sequence number... [Note] .../libexec/mysqld: ready for connections. Version: '5.0.27-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution There are no other log entries, so there's nothing here to indicate the problem. Please let me know if you can suggest a setting for more detailed logging. Can you enumerate the possible or likely causes of this error happening only occasionally and only for a second or two? mysql errors connectivity