skunkworx

I assumed that there was a postgresql version mismatch. Rather than downgrading to 9.5 I decided to remove the config and data directories and force a re-download of database as if it was a fresh install. This did throw up an error during install (see Below) this error was repeated forever. Due to the error I still thing there is something wrong with the docker image but since I restarted the docker it seems to be working. I did find a site where there was a method of upgrading a DB from 9.5 to 9.6.1 but I didn't try this at all. STATEMENT: ALTER TABLE dbmirror_pendingdata DROP CONSTRAINT "dbmirror_pendingdata_SeqId" CASCADE WARNING: SET TRANSACTION can only be used in transaction blocks WARNING: SET CONSTRAINTS can only be used in transaction blocks ERROR: constraint "dbmirror_pendingdata_SeqId" of relation "dbmirror_pendingdata" does not exist Skunk

I am getting exactly the same error. I tried deleting docker and image and redownloading bust still get same error. Any suggestions. Regards Skunk

Great work. Thank you very much. I hope your back gets better soon. Skunk Please post your settings from the plugin page. Sent from my SM-T817W using Tapatalk The settings as requested (should be attached as a png file. I wasn't sure how to make it appear inline in my post). Just wondering why you requested them? Skunk

Great work. Thank you very much. I hope your back gets better soon. Skunk

I'm sure he'll update it after the holidays. Since the releases appear to now be placed into version number sub folders rather than just lumped into "download" like before it's probably going to take more than just changing the repo url else it will just break again next version. Just give him a bit of time. Thanks For the reply. I'm fine with waiting as I know people do this for free and also have real life things to do also. I was just wanted to prompt a response to find out if it was going to be updated or if I should be looking for an alternative.

Any chance of an updated sabnzbd plugin that references the new repo structure

Only way is Community Applications clicking the will display the changelog for the app. But not all authors always remember to update it. Thanks for your last reply. It seems like there has been another round of updates to these dockers but for the life of me I can't seem to find what has been updated in them. The main repo pages for the ones I checked don't show any updates and if you drill down to the releases page it seems like the exact same release version# as the one from 9 days ago. The only thing I could see was that there was a failed build a day or two ago which seems like it might have somehow flagged a new version. I like to keep the dockers up-to-date but I also like to track what has changed. It seems like the last few updates haven't carried any updates to speak of unless I am just looking in the wrong place. Is seems like a concise version history is a feature that is lacking in docker and something that worked much better in the plugins . There must be a better/easier way of tracking the updates to these dockers as each update can be 10 - 100+ MB each which seems highly excessive for a change to two lines in a readme file.

I was wondering if the latest docker updates to couch, sonarr, headphones & musicbainz is anything more than updated URLs in the readme.md file? It seems overkill that a readme file triggers a docker image update but I might just be missing something obvious. Also is there an easy way from the unraid ui to see what has been updated in a docker and the size of the download will be easily? I did look at the github releases pages for each docker to try and work out what had been changed but I was not 100% sure I was looking in the right place. If this is the only place to see what has changed then it is a shame as it's not very user friendly considering nearly every thing else in unraid and your dockers are so well done.

I have exactly the same issue. Here is my log file. Any suggestions? DBDefs is in your config folder, may need editing postgres folders appear to be set 2015-12-03 23:38:30,468 CRIT Supervisor running as root (no user in config file) 2015-12-03 23:38:30,478 INFO supervisord started with pid 27 2015-12-03 23:38:31,480 INFO spawned: 'redis-server' with pid 31 2015-12-03 23:38:31,483 INFO spawned: 'postgres' with pid 32 2015-12-03 23:38:32,516 INFO success: redis-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-12-03 23:38:32,516 INFO success: postgres entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Dec 3 23:38:40 988cf1f9b8b2 syslog-ng[51]: syslog-ng starting up; version='3.5.3' 2015-12-03 23:40:04,201 WARN received SIGTERM indicating exit request 2015-12-03 23:40:04,201 INFO waiting for redis-server, postgres to die 2015-12-03 23:40:05,325 INFO exited: redis-server (exit status 0; expected) 2015-12-03 23:40:05,335 INFO stopped: postgres (exit status 0) DBDefs is in your config folder, may need editing postgres folders appear to be set 2015-12-03 23:40:05,989 CRIT Supervisor running as root (no user in config file) 2015-12-03 23:40:05,996 INFO supervisord started with pid 15 2015-12-03 23:40:07,000 INFO spawned: 'redis-server' with pid 19 2015-12-03 23:40:07,003 INFO spawned: 'postgres' with pid 20 2015-12-03 23:40:08,029 INFO success: redis-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-12-03 23:40:08,030 INFO success: postgres entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Dec 3 23:40:16 988cf1f9b8b2 syslog-ng[40]: syslog-ng starting up; version='3.5.3' 2015-12-03 23:47:23,232 WARN received SIGTERM indicating exit request 2015-12-03 23:47:23,239 INFO waiting for redis-server, postgres to die 2015-12-03 23:47:23,544 INFO exited: redis-server (exit status 0; expected) 2015-12-03 23:47:23,696 INFO stopped: postgres (exit status 0) DBDefs is in your config folder, may need editing postgres folders appear to be set 2015-12-03 23:47:53,572 CRIT Supervisor running as root (no user in config file) 2015-12-03 23:47:53,579 INFO supervisord started with pid 12 2015-12-03 23:47:54,581 INFO spawned: 'redis-server' with pid 16 2015-12-03 23:47:54,584 INFO spawned: 'postgres' with pid 17 2015-12-03 23:47:55,661 INFO success: redis-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-12-03 23:47:55,661 INFO success: postgres entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Dec 3 23:48:03 988cf1f9b8b2 syslog-ng[36]: syslog-ng starting up; version='3.5.3' Dec 3 23:59:01 988cf1f9b8b2 /USR/SBIN/CRON[44]: (root) CMD (/bin/bash /root/update-script.sh) Dec 4 00:00:01 988cf1f9b8b2 /USR/SBIN/CRON[54]: (root) CMD (/bin/bash /root/update-script.sh)

I think it is correct but with such limited log files it is hard to be certain. I've update and now get the following log [Jul 15 22:34:10] No-IP successfully called. Result was "nochg". How would I know if I have the correct config?

I had No-ip working with issues. I noticed there was an update to the docker so I updated. This broke the installation so after a bit of reading and research I sorted it out. But now I get an error when running the docker and it stops. [Jul 14 16:40:26] Something went wrong. Check your settings. Result was "nochg". [Jul 14 16:40:26] For an explanation of error codes, see http://www.noip.com/integrate/response I looked up the nochg result and it means that there was no ip update done because the ip submitted was current. This result shouldn't cause the docker to stop. The problem now is I can not get the docker to stay in a running state. I suppose when my ip changes I will be able to run it again and all will be good. But it is a bit of a pain. I would imagine rebooting my router might give me a new ip. But it would be better to have the response handled correctly.