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

InfluxDB and restarting Journald results in sigpipe #9210

Closed
msteggink opened this issue Dec 8, 2017 · 2 comments
Closed

InfluxDB and restarting Journald results in sigpipe #9210

msteggink opened this issue Dec 8, 2017 · 2 comments

Comments

@msteggink
Copy link

Bug report

System info: InfluxDB version influxdb-1.4.1-1.x86_64
systemd-219-30.el7_3.8.x86_64
Red Hat Enterprise Linux Server release 7.3 (Maipo)

Steps to reproduce:

  1. Verify influxdb is running (systemctl status influxdb)
  2. Restart Journald (systemctl restart systemd-journald)
  3. This may take a few minutes, but InfluxDB is then killed ( systemctl status influxdb)

Expected behavior: Keep on running

Actual behavior:

systemctl status influxdb
● influxdb.service - InfluxDB is an open-source, distributed, time series database
   Loaded: loaded (/usr/lib/systemd/system/influxdb.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Fri 2017-12-08 09:41:45 CET; 3min 13s ago
     Docs: https://docs.influxdata.com/influxdb/
  Process: 4516 ExecStart=/usr/bin/influxd -config /etc/influxdb/influxdb.conf $INFLUXD_OPTS (code=killed,
 Main PID: 4516 (code=killed, signal=PIPE)

Quick fix is to change the restart from on-failure to always.

Restart=always

Additional info: [Include gist of relevant config, logs, etc.]

Seems to be related to #7040

@dgnorton dgnorton added the 1.x label Jan 7, 2019
@stale
Copy link

stale bot commented Jul 24, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 24, 2019
@stale
Copy link

stale bot commented Jul 31, 2019

This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions.

@stale stale bot closed this as completed Jul 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants