# Intermittent errors using Signals plugin

**URL:** <https://forum.search-guard.com/t/intermittent-errors-using-signals-plugin/1745>\
**Category:** Signals Alerting\
**Created:** [January 22, 2020, 5:33pm UTC](https://forum.search-guard.com/t/intermittent-errors-using-signals-plugin/1745 "2020-01-22T17:33:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gandrademello](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/gandrademello/32/708_2.png) [@gandrademello](https://forum.search-guard.com/u/gandrademello)\
**Post date:** [January 22, 2020, 5:33pm UTC](https://forum.search-guard.com/t/intermittent-errors-using-signals-plugin/1745/1 "2020-01-22T17:33:21Z")

</div>

Hello everbody!

I know that Signals is still in beta, but I was trying to get a taste of it and I’m having a weird behavior using it. While executing any action in signals tab in kibana, sometimes it works and sometimes I get a `Unknown tenant: null` error.

When I do get the error, I get the following error on JS console:  
`{message: "Unknown tenant: null", body: {…}, path: "/_signals/watch/_main/_search?scroll=25s", statusCode: 500}`

Working:

 ![image](https://us1.discourse-cdn.com/flex019/uploads/search_guard/original/1X/a3d59ecf9792e5aab11d102b3d81c5f697a8436b.png)

Not working

 ![image](https://us1.discourse-cdn.com/flex019/uploads/search_guard/original/1X/13c41558f63f1d126a9c533890b9bc135973efc8.png)

Even when creating/deleting/updating the watchers or agents I am having the same behavior and would have to try several times until they get created/deleted/updated

I’m using ES 7.5.0 and Kibana 7.5.0 and also have multitenancy disabled in both (SG config and Kibana).

Thanks in advance

---

<div class="post-metadata">

**Author:** ![srgbnd](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/srgbnd/32/506_2.png) [@srgbnd](https://forum.search-guard.com/u/srgbnd)\
**Post date:** [January 23, 2020, 9:19am UTC](https://forum.search-guard.com/t/intermittent-errors-using-signals-plugin/1745/2 "2020-01-23T09:19:25Z")

</div>

Strange, I can’t reproduce the issue. Do you use the latest tech preview package? [Getting started | Alerting for Elasticsearch | Search Guard](https://docs.search-guard.com/latest/elasticsearch-alerting-getting-started)

Could you please share the following data?

1. Kibana config - kibana/config/kibana.yml
2. Kibana log. Make sure you have `logging.quiet: false` in kibana.yml to have logs
3. Elasticsearch log. Make sure you have the following lines in elasticsearch/config/log4j2.properties:

```auto
logger.sgs.name = com.floragunn.searchsupport
logger.sgs.level = debug

logger.lrt.name = com.floragunn.signals
logger.lrt.level = debug

logger.rh.name = com.floragunn.searchguard.support.ReflectionHelper
logger.rh.level = debug

logger.pe.name = com.floragunn.searchguard.privileges
logger.pe.level = debug

logger.sgf.name = com.floragunn.searchguard.filter.SearchGuardFilter
logger.sgf.level = debug

```

---

<div class="post-metadata">

**Author:** ![srgbnd](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/srgbnd/32/506_2.png) [@srgbnd](https://forum.search-guard.com/u/srgbnd)\
**Post date:** [January 23, 2020, 9:20am UTC](https://forum.search-guard.com/t/intermittent-errors-using-signals-plugin/1745/3 "2020-01-23T09:20:34Z")

</div>

Assigned @srgbnd on January 23, 2020, 9:20am UTC



---

<div class="post-metadata">

**Author:** ![gandrademello](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/gandrademello/32/708_2.png) [@gandrademello](https://forum.search-guard.com/u/gandrademello)\
**Post date:** [February 18, 2020, 10:17am UTC](https://forum.search-guard.com/t/intermittent-errors-using-signals-plugin/1745/4 "2020-02-18T10:17:23Z")

</div>

Hey @srgbnd sorry taking so long to answer here. I fixed it by redeploying the sg configurations (roles, role\_mappings, etc).  
After that it seems to work - not sure how I ended in that situation though.

Also I did tried setting the logs to `debug`, but I couldn’t find anything differente than that `Unknown tenant: null` message.

Anyway, tnks for answering back!