By whatever- on

After updating from 6.15 to 6.16 I'm getting this error in a lot of pages:

user warning: Table 'xviisinfo.drupal_semaphore' doesn't exist query: SELECT expire, value FROM drupal_semaphore WHERE name = 'locale_cache_pt-pt' in /home/sinfo/public_html/XVII/includes/lock.inc on line 154.

I have a feeling it has to do with the new "locking framework for long running operations"
http://drupal.org/node/251792

⋅ Categories: Drupal 6.x

Comments

Duplika’s picture

Duplika commented

Make sure you ran update.php. That error is normal after uploading the upgrade, that table doesn't exist until you execute the update.

zajicew’s picture

zajicew commented

confirmed.

astiak’s picture

astiak commented

It adds the necessary tables once you run update.php

enzo de simone’s picture

enzo de simone commented

I have the same problem that repeats on all sites where I uploaded the version 6.16

user warning: Table 'xxxxxxx_nuovo09.semaphore' doesn't exist query: SELECT expire, value FROM semaphore WHERE name = 'locale_cache_it' in /home/xxxxxx/public_html/includes/lock.inc on line 154.

and when I make update.php:

<!--[if lt IE 7]>
Fatal error: Call to undefined function phptemplate_get_ie_styles() in /home/xxxxxxx/public_html/themes/garland/maintenance-page.tpl.php on line 23
j0nathan’s picture

j0nathan commented

Hi,
I have the same problem when running update.php from 6.15 to 6.16:

<!--[if lt IE 7]>
Fatal error: Call to undefined function phptemplate_get_ie_styles() in /home/xxxxxxx/public_html/themes/garland/maintenance-page.tpl.php on line 23

I tried to remove the line 22, 23 and 24 in maintenance-page.tpl.php, but I got this error:

Fatal error: Call to undefined function phptemplate_body_class() in xxxxx/themes/garland/maintenance-page.tpl.php on line 26

So I rolled back to 6.15 and I am not able to update to 6.16.

knarzer77’s picture

knarzer77 commented

Hello,

i got a simular message while upgrading from 6.15 to 6.16:
user warning: Table 'db312195650.drupal_semaphore' doesn't exist query: SELECT expire, value FROM drupal_semaphore WHERE name = 'locale_cache_de' in /homepages/43/d98906702/htdocs/.../includes/lock.inc on line 154.

Jan

AdrianB’s picture

AdrianB commented

I had this as well. Figured it was nothing to worry about.

glassonline.ru’s picture

glassonline.ru commented

I have the same problem :( What to do?

Azol’s picture

Azol commented

You can safely ignore the error message, because the table will be created as soon as update.php runs:

Update #6054
CREATE TABLE {semaphore} ( `name` VARCHAR(255) NOT NULL DEFAULT '', `value` VARCHAR(255) NOT NULL DEFAULT '', `expire` DOUBLE NOT NULL, PRIMARY KEY (name), INDEX expire (expire) ) /*!40100 DEFAULT CHARACTER SET UTF8 */

This table didn't exist in earlier versions of Drupal.

federico’s picture

federico commented

Same problem, but i can't run update.php , it stucks at 'Run updates'.

I had temporarily disabled javascript, that caused update.php to stop. Now it works.

jozo.starosta’s picture

jozo.starosta commented

Sorry for posting this in various forum topics. By doing that, I hope that it can get sooner to a proper person who can fix it.
The original posting:
I have, actually, tried to upgrade from Drupal 6.10 to Drupal 6.16
that means, the following upgrades had to applied:
6050
6051
6052
6053
6054
6055

Immediately after trying to run 6050 I got this message:
• An unrecoverable error has occurred. You can find the error message below. It is advised to copy it to the clipboard for reference.
Please continue to the error page
• An HTTP error 0 occurred. http://www.laurelfoundation.ca/update.php?id=3&op=do
When I click the "error page":
• user warning: Table 'laurel314.laurel_semaphore' doesn't exist query: SELECT expire, value FROM laurel_semaphore WHERE name = 'menu_rebuild' in /home/9/d/c/2753/2753/public_html/includes/lock.inc on line 154.
• user warning: Table 'laurel314.laurel_semaphore' doesn't exist query: SELECT expire, value FROM laurel_semaphore WHERE name = 'menu_rebuild' in /home/9/d/c/2753/2753/public_html/includes/lock.inc on line 154.
The update process was aborted prematurely while running update #6050 in system.module. All errors have been logged. You may need to check the watchdog database table manually.
The "transcript" of the whole sequence of steps I have done is in http://drupal.org/files/issues/6.10-6.16.pdf.

What went wrong?
How can I upgrade from 6.10 to 6.16?

Ole Martin’s picture

Ole Martin commented

I got the this error message, but it was not possible to run update.php. Come only an error message on the screen without that I could go on
Message:

Fatal error: Call to undefined function phptemplate_get_ie_styles()() in /homexxxxxxxxxxxxx/themes/garland/maintenance-page.tpl.php on line xx"

j0nathan’s picture

j0nathan commented

Hi,
I've found an issue about this:
#732714: Call to undefined functions in garland/maintenance-page.tpl.php

Oshun’s picture

Oshun commented

Hello All.

I received that same error message, but now something else is not working correctly. I can login to my site, but I can't perform any administration functions.

Anytime I click on something a pop up window comes up with a camera that has a circle around it and a line through it.

I have no idea what I did wrong. Or how to correct.

Oshun’s picture

Oshun commented

I reloaded my older version of the database and everything works fine. I think there is something funny occurring when I update the databases. I still get the same error message as listed above, but at least the site functions now i.e. I can login and perform admin functions.

FnF’s picture

FnF commented

This can also be caused by improper permissions.

After uploading and extracting the update files, the permissions may be changed to 777. Which will cause that error if you run update.php as is, on some servers.

Change permissions on all new files after they are uploaded and extracted, to 0644, add "X" to directories, be sure to perform it recursively.

Then go ahead and run update.php, you should be good to go.

Rafael Lages’s picture

Rafael Lages commented

Im stucked at this point, there's any solution?

thanks

jasonm0928’s picture

jasonm0928 commented

I went to one of my drupal 6.15 sites and ran update.php to see what version of the system module it was on which was 6053. I noticed that when you upgrade to drupal 6.16 it added two new upgrade versions. 6054 and 6055. What I had done was run the 6055 update but not hte 6054 then 6055. I went back and ran the 6054 upgrade and it added the semaphore table and the errors were no more. I hope this helps someone.

BrianBZD’s picture

BrianBZD commented

Alright, I've been working on this for a few hours now.
I think I finally found the solution (for me at least).

First, I went into the settings.php. I commented out $base_url:
# $base_url = 'http://URL.org'; // NO trailing slash!

Then, I reloaded the page. I had to re-login (site was offline) by going to: URL/?q=user
and logged in under the original admin account

Then I ran: URL/update.php
ran the 6054 update (semaphore tables were thus created, FINALLY!!)

Went back to URL/update.php to try and 6055 update. But that failed "Can't DROP" SQL syntax as well as "Duplicate key name" errors.

Running the status report though said that everything is fine, so I am thinking I won't worry about it.

EXCEPT: Now user login doesn't work!!! Any and all users have to login through URL/?q=user, and the login block is useless.
**UPDATE: Had to go back in to the settings.php > commented out $base_url line. Don't know why this doesn't work (has something to do with .htaccess rewrite rules) and now login works.

Will update when I figure that out, or reply here if you know a fix.

Additionally, it was tricky to get the site back online. I had to un-comment the $base_url line. Then log off. Then go back to URL/?q=user, re-login.

The site is back up and running, and everything seems fine and updated to 6.16

jvieille’s picture

jvieille commented

I got this error on about half of my sites (multi-site config) when running update.php after loading D6.16 on D6.15
I ran update.php once more and the semaphor table creation proceeded then normally.

JV

Ole Martin’s picture

Ole Martin commented

I got this error message on a completely new installation (6.16) "

". This happened when I went from Garland to YaST (http://drupal.org/project/yast) So for me it was a theme issue. Went back to Garland and the problem disappeared