<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>故障排除 &#8211; 寂静花园</title>
	<atom:link href="https://www.addesp.com/archives/tag/%E6%95%85%E9%9A%9C%E6%8E%92%E9%99%A4/feed" rel="self" type="application/rss+xml" />
	<link>https://www.addesp.com</link>
	<description>寂静中交织着热情</description>
	<lastBuildDate>Sun, 30 Jan 2022 06:38:38 +0000</lastBuildDate>
	<language>zh-Hans</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.2</generator>
	<item>
		<title>Windows10 Cryptographic Services 占用过高</title>
		<link>https://www.addesp.com/archives/5599</link>
					<comments>https://www.addesp.com/archives/5599#comments</comments>
		
		<dc:creator><![CDATA[ADD-SP]]></dc:creator>
		<pubDate>Thu, 27 Jan 2022 14:12:10 +0000</pubDate>
				<category><![CDATA[笔记]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[故障排除]]></category>
		<guid isPermaLink="false">https://www.addesp.com/?p=5599</guid>

					<description><![CDATA[经常会在任务管理器内看到  Cryptographic Services 的 CPU 占用和硬盘占用很高，以至于降低系统变卡。手动关闭它过段时间还会自己出现，禁用这个服务过段时间后也会自动出现。]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading" id="症状">症状</h2>



<p class="wp-block-paragraph">经常会在任务管理器内看到  Cryptographic Services 的 CPU 占用和硬盘占用很高，以至于降低系统变卡。手动关闭它过段时间还会自己出现，禁用这个服务过段时间后也会自动出现。</p>



<h2 class="wp-block-heading" id="解决">解决</h2>



<ol class="wp-block-list"><li>右键 “此电脑”。</li><li>点击 “管理“。</li><li>双击 ”服务和应用程序“。</li><li>双击 ”服务“。</li><li>找到  “Cryptographic Services”，右键单击，点击 ”停止“。</li><li>找到文件夹 ”C:\Windows\System32\catroot2”，将其重命名为 “catroot2.old”。</li><li>重启服务 “Cryptographic Services”。</li></ol>



<p class="wp-block-paragraph">重启后这个文件夹应该会被自动创建，然后资源占用过高的问题应该就解决了（至少在博主的电脑上是解决了）。</p>



<h2 class="wp-block-heading" id="原理">原理</h2>



<p class="wp-block-paragraph">什么？Windows10 的东西你还想搞明白原理（玄学）？你太猖狂了，地球人！</p>



<h2 class="wp-block-heading" id="参考资料">参考资料</h2>



<p class="wp-block-paragraph"><a href="https://www.tecklyfe.com/fix-cryptographic-service-100-and-high-disk-usage/" target="_blank" rel="noreferrer noopener">Fix Cryptographic Services 100% and High Disk Usage &#8211; TeckLyfe</a></p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.addesp.com/archives/5599/feed</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Nextcloud 423 Locked</title>
		<link>https://www.addesp.com/archives/4589</link>
					<comments>https://www.addesp.com/archives/4589#comments</comments>
		
		<dc:creator><![CDATA[ADD-SP]]></dc:creator>
		<pubDate>Sat, 05 Jun 2021 04:07:42 +0000</pubDate>
				<category><![CDATA[Nextcloud]]></category>
		<category><![CDATA[故障排除]]></category>
		<guid isPermaLink="false">https://www.addesp.com/?p=4589</guid>

					<description><![CDATA[概述 Nextcloud 中对文件进行修改、删除操作会失败。网页端显示错误，客户端显示返回 HTTP 423  [&#8230;]]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">概述</h2>



<p class="wp-block-paragraph">Nextcloud 中对文件进行修改、删除操作会失败。网页端显示错误，客户端显示返回 HTTP 423 (Locked) 状态码。</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p>HTTP 423 状态码并未定义在 HTTP 标准中。其定义在 <a href="https://datatracker.ietf.org/doc/html/rfc4918#page-78" target="_blank" rel="noreferrer noopener" title="https://datatracker.ietf.org/doc/html/rfc4918#page-78">RFC 4918</a> 中作为 HTTP 协议的一个扩展。</p><cite><a href="https://datatracker.ietf.org/doc/html/rfc4918" target="_blank" rel="noreferrer noopener" title="https://datatracker.ietf.org/doc/html/rfc4918">HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)  &#8212; RFC 4918</a></cite></blockquote>



<h2 class="wp-block-heading">系统环境</h2>



<h3 class="wp-block-heading">宿主机</h3>



<ul class="wp-block-list"><li>OS：Ubuntu 20.04</li><li>Server：nginx-1.21.0</li><li>MySQL：8.0.25</li><li>Nextcloud：21.0.0</li></ul>



<h3 class="wp-block-heading">Docker</h3>



<ul class="wp-block-list"><li>php:8.07-fpm-alpine3.13</li></ul>



<h2 class="wp-block-heading">解决方法</h2>



<h3 class="wp-block-heading">临时解决</h3>



<ol class="wp-block-list"><li>开启维护模式，详见<a href="https://docs.nextcloud.com/server/latest/admin_manual/maintenance/backup.html" target="_blank" rel="noreferrer noopener" title="https://docs.nextcloud.com/server/latest/admin_manual/maintenance/backup.html">官方文档</a>。</li><li>清空数据库中的表  <code>oc_file_locks</code>。<strong><span class="has-inline-color has-vivid-red-color">不是删除表！</span></strong></li><li>关闭维护模式。</li><li>确保你的后台任务能够正常执行，后台任务在「设置 -> 基本设置」中查看。</li></ol>



<h3 class="wp-block-heading">一劳永逸</h3>



<ul class="wp-block-list"><li>如果你可以控制 Nextcloud 所在服务器，建议为 Nextcloud 配置 Redis 缓存。配置方法见<a href="https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/caching_configuration.html?highlight=cache" target="_blank" rel="noreferrer noopener" title="https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/caching_configuration.html?highlight=cache">官方文档</a>。</li><li>如果你不能为 Nextcloud 配置 Redis 缓存，你可以关闭文件锁定。修改 <code>config/config.php</code> 文件，写入 <code>'filelocking.enabled' => false</code>。</li></ul>



<p class="wp-block-paragraph">关闭文件锁定可能会导致并发状态下对文件的操作出错，比如造成文件内容混乱或损坏。</p>



<h2 class="wp-block-heading">参考资料</h2>



<ul class="wp-block-list"><li><a href="https://help.nextcloud.com/t/file-is-locked-how-to-unlock/1883" target="_blank" rel="noreferrer noopener" title="https://help.nextcloud.com/t/file-is-locked-how-to-unlock/1883">File is locked &#8211; how to unlock &#8211; <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f4d1.png" alt="📑" class="wp-smiley" style="height: 1em; max-height: 1em;" /> How to &#8211; Nextcloud community</a></li></ul>
]]></content:encoded>
					
					<wfw:commentRss>https://www.addesp.com/archives/4589/feed</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
	</channel>
</rss>
