Raspbian上snapd狂吃CPU问题

2020-07-22 作者： Fisherworks

To get rid of snapd on Raspbian/RaspberryPi OS Buster, since it eats lots of cpu power, especially on the old hardware, like a Pi 2B.

一台年迈的Pi 2B，运行着时时更新的Raspbian Buster，兢兢业业给娃做文件服务器，不亦乐乎。

一天apt dist-upgrade之后，就发现system load频繁升高，系统空载就能吃掉大致一个核的性能。top后画风大致是这样的。

➜  ~ top
top - 22:26:04 up 2 days, 13:44,  3 users,  load average: 0.96, 0.99, 0.93
Tasks: 143 total,   1 running, 142 sleeping,   0 stopped,   0 zombie
%Cpu(s):  8.4 us,  2.7 sy,  0.0 ni, 82.4 id,  6.3 wa,  0.0 hi,  0.2 si,  0.0 st
MiB Mem :    926.1 total,    222.2 free,    171.1 used,    532.7 buff/cache
MiB Swap:    100.0 total,    100.0 free,      0.0 used.    693.0 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
  345 root      20   0  968804  21248  13064 S  37.3   2.2   1065:41 snapd
   84 root      20   0       0      0      0 S   1.0   0.0  28:27.25 jbd2/mmcblk0p2-
15049 pi        20   0   10440   3096   2540 R   1.0   0.3   0:00.09 top
  346 root      20   0    2968   2060   1564 S   0.7   0.2   2:17.19 dhcpcd
17101 root       0 -20       0      0      0 I   0.7   0.0   2:49.94 kworker/0:1H-mmc_complete
   10 root      20   0       0      0      0 I   0.3   0.0   7:00.05 rcu_sched
   18 root       0 -20       0      0      0 I   0.3   0.0   4:21.89 kworker/1:0H-kblockd
   83 root       0 -20       0      0      0 I   0.3   0.0   4:24.37 kworker/2:1H-kblockd
  412 root      20   0   31976   9496   8068 S   0.3   1.0   0:29.19 nmbd

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

➜ ~ top

top - 22:26:04 up 2 days, 13:44, 3 users, load average: 0.96, 0.99, 0.93

Tasks: 143 total, 1 running, 142 sleeping, 0 stopped, 0 zombie

%Cpu(s): 8.4 us, 2.7 sy, 0.0 ni, 82.4 id, 6.3 wa, 0.0 hi, 0.2 si, 0.0 st

MiB Mem : 926.1 total, 222.2 free, 171.1 used, 532.7 buff/cache

MiB Swap: 100.0 total, 100.0 free, 0.0 used. 693.0 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND

345 root 20 0 968804 21248 13064 S 37.3 2.2 1065:41 snapd

84 root 20 0 0 0 0 S 1.0 0.0 28:27.25 jbd2/mmcblk0p2-

15049 pi 20 0 10440 3096 2540 R 1.0 0.3 0:00.09 top

346 root 20 0 2968 2060 1564 S 0.7 0.2 2:17.19 dhcpcd

17101 root 0 -20 0 0 0 I 0.7 0.0 2:49.94 kworker/0:1H-mmc_complete

10 root 20 0 0 0 0 I 0.3 0.0 7:00.05 rcu_sched

18 root 0 -20 0 0 0 I 0.3 0.0 4:21.89 kworker/1:0H-kblockd

83 root 0 -20 0 0 0 I 0.3 0.0 4:24.37 kworker/2:1H-kblockd

412 root 20 0 31976 9496 8068 S 0.3 1.0 0:29.19 nmbd

于是很想了解这货在干嘛，消耗这么多脑力，思考人生么？

➜  ~ sudo lsof -p 345
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
      Output information may be incomplete.
COMMAND PID USER   FD      TYPE     DEVICE SIZE/OFF   NODE NAME
snapd   345 root  cwd       DIR      179,2     4096      2 /
snapd   345 root  rtd       DIR      179,2     4096      2 /
snapd   345 root  txt       REG        7,0 13421332   7147 /snap/core/9291/usr/lib/snapd/snapd
snapd   345 root  mem       REG      179,2  1296004   2022 /lib/arm-linux-gnueabihf/libc-2.28.so
snapd   345 root  mem       REG      179,2   130416   2085 /lib/arm-linux-gnueabihf/libpthread-2.28.so
snapd   345 root  mem       REG      179,2    17708  10917 /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so
snapd   345 root  mem       REG      179,2   138604   1945 /lib/arm-linux-gnueabihf/ld-2.28.so
snapd   345 root    0r      CHR        1,3      0t0   1028 /dev/null
snapd   345 root    1u     unix 0xf31a5a4c      0t0  14576 type=STREAM
snapd   345 root    2u     unix 0xf31a5a4c      0t0  14576 type=STREAM
snapd   345 root    3u     IPv4     152109      0t0    TCP 192.168.50.127:48604->api.snapcraft.io:https (ESTABLISHED)
snapd   345 root    4u     IPv4     233503      0t0    TCP 192.168.50.127:40786->api.snapcraft.io:https (ESTABLISHED)
snapd   345 root    6u  a_inode       0,11        0   5804 [eventpoll]
snapd   345 root    7u     unix 0x5b752603      0t0  14350 /run/snapd.socket type=STREAM
snapd   345 root    8u     unix 0xfebd686d      0t0  14353 /run/snapd-snap.socket type=STREAM
snapd   345 root    9u      REG      179,2        0 386387 /var/lib/snapd/snaps/core_9668.snap.partial
snapd   345 root   12u  netlink                 0t0  18728 KOBJECT_UEVENT
snapd   345 root   13r     FIFO       0,10      0t0  18729 pipe
snapd   345 root   14w     FIFO       0,10      0t0  18729 pipe

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

➜ ~ sudo lsof -p 345

lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs

Output information may be incomplete.

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

snapd 345 root cwd DIR 179,2 4096 2 /

snapd 345 root rtd DIR 179,2 4096 2 /

snapd 345 root txt REG 7,0 13421332 7147 /snap/core/9291/usr/lib/snapd/snapd

snapd 345 root mem REG 179,2 1296004 2022 /lib/arm-linux-gnueabihf/libc-2.28.so

snapd 345 root mem REG 179,2 130416 2085 /lib/arm-linux-gnueabihf/libpthread-2.28.so

snapd 345 root mem REG 179,2 17708 10917 /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so

snapd 345 root mem REG 179,2 138604 1945 /lib/arm-linux-gnueabihf/ld-2.28.so

snapd 345 root 0r CHR 1,3 0t0 1028 /dev/null

snapd 345 root 1u unix 0xf31a5a4c 0t0 14576 type=STREAM

snapd 345 root 2u unix 0xf31a5a4c 0t0 14576 type=STREAM

snapd 345 root 3u IPv4 152109 0t0 TCP 192.168.50.127:48604->api.snapcraft.io:https (ESTABLISHED)

snapd 345 root 4u IPv4 233503 0t0 TCP 192.168.50.127:40786->api.snapcraft.io:https (ESTABLISHED)

snapd 345 root 6u a_inode 0,11 0 5804 [eventpoll]

snapd 345 root 7u unix 0x5b752603 0t0 14350 /run/snapd.socket type=STREAM

snapd 345 root 8u unix 0xfebd686d 0t0 14353 /run/snapd-snap.socket type=STREAM

snapd 345 root 9u REG 179,2 0 386387 /var/lib/snapd/snaps/core_9668.snap.partial

snapd 345 root 12u netlink 0t0 18728 KOBJECT_UEVENT

snapd 345 root 13r FIFO 0,10 0t0 18729 pipe

snapd 345 root 14w FIFO 0,10 0t0 18729 pipe

看起来是想回家拉点什么私货回来（api.snapcraft.io），但还是搞不懂，走io就走io，连续几天24小时一直吃那么多cpu是什么鬼？

完整阅读本篇»

强力！乳状积云+雷雨

2020-07-07 作者： Fisherworks

高考前日（2020-07-06）傍晚，迎来一场短时豪雨。
按父亲的话说，再干旱的年份，高考总要滴上几滴的，无他，老人言此乃龙王爷鼓励年轻人奋勇争先。何况今年本来雨水就足，这场不过1小时瓢泼大雨，算是给高考学子们示下的好兆头咯。

话说昨日晚霞长这样（小区群盗图）：

让人不禁联想起《航空气象》书里的乳状积云的照片：

再看当时的首都机场METAR情况（按时间早→晚排列）：

完整阅读本篇»

“小森林” 码工版

2020-06-28 作者： Fisherworks

明．陈全之《蓬窗日录》卷八：“春耕夏耨（nòu），敢辞涂足之勤；秋获冬藏，实切资身之望。”

日剧《小森林》，前后两部四集，全面的描绘出一个不甘挣扎于城市枯燥生活的妹子，返乡后独居，靠自己一双手打造返璞归真“小确幸”的图景，唯美、静心。本是2014/2015的片子，不知为何，去年突然火爆国内，还盖上“日版李子柒”的标签，颇觉给脑袋里整日萦绕“逃离北上广”的年轻人们一丝抚慰。

“农协开的小超市，冬雪中需步行一个半小时，而去临镇的大型城外超市购物，来回要一整天”，一句话下来，心凉半截；前可着村，但后不着店，换言之，一切靠自己了。

剧集展现给我们的，也确实如此：一日三餐，每餐结束之后，手头活计如果不是在准备下一餐，应该就是在准备下N餐（腌制发酵食品，或晾晒干制食品），日复一日，周而复始。另有国产美食剧集《一人食》好像也是在2014年上线的，并没有很火，我也没有看过，家里那口子倒是个不折不扣的美食爱好者。

洋洋洒洒说了这么多，跟码工又有几毛钱关系呢？码工嘛，又称“互联网从业者”，算是近年实体经济普遍乏力后，苦出身底层娃们为数不多的上升通道了。

所谓互联网大厂，自然有大厂的好处。流水线作业毕竟分工细，需求有人出，测试有人做，UI有人画，运维有人管，自己聚焦自己的一亩三分地；即使起新项目，研发主管还给脚手架工程做参考，说到底，搬砖就搬自己的砖，搬多少块结多少账，公平合理。要在大厂晋升，当然也是有讲究的。真材实料不可或缺，搬砖一路搬到CTO多半不可行；即使做技术主管，也得有点架构意识，当个“流水线线长”，知道不同目标需求下的技术组合和性能指标，关注外界趋势，跟合作项目组打太极，了解手底下那几个货适合搬什么砖，以及他们万一不干了，排队来搬砖的还有谁，等等。

言而总之，大厂工作如果不来点自黑，比拼个端午、中秋礼包设计，那真像极了城市生活两点一线，日子不停复制粘贴的感觉。作为移动互联网时代流水线工人，面对“弹性工作”、“996”等潜台词，再看看蒸蒸日上的业务，合同上不菲的现金和RSU，照旧叹一口气，进会议室继续抢项目撕B。

那你的意思是，码工也能回村自给自足，搞“一人码”？

也是，也不是。

全栈工程师不新鲜，算得上自给自足。至于要不要回村，您请自便，如果是农业创业，老板、市场、销售、PM、DevOps、运营、物流啥的您都一人扛了，咱也佩服；如若仅仅实现一人码，那大可不必，怎么也得考虑对接需求方要顺畅吧。

呃……废话太多，来点干货。

好吧，这篇围绕“一人码”的博文，其实来自于处理我“一人码”的一次线上故障。

完整阅读本篇»

CentOS7免费SSL证书及自动展期

2020-06-14 作者： Fisherworks

This post shows you how to obtain a wildcard SSL certificate for free (which values at least $50) from Let’s Encrypt on CentOS 7.x Linux, and get it setup to renew by itself with an automated script.

至于什么是SSL证书，有什么用，这里不赘述了。大致上，一个泛域名（通配符）DV证书，价值怎么也在CNY 2000/年开外，注意是按年缴费；企业型（OV）证书则更贵，年费肯定不下万。因此别嫌命令行操作不好搞，有免费午餐已然相当给力，还要啥自行车。

按规矩，周知一下，证书发行方是Let’s Encrypt。之所以能送免（bai）费（piao）证书，据说主要是全自动。证书生成、发放、展期等操作，都经shell脚本完全自动化 —— 无人工就成本低，蛮好理解；至于抢了那几家拦路收费的生意，咱也捧个人场，起码希望他们能一直坚持做下去。

证书自动获取

来一台阿里云上的CentOS7，以非root（但具备sudo权限）用户连接，先下载certbot-auto脚本，并授以执行权限。

[py27@fisher-test ~]$ wget https://dl.eff.org/certbot-auto 
--2020-06-11 22:57:34--  https://dl.eff.org/certbot-auto
正在解析主机 dl.eff.org (dl.eff.org)... 151.101.228.201, 2a04:4e42:1a::201 
正在连接 dl.eff.org ... 已连接。 
已发出HTTP 请求，正在等待回应... 200 OK
长度：79897 (78K) [application/octet-stream]
正在保存至: “certbot-auto”
 
100%[===============================>] 79,897      5.73KB/s 用时13s
 
2020-06-11 22:57:50 (6.03 KB/s) - 已保存 “certbot-auto” [79897/79897])

1

2

3

4

5

6

7

8

9

10

11

[py27@fisher-test ~]$ wget https://dl.eff.org/certbot-auto

--2020-06-11 22:57:34-- https://dl.eff.org/certbot-auto

正在解析主机 dl.eff.org (dl.eff.org)... 151.101.228.201, 2a04:4e42:1a::201

正在连接 dl.eff.org ... 已连接。

已发出HTTP 请求，正在等待回应... 200 OK

长度：79897 (78K) [application/octet-stream]

正在保存至: “certbot-auto”

100%[===============================>] 79,897 5.73KB/s 用时13s

2020-06-11 22:57:50 (6.03 KB/s) - 已保存 “certbot-auto” [79897/79897])

然后以手工完成“挑战”（challenge）的方式，获取泛域名（通配符）DV证书，其中挑战选择DNS，也即按脚本要求，手工在域名解析中增加TXT记录 —— 以此证明此域名归属于申请者。

[py27@fisher-test ~]$ ./certbot-auto certonly  -d *.fisher.cn --manual --preferred-challenges dns --server https://acme-v02.api.letsencrypt.org/directory
Requesting to rerun ./certbot-auto with root privileges...
./certbot-auto has insecure permissions!
To learn how to fix them, visit https://community.letsencrypt.org/t/certbot-auto-deployment-best-practices/91979/
Saving debug log to /var/log/letsencrypt/letsencrypt.log（这里存放获取证书全过程日志供参考）
Plugins selected: Authenticator manual, Installer None
Obtaining a new certificate
Performing the following challenges:
dns-01 challenge for fisher.cn
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NOTE: The IP of this machine will be publicly logged as having requested this
certificate. If you're running certbot in manual mode on a machine that is not
your server, please ensure you're okay with that.
 
Are you OK with your IP being logged?（作为申请数字证书的要求，是否可以记录本机IP）
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: Y
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Please deploy a DNS TXT record under the name
_acme-challenge.fisher.cn with the following value:（在域名中增加TXT解析，以完成“挑战”）
 
MomldPnAKL4I8bL8FiwmqvJJdE7E97RH-ARf7PZgw88
 
Before continuing, verify the record is deployed.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press Enter to Continue（此处暂停，登你的DNS，设置解析；搞定后此处回车）【注：过后可删除】
Waiting for verification...
Cleaning up challenges
 
IMPORTANT NOTES:
- Congratulations! Your certificate and chain have been saved at:（证书获取成功，存放位置如下）
   /etc/letsencrypt/live/fisher.cn/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/fisher.cn/privkey.pem
   Your cert will expire on 2020-09-11. To obtain a new or tweaked（证书过期时间，及更新方法）
   version of this certificate in the future, simply run certbot-auto
   again. To non-interactively renew *all* of your certificates, run
   "certbot-auto renew"
- If you like Certbot, please consider supporting our work by:
 
   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

[py27@fisher-test ~]$ ./certbot-auto certonly -d *.fisher.cn --manual --preferred-challenges dns --server https://acme-v02.api.letsencrypt.org/directory

Requesting to rerun ./certbot-auto with root privileges...

./certbot-auto has insecure permissions!

To learn how to fix them, visit https://community.letsencrypt.org/t/certbot-auto-deployment-best-practices/91979/

Saving debug log to /var/log/letsencrypt/letsencrypt.log（这里存放获取证书全过程日志供参考）

Plugins selected: Authenticator manual, Installer None

Obtaining a new certificate

Performing the following challenges:

dns-01 challenge for fisher.cn

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

NOTE: The IP of this machine will be publicly logged as having requested this

certificate. If you're running certbot in manual mode on a machine that is not

your server, please ensure you're okay with that.

Are you OK with your IP being logged?（作为申请数字证书的要求，是否可以记录本机IP）

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

(Y)es/(N)o: Y

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Please deploy a DNS TXT record under the name

_acme-challenge.fisher.cn with the following value:（在域名中增加TXT解析，以完成“挑战”）

MomldPnAKL4I8bL8FiwmqvJJdE7E97RH-ARf7PZgw88

Before continuing, verify the record is deployed.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Press Enter to Continue（此处暂停，登你的DNS，设置解析；搞定后此处回车）【注：过后可删除】

Waiting for verification...

Cleaning up challenges

IMPORTANT NOTES:

- Congratulations! Your certificate and chain have been saved at:（证书获取成功，存放位置如下）

/etc/letsencrypt/live/fisher.cn/fullchain.pem

Your key file has been saved at:

/etc/letsencrypt/live/fisher.cn/privkey.pem

Your cert will expire on 2020-09-11. To obtain a new or tweaked（证书过期时间，及更新方法）

version of this certificate in the future, simply run certbot-auto

again. To non-interactively renew *all* of your certificates, run

"certbot-auto renew"

- If you like Certbot, please consider supporting our work by:

Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate

Donating to EFF: https://eff.org/donate-le

那么证书如何将http通信升级为https，不同的后端有不同的代码实现方式。但就目前主流做法，大家倾向于让https通信脱离开发范畴，直接配置在httpd中，比如nginx config（或者apache之类均可）：

完整阅读本篇»

两机rsync定时单向只增同步

2020-05-27 作者： Fisherworks

事出有因

老房子装修没布网线，远在北卧192.168.1.128（wifi连接）是娃的网课机，需要播放音视频及office文档；该机wifi连接不算可靠（一堵大量钢筋砖混承重，一堵普通轻体），好的时候24Mbps，偶发连接不稳定的时候会断开；而路由器已经更新为口碑产品Netgear R6700
另有树莓派192.168.1.127（有线LAN，可靠连接）作为7×24文件服务器，用于从ddns接收外来课件，并对1.128提供文件共享服务

问题澄清

课件播放过程中，偶发wifi信号问题导致卡顿

问题思路

由于wifi中断为偶发，大部分情况下连接OK
采取让1.128机器定时（每1小时）去1.127机器同步课件的思路
前者存储大（HDD），后者小（TF），设计为单向同步；后者新增，前者同步，后者删除，前者保留

具体实现

#!/usr/bin/bash

echo `date`

FILE_SERVER=192.168.1.127
ping -c 3 -w 5 $FILE_SERVER
# ping不通则不进行同步（说明1.127未连接）
if [[ $? != 0 ]];then
    echo " target is offline! "
    exit 1
fi

pidof rsync
# 如果正在同步，则不开启新的同步
if [[ $? == 0 ]];then
    echo " rsync is still working! "
    exit 2
fi

echo "server ok, start transmission... "
rsync -uavzP --exclude=".*" pi@$FILE_SERVER:/share/documents '/home/py27/documents/learnings'
exit 0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

#!/usr/bin/bash

echo `date`

FILE_SERVER=192.168.1.127

ping -c 3 -w 5 $FILE_SERVER

# ping不通则不进行同步（说明1.127未连接）

if [[ $? != 0 ]];then

echo " target is offline! "

exit 1

fi

pidof rsync

# 如果正在同步，则不开启新的同步

if [[ $? == 0 ]];then

echo " rsync is still working! "

exit 2

fi

echo "server ok, start transmission... "

rsync -uavzP --exclude=".*" pi@$FILE_SERVER:/share/documents '/home/py27/documents/learnings'

exit 0

测试以上脚本工作ok后，将其加入crontab，每小时定时执行

py27@py27-vince:~$ crontab -l 
0 */1 * * * /home/py27/scripts/rsync_learnings.sh > /tmp/rsync_learnings.log  2>&1

1 2	py27@py27-vince:~$ crontab -l 0 /1 * * /home/py27/scripts/rsync_learnings.sh > /tmp/rsync_learnings.log 2>&1

后续计划

观察课件同步效果，有问题检查log，总之能用技术解决的问题，就别给人找事干
目前wifi网卡为Intel AC9260 M.2，两根8dBi天线；有空可以考虑升级到带延长线的磁性吸盘12dBi天线，增强wifi稳定性

完整阅读本篇»

Raspbian上snapd狂吃CPU问题

强力！乳状积云+雷雨

“小森林” 码工版

CentOS7免费SSL证书及自动展期

证书自动获取

两机rsync定时单向只增同步

事出有因

问题澄清

问题思路

具体实现

后续计划

关于Fisherworks

最近文章

功能

本站友链

实时天气

2024年十二月
一	二	三	四	五	六	日
« 10月
						1
2	3	4	5	6	7	8
9	10	11	12	13	14	15
16	17	18	19	20	21	22
23	24	25	26	27	28	29
30	31