Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New error this morning (5/1/2021) after years with no issues. #136

Open
RAWGamingNet opened this issue Apr 30, 2021 · 0 comments
Open

New error this morning (5/1/2021) after years with no issues. #136

RAWGamingNet opened this issue Apr 30, 2021 · 0 comments

Comments

@RAWGamingNet
Copy link

RAWGamingNet commented Apr 30, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant