[solved] 2.1.6 > 2.2.5 upgrade failing, Phar problems?

[paulbaker]

Attempting to do a customer upgrade 2.1.6 > 2.2.5.

Phar install was giving errors:

Code: Select all

[Thu Jan 11 10:59:48.405689 2018] [fcgid:warn] [pid 16216] [client 188.28.139.216:49350] mod_fcgid: stderr: PHP Fatal error:  Uncaught exception 'PharException' with message 'phar "/home/linweb22/k/king....com-1085056276/user/htdocs/cmsms-2.2.5-install.php" SHA1 signature could not be verified: broken signature' in /home/linweb22/k/king....com-1085056276/user/htdocs/cmsms-2.2.5-install.php:8
[Thu Jan 11 10:59:48.412073 2018] [fcgid:warn] [pid 16216] [client 188.28.139.216:49350] mod_fcgid: stderr: Stack trace:
[Thu Jan 11 10:59:48.412099 2018] [fcgid:warn] [pid 16216] [client 188.28.139.216:49350] mod_fcgid: stderr: #0 /home/linweb22/k/king....com-1085056276/user/htdocs/cmsms-2.2.5-install.php(8): Phar::webPhar(NULL, 'index.php')
[Thu Jan 11 10:59:48.412105 2018] [fcgid:warn] [pid 16216] [client 188.28.139.216:49350] mod_fcgid: stderr: #1 {main}
[Thu Jan 11 10:59:48.412117 2018] [fcgid:warn] [pid 16216] [client 188.28.139.216:49350] mod_fcgid: stderr:   thrown in /home/linweb22/k/king....com-1085056276/user/htdocs/cmsms-2.2.5-install.php on line 8

So I used the expanded installer but got this error:

Code: Select all

[Thu Jan 11 11:13:12.996421 2018] [fcgid:warn] [pid 12246] [client 188.28.139.216:58022] mod_fcgid: stderr: PHP Fatal error:  Class '__appbase\\nls.ph_nls' not found in /home/linweb22/k/king....com-1085056276/user/htdocs/lib/classes/class.nlstools.php on line 44

Phar details from phpinfo:

Could use some pointers here....?

Thanks

[Rolf]

Mod Security at this server?

[paulbaker]

Thanks Rolf, no mention of mod security on phpinfo and existing installation works without any problems that I can see.

[Jo Morg]

How did you upload the installer to the server?

[calguy1000]

SHA1 signature could not be verified: broken signature'

I'll bet you uploaded the installer using FTP... and in ASCII or auto mode.
FTP is evil and should not be used.

[paulbaker]

Thank you Rolf, Jo and Calguy.

I'll bet you uploaded the installer using FTP... and in ASCII or auto mode.

You got it. I was uploading the installer using the (crappy) browser based file manager that the client's host provides. It uploaded in ASCII without me being able to spot and change it.

Once I re-uploaded the installer using FTP set to binary mode, the upgrade went without a hitch.

Thanks again!

Is it time for a beer yet?

[calguy1000]

<cough>ssh/scp/sftp</cough>

learning those tools and basic shell commands is gonna save you a crapload of time.