<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Panic on sigtar.com</title>
		<link>https://sigtar.com/tags/panic/</link>
		<description>Recent content in Panic on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Thu, 10 Sep 2020 00:00:00 +1200</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/panic/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>emergency reboot a hung Linux host</title>
				<link>https://sigtar.com/2020/09/10/emergency-reboot-a-hung-linux-host/</link>
				<pubDate>Thu, 10 Sep 2020 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2020/09/10/emergency-reboot-a-hung-linux-host/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;https://sigtar.com/wp-content/uploads/Screenshot-Terminal.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Sometimes you need something that can kick a host a bit harder than the standard &lt;strong&gt;reboot&lt;/strong&gt; command. Even if you include the &lt;strong&gt;-f&lt;/strong&gt; switch to force, a hung task can prevent your host from rebooting.&lt;/p&gt;&#xA;&lt;p&gt;Try this - first enable the sysrq setting, then trigger. Your host should reboot immediately.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;sudo echo 1 &amp;gt; /proc/sys/kernel/sysrq&lt;/strong&gt;&lt;br&gt;&#xA;&lt;strong&gt;sudo echo b &amp;gt; /proc/sysrq-trigger&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Note : This is effectively a hard reset which does not cleanly shut services or tasks down. You may need to check your disk on some operating systems.&lt;/p&gt;</description>
			</item>
			<item>
				<title>time to disable coinhive - hysteria ensues</title>
				<link>https://sigtar.com/2018/10/29/time-to-disable-coinhive-hysteria-ensues/</link>
				<pubDate>Mon, 29 Oct 2018 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2018/10/29/time-to-disable-coinhive-hysteria-ensues/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://sigtar.com/2017/10/13/coinhive-alternative-to-ad-revenue/capture-ch/&#34;&gt;&lt;img src=&#34;https://sigtar.com/wp-content/uploads/Capture-CH.png&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;See my previous post here - &lt;a href=&#34;https://sigtar.com/2017/10/13/coinhive-alternative-to-ad-revenue/&#34;&gt;/2017/10/13/coinhive-alternative&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;So the trial of coinhive and associated monero browser mining has come to an end. It seems most corporate firewalls and security appliances detect and block access to my domain just being associated with the coinhive java-script.&lt;/p&gt;&#xA;&lt;p&gt;Even though i was being a polite net citizen and disclosing it on the site - firewalls with strict polices dont give it a chance. Several public DNS servers have also block listed the site - hopefully this will be undone soon.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Opensolaris - ZFS recovery after kernel panic</title>
				<link>https://sigtar.com/2009/10/19/opensolaris-zfs-recovery-after-kernel-panic/</link>
				<pubDate>Mon, 19 Oct 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/10/19/opensolaris-zfs-recovery-after-kernel-panic/</guid>
				<description>&lt;p&gt;Recently i hit what i thought was a huge disaster with my ZFS array. Essentially i was unable to import my zpool without causing the kernel to panic and reboot. Still unsure of the exact reason, but it didn&amp;rsquo;t seem to be due to a hardware fault. (zpool import showed all disks as ONLINE)&lt;/p&gt;&#xA;&lt;p&gt;When i tried to import with &lt;strong&gt;zpool import -f tank&lt;/strong&gt; the machine would lockup and reboot (panic).&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
