# Filebeat system and iptables module timezone offset issue

**URL:** https://discuss.elastic.co/t/filebeat-system-and-iptables-module-timezone-offset-issue/176732
**Category:** Beats
**Tags:** filebeat
**Created:** [April 13, 2019, 11:12am UTC](https://discuss.elastic.co/t/filebeat-system-and-iptables-module-timezone-offset-issue/176732 "2019-04-13T11:12:13Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)
#### Post date: [April 16, 2019, 11:13am UTC](https://discuss.elastic.co/t/filebeat-system-and-iptables-module-timezone-offset-issue/176732/2 "2019-04-16T11:13:12Z")

</div>

Hi @mback2k,

After changing the value of `var.convert_timezone` you need to setup the pipelines again. You can do it by restarting filebeat with `filebeat.overwrite_pipelines: true` in the configuration. Take into account that this option can override other pipelines that you have manually setup. You may want to remove this option once the pipelines are setup as you expect.

You can check if the pipelines are being correctly configured by executing `GET _ingest/pipeline/filebeat-6.7.1-system-*` and checking that the date processors include the timezone option, like in:

```auto
        "date" : {
          "field" : "system.syslog.timestamp",
          "target_field" : "@timestamp",
          "formats" : [
            "MMM d HH:mm:ss",
            "MMM dd HH:mm:ss"
          ],
          "timezone" : "{{ beat.timezone }}",
          "ignore_failure" : true
        }

```

Regards,  
Jaime.

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-system-and-iptables-module-timezone-offset-issue/176732)._