Failed to start td-agent
5,143 views
Skip to first unread message
Jac Geo
Feb 9, 2019, 12:03:01 AM2/9/19
to Fluentd Google Group
Can't start td-agent in linux 16.04
Job for td-agent.service failed because the control process exited with error code. See "systemctl status td-agent.service" and "journalctl -xe" for details.
systemctl status td-agent.service
Job for td-agent.service failed because the control process exited with error code. See "systemctl status td-agent.service" and "journalctl -xe" for details.
systemctl status td-agent.service
● td-agent.service - td-agent: Fluentd based data collector for Treasure Data
Loaded: loaded (/lib/systemd/system/td-agent.service; disabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Sat 2019-02-09 10:27:50 IST; 21s ago
Process: 10006 ExecStart=/opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-agent.pid $TD_
Feb 09 10:27:50 QB-TP3-1462 systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
Feb 09 10:27:50 QB-TP3-1462 systemd[1]: td-agent.service: Unit entered failed state.
Feb 09 10:27:50 QB-TP3-1462 systemd[1]: td-agent.service: Failed with result 'exit-code'.
Feb 09 10:27:50 QB-TP3-1462 systemd[1]: td-agent.service: Service hold-off time over, scheduling restart.
Feb 09 10:27:50 QB-TP3-1462 systemd[1]: Stopped td-agent: Fluentd based data collector for Treasure Data.
Feb 09 10:27:50 QB-TP3-1462 systemd[1]: td-agent.service: Start request repeated too quickly.
Feb 09 10:27:50 QB-TP3-1462 systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
Feb 09 10:27:50 QB-TP3-1462 systemd[1]: td-agent.service: Unit entered failed state.
Feb 09 10:27:50 QB-TP3-1462 systemd[1]: td-agent.service: Failed with result 'start-limit-hit'.
Mr. Fiber
Feb 10, 2019, 11:29:05 AM2/10/19
to Fluentd Google Group
Could you show journal log and td-agent log?
Masahiro
--
You received this message because you are subscribed to the Google Groups "Fluentd Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fluentd+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jac Geo
Feb 10, 2019, 11:35:05 PM2/10/19
to flu...@googlegroups.com, repea...@gmail.com
$ systemctl status td-agent.service
● td-agent.service - td-agent: Fluentd based data collector for Treasure Data
Loaded: loaded (/lib/systemd/system/td-agent.service; disabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Mon 2019-02-11 09:56:15 IST; 4s ago
Docs: https://docs.treasuredata.com/articles/td-agent
Process: 24632 ExecStart=/opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-agent.pid $TD_
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Unit entered failed state.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Failed with result 'exit-code'.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Service hold-off time over, scheduling restart.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: Stopped td-agent: Fluentd based data collector for Treasure Data.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Start request repeated too quickly.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Unit entered failed state.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Failed with result 'start-limit-hit'.
Docs: https://docs.treasuredata.com/articles/td-agent
Process: 24632 ExecStart=/opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-agent.pid $TD_
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Unit entered failed state.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Failed with result 'exit-code'.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Service hold-off time over, scheduling restart.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: Stopped td-agent: Fluentd based data collector for Treasure Data.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Start request repeated too quickly.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Unit entered failed state.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Failed with result 'start-limit-hit'.
$ journalctl -xe
--
-- Unit td-agent.service has begun starting up.
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/supervisor.rb:364:in `init
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/supervisor.rb
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/supervisor.rb
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/supervisor.rb
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/command/fluen
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/bin/fluentd:8:in `<top (
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/bin/fluentd:23:in `load'
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/bin/fluentd:23:in `<main>'
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Control process exited, code=exited status=1
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
-- Subject: Unit td-agent.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit td-agent.service has failed.
--
-- The result is failed.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Unit entered failed state.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Failed with result 'exit-code'.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Service hold-off time over, scheduling restart.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: Stopped td-agent: Fluentd based data collector for Treasure Data.
-- Subject: Unit td-agent.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit td-agent.service has finished shutting down.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Start request repeated too quickly.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
-- Subject: Unit td-agent.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit td-agent.service has failed.
--
-- The result is failed.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Unit entered failed state.
Feb 11 09:56:15 QB-TP3-1462 systemd[1]: td-agent.service: Failed with result 'start-limit-hit'.
Jean-Charles delon
Feb 11, 2019, 3:18:52 AM2/11/19
to Fluentd Google Group
Hi,
The failed start
Same issue here, with a RHEL 7.4 and td-agent-3.3.0-1.el7.x86_64
The issue seems to be related to systemctl, because "fluend" start normally with the full command line below ( if /var/run/td-agent/ exist)
/opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-agent.pid -c /etc/td-agent/td-agent.conf
/opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-agent.pid -c /etc/td-agent/td-agent.conf
The failed start
# systemctl start td-agent
Job for td-agent.service failed because start of the service was attempted too often. See "systemctl status td-agent.service" and "journalctl -xe" for details.
To force a start use "systemctl reset-failed td-agent.service" followed by "systemctl start td-agent.service" again.
# journalctl -xe
Feb 11 09:05:28 siy05x03 systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
-- Subject: Unit td-agent.service has failed
-- Defined-By: systemd
--
-- Unit td-agent.service has failed.
--
-- The result is failed.
Feb 11 09:05:28 siy05x03 systemd[1]: Unit td-agent.service entered failed state.
Feb 11 09:05:28 siy05x03 systemd[1]: td-agent.service failed.
Feb 11 09:05:28 siy05x03 systemd[1]: td-agent.service holdoff time over, scheduling restart.
Feb 11 09:05:28 siy05x03 systemd[1]: Starting td-agent: Fluentd based data collector for Treasure Data...
-- Subject: Unit td-agent.service has begun start-up
-- Unit td-agent.service has begun starting up.
Feb 11 09:05:28 siy05x03 systemd[1]: PID 383368 read from file /var/run/td-agent/td-agent.pid does not exist or is a zombie.
Feb 11 09:05:28 siy05x03 systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
-- Subject: Unit td-agent.service has failed
-- Defined-By: systemd
--
-- Unit td-agent.service has failed.
--
-- The result is failed.
Feb 11 09:05:28 siy05x03 systemd[1]: Unit td-agent.service entered failed state.
Feb 11 09:05:28 siy05x03 systemd[1]: td-agent.service failed.
Feb 11 09:05:28 siy05x03 systemd[1]: td-agent.service holdoff time over, scheduling restart.
Feb 11 09:05:28 siy05x03 systemd[1]: start request repeated too quickly for td-agent.service
Feb 11 09:05:28 siy05x03 systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
-- Subject: Unit td-agent.service has failed
-- Defined-By: systemd
--
-- Unit td-agent.service has failed.
--
-- The result is failed.
Feb 11 09:05:28 siy05x03 systemd[1]: Unit td-agent.service entered failed state.
Feb 11 09:05:28 siy05x03 systemd[1]: td-agent.service failed.
Feb 11 09:05:31 siy05x03 polkitd[1998]: Registered Authentication Agent for unix-process:383374:2564015578 (system bus name :1.109269 [<unknown>], object path /org/freedesktop/PolicyKit
Feb 11 09:05:31 siy05x03 systemd[1]: start request repeated too quickly for td-agent.service
Feb 11 09:05:31 siy05x03 systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
-- Subject: Unit td-agent.service has failed
-- Defined-By: systemd
--
-- Unit td-agent.service has failed.
--
-- The result is failed.
# vi /var/log/td-agent/td-agent.log
2019-02-11 09:05:26 +0100 [info]: parsing config file is succeeded path="/etc/td-agent/td-agent.conf"
2019-02-11 09:05:27 +0100 [info]: brokers has been set directly: ["XXXXXX:6668"]
2019-02-11 09:05:27 +0100 [info]: using configuration file: <ROOT>
...
...
</ROOT>
2019-02-11 09:05:27 +0100 [info]: starting fluentd-1.3.3 pid=383254 ruby="2.4.5"
2019-02-11 09:05:27 +0100 [info]: spawn command to main: cmdline=["/opt/td-agent/embedded/bin/ruby", "-Eascii-8bit:ascii-8bit", "/opt/td-agent/embedded/bin/fluentd", "--log", "/var/log/td-agent/td-agent.log", "--daemon", "/var/run/td-agent/td-agent.pid", "--under-supervisor"]
2019-02-11 09:05:27 +0100 [info]: parsing config file is succeeded path="/etc/td-agent/td-agent.conf"
2019-02-11 09:05:27 +0100 [info]: brokers has been set directly: ["siy05x03.hpmetier.sf.intra.laposte.fr:6668"]
2019-02-11 09:05:27 +0100 [info]: using configuration file: <ROOT>
...
...
</ROOT>
2019-02-11 09:05:27 +0100 [info]: starting fluentd-1.3.3 pid=383264 ruby="2.4.5"
2019-02-11 09:05:27 +0100 [info]: spawn command to main: cmdline=["/opt/td-agent/embedded/bin/ruby", "-Eascii-8bit:ascii-8bit", "/opt/td-agent/embedded/bin/fluentd", "--log", "/var/log/td-agent/td-agent.log", "--daemon", "/var/run/td-agent/td-agent.pid", "--under-supervisor"]
2019-02-11 09:05:28 +0100 [info]: parsing config file is succeeded path="/etc/td-agent/td-agent.conf"
2019-02-11 09:05:28 +0100 [info]: brokers has been set directly: ["XXXXXX:6668"]
2019-02-11 09:05:28 +0100 [info]: using configuration file: <ROOT>
...
...
</ROOT>
2019-02-11 09:05:28 +0100 [info]: starting fluentd-1.3.3 pid=383330 ruby="2.4.5"
2019-02-11 09:05:28 +0100 [info]: spawn command to main: cmdline=["/opt/td-agent/embedded/bin/ruby", "-Eascii-8bit:ascii-8bit", "/opt/td-agent/embedded/bin/fluentd", "--log", "/var/log/td-agent/td-agent.log", "--daemon", "/var/run/td-agent/td-agent.pid", "--under-supervisor"]
2019-02-11 09:05:28 +0100 [info]: parsing config file is succeeded path="/etc/td-agent/td-agent.conf"
2019-02-11 09:05:28 +0100 [info]: brokers has been set directly: ["XXXXXX:6668"]
2019-02-11 09:05:28 +0100 [info]: using configuration file: <ROOT>
...
...
</ROOT>
2019-02-11 09:05:28 +0100 [info]: starting fluentd-1.3.3 pid=383363 ruby="2.4.5"
2019-02-11 09:05:28 +0100 [info]: spawn command to main: cmdline=["/opt/td-agent/embedded/bin/ruby", "-Eascii-8bit:ascii-8bit", "/opt/td-agent/embedded/bin/fluentd", "--log", "/var/log/td-agent/td-agent.log", "--daemon", "/var/run/td-agent/td-agent.pid", "--under-supervisor"]
I've also check all the limits oft the host regarding this error
# systemctl start td-agent
Job for td-agent.service failed because a configured resource limit was exceeded. See "systemctl status td-agent.service" and "journalctl -xe" for details.
Regards
Mr. Fiber
Feb 11, 2019, 11:05:59 AM2/11/19
to Fluentd Google Group
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/supervisor.rb:364:in `init
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/supervisor.rb
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/supervisor.rb
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/supervisor.rb
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/command/fluen
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/bin/fluentd:8:in `<top (
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/bin/fluentd:23:in `load'
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/bin/fluentd:23:in `<main>'
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/supervisor.rb
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/supervisor.rb
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/supervisor.rb
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/lib/fluent/command/fluen
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/lib/ruby/gems/2.4.0/gems/fluentd-1.3.3/bin/fluentd:8:in `<top (
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/bin/fluentd:23:in `load'
Feb 11 09:56:15 QB-TP3-1462 fluentd[24632]: from /opt/td-agent/embedded/bin/fluentd:23:in `<main>'
This stacktrace shows the cause. Do you get full log of this?
This truncates log lines.
> The issue seems to be related to systemctl, because "fluend" start normally with the full command line below ( if /var/run/td-agent/ exist)
Does this mean no error happen with very simple conf like below, right?
<match test>
@type stdout
</match>
Jean-Charles delon
Feb 12, 2019, 3:40:56 AM2/12/19
to Fluentd Google Group
Hi,
Same behaviour for me with the simplest config.
# systemctl start td-agent
Job for td-agent.service failed because the control process exited with error code. See "systemctl status td-agent.service" and "journalctl -xe" for details.
# journalctl -xe
Feb 12 09:25:59 siy05x03 systemd[1]: td-agent.service: main process exited, code=exited, status=1/FAILURE
Feb 12 09:25:59 siy05x03 kill[127121]: kill: cannot find process ""
Feb 12 09:25:59 siy05x03 systemd[1]: td-agent.service: control process exited, code=exited status=1
Feb 12 09:25:59 siy05x03 systemd[1]: Unit td-agent.service entered failed state.
Feb 12 09:25:59 siy05x03 systemd[1]: td-agent.service failed.
Feb 12 09:25:59 siy05x03 systemd[1]: td-agent.service holdoff time over, scheduling restart.
Feb 12 09:25:59 siy05x03 systemd[1]: Starting td-agent: Fluentd based data collector for Treasure Data...
-- Subject: Unit td-agent.service has begun start-up
-- Defined-By: systemd
--
-- Unit td-agent.service has begun starting up.
Feb 12 09:25:59 siy05x03 systemd[1]: Started td-agent: Fluentd based data collector for Treasure Data.
-- Subject: Unit td-agent.service has finished start-up
-- Unit td-agent.service has finished starting up.
--
-- The start-up result is done.
Feb 12 09:25:59 siy05x03 systemd[1]: td-agent.service: main process exited, code=exited, status=1/FAILURE
Feb 12 09:25:59 siy05x03 kill[127135]: kill: cannot find process ""
Feb 12 09:25:59 siy05x03 systemd[1]: td-agent.service: control process exited, code=exited status=1
Feb 12 09:25:59 siy05x03 systemd[1]: Unit td-agent.service entered failed state.
Feb 12 09:25:59 siy05x03 systemd[1]: td-agent.service failed.
Feb 12 09:26:00 siy05x03 systemd[1]: td-agent.service holdoff time over, scheduling restart.
Feb 12 09:26:00 siy05x03 systemd[1]: start request repeated too quickly for td-agent.service
Feb 12 09:26:00 siy05x03 systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
-- Subject: Unit td-agent.service has failed
-- Defined-By: systemd
--
-- Unit td-agent.service has failed.
--
-- The result is failed.
Feb 12 09:26:00 siy05x03 systemd[1]: Unit td-agent.service entered failed state.
Feb 12 09:26:00 siy05x03 systemd[1]: td-agent.service failed.
->td-agent.log
2019-02-12 09:25:57 +0100 [info]: parsing config file is succeeded path="/etc/td-agent/td-agent.conf"
2019-02-12 09:25:57 +0100 [info]: using configuration file: <ROOT>
<match test>
@type stdout
</match>
</ROOT>
2019-02-12 09:25:57 +0100 [info]: starting fluentd-1.3.3 pid=127077 ruby="2.4.5"
2019-02-12 09:25:57 +0100 [info]: spawn command to main: cmdline=["/opt/td-agent/embedded/bin/ruby", "-Eascii-8bit:ascii-8bit", "/opt/td-agent/embedded/bin/fluentd", "--log", "/var/log/td-agent/td-agent.log", "--daemon", "/var/run/td-agent/td-agent.pid", "--under-supervisor"]
2019-02-12 09:25:58 +0100 [info]: parsing config file is succeeded path="/etc/td-agent/td-agent.conf"
2019-02-12 09:25:58 +0100 [info]: using configuration file: <ROOT>
<match test>
@type stdout
</match>
</ROOT>
2019-02-12 09:25:58 +0100 [info]: starting fluentd-1.3.3 pid=127088 ruby="2.4.5"
2019-02-12 09:25:58 +0100 [info]: spawn command to main: cmdline=["/opt/td-agent/embedded/bin/ruby", "-Eascii-8bit:ascii-8bit", "/opt/td-agent/embedded/bin/fluentd", "--log", "/var/log/td-agent/td-agent.log", "--daemon", "/var/run/td-agent/td-agent.pid", "--under-supervisor"]
2019-02-12 09:25:58 +0100 [info]: parsing config file is succeeded path="/etc/td-agent/td-agent.conf"
2019-02-12 09:25:58 +0100 [info]: using configuration file: <ROOT>
<match test>
@type stdout
</match>
</ROOT>
2019-02-12 09:25:58 +0100 [info]: starting fluentd-1.3.3 pid=127101 ruby="2.4.5"
2019-02-12 09:25:58 +0100 [info]: spawn command to main: cmdline=["/opt/td-agent/embedded/bin/ruby", "-Eascii-8bit:ascii-8bit", "/opt/td-agent/embedded/bin/fluentd", "--log", "/var/log/td-agent/td-agent.log", "--daemon", "/var/run/td-agent/td-agent.pid", "--under-supervisor"]
2019-02-12 09:25:59 +0100 [info]: parsing config file is succeeded path="/etc/td-agent/td-agent.conf"
2019-02-12 09:25:59 +0100 [info]: using configuration file: <ROOT>
<match test>
@type stdout
</match>
</ROOT>
2019-02-12 09:25:59 +0100 [info]: starting fluentd-1.3.3 pid=127111 ruby="2.4.5"
2019-02-12 09:25:59 +0100 [info]: spawn command to main: cmdline=["/opt/td-agent/embedded/bin/ruby", "-Eascii-8bit:ascii-8bit", "/opt/td-agent/embedded/bin/fluentd", "--log", "/var/log/td-agent/td-agent.log", "--daemon", "/var/run/td-agent/td-agent.pid", "--under-supervisor"]
2019-02-12 09:25:59 +0100 [info]: parsing config file is succeeded path="/etc/td-agent/td-agent.conf"
2019-02-12 09:25:59 +0100 [info]: using configuration file: <ROOT>
<match test>
@type stdout
</match>
</ROOT>
2019-02-12 09:25:59 +0100 [info]: starting fluentd-1.3.3 pid=127125 ruby="2.4.5"
2019-02-12 09:25:59 +0100 [info]: spawn command to main: cmdline=["/opt/td-agent/embedded/bin/ruby", "-Eascii-8bit:ascii-8bit", "/opt/td-agent/embedded/bin/fluentd", "--log", "/var/log/td-agent/td-agent.log", "--daemon", "/var/run/td-agent/td-agent.pid", "--under-supervisor"]
Mr. Fiber
Feb 12, 2019, 4:23:54 AM2/12/19
to Fluentd Google Group
Hmm... I re-checked latest 3.3.0-1 package on my fresh CentOS 7 environment and it worked.
Loaded: loaded (/usr/lib/systemd/system/td-agent.service; disabled; vendor preset: disabled)
Active: active (running) since Tue 2019-02-12 18:18:49 JST; 14s ago
Docs: https://docs.treasuredata.com/articles/td-agent
Process: 59471 ExecStart=/opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-agent.pid $TD_AGENT_OPTIONS (code=exited, status=0/SUCCESS)
Main PID: 59477 (fluentd)
CGroup: /system.slice/td-agent.service
|-59477 /opt/td-agent/embedded/bin/ruby /opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-ag...
`-59482 /opt/td-agent/embedded/bin/ruby -Eascii-8bit:ascii-8bit /opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon...
Feb 12 18:18:49 localhost.localdomain systemd[1]: Starting td-agent: Fluentd based data collector for Treasure Data...
Feb 12 18:18:49 localhost.localdomain systemd[1]: Started td-agent: Fluentd based data collector for Treasure Data.
LOCALHOST /home/repeatedly% curl -L https://toolbelt.treasuredata.com/sh/install-redhat-td-agent3.sh | sh
LOCALHOST /home/repeatedly% sudo systemctl start td-agent.service
LOCALHOST /home/repeatedly% sudo systemctl status td-agent.service
Loaded: loaded (/usr/lib/systemd/system/td-agent.service; disabled; vendor preset: disabled)
Active: active (running) since Tue 2019-02-12 18:18:49 JST; 14s ago
Docs: https://docs.treasuredata.com/articles/td-agent
Process: 59471 ExecStart=/opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-agent.pid $TD_AGENT_OPTIONS (code=exited, status=0/SUCCESS)
Main PID: 59477 (fluentd)
CGroup: /system.slice/td-agent.service
|-59477 /opt/td-agent/embedded/bin/ruby /opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-ag...
`-59482 /opt/td-agent/embedded/bin/ruby -Eascii-8bit:ascii-8bit /opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon...
Feb 12 18:18:49 localhost.localdomain systemd[1]: Starting td-agent: Fluentd based data collector for Treasure Data...
Feb 12 18:18:49 localhost.localdomain systemd[1]: Started td-agent: Fluentd based data collector for Treasure Data.
Did you execute any step before td-agent installation?
Jean-Charles delon
Feb 12, 2019, 5:04:03 AM2/12/19
to Fluentd Google Group
Yes, I follow the https://docs.fluentd.org/v0.12/articles/before-install and set the system parameters:
- Increase Max # of File Descriptors
- Optimize Network Kernel Parameters
(set via an ansible playbook, but I've done this several times on others hosts with no issue). This is a physical host with a pretty big hardware config, this is the only difference
Next try, uninstall, re-install the package.
Regards
Jean-Charles delon
Feb 19, 2019, 5:02:09 AM2/19/19
to Fluentd Google Group
I've found the problem.
Permissions on /tmp are too restrictive so "SERVERENGINE_SOCKETMANAGER_" socket file can't be created.
So I've set permissions corrects permissions on /tmp.
Best Regards
Reply all
Reply to author
Forward
0 new messages