By International Link on

Dear Sir / madam,

Please help me!!!
after i login this morning and when i read it @ afternoon the following message display and my website couldnt be read

Error
The website encountered an unexpected error. Please try again later. Error messagePDOException: SQLSTATE[HY000]: General error: 1033 Incorrect information in file: './inteecom_drup1/drup_semaphore.frm': SELECT expire, value FROM {semaphore} WHERE name = :name; Array ( [:name] => variable_init ) in lock_may_be_available() (line 165 of /home/inteecom/public_html/home/includes/lock.inc).

how can i solve this problem???

please help

Link

⋅ Categories: Drupal 7.x

Comments

International Link’s picture

International Link commented

and also the following message at the foot of my website

"Uncaught exception thrown in shutdown function.
PDOException: SQLSTATE[HY000]: General error: 1033 Incorrect information in file: './inteecom_drup1/drup_semaphore.frm': DELETE FROM {semaphore} WHERE (value = :db_condition_placeholder_0) ; Array ( [:db_condition_placeholder_0] => 12187154914dfef707cd5803.04192303 ) in lock_release_all() (line 247 of /home/inteecom/public_html/home/includes/lock.inc)."

please help

nfriend’s picture

nfriend commented

Were you able to figure this out? I was away from a perfectly working D7 site for about a week - still in development - and the same message greeted me - even my hosts backups prior to my last working date get this error?

Thanks in advance.
-Neil

renrez’s picture

renrez commented

I too am experiencing this issue, my site was working fine and now this error is appearing.

I am running 7.4

Lakeside’s picture

Lakeside commented

By any chance is your site hosted on GreenGeeks?

So far this has happened twice in three weeks.

The fix is to upload Drupal's core files. The database should still be intact.

Lakeside’s picture

Lakeside commented

AGAIN! It happened.

The hosting company had sent out an email saying that they were upgrading.

This time I sent the error message to customer support, which promptly upgraded it to level two. Soon thereafter someone from support sent an email saying that the problem was fixed--and it was (for now).

mudsurfer’s picture

mudsurfer commented

I have that error on a set of sites I have with GreenGeeks.com
They had a server crash about 12 hours ago, and when the webserver came back up, it looked like the MySQL services had not all started correctly. Support advised they started MySQL without the InnoDB component - they are trying to rectify now.
Earlier this morning all my sites were inaccessible (D6 and D7), but now it looks like the D6 sites are working, but the D7 sites are all throwing this error.
I had been very happy with Greengeeks - very cheap, and custoemr service response has been good, but now they are doing a table restore in database, and have it scheduled for 6 hours from now.
I suspect that is Ok for middle of the night in most of US, but that means the sites are down for my users all day today in Australia...
I might have to pay more for Australian hosting...

With regard to "the fix is to upload Drupal's core files", can you describe exactly what you have done to get a fix? Did you unpack a drupal core into the site via cpanel webftp, or otherwise? You don't know if there is a specific file rather than the whole core?

Thanks :)

Chris-G2unit’s picture

Chris-G2unit commented

Same error, and hosted at GreenGeeks too. I've just contacted support through their LiveChat. Here is their answer: "Our engineers are working diligently to restore service as soon as possible, because of the nature of the incident, there is no ETA. However, we will keep it to a minimum as much as we can.". I've given them the link to this thread, hoping it will help reducing the delay till recovery...

karenann’s picture

karenann commented

Encountered this recently and the issue was that an admin ran some database scripting assuming that all databases were InnoDB. Ours was MyISAM. This was the resulting error.