The system is currently offline. Chris tried to restart the mining servers to resolve an issue where some customers reported that "Live miner status" was not displaying their miners. However, when he attempted to restart the servers, a "no module named Cryptography" error occurred and the servers will not start. There were no code changes to cause the issue.
Chris is trying to determine what caused the problem and will provide more information as soon as he has some. He suspects the cause is that a Debian automatic update changed a package configuration.
System offline
Forum rules
The News forum is only for updates about the Prohashing pool.
Replies to posts in this forum should be related to the news being announced. If you need support on another issue, please post in the forum related to that topic or seek one of the official support options listed in the top right corner of the forums page or on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
The News forum is only for updates about the Prohashing pool.
Replies to posts in this forum should be related to the news being announced. If you need support on another issue, please post in the forum related to that topic or seek one of the official support options listed in the top right corner of the forums page or on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
-
Chris Sokolowski
- Site Admin
- Posts: 945
- Joined: Wed Aug 27, 2014 12:47 pm
- Location: State College, PA
Re: System offline
This issue is fixed. I had to force downgrade a package.
Re: System offline
it seems rather, um, bold, to allow automatic updates on a production system.
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: System offline
I'm not sure I agree. Testing every single update before release would cost so much that we would have to raise our fees. We'd have to hire someone solely to install packages on development.dnprod wrote:it seems rather, um, bold, to allow automatic updates on a production system.
The current process is that Chris reviews the updates that are available, and then sets calls aptitude upgrade to automatically upgrade the packages once he confirms there is nothing obviously wrong about them. This is the only time in two years that an upgrade using this method has caused any downtime, so I think it's fine.
The procedure saved a lot of potential problems because Chris was available when the servers were restarted to deal with the consequences of the update. One way of doing this that I would not recommend is to just allow the updates to install without Chris or anyone else having any input, because then the failure could have occurred when nobody was around to notice or resolve it.
Re: System offline
ah, so not fully automatic