Is this a healthy looking logfile?
Does this means it reboots every 15 minutes? That can not be a good thing?
please advise
hugo
syslog:
Dec 17 17:00:01 flukso-00757e cron.info crond[933]: crond: USER root pid 2983 cmd /usr/bin/fntp
Dec 17 17:05:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3000 cmd /usr/bin/heartbeat 0
Dec 17 17:05:03 flukso-00757e user.info heartbeat[3001]: POST https://api.flukso.net/device/00757e836fb97579b15600ce488e0fda: 200
Dec 17 17:15:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3011 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 17:15:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3012 cmd /usr/bin/fntp
Dec 17 17:30:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3031 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 17:30:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3033 cmd /usr/bin/fntp
Dec 17 17:45:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3051 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 17:45:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3054 cmd /usr/bin/fntp
Dec 17 18:00:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3071 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 18:00:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3074 cmd /usr/bin/fntp
Dec 17 18:05:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3091 cmd /usr/bin/heartbeat 0
Dec 17 18:05:03 flukso-00757e user.info heartbeat[3092]: POST https://api.flukso.net/device/00757e836fb97579b15600ce488e0fda: 200
Dec 17 18:15:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3102 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 18:15:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3103 cmd /usr/bin/fntp
Dec 17 18:30:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3122 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 18:30:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3125 cmd /usr/bin/fntp
Dec 17 18:45:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3142 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 18:45:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3144 cmd /usr/bin/fntp
Dec 17 19:00:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3162 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 19:00:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3165 cmd /usr/bin/fntp
Dec 17 19:05:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3182 cmd /usr/bin/heartbeat 0
Dec 17 19:05:02 flukso-00757e user.info heartbeat[3183]: POST https://api.flukso.net/device/00757e836fb97579b15600ce488e0fda: 200
Dec 17 19:15:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3193 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 19:15:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3195 cmd /usr/bin/fntp
Dec 17 19:30:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3219 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 19:30:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3222 cmd /usr/bin/fntp
No it does not do a reboot every 15mins. A health check of the flukso daemon is done instead. If this health check fails, then a reboot will be triggered as a last resort.
There are no pulse entries in the syslog. So please check this and this forum post.
Tx, now flukso is working just fine.
hugo
So what was the problem?