Jump to content

Leifgg

Members
 View Profile  See their activity

  • Posts

    408

  • Joined

  • Last visited

 Content Type 

Posts posted by Leifgg

    [support] limetech's docker repository

    in Docker Containers

    Posted

    I belive it's a lot easier than that. There is a thread about it but I don't have it now (I am not on my desktop PC).

     

    If I remember, just stop the current container, install the new one with exactly same folder mappings and then unistall the old one. This is what I did when I changed from Needo to Linuxserver. But a backup of the config might be good to have...

    [support] limetech's docker repository

    in Docker Containers

    Posted

    There is nothing more you need to install on unRAID but you need to configure Plex so it finds your media files.

     

    Since you have the Host Path: set to /mnt/user/Movies/ I guess that this is where your movies are.

     

    That folder is mapped to /movies and that is what the Plex app inside the container can see so you need to setup Plex and Add Library, select Movies and Add folders and browse for media folder and select Movies.

     

    You can find the Plex Web page on same IP as your serve on port 32400 (like this http://192.168.1.101:32400)

    [Plugin] IPMI for unRAID 6.1+

    in Plugin Support

    Posted

    Nope, If I go to Tools, IPMI tool all my sensors are gone.

     

    And the normal Dynamix temp and fan readings at the bottom right of the Web GUI is gone as well but it looks like it’s get overwritten by the error message as well. I was able to select and copy it:

    Array Started• Dynamix webGui v2016.02.09 Warning: array_combine(): Both parameters should have an equal number of elements in /usr/local/emhttp/plugins/ipmitool-plugin/include/ipmitool_helpers.php on line 59 Warning: array_combine(): Both parameters should have an equal number of elements in

    [Plugin] IPMI for unRAID 6.1+

    in Plugin Support

    Posted

    This is what I get. Its the SuperMicro board in my signature.

     

    root@unRAID1:~# /usr/bin/ipmitool -vc sdr
Running Get PICMG Properties my_addr 0x20, transit 0, target 0
Error Response 0xc1 from Get PICMG Properities
No PICMG Extenstion discovered
CPU Temp,33,degrees C,ok,3.1,Processor,Temperature,40.000,-4.000,89.000,100.000,100.000,95.000,0.000,0.000,0.000,-128.000,127.000
System Temp,33,degrees C,ok,7.1,System Board,Temperature,30.000,-4.000,74.000,90.000,85.000,80.000,-9.000,-7.000,-5.000,-128.000,127.000
Peripheral Temp,38,degrees C,ok,7.2,System Board,Temperature,30.000,-4.000,74.000,90.000,85.000,80.000,-9.000,-7.000,-5.000,-128.000,127.000
PCH Temp,45,degrees C,ok,7.3,System Board,Temperature,25.000,-4.000,67.000,100.000,95.000,90.000,-11.000,-8.000,-5.000,-128.000,127.000
VRM Temp,37,degrees C,ok,8.1,Memory Module,Temperature,25.000,-4.000,74.000,105.000,100.000,95.000,-9.000,-7.000,-5.000,-128.000,127.000
DIMMA1 Temp,29,degrees C,ok,32.64,Memory Device,Temperature,30.000,168.000,206.000,90.000,85.000,80.000,1.000,2.000,4.000,0.000,255.000
DIMMA2 Temp,31,degrees C,ok,32.65,Memory Device,Temperature,30.000,168.000,206.000,90.000,85.000,80.000,1.000,2.000,4.000,0.000,255.000
DIMMB1 Temp,29,degrees C,ok,32.68,Memory Device,Temperature,30.000,168.000,206.000,90.000,85.000,80.000,1.000,2.000,4.000,0.000,255.000
DIMMB2 Temp,30,degrees C,ok,32.69,Memory Device,Temperature,30.000,168.000,206.000,90.000,85.000,80.000,1.000,2.000,4.000,0.000,255.000
FAN1,900,RPM,ok,29.1,Fan Device,Fan,12800.000,2000.000,17000.000,25500.000,25400.000,25300.000,300.000,500.000,700.000,0.000,25500.000
FAN2,1000,RPM,ok,29.2,Fan Device,Fan,12800.000,2000.000,17000.000,25500.000,25400.000,25300.000,300.000,500.000,700.000,0.000,25500.000
FAN3,,,ns,29.3,Fan Device,Fan,12800.000,2000.000,17000.000,25500.000,25400.000,25300.000,300.000,500.000,700.000,0.000,25500.000
FAN4,,,ns,29.4,Fan Device,Fan,12800.000,2000.000,17000.000,25500.000,25400.000,25300.000,300.000,500.000,700.000,0.000,25500.000
FANA,1400,RPM,ok,29.5,Fan Device,Fan,12800.000,2000.000,17000.000,25500.000,25400.000,25300.000,300.000,500.000,700.000,0.000,25500.000
Vcpu,1.818,Volts,ok,3.2,Processor,Voltage,1.800,1.620,1.944,2.106,2.088,1.899,1.242,1.260,1.395,0.171,2.466
VDIMM,1.320,Volts,ok,32.1,Memory Device,Voltage,1.425,1.201,1.642,1.747,1.719,1.642,1.096,1.124,1.201,0.137,1.922
12V,12,Volts,ok,7.17,System Board,Voltage,12.000,10.776,12.918,13.224,13.224,12.918,10.164,10.521,10.776,0.219,13.224
5VCC,4.969,Volts,ok,7.33,System Board,Voltage,5.000,4.473,5.372,5.589,5.527,5.372,4.225,4.380,4.473,0.071,7.976
3.3VCC,3.314,Volts,ok,7.32,System Board,Voltage,3.299,2.969,3.554,3.689,3.659,3.554,2.804,2.894,2.969,0.179,4.004
VBAT,3.045,Volts,ok,7.18,System Board,Voltage,3.000,2.595,3.495,3.690,3.600,3.495,2.400,2.490,2.595,0.045,3.870
AVCC,3.314,Volts,ok,7.36,System Board,Voltage,3.299,2.594,3.494,3.689,3.599,3.494,2.399,2.489,2.594,0.164,3.989
VSB,3.239,Volts,ok,7.35,System Board,Voltage,3.299,2.594,3.494,3.689,3.599,3.494,2.399,2.489,2.594,0.149,3.974
Chassis Intru,AAh,ok,23.1,
root@unRAID1:~#

    Plex: Guide to Moving Transcoding to RAM

    in Docker Containers

    Posted

    Its depending on what Plex container you are using if you are able of doing it or not.

     

    I know that if you are using Linuxserver.io there is a possibility to do this since you can specify what version to download.

     

    Edit the container, enable Advanced View, look for the Variable Name: Version and set the Variable Value: to the version you like. You can find the different versions with release notes on the Plex download page.

    Plex_version.png.103c19c4eea6b97b8f367fdccdee72ba.png

    [Support] Linuxserver.io - Plex Media Server

    in Docker Containers

    Posted

    So for the past week or so I've been having some issues with Plex buffering a lot lately.  This is something that has not happened before in or out of network.  The devices having issues are my Vizio and Samsung smart TV's, which have the Plex app.  Both connected via wire.  I went on to my UnRaid docker and checked for updates, and it stated it had the latest.  I forced it to update, and I noticed that the container ID changed.

     

    Then I went to the Plex WebGui, settings, server, and I noticed it states

    Version 0.9.15.2! An update is available. Please install manually.
      How do I go about updating manually?

    Restart the container to update. Currently version 0.9.15.3 is the latest PlexPass release.

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    in Docker Containers

    Posted

    Well, let’s hope that some developer excepts the challenge.

     

    I am running CrashPlan in an Ubuntu VM and that works fine but there is still a lot of work to get it working in a container and there is no guarantee that an update to a new version doesn’t require some work to get it working again depending on what changes CrashPlan actually implements.

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    in Docker Containers

    Posted

    Just a clarification about these two containers, they are actually both version 4.4.1 but as soon as the CrashPlan container starts and connects to CrashPlan it will get updated to the latest version that is 4.5.2.

     

    If you just wait until the update of the CrashPlan container is done you will be able to connect with CrashPlan Desktop container (still on version 4.1.1). Be a bit patient, it might take 15 minutes or so.

     

    To get the CrashPlan Desktop container to auto update is probably not as easy since this this is most likely a subset of the CrashPlan app (that contains both the server and the client) so it’s probably a lot of manual work to strip out the code and adopting it for use with the CrashPlan Desktop container.

     

    One possible solution might be a new Container containing both the server and client that could replace these two containers. With some luck it might be easier to have that configuration to auto update without any interaction from the maintainer of the container.

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    in Docker Containers

    Posted

    Are you using Disk shares since you are using 

    /mnt/disk1/

    as your mount point? If you are using User shares it should be 

    /mnt/user/

     

    Regardless of this, if there is a share on disk1 you should be able to see it. If you go to Shares (using the unRAID GUI) your share should be visible there and you can use View to verify that the share really is located on the disk you believe it should be.

     

    I checked to rights for some of my shares and they have Owner:nobody, Group:users, permissions:0777

     

    Regarding the difficulties with your Windows client connecting to the CrashPlan container I believe that you should check your settings one more time. The most important parts are on page 9 and 10 in the Guide.

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    in Docker Containers

    Posted

    The article you refer to is related to on how to use CrashPlan on your server and use CrashPlan (as a client) on a computer to monitor and configure CrashPlan on the server.

     

    This is not applicable if you intend to use the CrashPlan container and the CrashPlan Desktop container.

     

    If you have the CrashPlan container and the CrashPlan Desktop containers installed on your server, you should connect with a Remote Desktop Client to the CrashPlan Desktop container to manage the CrashPlan container.

     

    Have a look on the guide in my signature.

     

    Yes I know what the article is for, I'm literate. I tried the crashplan desktop container and when I connected to the crashplan container on the same machine, the crashplan service would crash. Every single time. Which I had stated already.

     

    I used the tutorial I had linked to connect the crashplan on my unraid box using the crashplan UI on my desktop to configure the former.

    I do apologise but I might not understand your configuration correctly. What I recommend is to use the CrashPlan container and the CrashPlan Desktop container only, just to get you up and running.

     

    If you later would like to use the (CrashPlan) client on your PC instead of the CrashPlan Desktop container that will also work. When you say its crashing, can you post a screen dump so that we can have a look on it?

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    in Docker Containers

    Posted

    The article you refer to is related to on how to use CrashPlan on your server and use CrashPlan (as a client) on a computer to monitor and configure CrashPlan on the server.

     

    This is not applicable if you intend to use the CrashPlan container and the CrashPlan Desktop container.

     

    If you have the CrashPlan container and the CrashPlan Desktop containers installed on your server, you should connect with a Remote Desktop Client to the CrashPlan Desktop container to manage the CrashPlan container.

     

    Have a look on the guide in my signature.

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    in Docker Containers

    Posted

    I am not an expert on these log files but I don’t see any errors. It just looks different since you probably never been able to login and configure CrashPlan.

     

    You should be able to get the CrashPlan Desktop container started and to connect to it with Remote Desktop regardless if the CrashPlan container is running or not. You should be able to access the login screen and get to the CrashPlan splash screen.

    xrdp.png.7a140891a37193ff75746272d50214ee.png

    CP_splash.png.76cc8e0767f61aa282704ff72a186d31.png

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    in Docker Containers

    Posted

    If you are on Windows use Microsoft Remote Desktop client to connect to the CrashPlan Desktop container. You only need to enter the IP to your server. It will connect on port 3389 using the Remote Desktop Protocol.

     

    You can use other clients as well but there might be some configuration work to do. The client you use must be able to connect to the remote desktop server (xrdp) that is used for the CrashPlan Desktop container.

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    in Docker Containers

    Posted

    There are changes needed both on your Windows client as well as the configuration on unRAID. Check the Guide in my signature on page 9.

     

    The 4.5.2 client should be able to connect to the Docker container 4.4.1

     

    A good start (and a lot easier) is to use the CrashPlan container with the CrashPlan Desktop container just to get it running and later switch to the Windows client if you like that better.

    [CONTAINER] CrashPlan & CrashPlan-Desktop

    in Docker Containers

    Posted

    Remote desktop client failing, CrashPlan Desktop container and Mac.

     

    Regarding the CrashPlan Desktop container and Mac I have got that question before but I was not able to solve that (see a few posts up #614)

     

    At least there seems to be a problem related to using Microsoft Remote Desktop client on Mac connecting to the xrdp server used in the CrashPlan Desktop container.

    http://social.technet.microsoft.com/Forums/en-US/414827ef-15b8-444c-99b3-2d9ed8286850/mac-rdp-client-to-linux-xrdp-issues?forum=winRDc

     

    I don’t have any solution other than let Google find another remote desktop client that can connect to the xrdp server  ???

×
×
  • Create New...