LINUX.ORG.RU
ФорумAdmin

MySQL 5.1


0

0

/etc/init.d/mysql start Starting service MySQL warning: /var/run/mysql/mysql.sock didn't appear within 30 seconds chmod: cannot access `/var/run/mysql/mysqld.pid': No such file or directory

Естественно я проверил права на /var/run/mysql права есть Пробовал в my.cfg другую папку, не хочет он создавать .pid и .sock

openSUSE 11.3


/var/lib/mysql/хост.err

что в логе ошибок?

Sylvia ★★★★★
()

/var/log/mysql/mysqld.log

100729 8:27:15 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 100729 8:27:15InnoDB: Error: trying to access a stray pointer 0x35087ff8 InnoDB: buf pool start is at 0xb5078000, end at 0xb5878000 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/en/forcing-recovery.html InnoDB: how to force recovery. 100729 8:27:15 InnoDB: Assertion failure in thread 3072739552 in file ../../../storage/innobase/include/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/en/forcing-recovery.html InnoDB: about forcing recovery. 100729 8:27:15 - mysqld got signal 6 ; 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=262144 max_used_connections=0 max_threads=151 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133306 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... stack_bottom = (nil) thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x29) [0x85bd8b9] /usr/sbin/mysqld(handle_segfault+0x4cc) [0x824c49c] [0xffffe400] [0xffffe430] /lib/libc.so.6(gsignal+0x4f) [0xb72917ff] /lib/libc.so.6(abort+0x180) [0xb7293140] /usr/sbin/mysqld(page_cur_search_with_match+0x7f3) [0x8479993] /usr/sbin/mysqld(btr_cur_search_to_nth_level+0x608) [0x840b7e8] /usr/sbin/mysqld(btr_pcur_open_on_user_rec+0x7e) [0x84d4f9e]

mor
() автор топика
Ответ на: комментарий от mor

InnoDB: Error: pthread_create returned 11

ошибка сегментирования , так собрали пакет значит...
проверьте , может уже есть обновления исправленые


можно почистить /var/lib/mysql

и переустановить пакет с mysqld

или воспользоваться mysql_install_db
потом только права надо выставить правильно chown mysql.mysql -R /var/lib/mysql ( я точно не знаю как в OpenSUSE )

Sylvia ★★★★★
()
Ответ на: комментарий от mor

Все права я перепроверил уже, 777 даже выставлял до mysql_install_db не доходил, не поднимается он: mysql_install_db Installing MySQL system tables... 100729 9:22:03 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead. OK Filling help tables... 100729 9:22:03 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead. OK

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! To do so, start the server, then issue the following commands:

/usr/bin/mysqladmin -u root password 'new-password' /usr/bin/mysqladmin -u root -h srv.mor.local password 'new-password'

Alternatively you can run: /usr/bin/mysql_secure_installation

which will also give you the option of removing the test databases and anonymous user created by default. This is strongly recommended for production servers.

See the manual for more instructions.

You can start the MySQL daemon with: rcmysql start

You can test the MySQL daemon with mysql-test package

Please report any problems with the /usr/bin/mysqlbug script!

mysqld_safe 100729 09:22:47 mysqld_safe Logging to '/var/log/mysql/mysqld.log'. 100729 09:22:47 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 100729 09:22:48 mysqld_safe mysqld from pid file /var/lib/mysql/srv.mor.local.pid ended

mor
() автор топика
Ответ на: комментарий от mor

там другая сборка этого пакета, можете взять любой 5.1 если он запустится и будет работать, потом можно будет даже попробовать обновить, может быть с уже созданными базами он будет работать



Sylvia ★★★★★
()
Ответ на: комментарий от Sylvia

Нее, Sylvia, тут что то не то. Вечером приду домой попробую ручками собрать с офф.сайта мускуля

mor
() автор топика
Ответ на: комментарий от mor

Нашел фикс:

This updates fixes several problems with postfix: - using my_print_defaults command for parsing of /etc/my.cnf - using quotation marks: «$PF_CHROOT» - adding sysconfig option POSTFIX_MYSQL_CONN=(socket,tcp) - MYSQL_SOCK_DIR is mounted with '-o bind' to postfix CHROOT now

mor
() автор топика
Ответ на: комментарий от mor

tail srv.mor.local.err

InnoDB: Reading tablespace information from the .ibd files...

InnoDB: Restoring possible half-written data pages from the doublewrite

InnoDB: buffer...

InnoDB: Doing recovery: scanned up to log sequence number 0 37356

100729 11:07:25 InnoDB: Starting an apply batch of log records to the database...

InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed

InnoDB: Error: pthread_create returned 11

100729 11:07:26 mysqld_safe mysqld from pid file /var/run/mysql/mysqld.pid ended

100729 11:30:47 mysqld_safe mysqld from pid file /var/run/mysql/mysqld.pid ended

mor
() автор топика
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.