Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

239 INFO exited: setup (exit status 0; expected) #16

Closed
lx277856602 opened this issue May 22, 2018 · 1 comment
Closed

239 INFO exited: setup (exit status 0; expected) #16

lx277856602 opened this issue May 22, 2018 · 1 comment

Comments

@lx277856602
Copy link

hello,

I run it within docker,logontracer start failed,returned errors as follows:

[rancher@rancher ~]$ docker logs -f logontracer
/usr/lib/python2.7/site-packages/supervisor/options.py:461: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  'Supervisord is running as root and it is searching '
2018-05-22 16:41:45,714 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2018-05-22 16:41:45,716 INFO supervisord started with pid 1
2018-05-22 16:41:46,719 INFO spawned: 'logontracer' with pid 9
2018-05-22 16:41:46,720 INFO spawned: 'setup' with pid 10
2018-05-22 16:41:46,721 INFO spawned: 'neo4j' with pid 11
2018-05-22 16:41:48,502 INFO success: logontracer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-05-22 16:41:48,502 INFO success: setup entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-05-22 16:41:48,502 INFO success: neo4j entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-05-22 16:42:26,826 INFO exited: setup (exit status 0; expected)

how to solve above problem? Thanks!

@shu-tom
Copy link
Member

shu-tom commented May 23, 2018

This is a known warning message. The Docker image appears to working properly.
Did you input the correct IP address with option "-e LTHOSTNAME"?

@shu-tom shu-tom closed this as completed Jun 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants