Any solution ??
ssh - last step !
@alhatmy said:
keeps asking for the password …
On the slave, stop ssh and run it in a console:
sudo service ssh stop
sudo sshd -D -d
With that console open, try connecting via ssh from the master. Post the output back here so we can debug it.
fixed … thanx
first - set right permissions to .ssh dirs
second - edit mounts on slave - they must be exact as on master
please provide your email for “Paypal” as the main link isn’t working in github / or fix it …
Q: all transcoding goes to slave server - is this also a mistake? almsot all …
i want it to be balanced …
@alhatmy said:
please provide your email for “Paypal” as the main link isn’t working in github / or fix it …
The Paypal link in the README is accurate (at the bottom).
Q: all transcoding goes to slave server - is this also a mistake? almsot all …
i want it to be balanced …
You need to add the master as a transcode target using prt add.
@wnielson said:
@alhatmy said:
please provide your email for “Paypal” as the main link isn’t working in github / or fix it …The Paypal link in the README is accurate (at the bottom).
Q: all transcoding goes to slave server - is this also a mistake? almsot all …
i want it to be balanced …You need to add the
masteras a transcode target usingprt add.
do you mean, use “sudo -u plex -H prt add_host” in the master (and to add the master ip) ??
@alhatmy said:
do you mean, use “sudo -u plex -H prt add_host” in the master (and to add the master ip) ??
Yup, just like you did to add the slave before.
@wnielson said:
@CB2131 said:
Ok so that did the trick. Seems to be passing transcoding from the master to the slave. So given the Real-Time Load-Based Balancing…this will automatically shift jobs between the Master <------> Slaves based on CPU load?If One slave exists, does it pass jobs back to the master when CPU load hit a particular %?
By default, the
masteris not considered as a transcodeslave. If you want themasterto be considered aslaveas well, then runprt add_hostand use the loopback address127.0.0.1.
still 100% goes to slave …
hmmm, will try more …
whats wrong ?
pic: http://imgur.com/egtwSO3
hopes it’ll work … thanx a lot !
@liviy said:
WARNING ABOUT UPGRADING TO PMS 1.1 RELEASE
At first glance it would appear the coders of PMS have changed things AGAIN and it breaks PRT so if you’re using PRT I’d suggest you don’t upgrade until we can confirm whether it just broke PRT on my system or if it’s a common problem.Cheers,
Liviy
Also borked it for me. I’m sure a fix is on the way.
@LightSpeedTaco said:
Also borked it for me. I’m sure a fix is on the way.
Newest commit supports PMS version 1.1. Please report any issues you may encounter.
2 questions please
1- what is the issue with the below pic ? its still not working for both …
pic: http://imgur.com/egtwSO3
2- how to update Plex remote transcoder ? is it auto ?
@alhatmy said:
1- what is the issue with the below pic ? its still not working for both …
pic: http://imgur.com/egtwSO3
Does this work on the master?
sudo -u plex -H ssh 127.0.0.1
2- how to update Plex remote transcoder ? is it auto ?
No, it isn’t auto. You have to follow the same process you did for install. We’re working on adding documentation, so stay tuned.
1- its wokring for “Slave” only … thats my current problem (tried to add the real ip / 127) didn’t work …
2- thanx !
@alhatmy said:
1- its wokring for “Slave” only … thats my current problem (tried to add the real ip / 127) didn’t work …
I know, but I’m trying to find out if you can ssh from the master to the master. That might seem counter intuitive, but the master is treated just like a slave if it has been added as a transcode target. Therefore, keyless ssh from the master to the master must work. Does this work on the master?
sudo su plex
ssh 127.0.0.1
If that works, then the problem is coming from somewhere else.
Mine was working fine with the master ip. I added the real ip 192.168.2.2 instead of 127.0.0.1.
I read through all 18 pages of comments in this thread, scoured the forums, reddit, and github, and didn’t see anyone posting any scripts, or links to scripts, to dynamically spin up and down digitalocean instances.
Since it appears you would just have to script the installation instructions a tad (ie. add/remove hosts, edit exports, restart nfs) I’m guessing someone has already done this and I missed it. Does anyone have a digitalocean script that does this?
If not, I could take a stab at it but I am fuzzy on where PRT detects load and could call a script if a certain threshold is passed. In theory I would like to have one nearly unused instance running at all times as a buffer and allow a time for new instances to spin up and handle new load.
I’m also thinking we could use the floating ip / load balancing functionality digital ocean offers. But I haven’t really thought that through very much yet.
Oh, I almost forgot, the software works really really well and setting up the server went really smoothly. Great software, great instructions. Thanks!
I have a question that may have been answered already, but just in case it hasn’t…
I currently am running a server cluster out of old PC parts in Linux for my computational sciences lab…5 old Core 2 Duo’s nothing fancy. It greatly increases the speed of my figures being outputted.
Anyhow to the question, I would like to know if your Remote Transcoder will work on my clustered server system…in theory this should increase the transcoding power of Plex by leaps and bounds by allowing for distribution of transcode work load.
Is this something that is possible?
@dan.franks@gmail.com said:
Oh, I almost forgot, the software works really really well and setting up the server went really smoothly. Great software, great instructions. Thanks!
Awesome, glad you got it working easily! As to your comment about Digital Ocean, I know another user has been working on this here.
