SSN — это Social secyrity number ( Это в америка она гражданам и еще некоторым лицам выдаеться )
А EIN — я даже не знаю что это.
top-places.ru
top-place.ru
offersjob.ru
Оцените пожалуйста
Пароли сменил. Коды удалил вроде как.
Спасибо огромное!!!
А где такое?
Ап. Возьму заказ с новогодней скидкой.
А если сайт 2008, имееться в вебархиве, но в данный момент свободный, то значит ему почти 3 года?
Там беки с яндекс —51, и яндекс блоги — 13. Что думаете?
Отписал....
101223 13:39:53 InnoDB: Started; log sequence number 0 59557458
InnoDB: !!! innodb_force_recovery is set to 4 !!!
101223 13:39:53 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.51a-24+lenny1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
101223 13:39:54InnoDB: Assertion failure in thread 3013704592 in file dict0load.c line 369
InnoDB: Failing assertion: ut_dulint_cmp(table->id, mach_read_from_8(field)) == 0
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.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
101223 13:39:54 - 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=2097152
read_buffer_size=131072
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 219647 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thdxa27b068
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, fpxb3a13088, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81f3821
0x8346440
0x8342d18
0x82b61f9
0x82aa2df
0x8236c1d
0x822cfa8
0x822f4e1
0x822fb03
0x822fde7
0x82e52a1
0x82dd1f0
0x8255625
0x82520ab
0x8257196
0x82074dc
0x820de0e
0x8210793
0x821121a
0x8211b94
0x89ff3b
0x4bfbee
New value of fpnil) 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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xa2b3990 = SELECT CONCAT('SELECT COUNT(*) INTO @discard FROM `',
TABLE_SCHEMA, '`.`', TABLE_NAME, '`' )
FROM information_schema.TABLES WHERE ENGINE='MyISAM'
thd->thread_id=6
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.
101223 13:39:54 InnoDB: Started; log sequence number 0 59557458
101223 13:39:54 [Note] /usr/sbin/mysqld: ready for connections.
wiefix добавил 23.12.2010 в 16:46
Что это можетбыть?
