emanzx
11 Posts
Quote from emanzx on November 28, 2018, 2:32 pm
Petasan Version 2.0.0
3 node Cluster
Memory report from htop
Some log from syslog
how to solve this.. by the way I plan to update to 2.1 but worried there maybe problem as this is our production server.
thanks.
Petasan Version 2.0.0
3 node Cluster
Memory report from htop
Some log from syslog
how to solve this.. by the way I plan to update to 2.1 but worried there maybe problem as this is our production server.
thanks.
emanzx
11 Posts
Quote from emanzx on November 28, 2018, 2:40 pm
this error came out at the web admin
this error came out at the web admin
admin
2,930 Posts
Quote from admin on November 28, 2018, 5:51 pm
how much memory do you have ?
how many OSDs ?
if you restart the admin service
systemctl restart petasan-admin
does it release memory
How was the health of the cluster ? any OSDs down ?
do you see error in the log file
/opt/petasan/log/PetaSAN.log
how much memory do you have ?
how many OSDs ?
if you restart the admin service
systemctl restart petasan-admin
does it release memory
How was the health of the cluster ? any OSDs down ?
do you see error in the log file
/opt/petasan/log/PetaSAN.log
emanzx
11 Posts
Quote from emanzx on November 29, 2018, 2:33 am
Hi. Thanks for reply.
Node have 32GB ram.
OSD per node is 2
Total OSD is 6
restarting dont seem to release any memory.. maybe because the memory usage still low.
Health is clean and OK.
no error in PetaSAN.log detected.
only error I see is in syslog.
as I post above. about the unmatch time format.
Hi. Thanks for reply.
Node have 32GB ram.
OSD per node is 2
Total OSD is 6
restarting dont seem to release any memory.. maybe because the memory usage still low.
Health is clean and OK.
no error in PetaSAN.log detected.
only error I see is in syslog.
as I post above. about the unmatch time format.
admin
2,930 Posts
Quote from admin on November 29, 2018, 9:56 pm
This is strange as the error indicates a system time that does not include milliseconds, is this something that happened recently, have you did any changes to the system ?
Based on the log you posted, the following file should take care of missing milliseconds
https://drive.google.com/file/d/1v4Nomoete6D8ItTffaoQjFRQCdbM3gEE
place it to replace the file in the error log, the do a
systemctl restart petasan-admin
hope this fixes it, but again we can not reproduce this so cannot verify the fix.
This is strange as the error indicates a system time that does not include milliseconds, is this something that happened recently, have you did any changes to the system ?
Based on the log you posted, the following file should take care of missing milliseconds
https://drive.google.com/file/d/1v4Nomoete6D8ItTffaoQjFRQCdbM3gEE
place it to replace the file in the error log, the do a
systemctl restart petasan-admin
hope this fixes it, but again we can not reproduce this so cannot verify the fix.
emanzx
11 Posts
Quote from emanzx on November 30, 2018, 12:25 pm
I find the error is gone when I fix my time drift on the server that accessing the webUI. the time was set few hours into the future.. after I fix the time.. seem the error gone and my petasan works okay again.
I find the error is gone when I fix my time drift on the server that accessing the webUI. the time was set few hours into the future.. after I fix the time.. seem the error gone and my petasan works okay again.
