Octopus Box has a ERROR and Stop Streaming >satip plugin?

  • Hello together,


    i have many hours check my setup before, i post here my little problem with the OctopusNet v2 DVBS2-4 with satip Plugin.


    My vdr server starts with this options:



    For information about my tv compliance:


    on the Octopus Net Box, i have only 2 Ports activ, 1 & 2 and 3 & 4 has not connected to the lnb.
    Because, i have at the moment not enough cable from satelite device.
    All clients are stream with the streamdev plugin, and all clients have the vdr version >2.0


    Now i will tell us my Problem.


    One Client is active and have i look RTLNitro over the satip plugin.
    No i will change my channels step by step, from rtlnitro to ZDF or WDR, or ProSieben and ist works for 2-4 channels, after that - i have no stream from the octopus net, because on the webpage from the octopus box i will read ERROR.
    After i restart the box, over the website, i will have directly a stream and a picture.


    This information, i can tell you about the vdr server:



    What have i done, before i have written my problem down?
    I have compiled the vdr 2.1.7 and download the version of satip plugin 1.02. (gz file).
    I have played with the sat plugins options,
    I have played with the sources.conf,
    i have checked and changed my cables from lnbs.
    i have compiled the satip plugin,


    Can anyone tell me, where is my problem.
    Why run the octopus box into that error?
    Is it not possible to use the octopus box without all active ports?


    Sorry, i hope it is not a really big mistake from me, for this little problem.

    Development: Cubietruck, Debian Wheezy with VDR 2.1.6
    Master : Back to the Root, Intel System
    Slave I : Bananapi, with Debian Wheezy and VDR 2.1.6
    Slave II : AMD Athlon II X2 3Ghz. 2GB Ram; Asus M4N7B Pro; Gforce 8300

  • OctopusNet's octoserve daemon is sometimes a bit unstable (happens more easily with latest firmware versions) and you can restart it for example via commands.conf:


    Code
    http://<octopus net ip>/reboot.lua?restart_octo
  • hello rofafor,


    thanks for the answer!!



    OctopusNet's octoserve daemon is sometimes to be a bit unstable (happens more easily with latest firmware versions) and you can restart it for example via commands.conf


    okay, i did not know this, but i can read the status from octopusnet box and reboot the box directly from server.! :) i have a chance....
    it is a problem from the box, thats correct?


    many thanks for the answer rofafor.

    Development: Cubietruck, Debian Wheezy with VDR 2.1.6
    Master : Back to the Root, Intel System
    Slave I : Bananapi, with Debian Wheezy and VDR 2.1.6
    Slave II : AMD Athlon II X2 3Ghz. 2GB Ram; Asus M4N7B Pro; Gforce 8300

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!