AWS healthd 守护进程警告 - nginx 日志文件不存在

Laj*_*pat 9 nginx amazon-elastic-beanstalk

我已经使用 elasticbeanstalk 和 nginx 部署了一个 nodejs 应用程序。

当我检查日志目录 /var/log/nginx/

  1. healthd 文件夹存在并且
  2. nginx 正在创建 /var/log/nginx/healthd/application.log.2019-10-04-13

但是在 /var/log/healthd 文件夹中有一个 daemon.log 文件,我每 5 秒就会在其中收到以下错误。

    # Logfile created on 2019-10-04 13:46:46 +0000 by logger.rb/47272
A, [2019-10-04T13:46:46.849261 #8094]   ANY -- : healthd daemon 1.0.3 initialized
W, [2019-10-04T13:46:47.011762 #8094]  WARN -- : log file "/var/log/nginx/healthd/application.log.2019-10-04-13" does not exist
W, [2019-10-04T13:46:52.012037 #8094]  WARN -- : log file "/var/log/nginx/healthd/application.log.2019-10-04-13" does not exist
W, [2019-10-04T13:46:57.012270 #8094]  WARN -- : log file "/var/log/nginx/healthd/application.log.2019-10-04-13" does not exist
W, [2019-10-04T13:47:02.012593 #8094]  WARN -- : log file "/var/log/nginx/healthd/application.log.2019-10-04-13" does not exist
W, [2019-10-04T13:47:07.012811 #8094]  WARN -- : log file "/var/log/nginx/healthd/application.log.2019-10-04-13" does not exist
W, [2019-10-04T13:47:12.013037 #8094]  WARN -- : log file "/var/log/nginx/healthd/application.log.2019-10-04-13" does not exist
W, [2019-10-04T13:47:17.013245 #8094]  WARN -- : log file "/var/log/nginx/healthd/application.log.2019-10-04-13" does not exist
W, [2019-10-04T13:47:22.013467 #8094]  WARN -- : log file "/var/log/nginx/healthd/application.log.2019-10-04-13" does not exist
W, [2019-10-04T13:47:27.013679 #8094]  WARN -- : log file "/var/log/nginx/healthd/application.log.2019-10-04-13" does not exist
W, [2019-10-04T13:47:32.013903 #8094]  WARN -- : log file "/var/log/nginx/healthd/application.log.2019-10-04-13" does not exist
Run Code Online (Sandbox Code Playgroud)

那么如何让守护进程读取 nginx healthd 日志文件呢?

Ray*_*Ray 2

我也遇到了这个神秘的错误。尤其神秘的是,如果你检查一下,你会发现 /var/log/nginx/healthd/application.log.XXX 确实存在!

我发现在某些情况下,healthd 需要额外的配置来解决此错误。

看看这个: https: //docs.aws.amazon.com/elasticbeanstalk/latest/dg/health-enhanced-serverlogs.html

一旦我为 healthd 提供了正确的日志形成配置,这个错误就消失了。