693 replies to this topic

[Erik Slagter]

Okay next step. "It doesn't work". You know the drill, I guess.

 

BTW the version I commited last night runs fine on my solo2.

Edited by Erik Slagter, 16 April 2014 - 19:04.

[delavega]

a clean flash again i guess :s

[SpaceRat]

I've just tried streamproxy on a friend's Duo²:

Doesn't work (VLC can't connect).
No messages in dmesg

Now for the funny part:

killall streamproxy
/usr/bin/streamproxy

DNGN

killall streamproxy
/usr/bin/streamproxy -f

-> streamproxy works

killall streamproxy
/usr/bin/streamproxy

-> streamproxy fails

killall streamproxy
/usr/bin/streamproxy

-> streamproxy still fails

killall streamproxy
/usr/bin/streamproxy -f

-> streamproxy works

So it's definitely a streamproxy background/foreground issue.

Edited by SpaceRat, 16 April 2014 - 23:01.

[delavega]

so im not crazy lol

[SpaceRat]

so im not crazy lol

Nah, not you ... but the bug is ...

How on earth do you manage a program to behave differently just because it is running in background?

[Erik Slagter]

a clean flash again i guess :s

Really shouldn't be necessary. If in doubt, just remove the streamproxy package and reinstall it.

[Erik Slagter]

So it's definitely a streamproxy background/foreground issue.

I'll have a look, thanks.

You might want to run busybox-syslog, then do a logread and post the output here. If streamproxy is running in the background, it logs to syslog.

[Erik Slagter]

How on earth do you manage a program to behave differently just because it is running in background?

If you don't know how a properly written daemon differs in behaviour from a normal user process, then indeed you cannot explain this. Hint: think of all filedescriptors being closed, the process being placed in a new terminal session and process group, an extra fork and exit (otherwise the former is not allowed), no controlling terminal...

[Erik Slagter]

... also a call to vsyslog instead of fprintf for logging, and that's where the culprit seems to be.

Edited by Erik Slagter, 17 April 2014 - 18:24.

[delavega]

why not bring back the old system while this is being worked on?

[delavega]

cuz the actual builds arent stable when it comes to transcoding...

[Erik Slagter]

why not bring back the old system while this is being worked on?

cuz the actual builds arent stable when it comes to transcoding...

Why update every day if what you have is working satisfactory?

Please keep in mind the "beta" keyword.

[Erik Slagter]

The segfault problem (in the background) has been fixed.

Edited by Erik Slagter, 17 April 2014 - 19:02.

[delavega]

why not bring back the old system while this is being worked on?

>cuz the actual builds arent stable when it comes to transcoding...

Why update every day if what you have is working satisfactory?

Please keep in mind the "beta" keyword.

 

cuz im curious xD

[Erik Slagter]

Well, your curiousity is satisfied every day At one time it may be a pleasant surprise, another time it may be an unpleasant surprise.

 

BTW using the vu plus streaming proxies, you will have to resort to rebooting every about third transcoding session. I guess you don't really want that.

[delavega]

Ye well removed streamproxy and reinstalled,rebooted but it still wont work

 

im gonna flash an old build!

[Erik Slagter]

Don't do it. You don't understand.

 

- a new flash won't help

- if I change something, it will only get updated the next day

 

So just be patient, update tomorrow and it will work.

[delavega]

ok then because i have some backups from february and march xD

 

Might as well wait you always deliver

Edited by taboune, 17 April 2014 - 19:25.

[qnopli]

Hi,

 

my Duo2 isn't also able to stream anymore after upgrade. So I just wan't to add my error message here if I try to start Streaming:

 

Apr 17 21:26:15 vuduo2 daemon.err inetd[948]: can't execute '/usr/bin/transtreamproxy': No such file or directory
Apr 17 21:26:15 vuduo2 daemon.err inetd[949]: can't execute '/usr/bin/transtreamproxy': No such file or directory
Apr 17 21:26:15 vuduo2 daemon.err inetd[950]: can't execute '/usr/bin/transtreamproxy': No such file or directory

This comes in /var/log/Messages if I open stream in VLC. 

 

Also I don't  see a streamproxy service running if I do a ps. Starting streamproxy in console Fails with message:

root@vuduo2:~# streamproxy -f
streamproxy: AcceptSocket: cannot bind accept socket

 

Start and stop explicit streamproxy service shows:

root@vuduo2:~# /etc/init.d/streamproxy.sh start
Starting Streamproxy: streamproxy.
root@vuduo2:~# /etc/init.d/streamproxy.sh stop
Stopping Streamproxy: no /usr/bin/streamproxy found; none killed
streamproxy.

 

So thats all i know about this. I hope it gets soon fixed anyway ... Thank you

[Erik Slagter]

ok then because i have some backups from february and march xD

I'd rather you upgrade tomorrow and test, so I can fix things.