Over the last several weeks, i noticed parity check randomly starts. A quick look at the logs seems like it had an ungraceful shutdown, i have it plugged into an APC UPS and we have not had any power outages so i'm not sure what's causing this.

Any help with this please?

kenny-diagnostics-20260404-1609.zip

Server rebooting on its own is almost always a hardware issue, or bad power. You can retest without the UPS to rule that out.

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You could enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.

That might help us determine if there is anything pointing to a particular hardware issue although typically with hardware issues nothing gets logged.

5 hours ago, itimpi said:

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You could enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.

That might help us determine if there is anything pointing to a particular hardware issue although typically with hardware issues nothing gets logged.

Thanks, i already had the syslog server enabled and storing it in the appdata folder, with 3 local syslog files. When I checked though, i noticed there are no syslog files.

I thought that would be enough to store the files locally, i didn't realize i had to input the ip address of the server also (I was under the impression that setting was only to be filled in if i wanted to store the file on an external server).

I do believe it's the power supply though, it's a 650 watt and i think it was borderline with all the hardware i had running.

Any one figured it out? Same problem here. No reboots, but parity starts every other day on its own. I disabled the schedule completely, still dies it.

Thanks

Post diagnostics

I looked more into it, and apparently server reboots randomly and that is what causes parity to start , which us normal. Now I need to figure out why it does it.. All seems to be good and the server is on UPS so no power drops.

Apologies for hijacking thus thread, but is there any way to catch what's causing the reboots? My understanding once rebooted the logs are cleared. Thanks

1 hour ago, BKG said:

Apologies for hijacking thus thread, but is there any way to catch what's causing the reboots? My understanding once rebooted the logs are cleared. Thanks

Hardware issues, like start with the power supply.

However you can enable the syslog server for persistent syslogs

and yes, unclean shutdows trigger parity checks on startup after the shutdown.

Edited August 18Aug 18 by MowMdown