5.5.5 to 5.5.6 - upgrade losing will to live

[John.Ross]

Hello Fellas

After a very long evening upgrading everything which used to be a slam dunk in V4 I am now hitting Internal 500 errors so I cannot even access the upgrade scripts

I am either over tired and cant see the issue or it is really an error.

Set new .htaccess for https
Fill in usual details in config.php
Upload new 5.5.6 and overwrite files
https://www.hillmanimp.org/core/install/upgrade.php and I get 500 internal sever error

[In Omnibus]

Are you running PHP 7.1 or higher and SQL 5.6 or higher?
Have you edited both config.php files?
Is your .htaccess file updated and renamed?

[John.Ross]

Forums were fin on 5.5.5 had to go sleep though so I left the restore running so now forums are back as 5.5.5

Yes, renamed to .htaccess and uncommented

RewriteCond %{HTTPS} !=on
RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R=301,L]

Renamed config to config.php

In core only rename file config.php.new to config.php and apply usual edits

Thats 5.5.6 prepped, upload files (overwrite all) then run /core/install/upgrade.php

Anything I forgot ?

- J

[Mark.B]

We need the full scenario here. If you are already on 5.5.5, why are you changing the .htaccess and config files?

[John.Ross]

Mark

Sorry for the piece meal information, my eyes were literally closing last night

I was prepping the supplied /.htaccess and config files within the upload folder in the 5.5.6 download ready to upload over 5.5.5

The old files have been uploaded back in place and it is working so I will go back over the same path again in case the upload failed although nothing is in the failed transfer queue in Filezilla

[John.Ross]

OK, now I have a list of startup warnings which I assume is the files no longer needed so will continue with the update

John

[John.Ross]

Hmmmmm

Got rid of all warnings except the MD5 write which after settong to 400 still would not clear warning

The upgrade went as far as this



5.5.6
5.5.6

vbulletin-style.xml:
vbulletin-settings.xml:

5.5.6
5.5.6

vbulletin-language.xml:
vbulletin-adminhelp.xml:

vBulletin 5.5.6 Upgrade System
(Please be patient as some parts may take some time)
Upgrading to 5.5.6
Status: Aborted
50%
final Step #4

Fatal Error Occurred
Call to a member function fetch_userinfo() on null on /home1/nxonesix/public_html/hillmanimp/core/includes/functions.php : 1846

Script: final
Step: 4

[John.Ross]

Actual message

• 5.5.6
• 5.5.6

• vbulletin-style.xml:
• vbulletin-settings.xml:

• 5.5.6
• 5.5.6

• vbulletin-language.xml:
• vbulletin-adminhelp.xml:

vBulletin 5.5.6 Upgrade System
(Please be patient as some parts may take some time)


Upgrading to 5.5.6
Status: Aborted
50%














Upgrade Progress

• Upgrading to 5.5.6 Alpha 1
• Step 1 - Skipping step, not needed
• Upgrading to 5.5.6 Alpha 2
• Step 1 - Altering notice Table (1 of 1)
• Step 2 - Updating routenew table
• Step 3 - Rebuild datastore 'noticecache'.
• Step 4 - Altering profilefield table
• Step 5 - Updating datastore profile fields definition
• Upgrading to 5.5.6 Alpha 3
• Step 1 - Updating setting table (1 of 1)
• Step 2 - Altering smilie Table (1 of 1)
• Upgrading to 5.5.6 Alpha 4
• Step 1 - Skipping step, not needed
• Step 2 - Skipping step, not needed
• Upgrading to 5.5.6 Beta 1
• Upgrading to 5.5.6 Beta 2
• Upgrading to 5.5.6 Release Candidate 1
• Upgrading to 5.5.6 Release Candidate 2
• Upgrading to 5.5.6 Release Candidate 3
• Upgrading to 5.5.6
• Processing XML
• Step 1 - Import latest options
• Importing vbulletin-settings.xml
• Import Done
• Step 2 - Import latest admin help
• Importing vbulletin-adminhelp.xml
• Import Done
• Step 3 - Import latest language
• Importing vbulletin-language.xml
• Import Done
• Step 4 - Fatal Error Occurred

Status: Aborted

[John.Ross]

Just reran the upgrade script and it was fine

Diagnostics showed one file in template so I just reverted it and will see what that was.

Error log was removed

Now just need to get the md5 to stay non-writable, no many how many time i chmod in Filezilla it remains write on next refresh.

John

[John.Ross]

All done now, sorted, thanks for all the help fellas

Now back to same issues as on 5.5.5 where cant attach on eply :-(

[Wayne Luke]

We would need a support ticket with access to the server to understand what is happening.

[John.Ross]

Wayne, all sorted and it was a server issue, seemingly bluehosts has an issue with too many files being CHMOD to 777 which ended up I had to give up using filezilla and use the hosts file manager to set permissions properly as FZ was not setting them correctly

That was same issue with the md5# file warning, was setting it in Filezilla to not writabel and every time I got same warning in the update system, went back and write permissions were back.

Logged into host, used there file manager, set it read only, deed done. I sent them a support ticket as to why such a basic command was not being applied but no asnwer as yet.

At least now i know why and I am not losing my mind ! but it was not what I was expecting. I suspect that could also have ben come of the CSS loading issues I had on the change to https.

I tried using the alternative ftp client WinSCP and that seems to work, one to keep in mind, BH and FZ not always play nice :-(

John