I use ubuntu server 12.04 with apache and php5.2 with mysql 5.1, piwik 1.8.2
this is an updated install, however i have been using this version if piwik since its release, but this issue started 5 days ago,
This error is what shows when i try to login.
(this is only an issue with piwik not any other system on the server)
the only change that their had been was more memory added to the server, but have run many tests on memory and its nice and stable.
@matt updating Mysql server to version 5.5 may damage the other databases on the server, (i dont know for sure, and their is no good web info about it, which has given me peace of mind, which is why i have not messed with it)
is the away to reboot piwik’s database while keeping all archived data intact?
[quote=lesjokolat]
On the web i also saw the upgrade to MySQL as a likely solution.
I did see one refernce where it may be related to a memory limit.
Could you bump up the memory allocation to php or mysql and see if that helps in this case?
Have you tried another browser just to see if it changes teh result any. A screen shot of error could help as well.
regards[/quote]
oh yes that is a very good idea, the php.ini had not been adjusted to account to extra memory yet,
what peram is it for the php (line of code example)?
Heres one example not sure your php.ini set up but try as a guide to adjust yours . I read if one has it set to 32 then double it. once you hit 128 or higher sometimes you may be exceeding the actual apache limit so try to be reasonable when adjusting to not over compensate. Good luck
<?php
ini_set('memory_limit','40M');
$limit=100000000;
$tab=array();
for ($i=0;$i<=$limit;$i++){
$tab[]=$i*50000.0;
}
?>
Fixed, by updaing php.ini, but apache and mysql restart.
bUPDATE:[/b] I got an email from ubuntu, which says why i had the problem, thanks heavens it was not something i did because it all happend that same day, below is a part of the email they sent me.
[i]Hello Phillip,
Please forward this email to your technical contact(s) if you do not manage your Ubuntu system(s) directly.
We would like to inform you that on July 1, 2012 a bug a was exposed in the Linux kernel in connection with the June 30th Leap Second b. An Ubuntu bug c was consequently filed on Launchpad. The primary effect is high CPU load in kernel as well as user processes.
This bug affects all supported versions of Ubuntu. Note that this bug is very widespread, impacting almost all modern Linux operating systems.
A fix is currently being prepared for this issue. As a workaround for affected systems, either of the following actions should alleviate the CPU load:
Execute the following command as root (or prepend ‘sudo’ if non-root):
date -u -s “$(date -u -R)”
OR
Reboot
The permanent fix will be in the kernel well before the next leap second (as yet unannounced), which will be a minimum of six months away most likely in 2015.
Do not hesitate to contact Canonical Support if you require further help. You can do this via a support case within Landscape (https://landscape.canonical.com) or by phone (numbers listed in Landscape).
The Canonical Support Services Team
Canonical Group Limited 27th Floor, Millbank Tower 21-24 Millbank London SW1P 4QP United Kingdom[/i]