(10-06-2020 05:11 PM)zhihao Wrote: [ -> ]yes, I add CTs to cod://cod/CodExt.py as follows:
Code:
"bibo": {"proto":"git",
"repository": "bibo",
"habitat": "bibo",
"username": "git",
"default_branch": "rc",
"loc": "codb4.d-thinker.org"},
"bibo_backend": {"proto":"git",
"repository": "bibo_backend",
"habitat": "bibo",
"username": "git",
"default_branch": "rc",
"loc": "codb4.d-thinker.org"},
I changed bibo_backend to biboback, changed bibo to reside on codb3, and I changed their habitats to be prada.
Pls contact the guardians of codb3, such as Zijian, to add the CT bibo.
I have added CT biboback to codb4.
driver: 微信群内记录表示案例检索有问题
Quote:检察院 呀!土豆:
@lingu 刚刚客户反应以前能检索到两个的案例现在有一个检索不出来了,大概是什么原因
lingu:
可能是有bug,但暂时没法下结论。先看看日志然后找合适的时间试试能否重现这个问题
建议将群内两个日志logs.zip和ynetlog.zip记录于GCP://org/troubleshoot/procuratorate/log/
RR lingu
20210531 检察院系统无法运行,收集日志存放于GCP://org/procuratorate/supreme/log/wp289b/
RR lingu
I copy them to limbo305-1:/home/supporters/bibo_log too
(02-25-2021 06:26 PM)zhihao Wrote: [ -> ]driver: 微信群内记录表示案例检索有问题
Quote:检察院 呀!土豆:
@lingu 刚刚客户反应以前能检索到两个的案例现在有一个检索不出来了,大概是什么原因
lingu:
可能是有bug,但暂时没法下结论。先看看日志然后找合适的时间试试能否重现这个问题
建议将群内两个日志logs.zip和ynetlog.zip记录于GCP://org/troubleshoot/procuratorate/log/
RR lingu
OK but is troubleshoot an org?
change the gcp to gcp://org/procuratorate/troubleshoot/log/xyz
xyz is a name indicating what this log is.
(06-02-2021 12:22 PM)zhihao Wrote: [ -> ]20210531 检察院系统无法运行,收集日志存放于GCP://org/procuratorate/supreme/log/wp289b/
RR lingu
OK but pls change to GCP://org/procuratorate/supreme/lwp289b/log
Quote:I copy them to limbo305-1:/home/supporters/bibo_log too
Why do you copy there? If you plan to copy to a local dir, you'd better not define the gcp.
It looks like sage crashes after the walker on wp289b-6 runs 624 tasks.
To test, I am running wake_sage in tmux t3s on gm292-3.
Code:
[sage@limbo305-3 log]$ ~/sage/bin/wake_sage
sage talks to Sage every minute.
You may read the depgrid info in the ATPD log.
...
20210630/Qi reports that startbibo could not start ncat. Zhihao helped them reinstall cod://bibo but it did not help. lingu went to the site and found wp286b-6 has a full root. After clearing bibo history log (about 20GB), we were able to start sage. There we some strange auntie tasks in sage, I ran sage_clear on wp289b-1 to clear old tasks. Then I killed some old processes using port 62818, and ran startbibo again. This time it works.