raise RuntimeError('cannot schedule new futures after shutdown') RuntimeError: cannot schedule new futures after shutdown Error submitting job "Sync.transfer_mon_files (trigger: interval[0:01:00], next run at: 2023-12-17 22:57:55 CST)" to executor "default" Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/apscheduler/schedulers/base.py", line 978, in _process_jobs executor.submit_job(job, run_times) File "/usr/lib/python3.10/site-packages/apscheduler/executors/base.py", line 71, in submit_job self._do_submit_job(job, run_times) File "/usr/lib/python3.10/site-packages/apscheduler/executors/pool.py", line 28, in _do_submit_job f = self._pool.submit(run_job, job, job._jobstore_alias, run_times, self._logger.name) File "/usr/lib/python3.10/concurrent/futures/thread.py", line 167, in submit raise RuntimeError('cannot schedule new futures after shutdown') RuntimeError: cannot schedule new futures after shutdown
nastool吧 关注：352贴子：320
- 8回复贴，共1页
作者给出的处理方法：
1. 启动inotify报错/无法自动目录同步
问题描述 无法启动，日志报inotify instance limit reached、inotify watch limit reached等与inotify相关错误 目录同步无法自动同步或只有部份目录正常，但在服务中手动启动可以正常同步
解决办法：
宿主机上（不是docker容器里），执行以下命令（每行一个）：
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf
echo fs.inotify.max_user_instances=524288 | sudo tee -a /etc/sysctl.conf
sudo sysctl -p
1. 启动inotify报错/无法自动目录同步
问题描述 无法启动，日志报inotify instance limit reached、inotify watch limit reached等与inotify相关错误 目录同步无法自动同步或只有部份目录正常，但在服务中手动启动可以正常同步
解决办法：
宿主机上（不是docker容器里），执行以下命令（每行一个）：
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf
echo fs.inotify.max_user_instances=524288 | sudo tee -a /etc/sysctl.conf
sudo sysctl -p
扫二维码下载贴吧客户端
下载贴吧APP
看高清直播、视频！
看高清直播、视频！
贴吧热议榜
- 1TES是否能拿下CFO1772520
- 2郑钦文不敌斯瓦泰克无缘四强1293748
- 3普京表示俄罗斯同意停火30天1072008
- 4男子造谣明星澳门输10亿被拘948564
- 5电影靠延期刷票房？吧友甩数据936494
- 6哪吒2烂番茄震撼开局910325
- 7日本游客在长城光屁股被遣返774000
- 8土木传说之神秘红色螺丝688735
- 9崩铁3.1强度榜单合理性如何568788
- 10张继科事件还没有定论吗415695
