-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PHP Fatal error: causes update from 18.0.7 to 18.0.8 to fail #317
Comments
Hmmmm. Smells like a conflict with another app. Could you disable all optional apps, then try again? If that works re-enable the now disabled apps step by step and always retry |
I had the same issue and just solved it by disabling Suspicious Login via occ. I didn't test to see if it was a specific app conflict, but I know that most optional apps were already disabled at that point. |
I also have this issue. Version 3.2 seems to completely break Nextcloud 18. Shown in the log: "Argument 1 passed to "Symfony\Component\EventDispatcher\EventDispatcherInterface::dispatch()" must be an object, string given." Reverting to version 3.1 fixes it. |
Here to report that I also had this issue after the latest update to suspicous_login. @mhbates suggestion to disable it via occ worked. |
+1 |
Okay, so here's the deal: if nobody helps locate the conflict, we won't be able to fix the bug. |
Disabled everything that I can disable - still not working, same issue. Note that I checked the log and nextcloud after each disabled app.
|
I also had a conflict with the following error-message:
I disabled the app via occ for now. My enabled apps:
|
I am trying to give a full bug report here.
steps to reproduce
The following error has been loggend 5 times in a row:
further information for
After |
Okay thanks. In that case the conflict might be between Nextcloud and the app, which is … a bummer and really hard to fix. Let me see if I can delete the release, drop Nextcloud 18 support, and re-release. Please downgrade to the previous version. Thanks. |
Can we downgrade on the CLI? I don't know how to actually do that. |
You can't. Download the tarball, replace everything in the apps dir. Run the upgrade procedure. Done. |
Interesting though, a pure installation of Nextcloud 17/18/19/20 with this app installed does not cause any errors. So I think it might be caused by one other app. |
As mentioned these are all default apps (and recommended). But just for fun i did disabled all enabled apps - at least those who can be disabled. I dont get any error page.
|
Got it. So it might the difference between default apps (the ones that are packaged) and shipped apps (the ones that live in https://github.com/nextcloud/server). Thanks for testing! |
Landed here because update of this app from 3.1.0 to 3.2.0 broke my nextcloud 18.0.8 installation raising the mentioned error in nextcloud log. Manually downgrading to 3.1.0 through download of tarball fixed it. So there's something obvious: Changes from 3.1.0 to 3.2.0 throws the Symphony execption and therefore breaks nextcloud 18.0.8 in total. |
How is it obvious? |
When one has a working system (for years) and simply upgrades one (this) app and it does not work, then downgrades to previous version and it works again, this is what I would call "obvious". Don't agree? |
Well, if you only check the size of the archives 3.1 vs 3.2 - there is a substantial difference. Question: Which PHP Version are you folks running? |
Bingo! There is a new dev dependency that was accidentally added as production dependency. Let me fix that … |
See #319. It also contains a test build without this dependency. |
This one works fine with me. Also show's as 3.2.0 so is confirmed to be proper installed :) |
PHP 7.4.9 working as a charm |
@ChristophWurst Let us know when you released the last one in the official app-store :) |
v3.2.1 released: https://github.com/nextcloud/suspicious_login/releases/tag/v3.2.1 You can update via the apps settings of your Nextcloud, though due to caching of the latest releases you might not see the update immediately there. |
Nextcloud system becomes unusable:
A occ -h returns:
cf394fd77aca:/var/www/html$ occ -h -sh: occ: not found cf394fd77aca:/var/www/html$ ./occ -h PHP Fatal error: Declaration of Symfony\Component\Console\Input\ArrayInput::hasParameterOption($values, bool $onlyParams = false) must be compatible with Symfony\Component\Console\Input\InputInterface::hasParameterOption($values, $onlyParams = false) in /var/www/html/custom_apps/suspicious_login/vendor/symfony/console/Input/ArrayInput.php on line 202
Data log shows:
{"reqId":"UU9bPOOz4PvChBABRmpU","level":3,"time":"2020-08-31 17:35:21","remoteAddr":"","user":"--","app":"PHP","method":"","url":"--","message":"Declaration of Symfony\\Component\\Console\\Input\\ArrayInput::hasParamet erOption($values, bool $onlyParams = false) must be compatible with Symfony\\Component\\Console\\Input\\InputInterface::hasParameterOption($values, $onlyParams = false) at /var/www/html/custom_apps/suspicious_login/ven dor/symfony/console/Input/ArrayInput.php#202","userAgent":"--","version":"18.0.8.2"}
Going into the docker-session, one can disable the app with:
cf394fd77aca:/var/www/html$ ./occ app:disable suspicious_login suspicious_login disabled
The text was updated successfully, but these errors were encountered: