(solved) cannot upgrade from 1.1.x to 1.2.0

[ariom]

When i try to upgrade my TB store (custom theme from community theme) from 1.1.x to latest 1.2.0, the core updater module gives an error and says: Processing log (request failed, see JavaScript console):
looking in the log directory i found this error

*ERROR*     2021/03/14 - 04:58:34: Server error: `POST https://api.thirtybees.com/coreupdater/master.php` resulted in a `500 Internal Server Error` response:
{"success":false,"error":{"code":"GIT_ERROR","message":"Git command failed. Please contact thirtybees developers"}}
 at line 113 in file vendor/guzzlehttp/guzzle/src/Exception/RequestException.php

have someone else encountered the same problem and can explain why it happens or suggest a solution?

Tks in advance for any advice ....

[datakick]

Oh, I found a bug in the server tooling. @ariom please try update now

[datakick]

What version of core updater do you use?

I just tried it, and it works fine for me.

In server logs I can see that your core updater module sends request to list content of revision 1.1.x, but that doesn't exists anymore. But your module evidently believes it does, which is strange. Maybe some caching issues -- try to delete file /cache/GitUpdateStorage.php and try again.

[ariom]

Yes....! it is working for me now .... Tks a lot @datakick

[Traumflug]

On 3/14/2021 at 8:50 AM, datakick said:

In server logs I can see that your core updater module sends request to list content of revision 1.1.x, but that doesn't exists anymore.

Bleeding Edge currently lists '1.0.x', 1.1.x', 1.2.x' and 'main'.

[signcoders]

Hi guys, I have this error in my store upgrading from 1.1.0 to 1.2.0 (cpanel, centos 6, php 7.3, curl 7.76 -latest-, coreupdater 1.3.3 -latest-)

 

*ERROR*     2021/04/05 - 12:03:07: cURL error 2: easy handle already used in multi handle (see http://curl.haxx.se/libcurl/c/libcurl-errors.html) at line 186 in file vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php
 

 

 

 

 

Can you help me? Thank you in advance. (sorry for my english)

 

Edit: image in full size: https://postimg.cc/tsjPgGbX

Edited April 5, 2021 by signcoders
Link to image added

[Traumflug]

This is apparently a well known issue elsewhere and connected to libcurl 7.69.1. Switching to an earlier or later version (in cPanel) should solve it. Note that the Curl used by PHP isn't necessarily the same as the Curl used on the command line.

https://github.com/guzzle/guzzle/issues/2617#issuecomment-674176945

[signcoders]

Thank you @Traumflug for your quick response.

 

Solved migrating to CentOS 7/latest cPanel set up (v94.x). With CentOS 6 the latest available version of cPanel is 84.x, so no updates are available neither OS nor cPanel.

[veganline]

I have the same problem that hasn't gone away.
There's no setting I can find for libcurl or curl on my web host's php editor.
I tried changing from php 7.2 to php 7.1 and back with no result.
I tried copying a new updater file from github and posting it over the old one on a test site.

Sometimes my updator recognises versions like "1.1" "1.2", "stable", and sometimes it recognises a lot more, but whatever I try to update to whatever the error messages are below (if I have got the right log to upload).
Any ideas are welcome.
My site is working so: no  rush. I just want to solve this before it's important

PS I tried deleting the cache including /GitUpdateStorage.php 20210507_exception.log

Edited May 7, 2021 by veganline
I tried deleting the chache

[Traumflug]

libcurl isn't part of the thirty bees distribution. This problem persists or goes away independently on which tb version or updater module version is installed. This has to be solved on the OS level. Did you just switch back and forth between 7.1 and 7.2, or did you actually try with the other version?

Seeing different sets of versions might be the result of different choices in the upper updater menu, 'Stable' vs. 'Bleeding Edge'.

[veganline]

I tried with the other version of PHP. Also tried turning-on all extensions, without result, before reverting.
The error log is the same every time
*ERROR*     2021/05/08 - 09:49:31: Server error: `POST https://api.thirtybees.com/coreupdater/master.php` resulted in a `500 Internal Server Error` response:
{"success":false,"error":{"code":"INVALID_REQUEST","message":"Revision issue-1258 not found"}}

[Traumflug]

Well, that's an entirely distinct error. For some reason, Core Updater tries to fetch a Bleeding Edge version 'issue-1258', which indeed doesn't exist. Which also means, libcurl works fine in this case.

I'd proceed as following:

• Switch to PHP 7.2.
• Select back office -> Preferences -> Core Updater.
• Ignore errors appearing at this point.
• Select 'Stable' in the upper menu.
• Select '1.2.0' in the second menu.
• Click 'Compare'

This should work and bring up the 'Update' button.

[veganline]

Same thing. 🙁
Thanks for the idea!

[Traumflug]

This looks entirely fine. Just ignore the "current version".

[veganline]

Thanks for patience!
The module does not update though; the next button stays grey and the usual red error about "see javascript console" appears. I had a thought: my PHP 7.2 doesn't have libcurl; it has curl. Could that be the hitch?
For some reason my site fails if I just change PHP from 7.2 to 7.3

[Traumflug]

I think I've got it now. thirty bees' version of Core Updater chokes when being asked to update from an unknown version, AFAIR.

Core Updater 2.0 has this issue fixed: https://github.com/merchantsedition/coreupdater/releases/tag/2.0.0 (install the .zip file manually in your back office)

This version of Core Updater comes with not two, but four channels. Channels 'thirty bees Stable' and 'thirty bees Bleeding Edge' are fed by genuine thirty bees sources, so you get a genuine thirty bees installation after updating.

[veganline]

On 5/10/2021 at 12:16 PM, Traumflug said:

I think I've got it now. thirty bees' version of Core Updater chokes when being asked to update from an unknown version, AFAIR.

Core Updater 2.0 has this issue fixed: https://github.com/merchantsedition/coreupdater/releases/tag/2.0.0 (install the .zip file manually in your back office)

This version of Core Updater comes with not two, but four channels. Channels 'thirty bees Stable' and 'thirty bees Bleeding Edge' are fed by genuine thirty bees sources, so you get a genuine thirty bees installation after updating.

It worked! I took it slowly, on backup copies, and the new version still doesn't connect to a PHP 7.3 database, but the main thing is that it works. I tried a vanilla update module as well (thirtybees not merchants edition) and it didn't work.

Thanks.

[signcoders]

On 5/10/2021 at 6:16 AM, Traumflug said:

I think I've got it now. thirty bees' version of Core Updater chokes when being asked to update from an unknown version, AFAIR.

Core Updater 2.0 has this issue fixed: https://github.com/merchantsedition/coreupdater/releases/tag/2.0.0 (install the .zip file manually in your back office)

This version of Core Updater comes with not two, but four channels. Channels 'thirty bees Stable' and 'thirty bees Bleeding Edge' are fed by genuine thirty bees sources, so you get a genuine thirty bees installation after updating.

Thank you, Markus. ME looks fascinating, according to Release Notes. I will review it thoroughly.