node_exporter agent failed to start

2,544 views
Skip to first unread message

prakas...@gmail.com

unread,
Nov 12, 2018, 5:08:04 AM11/12/18
to Prometheus Users
I have configured node_exporter but it is failed to start. 

Below is the status: 
● node_exporter.service - Node Exporter
   Loaded: loaded (/etc/systemd/system/node_exporter.service; disabled; vendor p
   Active: failed (Result: exit-code) since Mon 2018-11-12 05:03:50 EST; 3s ago
  Process: 3244 ExecStart=/usr/local/bin/node_exporter (code=exited, status=1/FA
 Main PID: 3244 (code=exited, status=1/FAILURE)

I tried to kill the process and restart again. But when I execute kill command, it says no process found there. 

Please help me. 



Christian Hoffmann

unread,
Nov 12, 2018, 3:19:49 PM11/12/18
to prakas...@gmail.com, Prometheus Users
Hi,

On 11/12/18 11:08 AM, prakas...@gmail.com wrote:
> Below is the status: 
> ● node_exporter.service - Node Exporter
>    Loaded: loaded (/etc/systemd/system/node_exporter.service; disabled;
> vendor p
>    Active: failed (Result: exit-code) since Mon 2018-11-12 05:03:50 EST;
> 3s ago
>   Process: 3244 ExecStart=/usr/local/bin/node_exporter (code=exited,
> status=1/FA
>  Main PID: 3244 (code=exited, status=1/FAILURE)
>
> I tried to kill the process and restart again. But when I execute kill
> command, it says no process found there. 

From the provided systemd output, it seems like the process exits on its
own. That's probably why you are not able to kill it (it's already dead).

journalctl -u node_exporter -f should provide relevant logs from the
node_exporter binary.

The most common cause for startup problems are probably invalid command
line arguments, so I would suggest checking those.

You can also try to narrow the issue down by starting node_exporter
manually (i.e. without systemd) and move your working setup to the
systemd unit once you are done.

Kind regards,
Christian
Reply all
Reply to author
Forward
0 new messages