Extra copy of telegraf daemon

Bug #1614909 reported by Stuart Bishop
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Telegraf Charm
Invalid
High
Diko Parvanov

Bug Description

There seem to be two telegraf daemons running after deployment. I think one gets started when the package is installed and is never shut down.

Revision history for this message
Tejeev Patel (tejeevpatel) wrote :

We've seen two possible occurrences of this same issue.

Both alerted due to zombie processes via Nagios/Pager Duty but on investigation it looks like both times, we found two telegraf processes running. Both processes had zombie children in today's event.

The first time was on 2016-10-12 where we also saw that it had just upgraded (according to apt logs), but this time there was no associated upgrade.

We worked around it by kill -15 'ing the parent processes and starting one back up.

Tom Haddon (mthaddon)
Changed in telegraf-charm:
status: New → Confirmed
importance: Undecided → Medium
importance: Medium → High
Revision history for this message
Diko Parvanov (dparv) wrote :

Tried to reproduce on juju 2.7.1 with telegraf revision 30 on bionic of the charm and there is no duplicate daemon. (installed telegraf version is 1.12.6+git-b1a0a69~201911221541~ubuntu18.04.1).

Changed in telegraf-charm:
status: Confirmed → Invalid
assignee: nobody → Diko Parvanov (dparv)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.