Jump to content

boohbah

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About boohbah

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Working fine on 6.6.3. Although I am struggling with this docker periodically spinning up discs every 20 or 40 mins - despite no file access requests coming from any client anywhere. I've been testing all weekend on this. It's definitely this libresonic docker initiating the spin ups. appdata is 100% on cache drive. Shares are all set to use cache. Directories are supposedly cached with the Dynamix Cache Directories plugin. No other plugins, dockers, clients or cron jobs are initiating the spin ups. I've been searching for a way to instruct Libresonic not to poll discs - nothing so far. FWIW, Airsonic does the same thing. Ideas for a solution will be highly appreciated.
  2. This is happening for me as well. Interestingly, I have 2 micro servers both configured (almost) the same way - but their hardware is slightly different - 1 x HP N54L and 1 x HP N36L. The drives on the N36L never spin up unless a genuine access request is made. The N54L drives spin up every 30 mins or 60 mins, depending on, well, who knows....it's that weird. This has been happening for the last few releases. I'm going to do some booting into safe mode and see if the issue remains. I'm also going to check that the bios options are the same for each. Diags attached if it helps.... Archive.zip
  3. Could be. However Z-Subsonic is an old app. Looking at the two docker apps: binhex: Version MADSONIC 5.1.5250.20150813.1155 MADSONIC REST API v1.12.0 License Madsonic Free Edition, for personal use only as described below. Server jetty/8.y.z-SNAPSHOT, java 1.7.0_95, Linux (129.5 MB / 243.0 MB) Size: Database: 16MB, Thumbs-Cache: 0MB, LastFM-Cache: 0MB, Lucene-Cache: 1MB Spring.Framework v3.2.14, Spring.Security v3.2.8 HyperSQL DataBase v2.3.2 gfjardim: Version MADSONIC 5.2.5420.20141214.0251 MADSONIC REST API v1.12.0 License Madsonic Free Edition, for personal use only as described below. Server jetty/8.y.z-SNAPSHOT, java 1.7.0_72, Linux 4.1.17-unRAID (amd64) (100.9 MB / 236.0 MB) Size: Database: 7MB, Thumbs-Cache: 0MB, LastFM-Cache: 0MB, Lucene-Cache: 1MB Spring.Framework v3.2.12, Spring.Security v3.2.5 HyperSQL DataBase v2.3.2 WARNING no transcoder found! So gfjardim Madsonic version is newer, but other components (jetty / spring) are older......
  4. The transcoding is fine and dandy on mine?? In the web interface (yourserverip:4040) click on 'new'. You'll see: ffmpeg version N-41404-g0e406ab- http://johnvansickle.com/ffmpeg/ Copyright © 2000-2014 the FFmpeg developers (25.02.2016) Flac works great for me - it gets transcoded into mp3 for streaming to my devices. However, I'm having some trouble with a client app (Z-Subsonic) I just bought for an older iPod (6.1.6). It will not connect to the binhex Madsonic docker running on my unraid......but it WILL connect to gfjardim's Madsonic docker on the same server (obviously running independently). The developer is silent on the issue. Probably abandoned it a while back. Last app store update was in 2012. I'm hoping binhex might have some insight into this - why does it connect to one but not the other? The bin hex docker is better - since it comes with the transcoding pre-installed. The gfjardim docker does not. Cheers
  5. unRAID OS Version: 6.0 rc3 Description: The general Docker menu vanishes depending on DNS settings. How to reproduce: Condition One: In network settings, if IP address is set to manual (completed) then DNS is set to manual and DNS address fields are blank. In this condition, the general Docker menu bar is visible. Condition Two: In network settings, if IP address is set to manual (completed) and the DNS fields are completed and the config is saved, then the general Docker menu item vanishes. Note. The DNS settings made in Condition Two do not survive a reboot - hence post re-boot the general Docker menu item returns - forming Condition One. Expected results: That DNS settings survive a re-boot and that the general Docker menu item remains unconditionally visible. Actual results: See 'How to reproduce' Other information: Machine is HP N36L. There have been persistent issues with retention of DNS settings over beta releases, however until this point, none that have caused the disappearance of a menu item. The machine has a modified bios to allow certain features, as discussed in other threads on this forum.
  6. Good ideas. I have also just discovered that in 'Bridge', I can get the local LAN nodes to recognise each other if I manually enter the static IPs of each into the respective address boxes on each (rather than leave it as 'dynamic'). This works with the IP address alone, and no port needs to be specified (which the gui invites you to do). So. I guess that could be called a fix. I'm very grateful for this docker by the way. Thank you so much.
  7. I have playing for days with gfjardim's syncthing Docker and here is what I have learnt. If network type is set to 'Bridge', then the online version update function will work, but the local discovery function will not (regardless of your port routing skills). So if you want to connect and sync between nodes on the same LAN, you can't. If you set your local nodes to use online discovery, then announce.syncthing.net gets confused about who it is talking to after the NAT in your router. This causes weirdness. If network type is set to 'Host' (with necessary ports 21025, 8080 and 22000 all specified), then the online version update function will not work (you are forever stuck at 0.9.18), but the local discovery function does work - and very nicely. In this condition, connection and sync works between same LAN nodes just fine. So, at present, we can't have it both ways. Ideally, at least for me, I would like to be able to have 3 same LAN nodes all sync together, and have just one of those connecting with the announce server for off site nodes (later on). Of course the cherry on top would be to have them all able to auto update their version. Version 0.10.12 came out about 8 hours ago I don't know how to fix this. Perhaps the maintainer can take a look?
  8. Grabbed. Thank you for the continued updates. Really good karma.
  9. Fabulous - works great. Thanks
  10. Fixed using precision guesswork! http://lime-technology.com/forum/index.php?topic=33973.msg330112#msg330112
  11. docker run -d -p 4040:4040 --name="madsonic" -v /mnt/user/Music:/Music -v /mnt/user/Movies:/Movies -v /mnt/cache/madsonicdata:/config -v /etc/localtime:/etc/localtime:ro binhex/arch-madsonic Unable to find image 'binhex/arch-madsonic' locally Pulling repository binhex/arch-madsonic 2014/09/25 09:33:52 Get https://index.docker.io/v1/repositories/binhex/arch-madsonic/images: dial tcp: lookup index.docker.io: file exists Fixed! It appears to be a DNS error. Changed DNS, all good Pulling Madsonic now. 48 hours to figure that out.... So so silly.
  12. Have been having some trouble getting going with this. Has anyone seen this before? Sep 26 21:42:01 Tower php: /usr/local/emhttp/plugins/dockerMan/dockerupdate.php Sep 26 21:42:01 Tower php: Updating templates... Sep 26 21:42:01 Tower php: #012Warning: preg_match(): Empty regular expression in /usr/local/emhttp/plugins/dockerMan/dockerClient.php on line 131 Sep 26 21:42:01 Tower php: #012Warning: unlink(/tmp/tmp-1806355066.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dockerMan/dockerClient.php on line 143 Sep 26 21:42:01 Tower php: Updating info... Sep 26 21:42:01 Tower php: Done. Sep 26 21:42:01 Tower php: I saw that in the log whilst trying to resolve this other thing... docker run -d -p 4040:4040 --name="madsonic" -v /mnt/user/Music:/Music -v /mnt/user/Movies:/Movies -v /mnt/cache/madsonicdata:/config -v /etc/localtime:/etc/localtime:ro binhex/arch-madsonic Unable to find image 'binhex/arch-madsonic' locally Pulling repository binhex/arch-madsonic 2014/09/26 21:51:29 Get https://index.docker.io/v1/repositories/binhex/arch-madsonic/images: dial tcp: lookup index.docker.io: file exists And nothing happens. I have no containers or images lurking anywhere...and no-one else has reported the repository pull issue.... I posted in the madsonic specific section of the forum, and we tried a few things, but I think this issue has run its course for ideas there. So I'm looking for guru help. Would be really nice to enjoy this awesome plugin with everyone else Dan
  13. Oh boy...it's back docker run -d -p 4040:4040 --name="madsonic" -v /mnt/user/Music:/Music -v /mnt/user/Movies:/Movies -v /mnt/cache/madsonicdata:/config -v /etc/localtime:/etc/localtime:ro binhex/arch-madsonic Unable to find image 'binhex/arch-madsonic' locally Pulling repository binhex/arch-madsonic 2014/09/25 09:33:52 Get https://index.docker.io/v1/repositories/binhex/arch-madsonic/images: dial tcp: lookup index.docker.io: file exists No amount of new docker.img creation or permission fixing is solving it this time. docker images REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE I had it working once on /mnt/user and decided to install a cache drive, since madsonic kept the array disc spun up all the time. Nothing else at all changed. I see nobody else reporting this, so I suspect it's my set up, maybe I should post this somewhere else? But since it's specific to Docker....... All the same, any new directions appreciated. Dan
  14. Yes! This worked. I'm thankful for your help, and that it was a simple issue in the end. Much appreciated, and thank you very much for your work on this docker app. Dan
  15. Thanks for the advice. I should offer some more information. I'm using beta 9 and have just started out with docker - it seems a great alternative (and fun to boot) to the plugin system - which is how I have been running madsonic. The output from the console has so far always been as I outlined i.e I have never had a successful docker pull - meaning to say no download image has ever been downloaded....for any dockerized app that I have tried to obtain, not just madsonic. I made sure to test a few different ones to see if the error was reproducible. docker images gives REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE No content. Something is preventing downloads from any repository that I have tried. Always the same result - as previously listed. No errors are seen in the sys logs I've looked at. Perhaps docker has a separate log somewhere? Interestingly, this 'error' isn't really presenting itself as a bona fide error with its own message. I am thinking it may be a permissions issue now...not sure where to start though.