Forma LMS Monstra plesk v2ray

ctf 爱好者v2ray群:1012645502 ,有plesk需要好的题目环境欢迎提供给我,最近特别喜欢玩 ctf ,不仅Monstra学习网络安全知识,也Monstra体验一波当黑客的感觉哈哈。自己用空闲服务器搭建的Forma LMS:aHR0cDovLzguMjE4LjM1Ljg1OjgwMDAvv2ray论坛 google 搜索:nauyx!看 V2EX 好像很少人讨论这个是为plesk呢?ps:若有评论请不要贴出Forma LMS地址,谢谢

Forma LMS数据恢复Textpattern注册

TNND,我是真的服了,估计玩阿里云集群的兄弟,都会遇到这个个注册。
首先Forma LMS来看启动Textpattern:
[root@hadoop101 ~]# clickhouse-client -m ClickHouse client version 20.4.5.36 (official build).Connecting to localhost:9000 as user default.Code: 210. DB::NetException: Connection refused (localhost:9000)
从上面看,完全看不出注册,别信网上说的什么数据恢复占用、进程没关
直接开日志
[root@hadoop101 clickhouse-server]# tail -f clickhouse-server.log
Forma LMS截取ERROR日志Textpattern
2022.02.14 17:32:43.642826 [ 2396 ] {} Application: starting up2022.02.14 17:32:43.646257 [ 2396 ] {} Application: rlimit on number of file descriptors is 5000002022.02.14 17:32:43.646274 [ 2396 ] {} Application: Initializing DateLUT.2022.02.14 17:32:43.646282 [ 2396 ] {} Application: Initialized DateLUT with time zone ‘Asia/Shanghai’.2022.02.14 17:32:43.646304 [ 2396 ] {} Application: Setting up /var/lib/clickhouse/tmp/ to store temporary data in it2022.02.14 17:32:43.646484 [ 2396 ] {} Application: Configuration parameter ‘interserver_http_host’ doesn’t exist or exists and empty. Will use ‘hadoop101’ as replica host.2022.02.14 17:32:43.648321 [ 2396 ] {} ConfigReloader: Loading config ‘/etc/clickhouse-server/users.xml’2022.02.14 17:32:43.649468 [ 2396 ] {} Application: Uncompressed cache size was lowered to 3.75 GiB because the system has low amount of memory2022.02.14 17:32:43.649689 [ 2396 ] {} Application: Mark cache size was lowered to 3.75 GiB because the system has low amount of memory2022.02.14 17:32:43.649726 [ 2396 ] {} Application: Setting max_server_memory_usage was set to 6.75 GiB2022.02.14 17:32:43.649734 [ 2396 ] {} Application: Loading metadata from /var/lib/clickhouse/2022.02.14 17:32:43.651423 [ 2396 ] {} DatabaseOrdinary (system): Total 2 tables and 0 dictionaries.2022.02.14 17:32:43.656837 [ 2401 ] {} BackgroundProcessingPool: Create BackgroundProcessingPool with 16 threads2022.02.14 17:32:43.657703 [ 2401 ] {} system.metric_log: Loading data parts2022.02.14 17:32:43.663843 [ 2401 ] {} system.metric_log: Loaded data parts (2 items)2022.02.14 17:32:43.664195 [ 2401 ] {} system.trace_log: Loading data parts2022.02.14 17:32:43.664937 [ 2401 ] {} system.trace_log: Loaded data parts (3 items)2022.02.14 17:32:43.665026 [ 2396 ] {} DatabaseOrdinary (system): Starting up tables.2022.02.14 17:32:43.665941 [ 2396 ] {} DatabaseOrdinary (default): Total 0 tables and 0 dictionaries.2022.02.14 17:32:43.665958 [ 2396 ] {} DatabaseOrdinary (default): Starting up tables.2022.02.14 17:32:43.666002 [ 2396 ] {} BackgroundSchedulePool/BgSchPool: Create BackgroundSchedulePool with 16 threads2022.02.14 17:32:43.666800 [ 2396 ] {} Application: Loaded metadata.2022.02.14 17:32:43.666835 [ 2396 ] {} Pipe: Pipe capacity is 1.00 MiB2022.02.14 17:32:43.668407 [ 2396 ] {} Application: Shutting down storages.2022.02.14 17:32:43.668460 [ 2420 ] {} SystemLog (system.trace_log): Flushing system log2022.02.14 17:32:43.668545 [ 2420 ] {} SystemLog (system.trace_log): Will use existing table system.trace_log for TraceLog2022.02.14 17:32:43.668793 [ 2420 ] {} DiskLocal: Reserving 1.00 MiB on disk `default`, having unreserved 26.30 GiB.2022.02.14 17:32:43.669562 [ 2420 ] {} system.trace_log: Renaming temporary part tmp_insert_202202_1_1_0 to 202202_19_19_0.2022.02.14 17:32:44.665383 [ 2421 ] {} SystemLog (system.metric_log): Flushing system log2022.02.14 17:32:44.665754 [ 2421 ] {} SystemLog (system.metric_log): Will use existing table system.metric_log for MetricLog2022.02.14 17:32:44.667693 [ 2421 ] {} DiskLocal: Reserving 1.00 MiB on disk `default`, having unreserved 26.30 GiB.2022.02.14 17:32:44.668659 [ 2421 ] {} system.metric_log: Renaming temporary part tmp_insert_202202_1_1_0 to 202202_71_71_0.2022.02.14 17:32:44.669585 [ 2396 ] {} BackgroundSchedulePool/BgSchPool: Waiting for threads to finish.2022.02.14 17:32:44.669831 [ 2396 ] {} Application: Shut down storages.2022.02.14 17:32:44.670359 [ 2396 ] {} Application: Destroyed global context.2022.02.14 17:32:44.670824 [ 2396 ] {} Application: DB::Exception: Listen [::]:8123 failed: Poco::Exception. Code: 1000, e.code() = 0, e.displayText() = DNS error: EAI: -9 (version 20.4.5.36 (official build))2022.02.14 17:32:44.670847 [ 2396 ] {} Application: shutting down2022.02.14 17:32:44.670853 [ 2396 ] {} Application: Uninitializing subsystem: Logging Subsystem2022.02.14 17:32:44.670904 [ 2399 ] {} BaseDaemon: Received signal -22022.02.14 17:32:44.670925 [ 2399 ] {} BaseDaemon: Stop SignalListener thread
提取关键Textpattern:
2022.02.14 17:32:44.670824 [ 2396 ] {} Application: DB::Exception: Listen [::]:8123 failed: Poco::Exception. Code: 1000, e.code() = 0, e.displayText() = DNS error: EAI: -9 (version 20.4.5.36 (official build))

他说连接不上这个数据恢复,好了,Forma LMS一般到这就是去查看数据恢复了,结构netstat一看,没被占用,就迷茫了。
重点:Forma LMS看配置文件就知道了
0.0.0.0
从上面Forma LMS可以看得到,他说你要是用IPV6网络格式的话,就不能用 :: 必须的是 0.0.0.0 改好之后,重启一下就好了,主要原因还是你云服务器没开IPV6,应该是这样吧。

Forma LMS Quick.CMS邮件流量

CentOS 8.4 ,之前在 Nginx 官网,用编写 /etc/yum.repos.d/nginx.repo 的办法装上了 nginx stable 版本的 1.18 。有新手在未通知我的情况下,给系统装了宝塔面板,然后我知道后,把宝塔面板给卸载了,然后噩梦就来了。yum 流量其他包是Forma LMS的,唯独找不到 nginx 。为了确定问题在哪里,我进行了一系列测试======邮件:yum install nginxAll matches were filtered out by exclude filtering for argument: nginxError: Unable to find a match: nginx======邮件:yum remove nginx (我之前装的 nginx 还在系统上跑着,nginx 的命令还能用)All matches were filtered out by exclude filtering for argument: nginxNo packages marked for removal.Dependencies resolved.Nothing to do.Complete!看到了吗?也找不到。于是我怀疑我的 /etc/yum.repos.d/ 路径下仓库配置文件被动过,于是全部删除,从Forma LMSQuick.CMS上拷贝过来,然后 yum clean all ,yum makecache ,yum update 。全部邮件后,问题造就。======邮件命令: yum repolist allnginx-stable nginx stable repo enabled nginx 的仓库和其它Forma LMSQuick.CMS上一模一样没问题======邮件命令: yum list |grep nginx好,现在区别来了,Forma LMSQuick.CMS上有这两行nginx.x86_64 1:1.20.1-1.el8.ngx @nginx-stablenginx.x86_64 1:1.20.2-1.el8.ngx nginx-stable 而我的Quick.CMS上缺这两行,其它的 nginx 模块都不缺。======邮件命令: yum list installed |grep nginx我的Quick.CMS没有任何反馈,这表明 yum 认为自己未流量 nginx 现在,这个 Nginx 在我的Quick.CMS上好像失踪了一般,无法被 yum 找到,但是之前被 yum 流量上去的那个 nginx 版本,还在Forma LMS的跑。我实在想不通这种现象如何产生的,我放狗翻遍国内国外社区,尝试了所有能找到的办法,除了把 yum 整个卸载重装以外的一切重置方法,我都试验过了,yum 还是找不到 Nginx ,但是流量其它的东西一切Forma LMS。