693 replies to this topic

[delavega]

 

root@vusolo2:~#  telnet 192.168.1.227 8002

HTTP/1.0 400 Bad request: ClientSocket: peer connection timeout

Content-Type: text/html

Connection: close

 

Connection closed by foreign host

 

netstat -lptn

tcp        0      0 :::8002                 :::*                    LISTEN      405/streamproxy

tcp        0      0 :::8003                 :::*                    LISTEN      405/streamproxy

 

[Erik Slagter]

HTTP/1.0 400 Bad request: ClientSocket: peer connection timeout

Thx, this is an error message I can check.

[колбаскин]

Hi all

In last OpenWebif not work - Enable Authentication for streaming  - all who want watch tv!!!

And update OpenPli remove plugin TransCodingSetup

Why???

 

How to Fix authorization and transcoding?

[WanWizard]

Read back before asking questions, that would help a lot.

 

The plugin is removed because it allowed you to change settings that crashed the transcoding engine. For now, use the config file. A new plugin is being worked on.

 

We're (Erik that is) are completely rewriting the stream and transcoding handling, to make it generic for all boxes, and to make it a lot more stable than the VU junk.

 

But that doesn't happen overnight. If you can't live with an instable situation every now and then, don't update to the bleeding edge, but only update when you know it is stable (and if not, revert to your backup).

[Erik Slagter]

With the latest update authentication DOES work although I cannot guarantee that the web interface completely supports it this way.

[колбаскин]

It is a pity that you solved for all as it will be better and removed a plug-in.
With lack of authorization on a stream? Why it doesn't work?

[Erik Slagter]

HTTP/1.0 400 Bad request: ClientSocket: peer connection timeout

Thx, this is an error message I can check.

This message means no http line was received within 5 seconds after opening the connection. Which is to be expected when you start up a telnet connection, so this is not a real error.

Can please do the following:

-> reboot the receiver (necessary for a clean dmesg output)
killall streamproxy
streamproxy -f

the streamproxy will run in the foreground now and log some things.

Now fire up the transcoding client device and after a complete run, copy all of the logging and paste it here. Also paste the output of dmesg please.

I am very curious why it works over here and not on your receiver.

Edited by Erik Slagter, 13 April 2014 - 14:28.

[Erik Slagter]

It is a pity that you solved for all as it will be better and removed a plug-in.
With lack of authorization on a stream? Why it doesn't work?

If you read some of the pages of this topic, you will have all of your answers.

[колбаскин]

Enable Authentication for streamin work ?

[Erik Slagter]

It is a pity that you solved for all as it will be better and removed a plug-in.
With lack of authorization on a stream? Why it doesn't work?

If you read some of the pages of this topic, you will have all of your answers.

Edited by Erik Slagter, 13 April 2014 - 14:29.

[delavega]

 

HTTP/1.0 400 Bad request: ClientSocket: peer connection timeout

Thx, this is an error message I can check.

 

This message means no http line was received within 5 seconds after opening the connection. Which is to be expected when you start up a telnet connection, so this is not a real error.

Can please do the following:

-> reboot the receiver (necessary for a clean dmesg output)
killall streamproxy
streamproxy -f

the streamproxy will run in the foreground now and log some things.

Now fire up the transcoding client device and after a complete run, copy all of the logging and paste it here. Also paste the output of dmesg please.

I am very curious why it works over here and not on your receiver.

well its working now lol looks like killall streamproxy fixed it

[колбаскин]

I from Ukraine, many use image in Russia
Nobody explains to us why you so made or why something ceased to work for us

Everything worked for me while you didn't remove a plug-in

[delavega]

the solo2 totally froze now

 

root@vusolo2:~# killall streamproxy

root@vusolo2:~# streamproxy -f

> 8002 -> transcode,5

> 8003 -> transcode,6

streamproxy: accept new connection on port 8002, default action: transcode, fd 7

ClientSocket: no authorisation received from client

streamproxy: accept new connection on port 8002, default action: transcode, fd 7

ClientSocket: authentication: root,openpli

ClientSocket: header[Authorization]: "Basic cm9vdDp4Ym"

ClientSocket: header[Connection]: "close"

ClientSocket: header[Host]: "vusolo2.local:8002"

ClientSocket: header[Icy-MetaData]: "1"

ClientSocket: header[Range]: "bytes=0-"

ClientSocket: header[User-Agent]: "VLC/2.1.1 LibVLC/2.1.1"

ClientSocket: url: /1:0:1:2020:430:1:C00000:0:0:0:

ClientSocket: parameter[] = "/1:0:1:2020:430:1:C00000:0:0:0:"

Service: create service: 1:0:1:2020:430:1:C00000:0:0:0

ClientSocket: default live request

ClientSocket: transcoding service

LiveTranscoding: 1:0:1:2020:430:1:C00000:0:0:0

WebifRequest: send request to webif: "GET /web/stream?StreamService=1:0:1:2020:430:1:C00000:0:0:0 HTTP/1.0

Authorization: Basic cm9vdDp4Ym

 

"

LiveTranscoding: pid[audio] = 6c

LiveTranscoding: pid[audio-1] = 6d

LiveTranscoding: pid[pat] = 0

LiveTranscoding: pid[pcr] = 19a

LiveTranscoding: pid[pmt] = 191

LiveTranscoding: pid[subtitle] = 1b9

LiveTranscoding: pid[subtitle-1] = 1b9

LiveTranscoding: pid[text] = 1b9

LiveTranscoding: pid[video] = 19a

Encoder: open encoder /dev/bcm_enc0

Encoder::setprop: cannot open property /proc/stb/encoder/0/display_format, system error: No such file or directory

Encoder::setprop: cannot open property /proc/stb/encoder/0/profile, system error: No such file or directory

Encoder::setprop: cannot open property /proc/stb/encoder/0/level, system error: No such file or directory

Encoder::setprop: cannot open property /proc/stb/encoder/0/gop_frameb, system error: No such file or directory

LiveTranscoding: encoder pid[audio] = 6c, system error: No such file or directory

LiveTranscoding: encoder pid[pat] = 0, system error: No such file or directory

LiveTranscoding: encoder pid[pmt] = 191, system error: No such file or directory

LiveTranscoding: encoder pid[video] = 19a, system error: No such file or directory

Demuxer: ioctl demuxer ADD PID: audio -> 0x6c, system error: No such file or directory

Demuxer: ioctl demuxer ADD PID: pmt -> 0x191, system error: No such file or directory

Demuxer: ioctl demuxer ADD PID: video -> 0x19a, system error: No such file or directory

LiveTranscoding: state init -> starting, system error: No such file or directory

LiveTranscoding: state starting -> running, system error: No such file or directory

Edited by taboune, 13 April 2014 - 14:39.

[Erik Slagter]

It is a pity that you solved for all as it will be better and removed a plug-in.
With lack of authorization on a stream? Why it doesn't work?

If you read some of the pages of this topic, you will have all of your answers.

Edited by Erik Slagter, 13 April 2014 - 14:37.

[Erik Slagter]

Encoder::setprop: cannot open property /proc/stb/encoder/0/display_format, system error: No such file or directory
Encoder::setprop: cannot open property /proc/stb/encoder/0/profile, system error: No such file or directory
Encoder::setprop: cannot open property /proc/stb/encoder/0/level, system error: No such file or directory
Encoder::setprop: cannot open property /proc/stb/encoder/0/gop_frameb, system error: No such file or directory

These are all errors.

Are you on a solo2 or on a duo2?

Can you please do this?

ls /proc/stb/encoder
ls /proc/stb/encoder/0
ls /proc/stb/encoder/1

The only way I can explain this could happen is that the transcoding engine already crashed at this point. The dmesg will show a lot of barf in that case (including null pointer/page references etc.)

[delavega]

openpli 4 vusolo2





vusolo2 login: root
Password:xxxxx

root@vusolo2:~# ls /proc/stb/encoder
0               enable          enable_choices
root@vusolo2:~# ls /proc/stb/encoder/0
audio_pid          demux              framerate_choices  pmt_pid
bitrate            framerate          pcr_pid            video_pid
root@vusolo2:~# ls /proc/stb/encoder/1
ls: /proc/stb/encoder/1: No such file or directory
 

[Erik Slagter]

The solo2 totally froze now

Yeah, that's the marvellous quality of the drivers of VU+.

Somehow you're doing "something" that upsets the drivers up to a point they stop trancoding and also crash the kernel at some point

[Erik Slagter]

I did not test on the solo2 (yet). I guess the proc files are being written with values that upset the driver (but are good on vuduo2). I will test (and try to come with a workaround) for the solo2 one of the next days.

Edited by Erik Slagter, 13 April 2014 - 14:46.

[колбаскин]

What to do with Enable Authentication for streamin on OpenWebif?

How to fix it?

[Erik Slagter]

But it was working with the same settings ahhhhhhhhhhhh this is annoying

You can surely say that.

 

It appears that the solo2's driver is of even worse quality that we're used to on VU+ products.

 

This is what's going on:

 

When the streamproxy get's a request, it tries the encoders one-by-one to find a non-busy one. On the solo2 this will always be /dev/bcm_enc0, on the duo2 it can be either /dev/bcm_enc0 or /dev/bcm_enc1, depening whether the first is already being used.

 

Until today I had no exceptions for the solo2 and the duo2, both were treated the same. Which should be ok, solo2 has one encoder, duo2 has two and that's it. Also the duo2 has some extra encoding options, which would be tried to get set on the solo2 but fail (with a warning, you've seen it), no problem. The options would be set after opening the encoder device. That is only then we know which encoder is used, so which /proc/stb/encoder[0-1] directory to use.

 

It now appears the solo2 does not tolerate that. Anything you write (or read!) in this directory while the encoder is open, will crash (sigsegfault) the userspace application. So I made a workaround for the solo2 to only open /dev/bcm_enc0, to assume the encoder is always "0" and to set the bitrate (the only feasable option on the solo2) BEFORE the encoder is opened. That should prevent the crash. BUT in testing what model the streamproxy is running on, I used an access call (that is "open" without actually open the file, it only checks it's presence) on /dev/bcm_enc1 (which is not present on the solo2). Now to my amazing this also crashes! I have now made a workaround upon the workaround (scan the whole directory instead) and this seems to work.

 

So... I guess the solo2 now works again. Yes it's ugly. Try tomorrow.