lol they simply deleted the table or you did it instead of emptying it
Offline
I think i May have done that, bit not sure - still jetlagged and really should have slept instead of fiddling with this :p
Is there a simple way to add this back to the data, I tried to add "piwigo_sessions" it but asked for lots of variables I didnt understand :s
Thanks Flop
Offline
The SQL structure is described in install/piwigo_structure-mysql.sql
copy past the command for the two tables and execute in phpMyAdmin (modify the tables name to suit you prefix)
Offline
CREATE TABLE `piwigo_sessions` ( `id` varchar(255) binary NOT NULL default '', `data` mediumtext NOT NULL, `expiration` datetime NOT NULL default '0000-00-00 00:00:00', PRIMARY KEY (`id`) ) ENGINE=MyISAM;
from http://piwigo.org/dev/browser/trunk/ins … l.sql#L280
ps: arf mistic got me
Offline
Awesome, think thats it :-)
You guys are awesome - THANK YOU
The database is still showing at 100% usage (150mb) I am sure it is much less - but for now I leave it and ensure the site is working before I try to fix anything else :p lol
Offline
I have had this message form my ISP, does this help in sorting the problem?
Hi Steve,
This has now been resolved again and the database is working as expected.
It does not appear that any one is attacking your site. Looking through the logs, and the state of the database when we got to it, it would appear that your site is logging all hits to the database in a table called piwigo_history.
I am not sure if this is in built into piwigo or a plugin that has been installed on top. This is the table that had crashed and was causing the issues again this time. This table is also recording all bot GET requests from search engines which appears to be the cause of the table crashing.
If this is a plugin that is not required, I would suggest disabling it which will stop any further issues. However if this is an in built function then there is a plugin to exclude IP's from being recorded in this table. I have included a few of the main bot IP's bellow that would need to be added to this list.
If you have any further issues or questions please let me know.
Regards
Nick | IT Operations Engineer
Robot IP's
These make up over 4000 entries to the piwigo_history table over the last 3 days.
Any more can be found in your /logfiles/ex14****.log files and will reference robot / bot in the line.
178.154.243.81
66.249.66.187
66.249.66.144
66.249.66.91
5.10.83.73
5.10.83.45
5.10.83.49
5.10.83.23
5.10.83.75
5.10.83.86
5.10.83.31
66.249.66.203
5.10.83.84
5.10.83.82
5.10.83.15
5.10.83.72
5.10.83.19
5.10.83.57
5.10.83.80
5.10.83.41
Offline
so that's what I thought, the tables was getting to big for your hosting
so disable the history for non registred visitors, in the Piwigo Options, and you can use [extension by Eric] History IP Excluder or a htaccess to block some ip
Offline
Hi Flop, thanks for that, but I cannot see that option on my screen :p
I know I'm a pain lol
Offline
When I try to add lines to IP EXCLUDER I get this error
Fatal error: Call to undefined function is_adviser() in /home/linweb04/f/freezinglifethroughthelens.co.uk/user/htdocs/plugins/HistoryIPExcluder/admin/HIPE_admin.php on line 24
Offline
Hi,
I'll fix this in next plugin version (this evening).
Offline
skpManiac wrote:
Fatal error: Call to undefined function is_adviser() in /home/linweb04/f/freezinglifethroughthelens.co.uk/user/htdocs/plugins/HistoryIPExcluder/admin/HIPE_admin.php on line 24
Error fixed in plugin version 2.6.1 ;-)
Offline
Great work Eric - Thank you :)
I now have this config:
216.156.128.220
178.154.%
5.10.%
66.249.%
hopefully it will solve the problem I have been having
Steve
Offline