update from d8 to d9

[naienko]

I'm slow, I know.
Anyway, the update won't go. It says
Can't use an undefined value as a HASH reference at /dw/cgi-bin/DW/User/DVersion/Migrate8To9.pm line 40.
Compilation failed in require at /dw/bin/upgrading/d8d9-userpicrename.pl line 27.
BEGIN failed--compilation aborted at /dw/bin/upgrading/d8d9-userpicrename.pl line 27.

Plus, the update page no longer allows users to select a userpic for their entry, which I'm thinking is somehow related. nevermind, somehow that fixed itself. I don't know.

Comments

[exor674]

You need to update your database first.

http://wiki.dwscoalition.org/notes/Upgrading/Data_Version_9

[naienko]

I did that. Several times. Same error.

[exor674]

Just to make sure, you ran these commands:

$LJHOME/bin/upgrading/update-db.pl -r -p --innodb
$LJHOME/bin/upgrading/update-db.pl -r --cluster=all --innodb
$LJHOME/bin/upgrading/texttool.pl load

Did any of those error when you ran them?

[naienko]

It wasn't erroring, and then I ran those again just to be sure, and I got this on the first one.

Updating cluster: 0
Clock skew of 3 seconds between web([]) and db([])
# Not dropping table openid_external to be paranoid (use --drop)
# Not dropping table userblobcache to be paranoid (use --drop)
# Not dropping table captchas to be paranoid (use --drop)
# Not dropping table zip to be paranoid (use --drop)
# Not dropping table captcha_session to be paranoid (use --drop)
# Not dropping table commenturls to be paranoid (use --drop)
# Not dropping table qotd to be paranoid (use --drop)

cluster: status
0: OKAY

Populating database with base-data.sql.
Failed to read auto-increment value from storage engine at dw/bin/upgrading/update-db.pl line 508, <$fh> line 1207.

[foxfirefey]

Exploratory question:

What happens if you run ljdb? (It's in the dw/bin directory)

[naienko]

It connects right away and gives me a mysql prompt.

[fu]

Hmm, that sounds like it could be a case of this: http://bugs.dwscoalition.org/show_bug.cgi?id=3089

Can you check your proplist ids?

[naienko]

That bug is there. (Sorry, depression ate me.) tpropid went from 10 to 518

[naienko]

Okay. I seem to have made some kind of difference in the error. I tracked the error down to the specific lines, and on the tables in question I removed the auto_increment from the structure, saved, then reapplied it. Then I ran $LJHOME/bin/upgrading/update-db.pl -r -p --innodb again, and it worked properly. I don't know if this is going to be a permanent fix or not.

[fu]

You'll probably need to check that there's no tpropid with the value of 518 in talkprops (not just talkproplist).

On dev environments, we can work around it by restarting the db in between each update db, so that the auto increment resets. This may/may not be workable for you.