rjstott

Members
  • Posts

    83
  • Joined

  • Last visited

Posts posted by rjstott

  1. Bonieni, Frank1940,

     

    Thanks for all that. I am going to say that as far as I can tell the edit has fixed the problem and we can now connect to the internet from core activities including updates and terminal! My curiosity is still asking what changed in the new releases to cause the problem. But we have at last moved on and I have an up to date release. For some reason none of the OS X file tags show up but although I religously set these I never found a good use!

     

     

  2. Hi bonieni,

     

    I think to do this I have to remove the flash drive and edit the file through my Mac. Before I do this, there are two entries because there is an on board Realtek ethernet port and I have a PCIe network card with the Intel chip. There was some suggestion a long while back that the Realtel card was the issue so I added the Intel. As far as I can see eth1 is disabled (though where this setting is I don’t know). In any event there is currently no ethernet plugged into eth1 so it must be disabled? Additionally the Network.cfg file is identical between 6.6.7 and 6.7.7 so is there a difference between how the two versions use the .cfg data. I could believe that your suggestion could well fix this but being a curious old fart I like to know why?

     

    Any thought?

     

    Regards

     

    Richard

  3. Tried again with the latest 6.7 release and same problem, internat access is gone. Someone on the unRaid team must know of changes to networking that might have caused the problem.  I've gone back, again, to 6,6,7 and network access is working again. My diagnostice are on this thread! One more crumb, I'm fairly certain that internet access is working for Dockers. It just seems to be unRaid core functionality like updates and checking for them!

  4. I saw that suggestion in another thread so I tried it even though it can't possbly solve the problem if the server won't ping 8.8.8.8. It would resolve a problem with named sites of course. It didn't work when I tried it. I have added the diagnostics but of course they are for the reverted 6.6.7 but I guess all the basic data should be the same between the two releases! I note that the 8.8.8.8 is still resident in the first DNS entry and I must remember to put it back to my SmartDNS setting!

    tower-diagnostics-20190410-1315.zip

  5. I just upgraded to 6.7.0 rc7 and I lost internet access from unraid. The rest of my network is fine, I can access the GUI and I can ping my router from unraid. I can't ping 8.8.8.8 or any other internet address and some unraid functionality is lost such as docker updates (access to GitHub). A downgrade to 6.6.7 brings it all back!

     

    Any ideas?

  6. I'm having the same issue. It was working nicely and then it said there was an update which got it stuck as the update port isn't definable (7441?). So I reloaded the docker and then had endless problems as system.properties was missing and I'm guessing a simple typo has the wrong name system.propetties for recovery. Now I get stuck as above.

  7. I upgraded to 6.4.0 abd Dolphin no longer starts. I get the below error on the screen and the following in the log

     

    Sun Jan 28 09:41:25 2018
    vncext: VNC extension running!
    vncext: Listening for VNC connections on port 5901
    vncext: created VNC server for screen 0
    error opening security policy file /etc/X11/xserver/SecurityPolicy
    Openbox-Message: Failed to open the display from the DISPLAY environment variable.

    Xvnc Free Edition 4.1.1 - built Nov 18 2014 16:07:18
    Copyright (C) 2002-2005 RealVNC Ltd.
    See http://www.realvnc.com for information on VNC.
    Underlying X server release 40300000, The XFree86 Project, Inc
     

    Dolphin.jpeg

  8. I had terrible problems with all my dockers and part of the issue was that some of the files existed on both an array drive and the cache. I found the only way to get back to 'normal' was to delete all the support files in Appdata for Dockers on the array and the Cache then begin from scratch. You will lose all config data. It might be possible to copy some files elsewhere onto the array into a directory with a completely different name. This did work for me for everything I was worried about except Plex, where the support files are so numerous my server continually crashed. I still have a Docker.img file that exists on the cache and in the array that I can't fix. I also have a Mariadb database that I can't access but Nodered can.

     

    When copying make sure that you get the files you want as there may be two, one on the array and one on the cache.

  9. My system is a mess since upgrading to 6.4.0 as it forced a cache format.  I have resolved a lot (and lost a lot) but the latest one defeats me. The Docker.img file is shown as on the Cache where it should be and on an array drive. This confuses me and confuses Mover. I have deleted the Docker.img file and rebuilt my Dockers but the problem has persisted. I see other reports with solutions that should have worked if I deleted and recreated the Docker.img file. The file I use is 60GBytes so please don't tell me its run out of space and because of the issue I have yet to rebuild most of my Dockers.

     

    Here is Mover log:

     

    Jan 26 00:09:02 Media root: mover: started
    Jan 26 00:09:02 Media root: move: file /mnt/disk3/apps/Docker/docker.img
    Jan 26 00:09:02 Media root: move_object: /mnt/disk3/apps/Docker/docker.img File exists
    Jan 26 00:09:02 Media root: move_object: /mnt/disk3/apps/Docker: Directory not empty
    Jan 26 00:09:02 Media root: move_object: /mnt/disk3/apps: Directory not empty
    Jan 26 00:09:02 Media root: mover: finished

     

    Did I miss a real fix that works?

     

    I lost Docker data because the backup files I created suffered a similar fate and it has been difficult to establish which files were in current use etc.

         
  10. Hi,

     

    Just tried this and get an error as follows:

    "root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="FreePBX13" --net="bridge" -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -p 8082:8082/tcp -p 5060:5060/tcp mima84/docker-freepbx

    Unable to find image 'mima84/docker-freepbx:latest' locally
    Pulling repository docker.io/mima84/docker-freepbx
    /usr/bin/docker: Network timed out while trying to connect to https://index.docker.io/v1/repositories/mima84/docker-freepbx/images. You may want to check your internet connection or if you are behind a proxy..
    See '/usr/bin/docker run --help'.

    The command failed."

     

    Tried a second time and it has installed ok. Let's see what we can do! Thanks for the Docker, I'm sure there will be a lot of interest.

  11. Hi, just tried to install this docker and get an error as follows:

     

    "root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="HADashboard" --net="" -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -v "/mnt/cache/apps/Docker/apps/hadashboard/lib":"/lib":rw -v "/mnt/cache/apps/Docker/apps/hadashboard/dashboards":"/dashboards":rw -v "/mnt/cache/apps/Docker/apps/hadashboard/hapush":"/hapush/":rw -v "/mnt/cache/apps/Docker/apps/hadashboard/widgets":"/widgets":rw jcreynolds/docker-hadashboard

    508f63bdcb2ded5c1559bf957751524e9a97f29a5e567110207db8395e3a426b

    docker: Error response from daemon: Container command not found or does not exist.."

     

    Am I missing something? The subdirectories have been created but they are all empty!

     

  12. Squid, you are quite right, that solution would work fine for me. I'm sure your script works fine and I would have used it if it was incorporated into the 'built-in' list and the functionality wasn't so new. My posting was really a way of documenting the problem in case anyone else came across it (it fairly messes up the Plex database!). I guess I was also querying whether the original recommendation to put Dockers on the Cache was still good as without implementation of a solution there is possibly an issue. Finally, I wanted to see whether anyone else had experienced this problem.

     

    I ought to add that I had a security camera docker that filled the cache up too, so there are other apps that can cause a problem!

     

    Of course using some of the other new CA tools such as Backup etc will also help in this area.

     

    I think in my case I am going to go with a slight modification to your solution and that will be to create a transit media fileset where new media files are kept. This will allow me to vet the media (watch/listen) before running a batch archive to the unRaid storage. I have two other reasons for this, one is that I use 'shingled' drives where I believe write once may be advantageous and the second allows me to batch feed new media to a second storage system as an incremental backup.

  13. I've had my Dockers on the cache since I first started using Dockers. The main use is for the Plex Server and keeping the Plex Metedata files, Indices etc on cache certainly speeds things up.

     

    However, I have a problem. My Plex installation probably now uses half of the 256GB SSD cache drive and on more than one occasion I have managed to fill the balance of the cache with Media files in transit. By which I mean Mover hasn't got around to cleaning up the cache. Whilst this isn't a problem for those files, I'm pretty certain it does cause problems for the Dockers which may face a situation where the cache is full. I did see there was a script to invoke the mover and that this could run using the CA User Scripts. However, this seems to be a very clumsy solution to a problem that is inherent in using the cache for Dockers.

     

    So I was wondering whether anyone else has encountered this issue, whether they have adopted the script solution or is there another more elegant way of resolving this. I guess one way would be to install another SSD which is only used for the Docker files in which case it would be easy to monitor use of the Docker storage. Or perhaps what would be a solution would be for 'cache only' files to be allowed to overflow onto the unRaid drives should the cache become full. In which case the Mover would then cleanup 'cache only' files when space became available on the cache?

     

    Any thoughts?

     

     

  14. Hi,

     

    Many thanks, and yes you are right about posting, however as there are numerous error messages in the Plex startup log it is not always easy to know what is important and what isn't. I like lots of others suffer dreadfully when changes are made such that what we had stops working, the instructions for setting up no longer match reality and because it is so long since we actually set things up we are a bit blase about doing it. IMHO a missing / shouldn't cause so much grief and if it is so vital or obvious it should get better error reporting (perhaps you ommitted the / in the path definition). As a quick work around 'for example' I just tried to install the Plex server on my Mac. All went well BUT similarly the client refused to see the Media! The only thing that worked was to use 'Analyze' which I've never ever used before!

     

    Really appreciate the help

  15. Hi, here is the data you asked for and a short commentary.

     

    1) Add Docker without path to Media (attach 1)

    2) Plex start up, some network errors, I think I can ignore? (attach 2). Plex runs with Metadata but no Media

    3) Add path to Media (attach 3)

    4) Click done and Docker command fails and orphans the image (attach 4)

     

    I understand the path process and although it has changed this surely right? The Media is in sub-folders below LP2015 which I can map in Plex

    Plex_Docker_install.txt

    Plex_Log.txt

    Add_Path.jpg.2e8c65633ef21ba1694206dfcb23f22c.jpg

    Add_path_result.txt

  16. I just switched to this docker and I'm encountering some problems.

     

    1) I don't see anywhere to tell Plex where my media is. Previously I created paths to each Plex Category but there doesn't seem to be anywhere to add even a single path by default although the instructions imply there is

    2) So I add a simple Path config and the following error pops up - Says something about 'Invalid volume destination path: 'LP' mount path must be absolute.' but I use all I did was provide a name and use the path select process /mnt/user etc

    3) Then the Docker disappears and I am left with an empty orphan image file needing deleting?

    4) The default config file should be on the cache but it isn't so this needs correcting every install?

    5) Adding the Media path after a start (which Plex does though no media files just metadata) kills the image as per 2)

     

    I did visit the Linuxserver.io forum where there are reports of others with problems.

     

    Just tried the needo version and get this same error 'Invalid volume destination path: 'LP' mount path must be absolute'

     

    Advice/help please

  17. A bit of an update. I tried to re-format the cache drive, fell over the need to select only one pool device but eventually selected xfs and nothing happened. I did all the other bits of removing the cache, bringing the array back on line and selecting Format. It selects for about a second and resets. It certainly didn't format the drive. Anyway, reselected btfs and put the cache back. Eerything worked but in the process of copying files I've deleted a lot and created a bit of cache space. So no recurring log errors and we'll see how it goes.

     

    Bit odd that the Format didn't work, would I need to remove the drive and fromat it elsewhere?

     

    The Docker at 20GB will run Emby too, 'cos I have been there but it's no longer installed. I've also had other apps running with Emby so I doubt that was the problem.