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.
ich hatte gestern das gleiche problem, ich bemerkte es, weil beim kompilieren, da vdr vom plugin streamdev nichts sagte, kein Auflisten der plugins etc.
nur beim vdr --help gab vdr einen Fehler heraus "undefined symbol @...."
und die Hilfe vom streamdev wurde auch nicht angezeigt.
ich habe meine libvdr-streamdev, gelöscht und nochmals neu angefangen.
Sorry wenn ich nicht helfen konnte.
Hallo,
gibt dir vdr --help ein undefiniertes Zeichen von streamdev aus?
wie hast du das streamdev plugin im Ordner /PLUGINS/src/ benannt?
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.
sorry rofafor,
for my post, your satip plugin works very very fine...
Excuse me please!
i have build my cubietruck3 with a new power supply and i have use the short sata connection for my 3,5 hdd.
And now, it works, i will test and will write down the informations about this platform and how it works on productivity WAF (Womens acc....)
@all, they have a octopus net box
my box will get on work very hot, it feels like little bit to hot, has anyone the same problem?
I have no problems, but i will check before it give a problem.
thanks a lot for supporting and help!!
I also had strange problems with my Cubietruck while I was using a 500mA power supply. All sorts of strange problems, sometimes when compiling, sometimes runtime. So the system seems to behave a bit odd when underpowered.
Thanks for this answer!!
I have a powersupply in use with 12 volt and 4 Ampere.... and it dosent work.. for the 2,5 hdd i have in use 5 volts with 10 ampere....
it is really freaky.
Very freaky... situation Sorry, but it works... i see all is clear and fine on my cubietruck3 master vdr....
(i tell us a really! true story. )
i believe i have a problem with the cubietruck3 and the adapter for 3,5 Hdd.
it is also possible that it is a power component problem, because i have build the cubietruck "back to the roots", equals without the 3,5 HDD adapter and what happens?
i look tv on all on my vdr clients... ?
Sorry, but i can not believe it, my self ...
I'm running the satip plugin on arm platform (RaspberryPi) and it's rock stable. So your issue is not related to arm
Can you tell how does it works, with which options did you have compiled the vdr ??
I do have both v1 and v2 OctopusNet and no such problems detected here.
Okay thats is a good point for me, that i have a mistake in my work, comiling and anything else.
Couldn't it be armv7 related?
Did you use the compiler option "-fsigned-char" for CFLAGS and CXXFLAGS?
Nice to hear, i will check out for this.
Funktioniert's denn nun auf einer Intel Kiste?
Nein, weil die Intel kiste noch nicht fertig ist im Wiederaufbau.
Yes, of course vlc or anything else working fine.
okay,
ZitatWhy do u want to send back the gss, if it was working 7 days?
i have see many problems in the logs, "fix the Firmware" and after i read the threads here about the satip plugin, i read the octopus net devices are the best for this.
My Tests are okay with the gss box on arm hardware, but i have sometimes problem on work because the box restartet if the box has not understood that are only 2 LNBs are activatet.
I have configured on the bad internal website of gss.box and what i dont understand, the box are very hot on work with only 2 LNBs.
in addition i want to buy a device that are in the development, the inverto and gss satip boxes are for the manufactor okay, the development ends here.
My goal was to build a vdr network, not on intel hardware components with high power consumption, i want to build a vdr network with power saving arm components.
The vdr client with bananapi are very nice and useful and after that i want to change my intel master vdr with 200 watt power consumption, to an cubietruck with only 8 watt :-).
it is possible, that i come back with new infos, if i have my build on the intel platform ready.
But one sentence, is allowed, why does the gss.box never bring up the glibc problem, but the octopus net does?
Where is the problem?
my last chance: i will test my configuration on a intel platform.
I will report back if i am ready with build.
I have tested the my vdr with the GSS.box 7 days, with 24 hours and now i have buy a octopus Net v2 dvbs2-4 and the vdr will break down.
i dont know why but it is confused.
i will send the octopus and gss back to the seller... it doesnt work for me.
Hello again,
i have upload the debug on pastebin for you
The vdr stops with this answer:
/usr/local/bin/vdr -l 3 6 -P"satip -t 0xFFFF"
*** glibc detected *** /usr/local/bin/vdr: malloc(): memory corruption: 0xb1f76d58 ***
Aborted
Thank you for watching and the support.
If you think thats not your satip plugin, then tell me please
Jan 21 23:20:55 nslr001 vdr: [2523] found 28 locales in /usr/local/share/locale
Jan 21 23:20:55 nslr001 vdr: [2523] registered source parameters for 'A - ATSC'
Jan 21 23:20:55 nslr001 vdr: [2523] registered source parameters for 'C - DVB-C'
Jan 21 23:20:55 nslr001 vdr: [2523] registered source parameters for 'S - DVB-S'
Jan 21 23:20:55 nslr001 vdr: [2523] registered source parameters for 'T - DVB-T'
Jan 21 23:20:55 nslr001 vdr: [2526] epg data reader thread started (pid=2523, tid=2526, prio=high)
Jan 21 23:20:55 nslr001 vdr: [2526] reading EPG data from /var/cache/vdr/epg.data
Jan 21 23:20:55 nslr001 vdr: [2525] video directory scanner thread started (pid=2523, tid=2525, prio=high)
Jan 21 23:20:55 nslr001 vdr: [2526] epg data reader thread ended (pid=2523, tid=2526)
Jan 21 23:20:55 nslr001 vdr: [2524] video directory scanner thread started (pid=2523, tid=2524, prio=high)
Jan 21 23:20:55 nslr001 vdr: [2523] cTimeMs: using monotonic clock (resolution is 1 ns)
Jan 21 23:20:55 nslr001 vdr: [2528] SATIP discover thread started (pid=2523, tid=2528, prio=high)
Jan 21 23:20:55 nslr001 vdr: [2527] SATIP poller thread started (pid=2523, tid=2527, prio=high)
Jan 21 23:20:55 nslr001 vdr: [2523] new device number 1
Jan 21 23:20:55 nslr001 vdr: [2523] assuming manual start of VDR
Jan 21 23:20:55 nslr001 vdr: [2523] remote control KBD - learning keys
Jan 21 23:20:55 nslr001 vdr: [2531] section handler thread started (pid=2523, tid=2531, prio=low)
Jan 21 23:20:55 nslr001 vdr: [2530] SATIP#0 section handler thread started (pid=2523, tid=2530, prio=high)
Jan 21 23:20:55 nslr001 vdr: [2532] KBD remote control thread started (pid=2523, tid=2532, prio=high)
Jan 21 23:20:55 nslr001 vdr: [2529] SATIP#0 tuner thread started (pid=2523, tid=2529, prio=high)
Jan 21 23:20:55 nslr001 vdr: [2525] video directory scanner thread ended (pid=2523, tid=2525)
Jan 21 23:20:57 nslr001 vdr: [2524] video directory scanner thread ended (pid=2523, tid=2524)
Jan 21 23:22:26 nslr001 vdr: [2523] OSD size changed to 720x480 @ 1
Jan 21 22:42:52 nslr001 vdr: [1883] SATIP#0 tuner thread started (pid=1877, tid=1883, prio=high)
Jan 21 22:42:52 nslr001 vdr: [1882] SATIP discover thread started (pid=1877, tid=1882, prio=high)
Jan 21 22:42:52 nslr001 vdr: [1884] SATIP#0 section handler thread started (pid=1877, tid=1884, prio=high)
Jan 21 22:42:52 nslr001 vdr: [1885] section handler thread started (pid=1877, tid=1885, prio=low)
Hello rofafor,
excuse me for my silly art, I do not debug every day
i hope it helps.
Hello rofator,
i have test it with gdb...
(gdb) next
117 bool cCondVar::TimedWait(cMutex &Mutex, int TimeoutMs)
(gdb) next
[New Thread 0xb60f1460 (LWP 1238)]
Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb50f1460 (LWP 1214)]
0xb6c04f96 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
(gdb) backtrace
#0 0xb6c04f96 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0xb6c12f8a in raise () from /lib/arm-linux-gnueabihf/libc.so.6
#2 0xb6c15428 in abort () from /lib/arm-linux-gnueabihf/libc.so.6
#3 0xb6c3b10e in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
#4 0xb6c3b10e in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
it is helpful?
yes of course, for your thought of the error that i have:
I have start the vdr, without any plugins, only start with satip plugin, and the same error comes up.
vdr: malloc.c:3096: sYSMALLOc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) 
((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (struct malloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t))) - 1))) && ((old_top)->size & 0x1) && ((unsigned long)old_end & pagemask) == 0)' failed.
Aborted
it is possible to make a backtrace with the vdr ? Sorry you dont need to teach me, but i have a little problems to generate a correct backtrace.
