docker with shiny server pro问题

时间:2015-09-19 13:05:11

标签: r docker centos supervisord shiny-server

我在centos创建了两个带有闪亮服务器的泊坞窗:

  • Docker与shiny server - 免费版here
  • Docker与shiny server pro(使用临时许可证)here

这些泊坞窗在centos上,因为它最终将作为Linux的受支持版本(可能是dockerised或native)在RHEL上运行。目前,它们为测试和开发提供了便利的方式。

它们主要用于开发:它们包括RRStudio ServerShiny Server:可能不是Docker纯粹主义者会做或推荐的(可能是生产版本将基于docker)组成)。

我遇到的问题是,虽然Docker shiny server - 免费版工作正常, Docker shiny server pro无法正常工作(也许是supervisord的问题?) 。

2015-09-19 12:40:10,379 CRIT Supervisor running as root (no user in config file)
2015-09-19 12:40:10,385 INFO supervisord started with pid 1
2015-09-19 12:40:10,387 INFO spawned: 'shinyserver' with pid 8
2015-09-19 12:40:10,388 INFO spawned: 'rserver' with pid 9
2015-09-19 12:40:10,404 INFO success: rserver entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2015-09-19 12:40:10,405 INFO exited: rserver (exit status 0; expected)
2015-09-19 12:40:10,405 INFO received SIGCLD indicating a child quit
2015-09-19 12:40:10,955 INFO exited: shinyserver (exit status 8; not expected)
2015-09-19 12:40:10,955 INFO received SIGCLD indicating a child quit
2015-09-19 12:40:11,959 INFO spawned: 'shinyserver' with pid 31
2015-09-19 12:40:12,236 INFO exited: shinyserver (exit status 8; not expected)
2015-09-19 12:40:12,236 INFO received SIGCLD indicating a child quit
2015-09-19 12:40:14,243 INFO spawned: 'shinyserver' with pid 37
2015-09-19 12:40:14,520 INFO exited: shinyserver (exit status 8; not expected)
2015-09-19 12:40:14,521 INFO received SIGCLD indicating a child quit
2015-09-19 12:40:17,533 INFO spawned: 'shinyserver' with pid 43
2015-09-19 12:40:17,807 INFO exited: shinyserver (exit status 8; not expected)
2015-09-19 12:40:17,808 INFO received SIGCLD indicating a child quit
2015-09-19 12:40:18,811 INFO gave up: shinyserver entered FATAL state, too many start retries too quickly
2015-09-19 12:40:43,272 CRIT received SIGTERM indicating exit request

这是非常令人惊讶的,因为代码库是常见的(当然)。可能是关于如何产生过程的问题?

如果有人帮我在shiny server pro配置中找到错误,那就太棒了。

1 个答案:

答案 0 :(得分:2)

我设法解决了这个问题。正如所料,这是Group 0: "(^\s+)" Captures whitespace Group 1: "(\*{3})" captures '***' Group 2:"([a-zA-Z\s]+)" captures alpha characters and spaces Group 3: "(\*{3})*" captures 0 or or more occurrences of "***" 的错误配置。

闪亮的服务器需要以root身份启动,而我错误地使用了supervisord.conf而不是user=shiny。我很惊讶这并没有在免费版中产生错误。

这是后人的主管配置,使其成功:

user=root

dockerfile等可用on my github page smartinsightsfromdata