<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>Ha! Weblogic. Say no more!</div><div>On Thu, 2019-06-27 at 11:45 -0500, Todor Fassl via Ale wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>Never the less:</pre><a href="https://it.wisc.edu/security/bitcoin-malware-removed-uw-madison-servers-services-restored/"><pre>https://it.wisc.edu/security/bitcoin-malware-removed-uw-madison-servers-services-restored/</pre></a><pre><br></pre><pre><br></pre><pre><br></pre><pre><br></pre><pre>On 6/26/19 9:44 PM, Jeff Hubbs wrote:</pre><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>Anyone who is mining Bitcoin on even the most powerful extant x86_64 </pre><pre>server in 2019 is accomplishing essentially nothing.</pre><pre><br></pre><pre>On 6/26/19 6:06 PM, Todor Fassl wrote:</pre><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>I would not recommend ignoring high loads on a server these days. That </pre><pre>could be a sign someone is mining bitcoins on your server.</pre><pre><br></pre><pre><br></pre><pre><br></pre><pre>On 6/26/19 2:29 PM, Jeff Hubbs via Ale wrote:</pre><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>On 6/26/19 1:58 PM, Todor Fassl via Ale wrote:</pre><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>Right, but that is my point. If I run uptime and I see the load on a </pre><pre>system is high, I still have to manually figure out if it is cpu </pre><pre>bound, memory bound, or disk IO bound, or network IO bound. If you </pre><pre>google for tutorials on diagnosing load problems, they all say </pre><pre>something like "First run top and look at column 10. Then run iotop </pre><pre>and look at column 23. Then run netstat and ..." I don't think I </pre><pre>should have to do that in 2019.</pre></blockquote><pre><br></pre><pre>Maybe just go to lunch?</pre><pre><br></pre><pre>I'm only half-joking. Well, not even half.</pre><pre><br></pre><pre>At A Previous Employer (tm) the network operations group forced the </pre><pre>issue of running Nagios to monitor everything. I complied and put a </pre><pre>Nagios client on the Gentoo Linux file server I'd designed, built, </pre><pre>and managed for the entire company's use. Every night this machine </pre><pre>made Nagios absolutely explode with warnings. Of course it would, I </pre><pre>told them, it's running mksquashfs on all the Samba share volumes to </pre><pre>make backups and it lights up every core in the box in so doing </pre><pre>because the RAID1+0 is insanely fast in read and it's writing to a </pre><pre>completely different set of spindles on a completely different </pre><pre>controller. Moreover, it would do the same thing whenever ClamAV ran </pre><pre>because ClamAV was nicely multithreaded and would read at over </pre><pre>200MiB/s. It was expected, normal, and intended. The "problem," </pre><pre>plainly speaking, was Nagios.</pre><pre><br></pre><pre>The point of this graybeard parable is that machines turning into </pre><pre>hairdryers is not a bad thing on its face. It's different if e.g. a) </pre><pre>it can't complete something in the amount of time it has to do it per </pre><pre>line-of-business requirements b) you're limited on electrical or </pre><pre>cooling plant power c) your computers are doing something with no </pre><pre>utility or value. Just let the things glow red and go to lunch.</pre><pre><br></pre><pre>_______________________________________________</pre><pre>Ale mailing list</pre><a href="mailto:Ale@ale.org"><pre>Ale@ale.org</pre></a><pre><br></pre><a href="https://mail.ale.org/mailman/listinfo/ale"><pre>https://mail.ale.org/mailman/listinfo/ale</pre></a><pre><br></pre><pre>See JOBS, ANNOUNCE and SCHOOLS lists at</pre><a href="http://mail.ale.org/mailman/listinfo"><pre>http://mail.ale.org/mailman/listinfo</pre></a><pre><br></pre></blockquote><pre><br></pre></blockquote><pre><br></pre></blockquote><pre><br></pre></blockquote><div><span><pre><pre>-- <br></pre>James P. Kinney III
Every time you stop a school, you will have to build a jail. What you
gain at one end you lose at the other. It's like feeding a dog on his
own tail. It won't fatten the dog.
- Speech 11/23/1900 Mark Twain
http://heretothereideas.blogspot.com/
</pre></span></div></body></html>