Navigation Menu

Skip to content
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

Error: "Incorrect arguments to mysqld_stmt_execute" after update to 2.4.0 #5419

Closed
anonymous-matomo-user opened this issue Jul 7, 2014 · 6 comments
Assignees
Labels
Bug For errors / faults / flaws / inconsistencies etc. worksforme The issue cannot be reproduced and things work as intended.
Milestone

Comments

@anonymous-matomo-user
Copy link

Mysqli statement execute error : Incorrect arguments to mysqld_stmt_execute.

I see the error in my wordpress and after login to piwik interface. Can't downgrade, refreshing configuration didn't help.

My phpinfo: i imgur com/PIOeC7E.png

@anonymous-matomo-user
Copy link
Author

Attachment:
phpinfo.png

@agilob
Copy link

agilob commented Jul 9, 2014

Hi,

I had the same problem today after update to 2.4.0. I downgraded source code to 2.3.0, but it didn't help. I ended up reinstalling piwik 2.3.0. Provided the same DB details, piwik detected my old database, so I reused it. After that 'reinstallation' it works. Downgrade didn't help, reinstalling 2.3.0 did. Do you want me to try fresh reinstall of 2.4.0?

Piwik was able to gather data about visitors, so the problem existed while getting the data from DB.

@mattab mattab added this to the 2.5.0 - Piwik 2.5.0 milestone Jul 11, 2014
@tsteur
Copy link
Member

tsteur commented Jul 22, 2014

@agilob would be great if you could try an update to 2.4.1 or a reinstall. If the problem occurs again, would you mind sending us credentials to your Piwik and FTP so we could debug the issue? Or maybe you could let us know when this problem exactly occurs? Do you get a backtrace?

@agilob
Copy link

agilob commented Jul 22, 2014

Update to 2.4.1 was successful and it works fine. afair there was no backtrace.

@tsteur
Copy link
Member

tsteur commented Jul 23, 2014

Do you maybe have any special characters in your MySQL password?

There was a bug in 2.4.0 not reading/saving the MySQL password entry correct if it contained special characters such as "&" or "$". This would explain this behavior and would also explain why it didn't work after downgrading to 2.3.0 since the config probably still contained wrong characters. It is fixed in 2.4.1

@agilob
Copy link

agilob commented Jul 23, 2014

Yes, I use keepass to generate passwords with all sets of characters. Thanks for the info.

@tsteur tsteur closed this as completed Jul 24, 2014
@tsteur tsteur self-assigned this Jul 24, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. worksforme The issue cannot be reproduced and things work as intended.
Projects
None yet
Development

No branches or pull requests

4 participants