11 messages in com.mysql.lists.win32Re: Problems starting from the comman...| From | Sent On | Attachments |
|---|---|---|
| Patrice Serrand | 09 Dec 2005 06:55 | |
| Daniel da Veiga | 09 Dec 2005 07:09 | |
| Jorge Bastos | 09 Dec 2005 07:37 | |
| Patrice Serrand | 09 Dec 2005 11:16 | |
| Daniel da Veiga | 09 Dec 2005 11:26 | |
| Ken Resander | 11 Dec 2005 02:13 | |
| Richard AB | 11 Dec 2005 06:59 | |
| jbon...@sola.com.au | 11 Dec 2005 13:36 | |
| Patrice Serrand | 12 Dec 2005 06:42 | |
| Daniel da Veiga | 12 Dec 2005 07:08 | |
| Patrice Serrand | 12 Dec 2005 07:25 |
| Subject: | Re: Problems starting from the command line using 5.0.16![]() |
|---|---|
| From: | Richard AB (rica...@uol.com.br) |
| Date: | 12/11/2005 06:59:21 AM |
| List: | com.mysql.lists.win32 |
Hello.
It seems that your server is doing fine. As your log said, your server is good and ready for connections.
When you try to connect to mysql on windows and don´t inform a user name mysql use the default user ODBC. That´s because you got the permission denied error on one of your tries.
When you install mysql on windows (and all others OS) a user named root without a password is configured.
I think you already have a server running on your machine. Your just need to connect to it. Open your command line prompt and type 'mysql -u root' (without apostrofes), (on mysql bin directory 'C:\Program Files\MySQL\MySQL Server 5.0\bin' because i think it is not on your path).
Or use your prefered windows client for mysql to connect to server. Just remember that user is root and the password is empty.
After connected remember to set some password to your root account.
Good luck.
Richard AB.
----- Original Message ----- From: "Ken Resander" <resa...@speed.info.com.ph> To: <win...@lists.mysql.com> Sent: Sunday, December 11, 2005 7:13 AM Subject: Problems starting from the command line using 5.0.16
Here is a blow-by-blow account....
1. downloaded Essentials package and installed.
selections from Config Wizard were: Configration Type: Detailed Configuration Server Type: Developer machine Usage Type: Multifunctional Database (includes Innodb)
Outcome: the server did not start (also tried mysqld-nt from command line and found that Innodb had crashed/aborted)
2. uninstalled Mysql 5.0 and deleted mysql50 in Program Files - reinstalled
selections from Config Wizard were same except: Usage Type: Non-Transactional Database (does not include Innodb)
Outcome: server starts, but when running mysql/mysqlshow from command line I got message 'ERROR 1045 <28000> Access denied for user 'ODBC'@'localhost (using password NO)
3. uninstalled Mysql 5.0 and deleted mysql50 in Program Files - reinstalled
selection from Config Wizard were: Configration Type: Standard Configuration
Outcome : same as 2 above. Here is the content of the log for attempt 3:
'InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 051211 17:18:08 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 051211 17:18:10 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 10 MB InnoDB: Database physically writes the file full: wait... 051211 17:18:12 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file .\ib_logfile1 size to 10 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 051211 17:18:17 InnoDB: Started; log sequence number 0 0 051211 17:18:25 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections. Version: '5.0.16-nt' socket: '' port: 3306 Official MySQL binary'
from which it would appear that InnooDB started OK.
What might be the problem?
I am totally stuck, so would appreciate advice.
Best regards Ken Resander
--------------------------------------------------------------------------------
No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.13.12/194 - Release Date: 07/12/2005
-- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.13.13/197 - Release Date: 09/12/2005




