You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A few hours ago my h/s went to zero on a pool I connect with my proxy. It seems like it's an out of memory error from what I can find on the web. So I doubled the ram, number of cpus and added diskspace to my VPS and I'm still seeing this in my console on my proxy. I also changed pools in the json file just in case it was the pool. I pinged the proxy and that was good. Any help would be appreciated.
"proxy > 2021-04-30 17:53 +00:00: Worker 2831 died with code: null, and signal: SIGILL"
The "Worker" number keeps changing but the other parts of the message stay.
The text was updated successfully, but these errors were encountered:
A few hours ago my h/s went to zero on a pool I connect with my proxy. It seems like it's an out of memory error from what I can find on the web. So I doubled the ram, number of cpus and added diskspace to my VPS and I'm still seeing this in my console on my proxy. I also changed pools in the json file just in case it was the pool. I pinged the proxy and that was good. Any help would be appreciated.
"proxy > 2021-04-30 17:53 +00:00: Worker 2831 died with code: null, and signal: SIGILL"
The "Worker" number keeps changing but the other parts of the message stay.
The text was updated successfully, but these errors were encountered: