-
Notifications
You must be signed in to change notification settings - Fork 815
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
Cant start Datadog #1653
Comments
Hello @peterheard01, sorry to hear that you had trouble with the agent. |
Hi, I followed the flare instructions and this happened... Petes-MBP:bin peteheard$ sudo ./agent flare #1653 |
Hey @peterheard01, we will soon release a package for the Datadog Agent on Mac. You can already try it by using: https://gist.github.com/degemer/5f89f9c98633cf1ff6d1 |
Closing this issue, we released a native package for MacOS that fixes this issue. |
Hi Guys,
I am having real problems starting the agent on my mac getting the following (including when I omit the Sudo bit)....
Petes-MBP:.datadog-agent peteheard$ sudo sh bin/agent
Starting supervisor
2015-06-01 15:59:37,326 CRIT Supervisor running as root (no user in config file)
2015-06-01 15:59:37,327 INFO Increased RLIMIT_NOFILE limit to 1024
2015-06-01 15:59:37,343 INFO RPC interface 'supervisor' initialized
2015-06-01 15:59:37,344 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2015-06-01 15:59:37,344 INFO supervisord started with pid 11728
2015-06-01 15:59:38,349 INFO spawned: 'dogstatsd' with pid 11731
2015-06-01 15:59:38,352 INFO spawned: 'forwarder' with pid 11732
2015-06-01 15:59:38,354 INFO spawned: 'collector' with pid 11733
2015-06-01 15:59:38,356 INFO spawned: 'jmxfetch' with pid 11734
2015-06-01 15:59:38,542 INFO success: jmxfetch entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2015-06-01 15:59:38,542 INFO exited: jmxfetch (exit status 0; expected)
2015-06-01 15:59:38,616 INFO exited: forwarder (exit status 1; not expected)
2015-06-01 15:59:38,712 INFO exited: dogstatsd (exit status 1; not expected)
2015-06-01 15:59:39,750 INFO spawned: 'dogstatsd' with pid 11745
2015-06-01 15:59:39,753 INFO spawned: 'forwarder' with pid 11746
2015-06-01 15:59:39,936 INFO exited: forwarder (exit status 1; not expected)
2015-06-01 15:59:40,043 INFO exited: dogstatsd (exit status 1; not expected)
2015-06-01 15:59:41,045 INFO success: collector entered RUNNING state, process has stayed up for > than 2 seconds (startsecs)
2015-06-01 15:59:42,050 INFO spawned: 'dogstatsd' with pid 11759
2015-06-01 15:59:42,053 INFO spawned: 'forwarder' with pid 11760
2015-06-01 15:59:42,231 INFO exited: forwarder (exit status 1; not expected)
2015-06-01 15:59:42,339 INFO exited: dogstatsd (exit status 1; not expected)
2015-06-01 15:59:45,257 INFO spawned: 'forwarder' with pid 11765
2015-06-01 15:59:45,416 INFO spawned: 'dogstatsd' with pid 11766
2015-06-01 15:59:45,433 INFO exited: forwarder (exit status 1; not expected)
2015-06-01 15:59:45,695 INFO gave up: forwarder entered FATAL state, too many start retries too quickly
2015-06-01 15:59:45,713 INFO exited: dogstatsd (exit status 1; not expected)
2015-06-01 15:59:46,714 INFO gave up: dogstatsd entered FATAL state, too many start retries too quickly
The text was updated successfully, but these errors were encountered: