# Elastic Agent Panic with nil pointer on \`null\` processor

**URL:** <https://discuss.elastic.co/t/elastic-agent-panic-with-nil-pointer-on-null-processor/373078>\
**Category:** Elastic Agent\
**Created:** [January 10, 2025, 7:55pm UTC](https://discuss.elastic.co/t/elastic-agent-panic-with-nil-pointer-on-null-processor/373078 "2025-01-10T19:55:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![BenB196](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benb196/32/83401_2.png) [@BenB196](https://discuss.elastic.co/u/BenB196)\
**Post date:** [January 10, 2025, 7:55pm UTC](https://discuss.elastic.co/t/elastic-agent-panic-with-nil-pointer-on-null-processor/373078/1 "2025-01-10T19:55:08Z")

</div>

Hi, I was wondering if anyone else has hit this issue, if I define a `null` processor in an integration policy, the Elastic Agent will immediately enter a crashloop with the error:

```auto
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x5c9aa145445a]

```

To reproduce:

1. Elastic Agent (8.16.2)
2. Create an agent policy and assign agent to it
3. Create an integration on the agent policy (only thing that matters is that it supports setting processors.
4. Define a processor like:

```auto
processors:
- null

```

Observe when update rolls out that the agent is now in a crashloop.