# Debugging service issues in Rancher

**URL:** <https://forums.suse.com/t/debugging-service-issues-in-rancher/5087>\
**Category:** General\
**Created:** [January 4, 2017, 7:02pm UTC](https://forums.suse.com/t/debugging-service-issues-in-rancher/5087 "2017-01-04T19:02:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![henrywho](https://avatars.discourse-cdn.com/v4/letter/h/898d66/32.png) [@henrywho](https://forums.suse.com/u/henrywho)\
**Post date:** [January 4, 2017, 7:02pm UTC](https://forums.suse.com/t/debugging-service-issues-in-rancher/5087/1 "2017-01-04T19:02:01Z")

</div>

I’m currently using Rancher v1.1.4 with rancher-compose v0.8.5.

When I try to start a service with a bad entrypoint defined the service continually recreates itself, and I get this:

```auto
...
ERRO[0001] Failed to get logs for amos_amos-worker-resque-scheduler_1: Failed to find action: logs
...

```

If I use “View logs” on the container via the Rancher UI and time it perfectly, it gives the logs / and shows the error (missing script), but most of the time I can’t view the logs this way either.

Is there any way to get logs from a misbehaving service? Or to have rancher-compose only try to start the service once so that the container is left so that we can debug it?

---

<div class="post-metadata">

**Author:** ![David\_Sanftenberg](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/david_sanftenberg/32/2446_2.png) [@David\_Sanftenberg](https://forums.suse.com/u/David_Sanftenberg)\
**Post date:** [May 9, 2017, 12:01pm UTC](https://forums.suse.com/t/debugging-service-issues-in-rancher/5087/2 "2017-05-09T12:01:42Z")

</div>

I have the same question. There needs to be an easier way to get/keep these logs from failed containers, debugging is a massive pain having to expertly-time “view logs” before Rancher stops the container. Am I just missing something?
