# Logstash re-open logfile with SIGHUP

**URL:** <https://discuss.elastic.co/t/logstash-re-open-logfile-with-sighup/56904>\
**Category:** Logstash\
**Created:** [August 1, 2016, 3:57pm UTC](https://discuss.elastic.co/t/logstash-re-open-logfile-with-sighup/56904 "2016-08-01T15:57:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbaranski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mbaranski/32/4302_2.png) [@mbaranski](https://discuss.elastic.co/u/mbaranski)\
**Post date:** [August 1, 2016, 3:57pm UTC](https://discuss.elastic.co/t/logstash-re-open-logfile-with-sighup/56904/1 "2016-08-01T15:57:24Z")

</div>

I'm running logstash via the apt installed package on Ubuntu.

I am sending a SIGHUP to the process and it's not re-opening its logfiles.

> dpkg -l | grep logstash  
> ii logstash 1:2.3.4-1 all An extensible logging pipeline

If I do

> ps -ef | grep logstash

I get

`logstash 11786 1 12 11:54 pts/6 00:00:16 /usr/bin/java -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -Djava.awt.headless=true -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/var/lib/logstash -Xmx1g -Xss2048k -Djffi.boot.library.path=/opt/logstash/vendor/jruby/lib/jni -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -Djava.awt.headless=true -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/var/lib/logstash -XX:HeapDumpPath=/opt/logstash/heapdump.hprof -Xbootclasspath/a:/opt/logstash/vendor/jruby/lib/jruby.jar -classpath : -Djruby.home=/opt/logstash/vendor/jruby -Djruby.lib=/opt/logstash/vendor/jruby/lib -Djruby.script=jruby -Djruby.shell=/bin/sh org.jruby.Main --1.9 /opt/logstash/lib/bootstrap/environment.rb logstash/runner.rb agent -f /etc/logstash/conf.d -l /var/log/logstash/logstash.log --quiet`

And if I do `kill -1 11786` nothing happens. Any ideas?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [August 1, 2016, 5:07pm UTC](https://discuss.elastic.co/t/logstash-re-open-logfile-with-sighup/56904/2 "2016-08-01T17:07:27Z")

</div>

I'm not sure SIGHUP is supposed to make it reopen its log files. The only documented behavior AFAIK is that the config files should be reloaded.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 4:45am UTC](https://discuss.elastic.co/t/logstash-re-open-logfile-with-sighup/56904/3 "2017-07-06T04:45:34Z")

</div>