@robles-design opened this Issue on January 23rd 2019

Hello,

I'm getting the following error in my php-logs since version 3.8. I've updated to 3.8.1-b1, but the error is still there:
[PHP Warning: Error while sending STMT_CLOSE packet. PID=20377 in /www/htdocs/piwik/libs/Zend/Db/Statement/Mysqli.php on line 105

Best regards
Robert

@fdellwing commented on January 23rd 2019 Contributor

Please take a look at your PHP error log and your MySQL error log.

@robles-design commented on January 23rd 2019

This is my php error log created via .htaccess. It's a shared host I don't have access to the real logs.

@tsteur commented on January 23rd 2019 Member

I don't think we can do much here. Looks like some DB issue to me. Has this happened before? For how long have you been using Matomo? Did it happen with 3.8.0?

@robles-design commented on January 24th 2019

Yes, as I mentioned in my first post I'm getting the error since 3.8. That's why I updated to 3.8.1-b1 yesterday. There are some new errors now (3 times):
Error in Matomo: Zend_Session is currently marked as read-only.

There weren't any errors before version 3.8. I noticed the errors yesterday, because there were some Ooops warnings in the front end and I took a look in the logs. After the update to 3.8.1-b1 the Ooops warnings popped up two or three times again. Then I deleted all tmp files in the matomo directory and the Ooops warnings are gone now, but the errors in the php error log are still rising. Last one from 23-Jan-2019 17:40:04, German timezone.

@tsteur commented on January 24th 2019 Member

@diosmosis do you maybe have any ideas? not sure how this could happen and whether it is related to us. Wondering if it's due to changing the Dbtable session adapter or some general session work.

@tsteur commented on January 24th 2019 Member

I reckon maybe the Error in Matomo: Zend_Session is currently marked as read-only. errors are unrelated. Not sure.

@diosmosis commented on January 24th 2019 Member

@tsteur found this comment in another project: https://github.com/walkor/Workerman/issues/357#issuecomment-416863614 seems to suggest the problem occurs because something closes the connection and then php tries to close it itself. Possibly done at the end of a request?

@robles-design might be helpful to contact the web host in this case, though it is strange it would start happening after an update.

@robles-design commented on January 24th 2019

Ok, the good news: no new errors in the php error log since yesterday. Last one was Error in Matomo: Zend_Session is currently marked as read-only.

The bad news: it all starts again. Maybe it's related with the A/B-testing plugin, because the Oops warnings popped up first in one of the A/B tests, is there again and stays there even after a reload (see screenshot from today). It displays new entries in the overview.
matomo-ab-test-oops

Then going to the admin page I get this messages:
WARNING: /www/htdocs/piwik/core/DataTable/Row.php(623): Warning - Cannot use a scalar value as an array - Matomo 3.8.1-b1 - Please report this message in the Matomo forums: https://forum.matomo.org (please do a search first as it might have been reported already)

After a reload the admin messages are gone.

Matomo-Version: 3.8.1-b1
MySQL-Version: 5.7.21-nmm1-log
PHP-Version: 7.2.13-nmm1

@robles-design commented on January 26th 2019

No more errors in the php error log since 23-Jan-2019, but the A/B-testing plugin doesn't work (see last post). Any ideas?

@robles-design commented on January 28th 2019

Update: Since yesterday the A/B-testing plugin is working again, no more Oops warnings, nothing changed. Today I've updated to Matomo 3.8.1 and all works fine.

Thanks for your support. You can close this ticket now.

@tsteur commented on January 28th 2019 Member

Awesome glad it works now 👍 feel free to contact us directly through shop at innocraft.com if you otherwise experience any trouble re a/b testing.

Powered by GitHub Issue Mirror