mazma Posted August 23, 2015 Share Posted August 23, 2015 My CouchPotato has died, i.e. I can no longer connect to it. I've deleted the container and image and reinstalled, I've also tried using a different images. Rebooted server etc. No luck. Port 5050 doesn't show up on a port scan (not sure if it did before). Any idea? unRaid 6.0.1 Aug 22 22:37:44 Tower php: /usr/bin/docker start CouchPotato Aug 22 22:37:44 Tower php: CouchPotato Aug 22 22:37:48 Tower emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Aug 22 22:38:14 Tower emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Aug 22 22:38:34 Tower emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Aug 22 22:38:59 Tower emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Aug 22 22:39:33 Tower emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Aug 22 22:40:18 Tower emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Aug 22 22:41:30 Tower emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Aug 22 22:41:31 Tower kernel: mdcmd (49): spindown 0 Aug 22 22:42:12 Tower emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Aug 22 22:44:39 Tower kernel: mdcmd (50): spindown 8 Aug 22 22:45:25 Tower kernel: mdcmd (51): spindown 1 Aug 22 22:45:42 Tower kernel: mdcmd (52): spindown 2 Aug 22 22:45:48 Tower kernel: mdcmd (53): spindown 3 Aug 22 22:45:50 Tower kernel: mdcmd (54): spindown 4 Aug 22 22:45:52 Tower kernel: mdcmd (55): spindown 5 Aug 22 22:45:54 Tower kernel: mdcmd (56): spindown 6 Aug 22 22:45:58 Tower kernel: mdcmd (57): spindown 7 Aug 22 22:45:58 Tower kernel: mdcmd (58): spindown 9 Aug 22 22:46:01 Tower emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Quote Link to comment
Squid Posted August 23, 2015 Share Posted August 23, 2015 What are your port and volume mappings? Also post the log from CP (you can get to it from clicking the CP icon and selecting Logs) Quote Link to comment
mazma Posted August 23, 2015 Author Share Posted August 23, 2015 Default port mappings, 5050. Even tried different ports. Deleted the app folder and reinstalled, all working. Weird. Quote Link to comment
Leftie Posted November 1, 2015 Share Posted November 1, 2015 Had the same symptoms as mazma, i.e. no reachable Web GUI. Tried deleting the app-folder, but since that didn't help, I ended up having to delete the container and image before things started working again. So I had to reconfigure everything from scratch, but at least now it's up and running again Quote Link to comment
McCloud Posted November 8, 2015 Share Posted November 8, 2015 I had a similar issue, turns out my Docker image was full so that one particular machine was failing to start. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.