Closed (duplicate)
Project:
Drupal core
Version:
4.7.0-beta2
Component:
update system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Jan 2006 at 12:41 UTC
Updated:
2 Feb 2006 at 14:16 UTC
Step 1
In a freshly copied 4.6.3 DB (working with 4.6.5)
On linking to 4.7.0 beta2
Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'php', 'Unknown column 'referer' in 'field list'\nquery: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'page not found', '<em>node</em> not found.', 1, '', '/interactive470-beta2/', '', '60.226.18.121', 1136205210) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108.', 2, '', '/interactive470-beta2/', '', '60.226.18.121', 1136205210) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108
Home
Page not found
user warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'page not found', '<em>node</em> not found.', 1, '', '/interactive470-beta2/', '', '60.226.18.121', 1136205210) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108.
Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'php', 'Unknown column 'cache' in 'field list'\nquery: UPDATE sessions SET uid = 0, cache = 0, hostname = '60.226.18.121', session = 'messages|a:0:{}', timestamp = 1136205210 WHERE sid = 'c9777ccb740ed2ea9364f863d82b0b78' in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108.', 2, '', '/interactive470-beta2/', '', '60.226.18.121', 1136205210) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108
What the!
Step 2
link to update.php
which returns
Access denied
Access denied. You are not authorized to access this page. Please log in as the admin user (the first user you created). If you cannot log in, you will have to edit update.php to bypass this access check. To do this:
With a text editor find the update.php file on your system. It should be in the main Drupal directory that you installed all the files into.
There is a line near top of update.php that says $access_check = TRUE;. Change it to $access_check = FALSE;.
As soon as the script is done, you must change the update.php script back to its original form to $access_check = TRUE;.
To avoid having this problem in future, remember to log in to your website as the admin user (the user you first created) before you backup your database at the beginning of the update process.
Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'php', 'Unknown column 'cache' in 'field list'\nquery: UPDATE sessions SET uid = 0, cache = 0, hostname = '60.226.18.121', session = 'messages|a:0:{}', timestamp = 1136205422 WHERE sid = 'c9777ccb740ed2ea9364f863d82b0b78' in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108.', 2, '', '/interactive470-beta2/update.php', '', '60.226.18.121', 1136205422) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108
So knowledgeable friends....where do I go next?
I'm off to check whether the DB is nuked or still usable for the 4.6.5 install....luckily I have spare.
Comments
Comment #1
wellsy commentedSo step 3
RTFM or in this case the message in front of you.
So I did as the message suggested.
uploaded the new update.php to the site refreshed and then....
The result was the above
So I ran the script....
and after a long time was presented with
The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.
I'll report back again soon.
Comment #2
wellsy commentedstep 4
I went to the base url of the 4.7.0 beta2 install.
Initially the page came out of cache.
Refreshed and
So where to next gents?
I'll have a further look and see if DB is changed...will report soon.
Comment #3
wellsy commentedughh!
I took a screen shot of the db prior to upgrade but the page was not a the bottom of the screen when I took it so no totals are visible.
No way I can tell if it's changed or not now.
Anyway the 4.6.5 install can still use the database so I guess it must have failed to update eh?
Anyone here know how to proceed?
Comment #4
wellsy commentedOh yeah...using IE6
Comment #5
wellsy commentedDoes anyone know what proceedure to use get some 4.6.3 data into 4.7.0 beta2?
Comment #6
wellsy commentedDuh- I take it there is no proceedure?
So how do I move my 14mb of data to 4.7.0 stable release when that arrives?
Cmon there must be a way guys.
Comment #7
drummThis is not the way to encourage people to provide help.
Can you paste the output of the following SQL query run on your old database before allowing 4.7's update.php to touch it?
SELECT * FROM variable WHERE name LIKE 'update_%';And tell me which columns are in your system table:
DESCRIBE system;Comment #8
wellsy commentedFrom the way this bug report had been ignored I was under the belief that no-one had even read it.
You were the first to follow up since it was posted on the 2nd January.
I have spent many many hours trying to update 4.6.3 database to 4.7.0 beta 1 and 2 and have still not gained anything useful from the experience.
Frankly I have abandoned any further time wasting in this area.
I now await a stable release and confirmation of an update proceedure that works.
I will however do as you request when possible....I am struggling with very limited internet connectivity here at present.
I will report back with answers to your questions as soon as I am able.
Comment #9
wellsy commentedAs requested:
*****************************************************
SELECT *
FROM variable
WHERE name LIKE 'update_%';
no results reported
*****************************************************
DESCRIBE system;
filename varchar(255) PRI
name varchar(255)
type varchar(255)
description varchar(255)
status int(2) 0
throttle tinyint(1) 0
bootstrap int(2) 0
schema_version smallint(2) unsigned 0
*****************************************************
Comment #10
Bèr Kessels commenteddupe of http://drupal.org/node/46934
The tone in this issue is way too grim
Comment #11
wellsy commentedyep....it's grim when a detailed issue gets a grand total of two responces from the community and neither of those is of any assistance.
Both merely chastise me for my negative attitude. What do you expect my attitude to be when a valid issue report is ignored by all?
As mentioned I no longer waste my time with trying to get data into 4.7 beta. It simply does not work!
Oh, by the way, is there any possibility that data will be easily migrated to 4.7 release candidate?
No answer ever came to that question.
Comment #12
Bèr Kessels commentedplease post any constructive posts to the new thread. Thanks.