Your Remote syslog server seems a little complicated. Is that a different server?

If you want it to log to itself, just put localhost

7 hours ago, alonm15 said:

The strange part is, the server comes RIGHT back online. I don't have to go power it up. It crashes, then automatically restarts itself which seems to rule out a hardware issue.

Not sure why you would think this clears the hardware. This is something we see frequently in hardware issues, especially if the BIOS is set to automatically start the server if power is available.

so just like this?

yes

the server started crashing repeatedly on Sunday night. I had to leave town for work so I kicked off a memtest and it ran for 8 hours with no errors and passed. Is it possible RAM is potentially an issue or should I move on to testing other hardware components? PSU is also brand new.

Because memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

I believe i found the issue. It seemed to happen when plex would hammer the CPU during transcoding. I didn't know this was happening since the server would crash multiple times and clear out the log (Im sure i'm doing something wrong with the logs.) But it ended up being an apparently known issue with Linux i915 kernel drivers and transcoding. Froze up the CPU. hard system crash. I have many remote plex users so I'm not always sure when it is in use. I finally captured a log file when it crashed and could see the mover moving transcoder files which gave me the clue.

Hopefully this puts a bow on it. Thank you to everyone for the help.