Zum Inhalt springen
View in the app

A better way to browse. Learn more.

Fachinformatiker.de

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

schon wieder ein prob mit mysql :-(

Empfohlene Antworten

Veröffentlicht

hi,

ich habe mysql (Version 3.23.49) nochmal neu installiert (linux SuSE 7.3).

Ich bin wie folg vorgegangen:

das tar-file entpackt.

tar -xzf /usr/local/src/lamp/tarballs/mysql-3.23.49.tar.gz

cd /usr/local/src/lamp/mysql-3.23.49/

./configure --prefix=/usr/local/mysql/3.23.49 --localstatedir=/var/mysql/data

make

make install

ln -s /usr/local/mysql/3.23.49 /usr/local/mysql/current

mkdir /var/mysql

mkdir /var/mysql/data

scripts/mysql_install_db

/usr/local/mysql/current/bin/safe_mysqld &

und dann kam folgende Fehlermeldung:

[1] 2028

nazgul:/usr/local/mysql/current # Starting mysqld daemon with databases from /var/mysql/data

020511 14:35:00 mysqld ended

[1]+ Done bin/safe_mysqld

und wenn ich jetzt /usr/local/mysql/curent/bin/mysql -u root starte gibt er folgende Fehlermeldung aus:

ERROR 2002: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (111)

Ich komm einfach nicht weiter!!:rolleyes:

Viele Grüße

nazgul

hier ist die logdatei:

020511 22:47:24 mysqld started

020511 22:47:24 /usr/local/mysql/3.23.49/libexec/mysqld: Can't create/write to file '/var/mysql/data/nazgul.pid' (Errcode: 13)

020511 22:47:24 /usr/local/mysql/3.23.49/libexec/mysqld: Can't find file: './mysql/host.frm' (errno: 13)

020511 22:47:24 /usr/local/mysql/3.23.49/libexec/mysqld: Error on delete of '/var/mysql/data/nazgul.pid' (Errcode: 2)

020511 22:47:24 /usr/local/mysql/3.23.49/libexec/mysqld: Normal shutdown

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 agaist 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=8388600

record_buffer=131072

sort_buffer=2097144

max_used_connections=0

max_connections=100

threads_connected=0

It is possible that mysqld could use up to

key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K

bytes of memory

Hope that's ok, if not, decrease some variables in the equation

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...

Cannot determine thread, fp=0xbf5ff628, backtrace may not be correct.

Stack range sanity check OK, backtrace follows:

0x80aa5a9

0x40032bc4

0x80a9a21

0x80ad838

0x4002ff37

0x401d8baa

New value of fp=(nil) failed sanity check, terminating stack trace!

Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved

stack trace is much more helpful in diagnosing the problem, so please do

resolve it

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains

information that should help you find out what is causing the crash

020511 22:47:24 mysqld ended

020511 14:34:59 mysqld started

020511 14:35:00 /usr/local/mysql/3.23.49/libexec/mysqld: Can't create/write to file '/var/mysql/data/nazgul.pid' (Errcode: 13)

020511 14:35:00 /usr/local/mysql/3.23.49/libexec/mysqld: Can't find file: './mysql/host.frm' (errno: 13)

020511 14:35:00 /usr/local/mysql/3.23.49/libexec/mysqld: Error on delete of '/var/mysql/data/nazgul.pid' (Errcode: 2)

020511 14:35:00 mysqld ended

Dies ist öfters drin, es ist immer nur ein anderes Datum

Viele Grüße

nazgul

Danke!

Jetzt geht es wieder *Juhuuuuuuu*:D

Viele Grüße

nazgul

Archiv

Dieses Thema wurde archiviert und kann nicht mehr beantwortet werden.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.