# Watcher 500 Server Error
**URL:** https://discuss.elastic.co/t/watcher-500-server-error/111371
**Category:** Elasticsearch
**Created:** [December 12, 2017, 3:04pm UTC](https://discuss.elastic.co/t/watcher-500-server-error/111371 "2017-12-12T15:04:32Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@cadab](https://discuss.elastic.co/u/cadab)
#### Post date: [December 12, 2017, 3:04pm UTC](https://discuss.elastic.co/t/watcher-500-server-error/111371/1 "2017-12-12T15:04:32Z")
I've upgraded es and Kibana from 5.6.4 to 6.0.1, when attempting to view the 'watcher' from within Kibana\>Management I get a 'Watcher: Error 500 Internal Server Error: An internal server error occurred' error.
Kibana logs report ..
```
Error: json argument must contain a watchStatusJson property
at Function.getPropsFromUpstreamJSON (/usr/share/kibana/plugins/x-pack/plugins/watcher/server/models/watch/base_watch.js:90:13)
at Function.fromUpstreamJSON (/usr/share/kibana/plugins/x-pack/plugins/watcher/server/models/watch/monitoring_watch.js:51:13)
at Function.fromUpstreamJSON (/usr/share/kibana/plugins/x-pack/plugins/watcher/server/models/watch/watch.js:41:22)
at hits.map.hit (/usr/share/kibana/plugins/x-pack/plugins/watcher/server/routes/api/watches/register_list_route.js:41:24)
at Array.map (native)
```
I had no 'watches' set up prior to the upgrade other than the default 4 that get created,
I've tried deleting the .watches, not sure what else to try.
---
### Author:  [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [December 15, 2017, 1:28pm UTC](https://discuss.elastic.co/t/watcher-500-server-error/111371/2 "2017-12-15T13:28:53Z")
Hi @cadab,
Can you post the result of searching against the .watches index?
`curl -XPOST /.watches/_search`
Thanks!
---
### Author:  [@jduquette](https://discuss.elastic.co/u/jduquette)
#### Post date: [January 4, 2018, 2:49pm UTC](https://discuss.elastic.co/t/watcher-500-server-error/111371/3 "2018-01-04T14:49:18Z")
I am having a similar issue. We have 60+ watches setup, and after doing an infrastructure refresh, and loading the watches via the API, none\* of them are firing. I'm receiving the following error:
> {
> "type":"error",
> "@timestamp":"2018-01-03T19:16:57Z",
> "tags":[
>
> ],
> "pid":8275,
> "level":"error",
> "message":"json argument must contain a watchStatusJson property",
> "error":{
> "message":"json argument must contain a watchStatusJson property",
> "name":"Error",
> "stack":"Error: json argument must contain a watchStatusJson property\n at Function.fromUpstreamJSON (/usr/share/kibana/plugins/x-pack/plugins/watcher/server/models/watch\_status/watch\_status.js:123:13)\n at new WatchHistoryItem (/usr/share/kibana/plugins/x-pack/plugins/watcher/server/models/watch\_history\_item/watch\_history\_item.js:16:36)\n at Function.fromUpstreamJSON (/usr/share/kibana/plugins/x-pack/plugins/watcher/server/models/watch\_history\_item/watch\_history\_item.js:42:12)\n at executeWatch.then.hit (/usr/share/kibana/plugins/x-pack/plugins/watcher/server/routes/api/watch/register\_execute\_route.js:38:51)\n at bound (domain.js:280:14)\n at runBound (domain.js:293:12)\n at tryCatcher (/usr/share/kibana/node\_modules/bluebird/js/main/util.js:26:23)\n at Promise.\_settlePromiseFromHandler (/usr/share/kibana/node\_modules/bluebird/js/main/promise.js:503:31)\n at Promise.\_settlePromiseAt (/usr/share/kibana/node\_modules/bluebird/js/main/promise.js:577:18)\n at Promise.\_settlePromises (/usr/share/kibana/node\_modules/bluebird/js/main/promise.js:693:14)\n at Async.\_drainQueue (/usr/share/kibana/node\_modules/bluebird/js/main/async.js:123:16)\n at Async.\_drainQueues (/usr/share/kibana/node\_modules/bluebird/js/main/async.js:133:10)\n at Immediate.Async.drainQueues (/usr/share/kibana/node\_modules/bluebird/js/main/async.js:15:14)\n at runCallback (timers.js:666:20)\n at tryOnImmediate (timers.js:639:5)\n at processImmediate [as \_immediateCallback] (timers.js:611:5)"
> },
> "url":{
> "protocol":null,
> "slashes":null,
> "auth":null,
> "host":null,
> "port":null,
> "hostname":null,
> "hash":null,
> "search":"",
> "query":{
>
> ```
> },
> "pathname":"/api/watcher/watch/execute",
> "path":"/apiwatcher/watch/execute",
> "href":"/api/watcher/watch/execute"
>
> ```
>
> }
> }
What information from the
curl -XPOST /.watches/\_search are you looking for? Since we have some many watches it will be difficult to post the entire response.
---
### Author:  [@jduquette](https://discuss.elastic.co/u/jduquette)
#### Post date: [January 4, 2018, 9:10pm UTC](https://discuss.elastic.co/t/watcher-500-server-error/111371/4 "2018-01-04T21:10:48Z")
So this seems to be happening only when I try to simulate the watch. Running a request directly to elasticsearch gives me the desired results:
curl -XPOST '[http://myuser:mypass@elastic.mydomain.com:9200/\_xpack/watcher/watch/ThisWatch/\_execute?pretty](http://myuser:mypass@elastic.mydomain.com:9200/_xpack/watcher/watch/ThisWatch/_execute?pretty)' -H 'Content-Type: application/json' -d'{"trigger\_data" : { "triggered\_time" : "now","scheduled\_time" : "now"},"ignore\_condition" : true, "action\_modes" : {"my-action" : "force\_simulate" },"record\_execution" : true }'
I ran the above request from my kibana instance, which is the same instance I am trying to run the simulation in.
I as have these setup on a cron schedule, they seem to be firing correctly as well. Any ideas why I can't get the simulation to work?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 1, 2018, 9:11pm UTC](https://discuss.elastic.co/t/watcher-500-server-error/111371/5 "2018-02-01T21:11:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.