Sorry we didn't smash a block before the halving. Luck wasn't on our side, and I checked logs to make sure there were no failed block submits  

I have to reassess whether I wish to keep this pool open or not. Removing the shared pool has trimmed the resource requirements and the server should be more than capable of running this solo pool now. I suspect the pool will probably not even find a block for months now with the halving so the cost of running it versus any profit would be the worst ever as well, but that was already factored in by increasing the pool fee to 2%. For the time being I will keep it running while I make my decision.

I've been thinking about what stresses me most about this pool that makes it troublesome to run, and it's the risk associated with it more than anything. The disaster I had with the conversion to segwit, and the server overload issue I had yesterday would never be well received. As I feel a sense of responsibility I can't just say "bad luck" to the people who dumped a lot of money's worth of hash into the pool. If the burden of responsibility was off me in case of disasters like that, I could keep the pool running as is. Considering I'm only running this as a service to the community as is, the thought of having to fork out hundreds or even thousands of dollars for something going wrong makes it really stupid to run.