易栈网-膘叔

jq是linux命令行下读取和解析JSON的好工具。只是好象不能jq xxx.json这样的用法，但没事，可以通过管道符，cat xxx.json|jq 就OK了

在这里：https://www.tuicool.com/articles/vieMN3Q有详细的教程，写的非常完整，但如果简单的使用，并不需要完整的看完，只要记得几个用法就行

来个简单的数据：{"code":1,"msg":"ok","data":{"fields":["a","b","c"],"items":[{1,2,3},{11,22,33}],"other":[{"x":1,"y":1},{"x":2,"y":2}]}}

1、获取items节点： cat xxx.json|jq ".data.items"

2、获取items下第二条数据的第二个，即22.   cat xxx.json|jq ".data.items[1][1]"

3、获取other下的所有x节点： cat xxx.json|jq ".data.other[].x"

是不是很方便？如果要自定义格式输出，还可以这样

1、将所有x节点用{"items":[]}格式输出： cat xxx.json| jq "{items: [ .data.other[].x ]}" ，

如果要看更多的用法，还是上面的网址里更详细一点。我这只是简单的用一下。。或者说是临时在服务器上测试数据，让自己看起来会比较方便一点。还有一个原因是我在服务器上用这个的最大理由。有时候JSON拿到的时候中文都是转义过的。用jq，可以直接看中文。这点比较爽

 如题。如果文件是"-test.log"，是的你没看错。文件名前面有一个减号。如果你直接使用：rm -test.log，会报如下错误：

毕竟。- 是有特殊意义的。那怎么删除呢？也简单：

文件就这样被删除了。事实上，象这种"-"（减号、负号）开头的文件。因为它自带的特殊意义（linux下命令行的参数前缀），所以你用touch\vim等命令，其实都无法创建这样的文件。不信你试试"touch -test.log"。当然，你也是可以用touch -- -test.log来创建（其他类似）

 比较简单的设置，就是利用 sshconfig 。

 上一篇博客说了。我用vsc的ssh-remote的时候，30秒或者1分钟必断。错误信息一直就类似：

[04:30:38.608] "install" terminal command done
[04:30:38.609] Install terminal quit with output:
[04:31:18.258] SSH Resolver called for "ssh-remote+neatstudio.com", attempt 2
[04:31:18.258] SSH Resolver called for host: neatstudio.com
[04:31:18.259] Setting up SSH remote "neatstudio.com"
[04:31:18.259] Using commit id "f06011ac164ae4dc8e753a3fe7f9549844d15e35" and quality "stable" for server
[04:31:18.263] Running script with connection command: ssh -o ClearAllForwardings=true -o ConnectTimeout=15 neatstudio.com bash
[04:31:18.263] Install and start server if needed
[04:31:35.269] Connecting with SSH timed out
[04:31:35.269] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"Timeout"},"measures":{"resolveAttempts":2,"retries":1}}
[04:31:35.269] ------

重连后也是

[04:37:06.477] SSH Resolver called for "ssh-remote+neatstudio.com", attempt 12
[04:37:06.477] SSH Resolver called for host: neatstudio.com
[04:37:06.477] Setting up SSH remote "neatstudio.com"
[04:37:06.478] Using commit id "f06011ac164ae4dc8e753a3fe7f9549844d15e35" and quality "stable" for server
[04:37:06.479] Running script with connection command: ssh -o ClearAllForwardings=true -o ConnectTimeout=15 neatstudio.com bash
[04:37:06.480] Install and start server if needed
[04:37:21.515] > ssh: connect to host 123.176.103.247 port 22: Operation timed out
[04:37:21.515] Got some output, clearing connection timeout
[04:37:21.776] "install" terminal command done
[04:37:21.776] Install terminal quit with output: ssh: connect to host 123.176.103.247 port 22: Operation timed out
[04:37:21.776] Received install output: ssh: connect to host 123.176.103.247 port 22: Operation timed out
[04:37:21.777] The operation timed out
[04:37:21.777] TELEMETRY: {"eventName":"resolver","properties":{"outcome":"failure","reason":"OfflineError"},"measures":{"resolveAttempts":12,"retries":1}}
[04:37:21.777] ------

发了ticket给layerstack。他们测试也来没有这个问题。我开始以为是什么openfiles limit的问题。也打开到最大了。

期间调整了一下这个：echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p，因为开始有报inotify max error

直到他们给我发了一个ticket：

Thank you for your patience in this matter.

We have investigated the issue in detail and we are not able to recreate the issue from our end. We have checked the same from multiple locations and find out its working fine.

The reported issue seems to be related to your local ISP, so we suggest you to change the standard port (22) of SSH to some other non standard port like 2222 or 2244, in server and recheck the issue.

Please do have a check on our above suggestion and let us know if you still face any issues in accessing.

所以我就想了一下，直接把PORT改成了2222，2223，2244，然而仍然 失败，最后我用了一个超大端口，居然正常了

 如题。本来想切caddy的。caddy已经更新。但因为我用的是lightsail，结果又不能自动更新。而当前域名，我切到了aws 的lightsail。因为lightsail属于aws旗下，必须得由IAM等管理工具来配权限，然而lightsail却只有action没有policy。不知道怎么配了

但奇怪的是，ssldocker却可以申请证书。caddy一直报没有权限（caddy我还配置了aws_app_key.....反而不行，而ssldocker啥也不要）

再坚持几天。如果ssldocker继续 不稳定（systemd 重启失败多次），还是恢复成nginx + acme.sh （或者certbot）。。或者。。。实在不行，切回dnspod！！！NND