you can check logs/cron.log
when cron.php starts - it writes something into that log
you can try tio run it manually during peak hours
Cron Error
Re: Cron Error
Don't forget to run script update
Re: Cron Error
Hi,
Yes I did check cron.log and thats where I saw many such alerts during traffic peak hour:
2019-08-19 13:06:01: Alert !!! Looks like crontab doesn't run cron.php every minute. Data file too big (0.2136869430542, 0.20806193351746)
When I run this manually the stats start building up again. But I cannot keep manually running the cron during peak hour every minute. When I got hosting to check they said that there are no errors with the crons and they are running fine. Any idea how to debug this issue?
Yes I did check cron.log and thats where I saw many such alerts during traffic peak hour:
2019-08-19 13:06:01: Alert !!! Looks like crontab doesn't run cron.php every minute. Data file too big (0.2136869430542, 0.20806193351746)
When I run this manually the stats start building up again. But I cannot keep manually running the cron during peak hour every minute. When I got hosting to check they said that there are no errors with the crons and they are running fine. Any idea how to debug this issue?
Re: Cron Error
"2019-08-19 13:06:01: Alert !!!"
what;s time before this line?
what;s time before this line?
Don't forget to run script update
Re: Cron Error
Hi,
I checked recent logs and it looks like this:
2019-08-20 00:59:01: Skip in ip 64.233.173.51 (0.34102582931519, 0.00028514862060547)
2019-08-20 00:59:02: Process traders (1.9112989902496, 1.5702741146088)
2019-08-20 00:59:03: Check timed forces (1.992262840271, 0.080960035324097)
2019-08-20 00:59:03: Calculate priority (1.9930109977722, 0.00074601173400879)
2019-08-20 00:59:03: Soft force (2.3145937919617, 0.32158398628235)
2019-08-20 00:59:03: Write config (2.315144777298, 0.00054788589477539)
2019-08-20 00:59:03: Schedule function delete_script_messages at 2019-11-17 23:58:47 ( now 2019-08-20 00:59:03) (2.3363378047943, 0.021192073822021)
2019-08-20 00:59:03: Cron job :: finished (2.3379678726196, 0.0016250610351562)
2019-08-20 01:00:01: Schedule function write_history at 2019-08-20 02:00:00 ( now 2019-08-20 01:00:01) (0.0010800361633301, 0.0010859966278076)
2019-08-20 01:00:01: Reset 1 .. 00 (0.0016331672668457, 0.00055098533630371)
2019-08-20 01:00:01: Write history (0.0033011436462402, 0.0016632080078125)
2019-08-20 01:00:02: Alert !!! Looks like crontab doesn't run cron.php every minute. Data file too big (0.26238417625427, 0.25908303260803)
2019-08-20 01:00:02: Process traffic (0.26835417747498, 0.0059709548950195)
Please let me know what could be wrong.
I checked recent logs and it looks like this:
2019-08-20 00:59:01: Skip in ip 64.233.173.51 (0.34102582931519, 0.00028514862060547)
2019-08-20 00:59:02: Process traders (1.9112989902496, 1.5702741146088)
2019-08-20 00:59:03: Check timed forces (1.992262840271, 0.080960035324097)
2019-08-20 00:59:03: Calculate priority (1.9930109977722, 0.00074601173400879)
2019-08-20 00:59:03: Soft force (2.3145937919617, 0.32158398628235)
2019-08-20 00:59:03: Write config (2.315144777298, 0.00054788589477539)
2019-08-20 00:59:03: Schedule function delete_script_messages at 2019-11-17 23:58:47 ( now 2019-08-20 00:59:03) (2.3363378047943, 0.021192073822021)
2019-08-20 00:59:03: Cron job :: finished (2.3379678726196, 0.0016250610351562)
2019-08-20 01:00:01: Schedule function write_history at 2019-08-20 02:00:00 ( now 2019-08-20 01:00:01) (0.0010800361633301, 0.0010859966278076)
2019-08-20 01:00:01: Reset 1 .. 00 (0.0016331672668457, 0.00055098533630371)
2019-08-20 01:00:01: Write history (0.0033011436462402, 0.0016632080078125)
2019-08-20 01:00:02: Alert !!! Looks like crontab doesn't run cron.php every minute. Data file too big (0.26238417625427, 0.25908303260803)
2019-08-20 01:00:02: Process traffic (0.26835417747498, 0.0059709548950195)
Please let me know what could be wrong.
Re: Cron Error
please, run update
Looks like you have a lot of traffic at that domain and it generates a lot of logs, I've added buffers
Looks like you have a lot of traffic at that domain and it generates a lot of logs, I've added buffers
Don't forget to run script update
Re: Cron Error
Hi,
I ran upgrade and will monitor for stats issue during traffic peak hour:
Your Build 201908201547 (Current build: 201908201547 )
Another thing I have noticed lately is whichever sites I upgrade the script messages like Anticheat, proxy traffic, errors they all don't post the messages in the script_messages sections. Any idea how to fix this? I even tried upgrading multiple times but still those messages do not show up.
I ran upgrade and will monitor for stats issue during traffic peak hour:
Your Build 201908201547 (Current build: 201908201547 )
Another thing I have noticed lately is whichever sites I upgrade the script messages like Anticheat, proxy traffic, errors they all don't post the messages in the script_messages sections. Any idea how to fix this? I even tried upgrading multiple times but still those messages do not show up.
Re: Cron Error
please, check out
settings - admin area
Message Type Write to Script Messages
settings - admin area
Message Type Write to Script Messages
Don't forget to run script update
Re: Cron Error
Hi,
After upgrade the stats were counting fine, but the logs for the site really become huge. Right now I am having another issue in which mysql is getting overloaded because it is using up entire RAM of the server. Here is what my host said:
"The sites are timing out because of all these queries that are stuck in a state of converting HEAP to MyISAM using up all the RAM on dbserver.
These queries are using SUM(), MAX(), ORDER BY, and GROUP BY functions on fields that are not Indexed. I am adding indexes to these files now. That should allow these queries to complete Considerably faster, and therefore use less RAM"
This is the query that causes it:
SELECT `search_query` , `gal_id`, SUM(hits) as hits, SUM(items_found) as items_found, max(date) as date FROM rot_search_queries as rs WHERE 1 = 1 GROUP BY rs.search_query, rs.gal_id ORDER BY hits DESC LIMIT 0, 62
After adding the indexes again after few days entire RAM of 64GB is being used by the server.
Any idea how to resolve this situation?
After upgrade the stats were counting fine, but the logs for the site really become huge. Right now I am having another issue in which mysql is getting overloaded because it is using up entire RAM of the server. Here is what my host said:
"The sites are timing out because of all these queries that are stuck in a state of converting HEAP to MyISAM using up all the RAM on dbserver.
These queries are using SUM(), MAX(), ORDER BY, and GROUP BY functions on fields that are not Indexed. I am adding indexes to these files now. That should allow these queries to complete Considerably faster, and therefore use less RAM"
This is the query that causes it:
SELECT `search_query` , `gal_id`, SUM(hits) as hits, SUM(items_found) as items_found, max(date) as date FROM rot_search_queries as rs WHERE 1 = 1 GROUP BY rs.search_query, rs.gal_id ORDER BY hits DESC LIMIT 0, 62
After adding the indexes again after few days entire RAM of 64GB is being used by the server.
Any idea how to resolve this situation?
Re: Cron Error
rot_search_queries
how many records do you have here?
or send me PMA, i'll check the query
how many records do you have here?
or send me PMA, i'll check the query
Don't forget to run script update
Re: Cron Error
On the biggest sites I purged it and just linked the important ones from the site as records was about 200k for rot_search_queries, other sites average is about 50-80k.