Possible Bug ?

[kako]

Hi everybody!

I've started to deal with ZM 1.24.2. After few hours I've experienced, there are many events in the event list is dated to 1970.01.01. OK, don't panic, googled for it, and found many similar experiences. In a forum I've fount a (n almost) solution. Somebody said it is because of the mysql, and datailed some parameters what I have to tune, and it will work normally (heap table size, tmp table size, query cache etc.) and suggested to install mysqltuner and let I see which parameter have I tune yet.
I've made the proposed changes, but the problem is the same. I've started to see the mysqltuner, what else parameters have I change. There were settings when it used 7GB!!! of memory from the installed 4GB, and wasn't enough by the mysqltuner. Is it normal?
Now the maximal possible mem.usage is 3,6GB, but the date is incorrect sometimes.
This is a 2xdual core xeon HP server with 4G ram. By myself it MUST be enough for processing the images of 2 netcam. But sometimes one of the zm processes uses the cpu by 100% for many minutes long. What could be the problem??

Thanks
Kako


The mysqltuner's output is
---------------------
-------- Performance Metrics -------------------------------------------------
[--] Up for: 1d 17h 33m 52s (38K q [0.257 qps], 2K conn, TX: 310M, RX: 3M)
[--] Reads / Writes: 31% / 69%
[--] Total buffers: 34.5M per thread and 282.0M global
[!!] Maximum possible memory usage: 3.6G (95% of installed RAM)
[OK] Slow queries: 0% (0/38K)
[OK] Highest usage of available connections: 21% (21/100)
[OK] Key buffer size / total MyISAM indexes: 16.0M/671.0K
[OK] Key buffer hit rate: 99.8%
[OK] Query cache efficiency: 87.3%
[OK] Query cache prunes per day: 0
[OK] Sorts requiring temporary tables: 0%
[!!] Temporary tables created on disk: 28%
[OK] Thread cache hit rate: 99%
[OK] Table cache hit rate: 84%
[OK] Open file limit used: 6%
[OK] Table locks acquired immediately: 100%

-------- Recommendations -----------------------------------------------------
General recommendations:
Reduce your overall MySQL memory footprint for system stability
Enable the slow query log to troubleshoot bad queries
When making adjustments, make tmp_table_size/max_heap_table_size equal
Reduce your SELECT DISTINCT queries without LIMIT clauses
Variables to adjust:
*** MySQL's maximum memory usage exceeds your installed memory ***
*** Add more RAM before increasing any MySQL buffer variables ***
tmp_table_size (> 512M)
max_heap_table_size (> 128M)