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
Notice - unserialize(): Error at offset 0 of 53988 bytes #14229
Comments
We encounter the same error since updating to Matomo 3.9 this morning. We are using PHP 7.0.33 though. |
Has same issue! |
Same problem since updating to Matomo 3.9. Using PHP 7.2. |
Is the problem maybe that some logging seems to be enabled? eg. the response is:
and the first line is Can you maybe check that DEBUG logging is disabled? https://matomo.org/faq/troubleshooting/faq_115/ |
|
global.ini.php log_level = WARN |
I believe I have the same issue since upgrading to Matomo 3.9.0 this morning. |
Same here. I also get a "Password changed" mail each time I login via LDAP. |
same here. maybe this issue will have a lot other users. |
Using the "real" cron feature for the first time in Matomo 3.9.0 and got this error straight away. |
Same issue here:
|
I did stumple across an interessting case: Our archiving was running fine with php7.0 (I hardcoded it sometime ago in the cron, website runs 7.2). I just ran the command with php7.2 and got the error, afterwards I was not able to run the command with php7.0 again. |
@fdellwing As I have no idea why this could happen, I'd suggest running |
Clearing the cache did not solve the problem. |
Ok, this error is definitely a regression of #13923 You may apply the attached patch file to your Matomo instance to revert these changes until the problem is solved.
(Calling with --reject because some files are not packed into release) 0001-Revert-Enable-fingers-crossed-handler-via-INI-config.patch.txt //cc @diosmosis |
@fdellwing Your patch seems to work fine for us, thanks a lot! Do we have to keep anything in mind when updating Matomo via the user interface the next time or will it simply overwrite the patched parts of the code without causing a fuss? |
@timEulitz |
Patch solved the cron problem. Still get the password changed notification, seems to be unrelated. |
@arndbernstein This sounds completely unrelated, could you please open an issue here: |
Applying the patch solved the problem on our hand. |
If I had to guess there is error occurring that is now visible in whatever is trying to be |
|
after apply the patch, the file integrity check fails and reports that there are some files with not the expected file sizes. did i something wrong or is that normal!? |
Patch fixed it, thanks! But now i get an "SQLSTATE Syntax error or access violation" when i run the cron archiving:
I'm using MariaDB 10.3.13 Galera Cluster, maybe unrelated? |
Same issue to my installation. I don't have ssh access to my hosting, how can I fix it? |
@fdellwing Even when you update from the release candidate to the stable version? |
I only tried 3 step upgrade after the auto update failed. But I now can do it unlimited times with always the problem afterwards. |
@Findus23 Yes, that's how I was able to reproduce and fix the other issue affecting the update. But I don't have an issue w/ core:archive. It's possibly due to using a mac, I'll try going through docker. @michaellass @fdellwing The output is truncated, there's likely much more not being displayed. If |
@diosmosis thanks for the tip! Here's the full output. |
Thanks @michaellass! Looks like there is actually no error or warning, the log level is simply changed to DEBUG for some reason, but only in those archiving requests. I'll see if I can pinpoint a cause. |
@michaellass could you try the following change to see if it fixes the issue for you? comment out https://github.com/matomo-org/matomo/blob/3.x-dev/plugins/Monolog/config/config.php#L51-L62 |
I tried but that's not it. The errors still occur. |
I am now able to reproduce this through docker, will put up a fix as soon as possible. |
@michaellass created a fix here: #14239 Can you see if it works for you? |
Yes, that change fixes it! 🎉 |
And what if my installation does not use git? |
@ZAZmaster there's a fix here: #14239, it's a small change that can be applied directly. Or you might be able to workaround it by just enabling the file logger in your INI config. |
@diosmosis thx! |
The fix #14239 works perfectly. |
works for me too. Archiving CLI works again |
@ZAZmaster Just to make you aware of this: You just need git installed to apply a patch, it does not need to be a git repo or something along those line. @diosmosis Fix works for me. |
Can confirm, the fix in #14239 works, the Cron runs smoothly on my installation now! |
A quick note, you do not need to type the changes yourself, you can just get the patch from GitHub: https://patch-diff.githubusercontent.com/raw/matomo-org/matomo/pull/14239.patch |
Confirm #14239 works here. Had the issue after upgrading to 3.9.0 running PHP 7.0.32. |
I can also confirm the patch is working with PHP 7.3 |
Patch works with 7.3.3 |
The patch works both on PHP 7.0 and 7.1. Tnx. |
Mysql 5.7.23-23-57 Patch working |
PHP 7.0.21 |
The source of the error has been found, please take a look at #14229 for the fix.
This error has been reported quite a few times on the forum, so I'll create an issue.
What is known:
https://forum.matomo.org/t/empty-or-invalid-response/31848
https://forum.matomo.org/t/empty-or-invalid-response-when-core-archive/32106
https://forum.matomo.org/t/error-making-archive/32110
The text was updated successfully, but these errors were encountered: