使用os.uptime()值,Pm2 3.5错误,我们无法从/ proc / uptime中找到正常运行时间

问题描述 投票:1回答:1

我们使用os.uptime()值,Pm2 3.5错误,从/ proc / uptime中找不到正常运行时间

2020-02-11T20:11:43: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2020-02-11T20:12:13: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2020-02-11T20:12:43: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2020-02-11T20:13:13: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2020-02-11T20:13:43: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2020-02-11T20:14:13: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2020-02-11T20:14:43: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2020-02-11T20:15:43: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
2020-02-11T20:16:13: PM2 warn: [pidusage] We couldn't find uptime from /proc/uptime, using os.uptime() value
node.js pm2
1个回答
0
投票

我没有防弹证据,但是当我们将PM2从4.2.3更新到4.4时,我们的项目中出现了相同的错误老实说,我们将模块安装在具有互联网的主机上,然后将其复制到生产环境中,虽然可以多次工作,但这仍然是一种不好的做法。因此,降级到4.2.3(通过Nexus正确安装)后,一切正常[]

© www.soinside.com 2019 - 2024. All rights reserved.