The db_dump program that dumps the data for the external stats sites only runs once per day. In case of an error (even a transient one) there is no stats export for the whole day.
In this case db_dump couldn't connect to the Db, probably because of the high load (many schedulers running) at that time.
I added a feature to db_dump that will automatically retry after half an hour in case of a connection failure. At least in case of this particular error stats shouldn't be missing for a whole day anymore.
The db_dump program that dumps the data for the external stats sites only runs once per day. In case of an error (even a transient one) there is no stats export for the whole day.
In this case db_dump couldn't connect to the Db, probably because of the high load (many schedulers running) at that time.
I added a feature to db_dump that will automatically retry after half an hour in case of a connection failure. At least in case of this particular error stats shouldn't be missing for a whole day anymore.
BM
Thank you, Bernd.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
Working again, thx
)
Working again, thx
DSKAG Austria Research Team: [LINK]http://www.research.dskag.at[/LINK]
The db_dump program that
)
The db_dump program that dumps the data for the external stats sites only runs once per day. In case of an error (even a transient one) there is no stats export for the whole day.
In this case db_dump couldn't connect to the Db, probably because of the high load (many schedulers running) at that time.
I added a feature to db_dump that will automatically retry after half an hour in case of a connection failure. At least in case of this particular error stats shouldn't be missing for a whole day anymore.
BM
BM
RE: The db_dump program
)
Thank you, Bernd.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.