Salve, sto provando a lanciare mysql su vista ma compare un errore grave.
Ho effettuato la configurazione ma senza installare il server come servizio, quando ne ho bisogno lo vorrei lanciare da console.
Questo è l'errore quando lancio mysqld --console
Questo è il percorso di c:\MySQL Datafilescodice:;InnoDB: End of page dump 081018 10:40:20 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432 InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0 InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0 InnoDB: Page number (if stored to page already) 0, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be a freshly allocated page 081018 10:40:20InnoDB: Error: trying to access a stray pointer 85663FF8 InnoDB: buf pool start is at 05654000, end at 08554000 InnoDB: Probable reason is database corruption or memory InnoDB: corruption. If this happens in an InnoDB database recovery, see InnoDB: http://dev.mysql.com/doc/refman/5.1/...-recovery.html InnoDB: how to force recovery. 081018 10:40:20 InnoDB: Assertion failure in thread 4532 in file F:\build\mysql -6.0.6-alpha-winbuild\mysql-community-nt-6.0.6-alpha-build\storage\innobase\incl ude\buf0buf.ic line 264 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/...-recovery.html InnoDB: about forcing recovery. 081018 10:40:20 - mysqld got exception 0xc0000005 ; 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=26214400 read_buffer_size=65536 max_used_connections=0 max_threads=100 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58243 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x0 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... 00724084 mysqld.exe!??? The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash.
Ho disabilitato il controllo utente in vista.
Seguendo uno dei link di cui sopra ho provato ad inserire nel file my.ini il seguente parametro
innodb_force_recovery = 4
ma ovviamente non ha funzionato quando ho poi rilanciato mysqld.
So che probabilmente funzionerebbe installandolo come servizio di windows ma a me serve lanciarlo solo quando necessario.
Qualche idea?
Rispondi quotando
