Új hozzászólás Aktív témák

• #2550 lezso6 HÁZIGAZDA VladimirR #2549

  Új Válasz 2008-08-05 18:15:22 #2550

  Új hozzászólás

  Összes hozzászólása itt Válaszok az összes hozzászólására itt Válaszok erre a hozzászólásra

  Privát üzenet küldése

  

  lezso6

  HÁZIGAZDA

  LOGOUT blog (1)

  válasz VladimirR #2549 üzenetére

  Köszi, megcsináltam amit írtál, és az etch-es sorokat írtam csak be, ha ez jó.
  A mysql-server telepítésnél valami hibát jelez a cucc. Mi akar lenni az alábbi?
  Valami pluszt még fel kéne tenni előtte? Mindig ezt írja. (bocsia hosszúságért )

  h-241:~# apt-get install mysql-server-5.0
  Reading package lists... Done
  Building dependency tree... Done
  Suggested packages:
  tinyca
  The following NEW packages will be installed:
  mysql-server-5.0
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0B/25.2MB of archives.
  After unpacking 67.7MB of additional disk space will be used.
  WARNING: The following packages cannot be authenticated!
  mysql-server-5.0
  Install these packages without verification [y/N]? y
  Preconfiguring packages
  ...
  [...]
  ...
  Selecting previously deselected package mysql-server-5.0.
  (Reading database ... 12854 files and directories currently installed.)
  Unpacking mysql-server-5.0 (from .../mysql-server-5.0_5.0.32-7etch6_i386.deb) ...
  Setting up mysql-server-5.0 (5.0.32-7etch6) ...
  Stopping MySQL database server: mysqld.
  080805 16:09:05 [Warning] Ignoring user change to 'mysql' because the user was set to 'root' earlier on the command line
  
  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 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=131072
  max_used_connections=0
  max_connections=100
  threads_connected=0
  It is possible that mysqld could use up to
  key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K
  bytes of memory
  Hope that's ok; if not, decrease some variables in the equation.
  
  thd=(nil)
  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=0x42302158, backtrace may not be correct.
  Stack range sanity check OK, backtrace follows:
  0x81c06b9
  (nil)
  0x4027c01e
  New value of fp=(nil) failed sanity check, terminating stack trace!
  Please read http://dev.mysql.com/doc/mysql/en/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/en/Crashing.html contains
  information that should help you find out what is causing the crash.
  Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
  invoke-rc.d: initscript mysql, action "start" failed.
  dpkg: error processing mysql-server-5.0 (--configure):
  subprocess post-installation script returned error exit status 1
  Errors were encountered while processing:
  mysql-server-5.0
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  h-241:~#

  Még annyi van hogy a servernek 64 mega memóriája van, de a kondigurációs fájlba az van írva, hogy az ott lévő konfignak elég 32 is.

Új hozzászólás Aktív témák