I’m not sure what you mean, I haven’t set anything up to direct logs to the logs folder.
Because this line is indicating that the new version is not available for your node now. It will check later.
But you seems have the node down, or am I wrong?
If you have it down, you must have a log entries - why.
If you didn’t change the log.output: parameter neither in the config.yaml nor as a command line option, it must print all log messages to stdout/stderr, so you should see something in your logs even by docker logs storagenode.
If you did redirect, you need to check the file instead, because after redirection docker logs will show only messages from the supervisor and storagenode-updater, but not from storagenode.
I don’t redirect the logs. As I have written before, these were the last lines in the log. It seems that only the storagenode-updater was still working and produced log entries.
Yeah, this is what’s happening to me. My uptime checks said the service was up but I have had 0 egress the past 4 days due to me not noticing.
Yes and I think Docker also claimed everything was running…
So not so great to detect this error.
1 Like
had also 2 windows native nodes not reacting to manual restarts of the service, had to do reboot of the system, since that, not reproduceable.
mine did too.
@Alexey should a bug report be filed?
Yes, please, do it. I do not have this issues on my nodes, so do not know how to reproduce and I do not have also full logs around the time of the issue, which developers are likely to require.