逆光之数

MySQL误操作后数据恢复（delete）

Posted on 2024-09-21 Edited on 2025-03-12

误删除数据恢复

client online 监听

Posted on 2022-08-22 Edited on 2024-03-21

用户状态监测

根据client的ping消息，监听用户状态

分时采集ping 消息

每隔5S，采集10S内的ping消息

time_now, ms_delta, listen_list = int(time.time()), 0, []
while ms_delta < 10:
    value = MQ.message
    if value:
        listen_list.append(value)
    ms_delta = int(time.time()) - time_now
func(listen_list)
time.sleep(5)

这里面有一个小技巧，采集10S内的ms，可以用时间差作为循环控制条件

差值思想，获取未ping的客户端（下线状态）

上述步骤获取当前10S内的ping消息，online_list

关键：通过redis获取上次前10S内的ping消息，last_online

如果last_online为空，说明当前offline_list不存在。将当前的online_list存入到redis，并作为下次的last_online

cache_key = ""
   if not value_list:
       redis_client.delete(cache_key)

   with redis_client.pipeline() as pipe:
       pipe.multi()
       pipe.delete(cache_key)
       pipe.sadd(cache_key, *value_list)
       pipe.expireat(cache_key, expired_at)
       pipe.execute()

如果last_online不为空，则当前不在线状态为：offline_list = last_online - online_list

kafka-python debug log

Posted on 2021-12-03 Edited on 2024-03-21

python禁掉kafka debug日志

django 中使用kafka，但kafka 的debug日志会无限输出到日志文件中，非常头痛。

1
2
3

INFO 2022-07-29 08:46:51,544 0cd0ec8c3b57480093f54a8907cb2a63 [base._handle_group_coordinator_response line:694] Discovered coordinator coordinator-0 for group g1
WARNING 2022-07-29 08:46:51,544 0cd0ec8c3b57480093f54a8907cb2a63 [base.coordinator_dead line:716] Marking the coordinator dead (node coordinator-0) for group g1: Node Disconnected.
WARNING 2022-07-29 08:46:51,544 2d9682ce3ecd4d0481e70f9acd8ebdf2 [base.coordinator_dead line:716] Marking the coordinator dead (node coordinator-0) for group g1: Node Disconnected.

根本原因在于，kafka的python包中 logger = logging.getLogger("kafka")
如果在django 的setting中没有定义 kafka 的logger，那会直接输出到 ROOT中。

解决方法也很简单，在setting的logging配置中配置下 kafka logger

"loggers": {
    "kafka": {
        "handlers": ["console"],
        "propagate": False,
        "level": "WARNING",
    },
    ...
},

或者

1	logging.getLogger("kafka").setLevel(logging.WARNING)

日志level，看需求，一般是INFO，不像看到相关的kafka任何信息直接使用ERROR

nginx log tar

Posted on 2020-02-22 Edited on 2024-03-21

shell script

#!/bin/bash
logroot="/usr/servers/nginx/logs"
hisroot=$logroot/log-history
sudo mkdir -p $hisroot
day=$(date '+%Y%m%d')
aclogname="${day}-access.log"
erlogname="${day}-error.log"
cat $logroot/api-access.log > $hisroot/$aclogname
cat $logroot/api-error.log > $hisroot/$erlogname
sudo truncate -s 0 $logroot/api-access.log
sudo truncate -s 0 $logroot/api-error.log

nginx openresty

Posted on 2019-12-03 Edited on 2024-03-21

openresty install

https://blog.csdn.net/fyq201749/article/details/80981350

nginx web page 404

Posted on 2019-12-02 Edited on 2024-03-21

nginx web page 404

location / {
    root   /file_path;
    index  index.html index.htm;
    try_files $uri $uri/ @rewrites;
}
location @rewrites {rewrite ^(.+)$ /index/index.html last;}