Skip to content
This repository has been archived by the owner on Mar 18, 2024. It is now read-only.

Civicrm crashed during upgrade #30

Open
partibrejker2 opened this issue May 9, 2018 · 18 comments
Open

Civicrm crashed during upgrade #30

partibrejker2 opened this issue May 9, 2018 · 18 comments

Comments

@partibrejker2
Copy link

Hi, today i tried to upgrade extension and it crashed my Civicrm.
I can access Joomla normally, but when i click on Civicrm, it shows HTTP ERROR 500.

Civicrm is 4.7
Joomla 3.8.7.
PHP Version 7.0.30

@partibrejker2
Copy link
Author

update - cannot access administrator part of Joomla. After login just blank screen.

@kcristiano
Copy link

kcristiano commented May 9, 2018

@mlutfy I did an update today to v 3.3 that also resulted in a white screen. Reverting to v2.9 solved the issue

CiviCRM 5.1.0
PHP 5.6.33-0+deb8u1
WP 4.9.6

Here is the error from the php error log.

[Wed May 09 07:56:56.506464 2018] [proxy_fcgi:error] [pid 17520:tid 139867448293120] [client ] AH01071: Got error 'PHP message: PHP Warning: require_once(/home/members/<>/sites/<>/web/wp-content/civicrm/extensions/ca.bidon.reporterror/vendor/autoload.php): failed to open stream: No such file or directory in /home/members/<>/sites/<>.org/web/wp-content/civicrm/extensions/ca.bidon.reporterror/reporterror.php on line 9\n
PHP message: PHP Fatal error: require_once(): Failed opening required '/home/members/<>/sites/<>.org/web/wp-content/civicrm/extensions/ca.bidon.reporterror/vendor/autoload.php' (include_path='.:/home/members/<>/sites/<>.org/web/wp-content/plugins/civicrm/civicrm:/home/members/<>/sites/<>.org/web/wp-content/plugins/civicrm/civicrm/packages:/home/members/<>/sites/<>.org/web/wp-content/plugins/civicrm/civicrm/vendor/tecnickcom:/home/members/<>/sites/<>.org/web/wp-content/plugins/civicrm/civicrm/vendor/phpseclib/phpseclib/phpseclib:/home/members/<>/sites/<>.org/web/wp-content/plugins/civicrm/civicrm/vendor/pear/pear_exception:/home/members/<>/sites/<>.org/web/wp-content/plugins/civicrm/civicrm/vendor/pear/auth_sasl:/home/members/<>/sites/<>.org/web/wp-content/plugins/civicrm/civicrm/vendor/pear/net_socket:/home/members/<>/sites/<>.org/web/wp-content/plugins/civicrm/civicrm/vendor/pear/net_smtp:/home/members/<>/sites/<>.org/web/wp-content/plugins/civicrm/civicrm/vendor/pear/validate_financ...\n', referer: https://www.<>.org/wp-admin/admin.php?page=CiviCRM&q=civicrm%2Fadmin%2Fextensions&reset=1

@mlutfy
Copy link
Owner

mlutfy commented May 9, 2018

hi @partibrejker2, did you update to the packaged version with the "vendor" directory? c.f. https://github.com/mlutfy/ca.bidon.reporterror/releases/tag/3.1 (reporterror-3.1.tar.gz)

If not, what is the method you currently use? I guess it might be good to better safeguard against this.

@kcristiano
Copy link

@mlutfy I updated via the CiviCRM extension screen the first time, then I manually retrieved the 3.3 package from the releases page.

I will try this again on the staging site we have. I did this update live on production.

@partibrejker2
Copy link
Author

Hi Mlufty

like cristiano i updated via CiviCRM extension screen. And the error is the same.
I would appreciate if somebody could help me at least revert this.

[09-May-2018 10:29:29 Europe/*] PHP Warning: require_once(*/media/civicrm/ext/ca.bidon.reporterror/vendor/autoload.php): failed to open stream: No such file or directory in */media/civicrm/ext/ca.bidon.reporterror/reporterror.php on line 9 [09-May-2018 10:29:29 Europe/*] PHP Fatal error: require_once(): Failed opening required '*/media/civicrm/ext/ca.bidon.reporterror/vendor/autoload.php' (include_path='.:/*/administrator/components/com_civicrm/civicrm:/*/administrator/components/com_civicrm/civicrm/packages:/*/administrator/components/com_civicrm/civicrm/vendor/tecnickcom:/*/administrator/components/com_civicrm/civicrm/vendor/phpseclib/phpseclib/phpseclib:/*/administrator/components/com_civicrm/civicrm/vendor/pear/pear_exception:/*/administrator/components/com_civicrm/civicrm/vendor/pear/auth_sasl:/*/administrator/components/com_civicrm/civicrm/vendor/pear/net_socket:/*/administrator/components/com_civicrm/civicrm/vendor/pear/net_smtp:/home/evoli in /*/media/civicrm/ext/ca.bidon.reporterror/reporterror.php on line 9

@mlutfy
Copy link
Owner

mlutfy commented May 9, 2018

I deleted the release node from civicrm.org. (although some may still have it in their cache)

@kcristiano
Copy link

I just tried a direct download and I don't see a vendor directory in the extension.

@mlutfy
Copy link
Owner

mlutfy commented May 9, 2018

I just tried a direct download and I don't see a vendor directory in the extension.

Using: https://github.com/mlutfy/ca.bidon.reporterror/releases/download/3.1/reporterror-3.1.tar.gz ?

@kcristiano
Copy link

kcristiano commented May 9, 2018

I should have included the link.

I used https://github.com/mlutfy/ca.bidon.reporterror/archive/3.1.zip

not https://github.com/mlutfy/ca.bidon.reporterror/releases/download/3.1/reporterror-3.1.tar.gz

Off to try again. Still unsure why the CiviCRM updater failed.

UPDATE: of course that worked. I did have to manually update the extension db and the cache, but as this is a manual update, that does make sense.

@partibrejker2
Copy link
Author

so, what do i do to get my website back? :)

@mlutfy
Copy link
Owner

mlutfy commented May 9, 2018

@partibrejker2
Copy link
Author

i have never done it before.
Do i just copy the files?
If so, do i just copy them to : media/civicrm/ext ?

Do i have to do anything in the database?

thank you for your help

@mlutfy
Copy link
Owner

mlutfy commented May 9, 2018

yep, that should work.

Worst case, you can also try deleting the ca.bidon.reporterror directory, then go to Admin > System > Extension, click 'refresh', then re-install (I updated the link there).

@partibrejker2
Copy link
Author

Thx,

i had to delete it.
Now:

image

@mlutfy
Copy link
Owner

mlutfy commented May 9, 2018

Getting there .. ;)

Can you refresh your extension list and try again? I updated for a zip file.

@mattwire
Copy link
Contributor

@mlutfy Running composer install works when doing a git clone as the vendor dir is not included in the github repository. This caught me out as it's a new dependency. Could you add something to the readme?

@mlutfy
Copy link
Owner

mlutfy commented May 14, 2018

@mattwire good idea, added a2e4081 (although I suspect most people don't read that. It would be better to check before requiring the autoload, and if it's missing show a status message?)

@mattwire
Copy link
Contributor

It would be better to check before requiring the autoload, and if it's missing show a status message

@mlutfy Yes, good idea. I think some other extensions have handled things in a similar way (eg. mosaico).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants