# Custom beat not working flag redefined: strict.perms

**URL:** <https://discuss.elastic.co/t/custom-beat-not-working-flag-redefined-strict-perms/245478>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [August 18, 2020, 6:26pm UTC](https://discuss.elastic.co/t/custom-beat-not-working-flag-redefined-strict-perms/245478 "2020-08-18T18:26:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dowdyph0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dowdyph0/32/74109_2.png) [@dowdyph0](https://discuss.elastic.co/u/dowdyph0)\
**Post date:** [August 18, 2020, 6:26pm UTC](https://discuss.elastic.co/t/custom-beat-not-working-flag-redefined-strict-perms/245478/1 "2020-08-18T18:26:27Z")

</div>

Hi, I've created a custom protocol beat using the python script **scripts/create\_tcp\_protocol.py**.

I've tweaked some things that we're not ok in the code like

`(*common.IPPortTuple)` entries in trans.go

So, i've managed to compile my module successfully.

But I'm getting a flag redefinition error when I try to run it.

**flag redefined: strict.perms** is the error.

It seems that **scripts/create\_tcp\_protocol.py** is based on a template that uses a legacy configuration structure?

How can i avoid that?

---

<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:** [September 15, 2020, 8:26pm UTC](https://discuss.elastic.co/t/custom-beat-not-working-flag-redefined-strict-perms/245478/2 "2020-09-15T20:26:28Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.