Upgrading Drupal

I've installed drupal on my local machine. I use it as Open atrium and it works fine and without error messages.
Now I've upgraded the drupal core at version Drupal 6.16 and got this message:

user warning: Table 'atrium.semaphore' doesn't exist query: SELECT expire, value FROM semaphore WHERE name = 'locale_cache_de' in \atrium-1-0-beta5\includes\lock.inc on line 154.

I don't understand this message and can't fix it.
That's right: I haven't got a table atrium.semaphore/semaphore at my sql-db.

Could you explain the message?

Many thanx for help.

Hi, I'm trying to upgrade my sites from 6.15 to 6.16. The first one worked fine (apart from the semaphore error, which as others have noted, didn't actually affect the upgrade).

I'm trying to update two different sites now, and they are both experiencing the same problem: when I run the update.php, all modules show "no updates available" and when done, I'm still running 6.15.

We Need an upgrade module or something.

I got this big surprise this morning 6.16 Drupal released.

Currently, I maintain 19 Drupal sites.

Some have a large number of 3rd party contributed modules.

It takes most of the day to upgrade all the sites.

Disabling all the 3rd party modules, changing the theme to a default theme, backing up the sites directory, go into Cpanel, identify the database and users then I backup the Mysql, etc.

We really need more efficiency for upgrading.

We just upgraded to 6.16.
A new user tried to register and clicked on the "Check Availability" and he is getting an error: "This username is taken" for any username. We verified that it does this consistently, but that the actual registration does work if people do not try to "verify"

Any idea where to look for either
1- fixing it
2- disabling this button/feature
3- Change the text message above or below to warn people not to use it until it is fixed?

Thanks

I am about to upgrade from 6.15 to 6.16 and was wondering how necessary it was to completely backup my database and turn off all my custom modules. I have a ton of modules and turning them back on it a pain. I have used this other CMS called CMSmadesimple and when there is a small point upgrade all you have to do is copy the new files over the old ones and there is no need to back up or turn off anything. I was just wondering if I just copied the new 6.16 files over the old ones for drupal will it mess up everything. Any advice would be most appreciated.

Just upgraded last night to 6.16 and noticed now that when making changes to a new theme, they aren't being shown in Drupal. I have tried emptying the Cache and re-registering the themes (through the Devel Module). Nothing seems to work. Is this a bug of 6.16?

Is there a way to manually go into the MySQL and reset where Drupal looks for this theme (i.e. to force Drupal to forget the theme)?