# No debugging data returning after restarting beat with debugging/logging turned on
**URL:** https://discuss.elastic.co/t/no-debugging-data-returning-after-restarting-beat-with-debugging-logging-turned-on/39807
**Category:** Beats
**Created:** [January 21, 2016, 6:09pm UTC](https://discuss.elastic.co/t/no-debugging-data-returning-after-restarting-beat-with-debugging-logging-turned-on/39807 "2016-01-21T18:09:48Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@adron](https://discuss.elastic.co/u/adron)
#### Post date: [January 21, 2016, 6:09pm UTC](https://discuss.elastic.co/t/no-debugging-data-returning-after-restarting-beat-with-debugging-logging-turned-on/39807/1 "2016-01-21T18:09:48Z")
I'm using elasticsearch w/ Kibana 4.0 w/ the AWS managed setup. I'm working on figuring out if all my beats are actually reporting so I'm checking as I install topbeat on each new system throughout my environment. I have some instances running in Rackspace, AWS, and Azure, all that have to report to the AWS managed elasticsearch instance. Currently I've got the beats service started on a few machines, and when I go back to restart with debugging I'm running into this situation...
```
ubuntu@ip-xxx-yy-zz-ddd:/etc/topbeat$ sudo /etc/init.d/topbeat stop
ubuntu@ip-xxx-yy-zz-ddd:/etc/topbeat$ sudo /etc/init.d/topbeat start -c ./topbeat.yml -e -v -d "*"
ubuntu@ip-xxx-yy-zz-ddd:/etc/topbeat$
```
I stop topbeat with "`sudo /etc/init.d/topbeat stop`" and then start it up again with "`sudo /etc/init.d/topbeat start -c ./topbeat.yml -e -v -d "*"`" but then I get nothing after that. If I just issue a "`sudo /etc/init.d/topbeat start`" I get "`/usr/bin/topbeat-god already running.`"
Why is the debugging/logging data not coming out at stdout? Any troubleshooting idea?
---
### Author:  [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)
#### Post date: [January 22, 2016, 2:00am UTC](https://discuss.elastic.co/t/no-debugging-data-returning-after-restarting-beat-with-debugging-logging-turned-on/39807/2 "2016-01-22T02:00:28Z")
Hi @adron, the init.d script does not accept those parameters. Try this instead:
```auto
sudo /etc/init.d/topbeat stop
sudo /usr/bin/topbeat -c ./topbeat.yml -e -v -d "*"
```
---
### Author:  [@adron](https://discuss.elastic.co/u/adron)
#### Post date: [January 22, 2016, 8:57pm UTC](https://discuss.elastic.co/t/no-debugging-data-returning-after-restarting-beat-with-debugging-logging-turned-on/39807/3 "2016-01-22T20:57:35Z")
Just curious, where is this located in the documentation? That is, where and how to use examples. I found the area that explains the switches but there doesn't seem to be anything specific about how the service is or isn't running on the various operating systems.
---
### Author:  [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)
#### Post date: [January 22, 2016, 9:14pm UTC](https://discuss.elastic.co/t/no-debugging-data-returning-after-restarting-beat-with-debugging-logging-turned-on/39807/4 "2016-01-22T21:14:53Z")
Adron, please see this ticket. If you specific recommendations, we would love to have your comments. Thanks
>
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 9:56pm UTC](https://discuss.elastic.co/t/no-debugging-data-returning-after-restarting-beat-with-debugging-logging-turned-on/39807/5 "2017-07-05T21:56:27Z")