Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SLS ERROR: CSLSSrt::libsrt_neterrno, err=5003, Operation not supported: Bad parameters. #1

Closed
chenwdong opened this issue Oct 19, 2019 · 25 comments

Comments

@chenwdong
Copy link

image

@chenwdong
Copy link
Author

maybe srt version is not right?

@Edward-Wu
Copy link
Owner

hi, chenwdong, please paste your command, or maybe you can add 'sudo' before your command.

@chenwdong
Copy link
Author

./sls -c ../sls.conf

@chenwdong
Copy link
Author

srt {
worker_threads 2;
log_file logs/error.log ;
log_level info;
worker_connections 300 ;
server {
listen 8089;
latency 20; #ms
domain_player live.sls.com live-1.sls.com;
domain_publisher uplive.sls.com;
backlog 100; #accept connections at the same time
app {
app_player live ;
app_publisher live ;
}
}
}

@chenwdong
Copy link
Author

My account is root

@chenwdong
Copy link
Author

I am using the latest srt compiled project, tried many times, are the same error, what is the problem?

@chenwdong chenwdong changed the title why SLS ERROR: CSLSSrt::libsrt_neterrno, err=5003, Operation not supported: Bad parameters. why Oct 20, 2019
@chenwdong chenwdong changed the title SLS ERROR: CSLSSrt::libsrt_neterrno, err=5003, Operation not supported: Bad parameters. why SLS ERROR: CSLSSrt::libsrt_neterrno, err=5003, Operation not supported: Bad parameters. Oct 20, 2019
@chenwdong
Copy link
Author

chenwdong commented Oct 20, 2019 via email

@Edward-Wu
Copy link
Owner

hi,what is your os, and version?

@chenwdong
Copy link
Author

CentOS Linux release 7.2.1511 (Core)

@chenwdong
Copy link
Author

Are you compiling with the latest version, is the result different?

@chenwdong
Copy link
Author

image

@chenwdong
Copy link
Author

Is it where I am doing wrong?

@chenwdong
Copy link
Author

I really want to try the latency, but I haven’t run it all the time.

@Edward-Wu
Copy link
Owner

today i will use the lastest version of srt to test. please wait a minute.

@Edward-Wu
Copy link
Owner

hi, please use the srt 1.3 temporary, i will spent time to resolve this issue on v1.4.
thank you.

@chenwdong
Copy link
Author

thank you !

@Edward-Wu
Copy link
Owner

hi, chenwdong
can you paste your cmd about flow stopped for a short while?

btw, i test the libsrt v1.4.0 for this issue, the reason is that srt update the result of srt_epoll_wait function , i have consulted with srt-team but no feedback.

if you want use the libsrt v1.4.0, you can change the function CSLSGroup::handler() in SLSGroup.cpp file(Line:110):

change from:
if (ret == SRT_ETIMEOUT)//6003
ret = SLSERROR(EAGAIN);
else
ret = CSLSSrt::libsrt_neterrno();
to
if (ret == SRT_ETIMEOUT)//6003
ret = SLSERROR(EAGAIN);
else{
//ret = CSLSSrt::libsrt_neterrno();
}

i will wait for srt-team about the reason.

@chenwdong
Copy link
Author

Stopped for a short while This problem is my operation error, srt1.3 is OK

@chenwdong
Copy link
Author

chenwdong commented Oct 26, 2019 via email

@Edward-Wu
Copy link
Owner

hi, chenwdong.
it's very good idea to add srt to nginx. i know nginx event based on epoll also.but srt encapsulates epoll within its api, mybe you need to think them clearly.

@chenwdong
Copy link
Author

I know that epoll is just an engine of nginx. It is completely possible to replace epoll of nginx with epoll of srt.

@chenwdong
Copy link
Author

i will try

@Edward-Wu
Copy link
Owner

hi, chenwdong
i has resolved this issue according to the srt team's suggestions and updated sls source code. If you want to know the detail about please see Haivision/srt#918

hope your great work about sls with nginx.

thank you.

@chenwdong
Copy link
Author

thank you!

@chenwdong
Copy link
Author

good

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants