- Home
- Categorie
- Coding e Sistemistica
- Hosting e Cloud
- problemi avvio mysql
- 
							
							
							
							
							
problemi avvio mysqlciao a tutti 
 spero di essere nella sezione giusta e che qualcuno possa aiutarmi!
 premetto che non capisco nulla di php o html, ecco perchè da un paio d'anni lavoro al mio sito personale con mamp (su macbook con sistema operativo snowleopard) e joomla per poter "sperimentare" anche in locale prima di pubblicare sul web.
 qualche giorno fa ho installato lion ed ecco che all'apertura di mamp si avvia apache ma non mysql; ho cambiato porte ma niente, ho disinstallato e reinstallato ma niente....
 a questo punto ho resettato mac e reinstallato il vecchi snowleopard
 riscaricato dal sito ufficiale mamp e installato nuovamente...niente!
 se qualcuno può dirmi cosa posso fare, se controllare qualche file e dove trovarlo ecc....
 grazie mille
 
- 
							
							
							
							
							
I log ti dicono cos'è che non va. Non so esattamente dove mamp li mette quindi dovresti cercare un pò sul disco. 
 
- 
							
							
							
							
							
ci sono 2 files nella cartella "logs" 
 apache_error.log
 mysql_error_log.err:
 111013 13:55:24 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql
 111013 13:55:25 [Warning] You have forced lower_case_table_names to 0 through a command-line option, even though your file system '/Applications/MAMP/db/mysql/' is case insensitive. This means that you can corrupt a MyISAM table by accessing it with different cases. You should consider changing lower_case_table_names to 1 or 2
 111013 13:55:25 [Warning] One can only use the --user switch if running as root111013 13:55:25 [Note] Plugin 'FEDERATED' is disabled. 
 111013 13:55:25 InnoDB: The InnoDB memory heap is disabled
 111013 13:55:25 InnoDB: Mutexes and rw_locks use GCC atomic builtins
 111013 13:55:25 InnoDB: Compressed tables use zlib 1.2.3
 111013 13:55:25 InnoDB: Initializing buffer pool, size = 128.0M
 111013 13:55:25 InnoDB: Completed initialization of buffer pool
 InnoDB: The first specified data file ./ibdata1 did not exist:
 InnoDB: a new database to be created!
 111013 13:55:25 InnoDB: Setting file ./ibdata1 size to 10 MB
 InnoDB: Database physically writes the file full: wait...
 111013 13:55:26 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
 InnoDB: Setting log file ./ib_logfile0 size to 5 MB
 InnoDB: Database physically writes the file full: wait...
 111013 13:55:26 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
 InnoDB: Setting log file ./ib_logfile1 size to 5 MB
 InnoDB: Database physically writes the file full: wait...
 InnoDB: Doublewrite buffer not found: creating new
 InnoDB: Doublewrite buffer created
 InnoDB: 127 rollback segment(s) active.
 InnoDB: Creating foreign key constraint system tables
 InnoDB: Foreign key constraint system tables created
 111013 13:55:27 InnoDB: 1.1.5 started; log sequence number 0
 111013 13:55:27 [Note] Event Scheduler: Loaded 0 events
 111013 13:55:27 [Note] /Applications/MAMP/Library/bin/mysqld: ready for connections.
 Version: '5.5.9' socket: '/Applications/MAMP/tmp/mysql/mysql.sock' port: 8889 Source distribution
 111013 13:55:30 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql
 111013 13:55:30 [Warning] You have forced lower_case_table_names to 0 through a command-line option, even though your file system '/Applications/MAMP/db/mysql/' is case insensitive. This means that you can corrupt a MyISAM table by accessing it with different cases. You should consider changing lower_case_table_names to 1 or 2
 111013 13:55:30 [Warning] One can only use the --user switch if running as root111013 13:55:30 [Note] Plugin 'FEDERATED' is disabled. 
 111013 13:55:30 InnoDB: The InnoDB memory heap is disabled
 111013 13:55:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins
 111013 13:55:30 InnoDB: Compressed tables use zlib 1.2.3
 111013 13:55:30 InnoDB: Initializing buffer pool, size = 128.0M
 111013 13:55:30 InnoDB: Completed initialization of buffer pool
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 111013 13:55:30 InnoDB: Retrying to lock the first data file
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 111013 13:55:40 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql
 111013 13:55:40 [Warning] You have forced lower_case_table_names to 0 through a command-line option, even though your file system '/Applications/MAMP/db/mysql/' is case insensitive. This means that you can corrupt a MyISAM table by accessing it with different cases. You should consider changing lower_case_table_names to 1 or 2
 111013 13:55:40 [Warning] One can only use the --user switch if running as root111013 13:55:40 [Note] Plugin 'FEDERATED' is disabled. 
 111013 13:55:40 InnoDB: The InnoDB memory heap is disabled
 111013 13:55:40 InnoDB: Mutexes and rw_locks use GCC atomic builtins
 111013 13:55:40 InnoDB: Compressed tables use zlib 1.2.3
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 111013 13:55:40 InnoDB: Initializing buffer pool, size = 128.0M
 111013 13:55:40 InnoDB: Completed initialization of buffer pool
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 111013 13:55:40 InnoDB: Retrying to lock the first data file
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 111013 13:55:42 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql
 111013 13:55:42 [Warning] You have forced lower_case_table_names to 0 through a command-line option, even though your file system '/Applications/MAMP/db/mysql/' is case insensitive. This means that you can corrupt a MyISAM table by accessing it with different cases. You should consider changing lower_case_table_names to 1 or 2
 111013 13:55:42 [Warning] One can only use the --user switch if running as root111013 13:55:42 [Note] Plugin 'FEDERATED' is disabled. 
 111013 13:55:42 InnoDB: The InnoDB memory heap is disabled
 111013 13:55:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
 111013 13:55:42 InnoDB: Compressed tables use zlib 1.2.3
 111013 13:55:42 InnoDB: Initializing buffer pool, size = 128.0M
 111013 13:55:42 InnoDB: Completed initialization of buffer pool
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 111013 13:55:42 InnoDB: Retrying to lock the first data file
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 111013 13:55:43 mysqld_safe Starting mysqld daemon with databases from /Applications/MAMP/db/mysql
 111013 13:55:43 [Warning] You have forced lower_case_table_names to 0 through a command-line option, even though your file system '/Applications/MAMP/db/mysql/' is case insensitive. This means that you can corrupt a MyISAM table by accessing it with different cases. You should consider changing lower_case_table_names to 1 or 2
 111013 13:55:43 [Warning] One can only use the --user switch if running as root111013 13:55:43 [Note] Plugin 'FEDERATED' is disabled. 
 111013 13:55:43 InnoDB: The InnoDB memory heap is disabled
 111013 13:55:43 InnoDB: Mutexes and rw_locks use GCC atomic builtins
 111013 13:55:43 InnoDB: Compressed tables use zlib 1.2.3
 111013 13:55:43 InnoDB: Initializing buffer pool, size = 128.0M
 111013 13:55:43 InnoDB: Completed initialization of buffer pool
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 111013 13:55:43 InnoDB: Retrying to lock the first data file
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.
 InnoDB: Unable to lock ./ibdata1, error: 35
 InnoDB: Check that you do not already have another mysqld process
 InnoDB: using the same InnoDB data or log files.queste ultime righe ripetute quasi all'infinito! 
 
- 
							
							
							
							
							
C'è un lock file presente che va cancellato. Ti conviene eliminare httpd.pid in MAMP/Library/logs/ e mysql.pid in MAMP/tmp/mysql/. Poi riavviare sia apache che mysql. 
 
- 
							
							
							
							
							
gli unici file che ho trovato in MAMP/Library/logs/ sono questi: 
 httpd-mpm.conf
 httpd-mpm.conf
 httpd.confper quello che riguarda mysql.pid non ho trovato nulla in nessuna cartella! 
 
- 
							
							
							
							
							
mi correggo....nel percorso mamp/library/logs non ho nessun file! 
 
- 
							
							
							
							
							
Sul sito di mamp dicono che i log si trovano qui /Applications/MAMP/logs mentre mysql.pid si trova in /Applications/MAMP/tmp/mysql/ occhio che potrebbe essere nascosti e quindi visibili solo da terminale