Jump to content

TUMS

Members
  • Posts

    337
  • Joined

Posts posted by TUMS

  1. If you install the needo plex docker it automatically works with plex pass. That's what i'm running....

    needo isn't around much these days. linuxserver.io is probably most recommended and support plexpass and betas.

     

    Maybe so but he's definitely still updating it.  In fact I just got an update today to 1.4.1.3662

     

    That is the nature of the docker "update" by restarting it. It goes out and gets the latest build from Plex. Needo hasn't touched the docker container code in months.

     

    The implication is that the docker code needs to be touched.

    Is there something about Needo's docker code that needs updating?

     

    Good question.

    Probably nothing wrong with Needo's code.  The thing is that if/when any one ever has a problem with Plex and they are running the container from Needo, the first troubleshooting suggestion is to switch to linuxserver or binhex, as those two still actively support their containers whereas everything from Needo is basically without any author/maintainer support at all

     

    Thanks squid.  I'll probably leave it alone for now.  I've had no problems with it.

  2. If you install the needo plex docker it automatically works with plex pass. That's what i'm running....

    needo isn't around much these days. linuxserver.io is probably most recommended and support plexpass and betas.

     

    Maybe so but he's definitely still updating it.  In fact I just got an update today to 1.4.1.3662

     

    That is the nature of the docker "update" by restarting it. It goes out and gets the latest build from Plex. Needo hasn't touched the docker container code in months.

     

    The implication is that the docker code needs to be touched.

    Is there something about Needo's docker code that needs updating?

     

    Good question.

  3. That is the nature of the docker "update" by restarting it. It goes out and gets the latest build from Plex. Needo hasn't touched the docker container code in months.

     

    Thanks.  I should probably try and switch over to linuxserver.io plex docker soon then... Is there a way to switch and have it still recognize my needo created plex library or do I have to delete everything?

     

    edit...nevermind, I found it

    http://lime-technology.com/forum/index.php?topic=40937.msg445818#msg445818

  4. If you install the needo plex docker it automatically works with plex pass. That's what i'm running....

    needo isn't around much these days. linuxserver.io is probably most recommended and support plexpass and betas.

     

    Maybe so but he's definitely still updating it.  In fact I just got an update today to 1.4.1.3662

  5. Interesting but hopefully just a coincidence.  I'm pretty sure i've swapped around cables in the past before.  One thing is APC cables have part numbers on them so you can definitely run the numbers before using to make sure they're compatible with the ups you are using.

  6. I've got literally a pile of APC cables from all the ups's i've bought over the years.  And on most of the newer higher end APC models you can just use any old generic USB cable (one with a normal end on it as opposed to the apc rj45 usb) It doesn't have to specifically be a APC usb cable.

  7. I'm having the same type of issues with my wdtv live box and private shares.  And activating ntlm in the config didn't help either.  I'm probably going to have to go back to 6.2.4 till all this is resolved...

     

    Feel free to enable the syslog/log level settings and see what the syslog says about why your connection is failing.

    It may give some insight.

     

    Thanks, good idea!  I'll try and look at this tomorrow when I get some time.

  8. Upgraded nicely, I was looking forward to be rid of my build of apcupsd but modbus is still disabled in this update, can you enable it please.

     

    All recent mid to high end APC UPS implement it (smart-ups), and it's the only way to get any useful data from them, classic USB just gives runtime.

    I don't mind using my own build but since I have not control over what the php part is doing and I'm not sure how you configured your build it still feels iffy...

     

    Thanks for all the hard work.

     

    Modbus with a serial cable works now, but yeah it would be nice to be able to use modbus with a USB cable.

  9. I just started getting these the other day in my log file. Otherwise system seems to be functioning fine.  Anyone have any clues as to what this is? Do you guys think this is anything to worry about?

     

    Actually I just introduced a new drive (hgst he8) into my array the other day and that was about the time I started seeing these warnings in my log.

     

    Thank you!

     

     

    Feb 1 06:03:06 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:09 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:09 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:11 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:11 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:11 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:11 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:11 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:19 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:19 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:19 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:19 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:19 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:23 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:23 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:23 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 06:03:23 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 07:15:46 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 07:15:46 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 07:15:46 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

    Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

  10. For gaming i'd probably choose a single e5 with a high clock speed. Probably a Xeon E5-1650v4

    Stock @3.6ghz -- turbo 3.8ghz.

    Passmark 14364

     

    https://www.newegg.com/Product/Product.aspx?Item=274-000A-00083&cm_re=e5_1650_v4-_-274-000A-00083-_-Product

     

    https://www.newegg.com/Product/Product.aspx?Item=N82E16813182927&cm_re=x10srl-f-_-13-182-927-_-Product

     

    Don't know if it would handle 2 people gaming at the same time plus HD plex streaming though.... Guess it would depend on the games being played.

     

     

  11. At the moment, I am testing some drives and using an Adaptec maxCache™ 5805ZQ RAID controller, the drives are configured on the card as JBOD and the card is connected to the backplane. So not sure if its the Adaptec card that is not passing through the temps or what?

     

    Yeah it's either your raid controller or your new case/backplane.  I use IBM M1015 cards with norco 4224 backplanes and can see drive temps no problem so somethings not right with your setup.

×
×
  • Create New...