Kindly asking you for help,
I set up XAMPP, tuned and filled the site with the information CMS Joomla. It took me very long but then I noticed that XAMPP autoloading (startup) was not functioning. I followed lots of various instructions and it looks like that I did something wrong to the access rights to XAMPP catalogues and files - now XAMPP won't start. I've tried to fix it but in vain.
So, if there any way not to get everything back as it was, but, at least, to save the site database ?
Thank you beforehand for any help.
debian:/opt/lampp/bin# /opt/lampp/lampp start
- Code: Select all
Starting XAMPP for Linux 1.7.4-beta4...
XAMPP: Starting Apache with SSL (and PHP5)...
XAMPP: Starting MySQL...
XAMPP: Couldn't start MySQL!
XAMPP: XAMPP-ProFTPD is already running.
XAMPP for Linux started.
http://veloball.ru/
Database Error: Unable to connect to the database:Could not connect to MySQL
http://veloball.ru/phpmyadmin/
Welcome to phpMyAdmin -> #2002 Cannot log in to the MySQL server
/opt/lampp/sbin/mysqld --user=mysql
- Code: Select all
100820 10:37:26 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
100820 10:37:26 [Note] Plugin 'FEDERATED' is disabled.
100820 10:37:26 InnoDB: Started; log sequence number 0 44263
100820 10:37:26 [Note] PrimeBase XT (PBXT) Engine 1.0.11-6 Pre-GA loaded...
100820 10:37:26 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
100820 10:37:26 [Note] The server was not shutdown correctly, recovery required
100820 10:37:26 [Note] Recovering after a crash using tc.log
100820 10:37:26 - 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=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 = 133316 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
/opt/lampp/sbin/mysqld(my_print_stacktrace+0x26)[0x847e346]
/opt/lampp/sbin/mysqld(handle_segfault+0x3ff)[0x81c93df]
[0xb76fa400]
/opt/lampp/sbin/mysqld(_ZN11TC_LOG_MMAP4openEPKc+0x289)[0x826d669]
/opt/lampp/sbin/mysqld[0x81ce775]
/opt/lampp/sbin/mysqld(main+0x1d5)[0x81c9b55]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb735e455]
/opt/lampp/sbin/mysqld[0x8112801]
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.
/opt/lampp/var/mysql/debian.err
- Code: Select all
100820 10:56:15 mysqld_safe Starting mysqld daemon with databases from /opt/lampp/var/mysql
100820 10:56:15 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
100820 10:56:15 [Note] Plugin 'FEDERATED' is disabled.
100820 10:56:15 InnoDB: Started; log sequence number 0 44263
100820 10:56:15 [Note] PrimeBase XT (PBXT) Engine 1.0.11-6 Pre-GA loaded...
100820 10:56:15 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
100820 10:56:15 [Note] The server was not shutdown correctly, recovery required
100820 10:56:15 [Note] Recovering after a crash using tc.log
100820 10:56:15 - 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=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 = 133316 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
/opt/lampp/sbin/mysqld(my_print_stacktrace+0x26)[0x847e346]
/opt/lampp/sbin/mysqld(handle_segfault+0x3ff)[0x81c93df]
[0xb777d400]
/opt/lampp/sbin/mysqld(_ZN11TC_LOG_MMAP4openEPKc+0x289)[0x826d669]
/opt/lampp/sbin/mysqld[0x81ce775]
/opt/lampp/sbin/mysqld(main+0x1d5)[0x81c9b55]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb73e1455]
/opt/lampp/sbin/mysqld[0x8112801]
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.
100820 10:56:15 mysqld_safe mysqld from pid file /opt/lampp/var/mysql/debian.pid ended
debian:~# ls -l /opt/lampp/
- Code: Select all
total 172
drwxrwxrwx 2 root root 12288 2010-08-05 11:13 bin
drwxrwxrwx 2 root root 4096 2004-07-14 18:04 cgi-bin
drwxrwxrwx 3 root root 4096 2009-04-13 20:38 error
drwxrwxrwx 8 root root 4096 2010-08-03 16:45 etc
drwxrwxrwx 5 root root 4096 2010-08-14 00:12 htdocs
drwxrwxrwx 3 root root 4096 2003-05-31 03:38 icons
drwxrwxrwx 3 root root 4096 2010-08-05 11:13 include
-rwxrwxrwx 1 root root 15204 2010-08-05 10:59 lampp
drwxrwxrwx 14 root root 12288 2010-08-13 23:46 lib
drwxrwxrwx 2 root root 4096 2006-04-26 21:46 libexec
drwxrwxrwx 36 root root 4096 2009-08-24 10:52 licenses
drwxrwxrwx 2 root root 4096 2010-08-20 10:56 logs
drwxrwxrwx 6 root root 4096 2010-08-05 11:13 man
drwxrwxrwx 2 root root 4096 2010-08-05 11:13 modules
drwxrwxrwx 11 root root 4096 2010-08-13 23:46 phpmyadmin
-rwxrwxrwx 1 root root 63791 2010-08-04 17:28 RELEASENOTES
drwxrwxrwx 2 root root 4096 2010-08-05 11:13 sbin
drwxrwxrwx 15 root root 4096 2010-08-05 11:07 share
drwxrwxrwx 4 root root 4096 2010-08-14 01:45 tmp
drwxrwxrwx 6 root root 4096 2010-08-20 10:56 var
Any more logs?
