Re: Problems Starting MySQL
Anyone have any ideas on this one? Many thanks. RobL On Friday 10 February 2006 15:07, Rob Lacey wrote: Running as root. RobL On Friday 10 February 2006 14:55, sheeri kritzer wrote: Are you running the startup script as root, or is it setuid? -Sheeri On 2/10/06, Rob Lacey [EMAIL PROTECTED] wrote: Wondering if anyone can shed some light on a problem I am experiencing. I am running MySQL 4.1 on a Red Hat Enterprise Linux ES release 4 (Nahant Update 2) machine. I have been trying to get the default /etc/init.d/mysqld script to restart the server but I keep running into the same problems. The MySQL server itself is running at the moment and has a number of live databases on it. 060209 18:40:43 mysqld started 060209 18:40:43 [Warning] Can't create test file /var/lib/mysql/thirdeye.lower-test /usr/libexec/mysqld: Can't change dir to '/var/lib/mysql/' (Errcode: 13) 060209 18:40:43 [ERROR] Aborting 060209 18:40:43 [Note] /usr/libexec/mysqld: Shutdown complete 060209 18:40:43 mysqld ended I can't see where the thirdeye.lower-test file creation is coming into this at all. Since as far as can see the startup script doesn't seem to call any script to create test databases. Is this part of mysqld_safe? I can also see that /var/lib/mysql is already owned by mysql.mysql with 755 permissions. Indeed the RedHat startup script makes this so. Therefore the permissions error seems extremely odd as they seem fine to me. I can start the server using the following directly on the command line, which is what the startup script ultimately runs anyway. /usr/bin/mysqld_safe --defaults-file=/etc/my.cnf --pid-file= /var/run/mysqld/mysqld.pid /dev/null 21 Can anyone give me something further to go on? Many thanks. Rob -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Problems Starting MySQL
Wondering if anyone can shed some light on a problem I am experiencing. I am running MySQL 4.1 on a Red Hat Enterprise Linux ES release 4 (Nahant Update 2) machine. I have been trying to get the default /etc/init.d/mysqld script to restart the server but I keep running into the same problems. The MySQL server itself is running at the moment and has a number of live databases on it. 060209 18:40:43 mysqld started 060209 18:40:43 [Warning] Can't create test file /var/lib/mysql/thirdeye.lower-test /usr/libexec/mysqld: Can't change dir to '/var/lib/mysql/' (Errcode: 13) 060209 18:40:43 [ERROR] Aborting 060209 18:40:43 [Note] /usr/libexec/mysqld: Shutdown complete 060209 18:40:43 mysqld ended I can't see where the thirdeye.lower-test file creation is coming into this at all. Since as far as can see the startup script doesn't seem to call any script to create test databases. Is this part of mysqld_safe? I can also see that /var/lib/mysql is already owned by mysql.mysql with 755 permissions. Indeed the RedHat startup script makes this so. Therefore the permissions error seems extremely odd as they seem fine to me. I can start the server using the following directly on the command line, which is what the startup script ultimately runs anyway. /usr/bin/mysqld_safe --defaults-file=/etc/my.cnf --pid-file= /var/run/mysqld/mysqld.pid /dev/null 21 Can anyone give me something further to go on? Many thanks. Rob -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Problems Starting MySQL
Are you running the startup script as root, or is it setuid? -Sheeri On 2/10/06, Rob Lacey [EMAIL PROTECTED] wrote: Wondering if anyone can shed some light on a problem I am experiencing. I am running MySQL 4.1 on a Red Hat Enterprise Linux ES release 4 (Nahant Update 2) machine. I have been trying to get the default /etc/init.d/mysqld script to restart the server but I keep running into the same problems. The MySQL server itself is running at the moment and has a number of live databases on it. 060209 18:40:43 mysqld started 060209 18:40:43 [Warning] Can't create test file /var/lib/mysql/thirdeye.lower-test /usr/libexec/mysqld: Can't change dir to '/var/lib/mysql/' (Errcode: 13) 060209 18:40:43 [ERROR] Aborting 060209 18:40:43 [Note] /usr/libexec/mysqld: Shutdown complete 060209 18:40:43 mysqld ended I can't see where the thirdeye.lower-test file creation is coming into this at all. Since as far as can see the startup script doesn't seem to call any script to create test databases. Is this part of mysqld_safe? I can also see that /var/lib/mysql is already owned by mysql.mysql with 755 permissions. Indeed the RedHat startup script makes this so. Therefore the permissions error seems extremely odd as they seem fine to me. I can start the server using the following directly on the command line, which is what the startup script ultimately runs anyway. /usr/bin/mysqld_safe --defaults-file=/etc/my.cnf --pid-file= /var/run/mysqld/mysqld.pid /dev/null 21 Can anyone give me something further to go on? Many thanks. Rob -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Problems Starting MySQL
Running as root. RobL On Friday 10 February 2006 14:55, sheeri kritzer wrote: Are you running the startup script as root, or is it setuid? -Sheeri On 2/10/06, Rob Lacey [EMAIL PROTECTED] wrote: Wondering if anyone can shed some light on a problem I am experiencing. I am running MySQL 4.1 on a Red Hat Enterprise Linux ES release 4 (Nahant Update 2) machine. I have been trying to get the default /etc/init.d/mysqld script to restart the server but I keep running into the same problems. The MySQL server itself is running at the moment and has a number of live databases on it. 060209 18:40:43 mysqld started 060209 18:40:43 [Warning] Can't create test file /var/lib/mysql/thirdeye.lower-test /usr/libexec/mysqld: Can't change dir to '/var/lib/mysql/' (Errcode: 13) 060209 18:40:43 [ERROR] Aborting 060209 18:40:43 [Note] /usr/libexec/mysqld: Shutdown complete 060209 18:40:43 mysqld ended I can't see where the thirdeye.lower-test file creation is coming into this at all. Since as far as can see the startup script doesn't seem to call any script to create test databases. Is this part of mysqld_safe? I can also see that /var/lib/mysql is already owned by mysql.mysql with 755 permissions. Indeed the RedHat startup script makes this so. Therefore the permissions error seems extremely odd as they seem fine to me. I can start the server using the following directly on the command line, which is what the startup script ultimately runs anyway. /usr/bin/mysqld_safe --defaults-file=/etc/my.cnf --pid-file= /var/run/mysqld/mysqld.pid /dev/null 21 Can anyone give me something further to go on? Many thanks. Rob -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: problems starting MySQL with InnoDB tables
In the process I noticed somehow someone had managed to install a slightly different version of mysql vs. mysql-max, so I uninstalled everything msyql related and started over, came right up with InnoDB support! - Kevin Korngut Mr. Magoo JANIMATION INC. www.janimation.com http://www.janimation.com/ Gleb Paharenko said the following on 5/13/2005 4:34 PM: Hello. You have a rather old version and it is built manually. I suggest you to upgrade to the latest release (4.1.11 or if it is impossible, then to 4.0.24). And check if problem is solved after that. kevin korngut [EMAIL PROTECTED] wrote: [-- text/plain, encoding 7bit, charset: ISO-8859-1, 74 lines --] I'm attempting to configure mysql with InnoDB tables and I'm running into problems. And am using the following version of mysqld-max, Ver 4.0.18-Max for suse-linux on i686 (Source distribution) First I uncommented the following lines in /etc/my.cnf: # Uncomment the following if you are using InnoDB tables innodb_data_home_dir = /var/lib/mysql/ innodb_data_file_path = ibdata1:10M:autoextend innodb_log_group_home_dir = /var/lib/mysql/ innodb_log_arch_dir = /var/lib/mysql/ # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 16M innodb_additional_mem_pool_size = 2M # Set .._log_file_size to 25 % of buffer pool size innodb_log_file_size = 5M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 Then I attempted to start mysqld-max as the user mysql (mysqld-max -u mysql) and got the following: mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 80383 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8434638 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Bogus stack limit or frame pointer, fp=0xbffbcea4, stack_bottom=0x7ca35f80, thread_stack=196608, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x7bcf0ff0 is invalid pointer thd-thread_id=0 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. I then tried mysqld-max -u root which created the InnoDB file; however, when I then attempted to start mysql I got the above error (again, running it as the user mysql and not as root) Anyone seen this or happen to know what's going on?
problems starting MySQL with InnoDB tables
I'm attempting to configure mysql with InnoDB tables and I'm running into problems. And am using the following version of mysqld-max, Ver 4.0.18-Max for suse-linux on i686 (Source distribution) First I uncommented the following lines in /etc/my.cnf: # Uncomment the following if you are using InnoDB tables innodb_data_home_dir = /var/lib/mysql/ innodb_data_file_path = ibdata1:10M:autoextend innodb_log_group_home_dir = /var/lib/mysql/ innodb_log_arch_dir = /var/lib/mysql/ # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 16M innodb_additional_mem_pool_size = 2M # Set .._log_file_size to 25 % of buffer pool size innodb_log_file_size = 5M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 Then I attempted to start mysqld-max as the user mysql (mysqld-max -u mysql) and got the following: mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 80383 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8434638 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Bogus stack limit or frame pointer, fp=0xbffbcea4, stack_bottom=0x7ca35f80, thread_stack=196608, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x7bcf0ff0 is invalid pointer thd-thread_id=0 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. I then tried mysqld-max -u root which created the InnoDB file; however, when I then attempted to start mysql I got the above error (again, running it as the user mysql and not as root) Anyone seen this or happen to know what's going on? -- - Kevin Korngut Mr. Magoo JANIMATION INC. www.janimation.com http://www.janimation.com/
problems starting mysql - malloc?
Hi all, I've had a mysql db server running fine for a few months now, and all of a sudden, I'm having trouble with it. when starting the service, the error log contains the following 88888 021119 09:58:56 mysqld started /usr/sbin/mysqld: Can't read dir of '/root/tmp/' (Errcode: 13) 021119 9:58:58 bdb: malloc: Cannot allocate memory: 10485760 021119 9:58:58 Can't init databases 021119 09:58:58 mysqld ended 88888 I have no idea why it it looking in root/tmp for anything any ideas on where to start?? Thanks Albert ___ http://www.webmail.co.za the South-African free email service NetWiseGurus.Com Portal - Your Own Internet Business Today! - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Problems starting mysql on sun solaris 8
chown -R mysql.mysql /usr/local/mysql ROUTLEY, Merrindal (MR) wrote: Hi all, I have recently downloaded mysql version 3.23.45 and I am struggling to get it to start. Every time I type in ./safe_mysqld the program starts and then shuts down immediately with the following being written to the error log: --- mysqld started /usr/local/mysql/libexec/mysqld: Can't find file: './mysql/host.frm' (errno:13) /usr/local/mysql/libexec/mysqld: Normal Shutdown --- Initially there wasn't any 'host.frm' in the mysql home directory but I found one in the mysql/var/mysql directory. I've tried creating a link from the mysql home directory to the host.frm in the mysql/var/mysql directory but this makes no difference. I've tried changing permissions on both the host.frm file and the link so that they were read/write/execute for everybody but this makes no difference. I am running the 'safe_mysqld' command as root. I have run the ./mysql_install_db command which I think has run sucessfully. I received the following message when I ran this command. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Problems starting mysql on sun solaris 8
Hi all, I have recently downloaded mysql version 3.23.45 and I am struggling to get it to start. Every time I type in ./safe_mysqld the program starts and then shuts down immediately with the following being written to the error log: --- mysqld started /usr/local/mysql/libexec/mysqld: Can't find file: './mysql/host.frm' (errno:13) /usr/local/mysql/libexec/mysqld: Normal Shutdown --- Initially there wasn't any 'host.frm' in the mysql home directory but I found one in the mysql/var/mysql directory. I've tried creating a link from the mysql home directory to the host.frm in the mysql/var/mysql directory but this makes no difference. I've tried changing permissions on both the host.frm file and the link so that they were read/write/execute for everybody but this makes no difference. I am running the 'safe_mysqld' command as root. I have run the ./mysql_install_db command which I think has run sucessfully. I received the following message when I ran this command. --- sh-2.03# ./mysql_install_db Installing all prepared tables 020920 11:50:57 /usr/local/mysql/libexec/mysqld: Shutdown Complete To start mysqld at boot time you have to copy support-files/mysql.server to the right place for your system PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! This is done with: /usr/local/mysql/bin/mysqladmin -u root -p password 'new-password' /usr/local/mysql/bin/mysqladmin -u root -h imrahil -p password 'new-password' See the manual for more instructions. NOTE: If you are upgrading from a MySQL = 3.22.10 you should run the /usr/local/mysql/bin/mysql_fix_privilege_tables. Otherwise you will not be able to use the new GRANT command! You can start the MySQL daemon with: cd /usr/local/mysql ; /usr/local/mysql/bin/safe_mysqld You can test the MySQL daemon with the benchmarks in the 'sql-bench' directory: cd sql-bench ; run-all-tests Please report any problems with the /usr/local/mysql/bin/mysqlbug script! The latest information about MySQL is available on the web at http://www.mysql.com Support MySQL by buying support/licenses at https://order.mysql.com --- Does anyone out there have any ideas as to what I might be doing wrong? Regards Mindy - This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. /\\\/\\\/\\\/ / Merrindal (Mindy) Routley / \\\ \\\ \\\ / / Network Design Engineer / /\\\/\\\/\\\/ /87 Peters Ave, Mulgrave / / \\\ \\\ \\\ / PO Box 4112, Mulgrave, Vic, 3170, AUSTRALIA / /\\\/\\\ \\\/ Ph:+61 3 85614263 Fax:+61 3 95609055 Tele-IP Ltd WWW: http://www.tele-ip.com.au - - This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. /\\\/\\\/\\\/ / Merrindal (Mindy) Routley / \\\ \\\ \\\ / / Network Design Engineer / /\\\/\\\/\\\/ /87 Peters Ave, Mulgrave / / \\\ \\\ \\\ / PO Box 4112, Mulgrave, Vic, 3170, AUSTRALIA / /\\\/\\\ \\\/ Ph:+61 3 85614263 Fax:+61 3 95609055 Tele-IP Ltd WWW: http://www.tele-ip.com.au - - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Problems starting MySQL as a Service for all users
Kirk, I am somewhat confused by your question. I must misunderstand what it is that you are trying to ask, because what it appears that you are asking makes no sense. Once MySQL was installed as a service, why does it matter which account starts it? Are you not the admin on the box? Are you trying to start multiple instances of the MySQL service? Logging off of the admin account will not stop a service on a Windows 2000 box. Even though you log off the admin account, MySQL should still be running. Or, when you say started do you mean connect to the running server? What is the output of the following command on the server running MySQL? netstat -a -p tcp Respectfully, Charles Q. At 08:23 PM 6/5/2002 -0500, you wrote: I've installed MySQL as a service using mysqld-nt --install on W2K. No problem there, says service successfully installed. BUT, when I try to log off the admin account and on to the regular power user account MySQL will not start automagically and cannot be started manually. Pop back over to the admin account and MySQL acts like nothing was ever wrong. Is this an issue that can be overcome by manually installing MySQL as a service instead of using the above? And how do you accomplish that? If you know or have heard of this before please help me out; I'd really like to have MySQL running for all users (that would enable the Apache-based site I'm running on the same box to access the database at all times). Thanks! Kirk - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: Problems starting MySQL as a Service for all users
I don't think this makes sense either, but you will see what I mean: FOR MY ADMIN ACCOUNT C:\netstat -a -p tcp Active Connections Proto Local Address Foreign AddressState TCPdynamic:http dynamic:0 LISTENING TCPdynamic:epmap dynamic:0 LISTENING TCPdynamic:microsoft-ds dynamic:0 LISTENING TCPdynamic:1025 dynamic:0 LISTENING TCPdynamic:1027 dynamic:0 LISTENING TCPdynamic:1031 dynamic:0 LISTENING TCPdynamic:3306 dynamic:0 LISTENING TCPdynamic:1031 dynamic:3306 ESTABLISHED TCPdynamic:3306 dynamic:1031 ESTABLISHED TCPdynamic:netbios-ssndynamic:0 LISTENING FOR THE REGULAR USER ACCOUNT C:\netstat -a -p tcp Active Connections Proto Local Address Foreign AddressState TCPdynamic:http dynamic:0 LISTENING TCPdynamic:epmap dynamic:0 LISTENING TCPdynamic:microsoft-ds dynamic:0 LISTENING TCPdynamic:1025 dynamic:0 LISTENING TCPdynamic:1027 dynamic:0 LISTENING TCPdynamic:3306 dynamic:0 LISTENING TCPdynamic:netbios-ssndynamic:0 LISTENING I was under the impression that once something is installed as a service, it is available to the system for all users. This is not the case here. In fact, once I log off admin and onto the other accounts the winmysqladmin manager (which I put in startup for all users) asks if I want to install the service!!! When I click OK it says install failed and I actually have to shut down the tool in order to log off (or else the system hangs). My web site can connect to the server using PHP scripts to grab data with no problems when the admin account is running, but as soon as I log off and on to another account the dynamic part of the site dies. Again, when I was on my admin account I installed the MySQL service from the command prompt using: mysqld-nt --install and the result was service has been installed (paraphrasing). I have uninstalled MySQL completely and reinstalled only to run into the same problem. I'm using the 3.23.49 binary package. -Kirk -Original Message- From: Charles Quesenberry [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 11:25 AM To: Kirk Brannan Babb Cc: [EMAIL PROTECTED] Subject: Re: Problems starting MySQL as a Service for all users Kirk, I am somewhat confused by your question. I must misunderstand what it is that you are trying to ask, because what it appears that you are asking makes no sense. Once MySQL was installed as a service, why does it matter which account starts it? Are you not the admin on the box? Are you trying to start multiple instances of the MySQL service? Logging off of the admin account will not stop a service on a Windows 2000 box. Even though you log off the admin account, MySQL should still be running. Or, when you say started do you mean connect to the running server? What is the output of the following command on the server running MySQL? netstat -a -p tcp Respectfully, Charles Q. At 08:23 PM 6/5/2002 -0500, you wrote: I've installed MySQL as a service using mysqld-nt --install on W2K. No problem there, says service successfully installed. BUT, when I try to log off the admin account and on to the regular power user account MySQL will not start automagically and cannot be started manually. Pop back over to the admin account and MySQL acts like nothing was ever wrong. Is this an issue that can be overcome by manually installing MySQL as a service instead of using the above? And how do you accomplish that? If you know or have heard of this before please help me out; I'd really like to have MySQL running for all users (that would enable the Apache-based site I'm running on the same box to access the database at all times). Thanks! Kirk - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Problems starting MySQL as a Service for all users
FOR MY ADMIN ACCOUNT C:\netstat -a -p tcp TCPdynamic:3306 dynamic:0 LISTENING FOR THE REGULAR USER ACCOUNT C:\netstat -a -p tcp TCPdynamic:3306 dynamic:0 LISTENING ^ The port is available under both accounts - the server is running. I was under the impression that once something is installed as a service, it is available to the system for all users. This is not the case here. In fact, once I log off admin and onto the other accounts I just proove you wrong... Again, when I was on my admin account I installed the MySQL service from the command prompt using: mysqld-nt --install and the result was service has been installed (paraphrasing). I have uninstalled MySQL completely and reinstalled only to run into the same problem. I'm using the 3.23.49 binary package. In your service manager (in the control panel), is the service listed there, and is it started? I personally, don't use the GUI mysqladmin utility. mysql-nt --install installs the service, then I use service manager just like I would for any other service (like IIS) on NT to be started. When you're as a default non admin user account, did you ever try mysql to connect to the server, or even better, telnet to port 3306 ? If so, what errors did you receive back from mysql or the telnet? If you didn't maybe it's time that you do. I doubt this is a service related problem, but I may be wrong... Using the right usernames / passwords / host addresses will also help your cause when you have trouble connecting to the mysql server. -Original Message- From: Charles Quesenberry [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 11:25 AM To: Kirk Brannan Babb Cc: [EMAIL PROTECTED] Subject: Re: Problems starting MySQL as a Service for all users Kirk, I am somewhat confused by your question. I must misunderstand what it is that you are trying to ask, because what it appears that you are asking makes no sense. Once MySQL was installed as a service, why does it matter which account starts it? Are you not the admin on the box? Are you trying to start multiple instances of the MySQL service? Logging off of the admin account will not stop a service on a Windows 2000 box. Even though you log off the admin account, MySQL should still be running. Or, when you say started do you mean connect to the running server? What is the output of the following command on the server running MySQL? netstat -a -p tcp Respectfully, Charles Q. At 08:23 PM 6/5/2002 -0500, you wrote: I've installed MySQL as a service using mysqld-nt --install on W2K. No problem there, says service successfully installed. BUT, when I try to log off the admin account and on to the regular power user account MySQL will not start automagically and cannot be started manually. Pop back over to the admin account and MySQL acts like nothing was ever wrong. Is this an issue that can be overcome by manually installing MySQL as a service instead of using the above? And how do you accomplish that? If you know or have heard of this before please help me out; I'd really like to have MySQL running for all users (that would enable the Apache-based site I'm running on the same box to access the database at all times). Thanks! Kirk - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Problems starting MySQL as a Service for all users
I've installed MySQL as a service using mysqld-nt --install on W2K. No problem there, says service successfully installed. BUT, when I try to log off the admin account and on to the regular power user account MySQL will not start automagically and cannot be started manually. Pop back over to the admin account and MySQL acts like nothing was ever wrong. Is this an issue that can be overcome by manually installing MySQL as a service instead of using the above? And how do you accomplish that? If you know or have heard of this before please help me out; I'd really like to have MySQL running for all users (that would enable the Apache-based site I'm running on the same box to access the database at all times). Thanks! Kirk - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Problems starting mysql
Hello everyone, I have been running mysql for a little while now and my filesystem seems to get a little tight. I decided to setup a file server that would provide one of its disk to act as the mysql data drive. Anyhow, the operation seemed to be quite simple: 1. Mount the new partition using nfs to /new 2. Copy the current mysql data to the new mount (cp -a /old /new) 3. Umount /old 4. Mount /new where /old what mounted 5. Restart mysql Well the problems appears when I try to restart the DB. In fact, mysql does not output any error message to the log files and that's what puzzles me. Here's the output: mysqld started on Thu Sep 20 22:36:47 EDT 2001 mysqld ended on Thu Sep 20 22:36:47 EDT 2001 Here's what I'm using: mysqld Ver 3.22.27 for unknown-linux-gnu on armv4l I know I should upgrade... Any ideas? I'm stumped. This was supposed to be simple. Ciao, P - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
