Dear Adam,
Sorry to resend because I didn't get the answer, thanks before.
It’s likely that you need more CPU, rather than more RAM. Ending up in
these out of memory scenarios are usually because the CPU was too slow and too many processes piled up.
The processor full if there's a poll is running after that it will normal again.
I've follow the tutorial to using persistent ramdisk https://docs.observium.org/persistent_ramdisk/
If ramdisk, RAM and swap are full, does the RRD still written ?
Because in that condition, the graph not written and there's an error when access the gui: *"DB Error 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)*" after restart the DB service it will normal again. please advice.
If you can’t see historic data, it means the RRD containing the historical
data has been somehow overwritten. Observium won’t do this by itself, so somehow you managed to delete or move the original RRDs.
You can restore the RRDs from backup, and it should write to these.
I can manual restore from backup of the backup ramdisk, thanks.
Because when I try to manual extract the ramdisk data from LZOP first backup file it end with error.
Though, if the RRDs have somehow disappeared, I’d check to make sure you
don’t have some form of filesystem/storage corruption, because the two might be linked.
After investigate, when the shutdown process, the ramdisk didn't write the latest data before the server turn off.
Because I didn't see any log about Ramdisk write data to hardisk.
How to achieve it ? because in the document didn't explain detail about it.
When startup process it succesfull load the data from ramdsk via rc.local script but the data loaded is corrupt, I can confrm this because when I try to manual extract from LZOP compression end with error, only some graph can be restored. Please advice.
BTW, please don’t send images to the mailing list.
Sorry I've resend the mail but forgot to cancel the first one.
Demikian yang dapat kami sampaikan, terimakasih.
Regards, Aulia Rahman
On Thu, Nov 12, 2020 at 3:36 PM Adam Armstrong adama@observium.org wrote:
It’s likely that you need more CPU, rather than more RAM. Ending up in these out of memory scenarios are usually because the CPU was too slow and too many processes piled up.
If you can’t see historic data, it means the RRD containing the historical data has been somehow overwritten. Observium won’t do this by itself, so somehow you managed to delete or move the original RRDs.
You can restore the RRDs from backup, and it should write to these.
Though, if the RRDs have somehow disappeared, I’d check to make sure you don’t have some form of filesystem/storage corruption, because the two might be linked.
BTW, please don’t send images to the mailing list.
Thanks,
Adam.
Demikian yang dapat kami sampaikan, terimakasih.
Regards,
Aulia Rahman