| View previous topic :: View next topic |
| Author |
Message |
sven
Joined: 09 Apr 2014
Posts: 34
|
 Posted: Thu Sep 04, 2014 10:32 am Post subject: Listening sockets already open on reload |
 |
|
I have made some changes to the Icecast configuration so it runs at port 80, 443 and 8000 (as fallback). The part in my config that does this, looks like:
| Code: |
<security>
<chroot>0</chroot>
<changeowner>
<user>icecast2</user>
<group>icecast</group>
</changeowner>
</security>
<hostname>192.168.1.51</hostname>
<listen-socket>
<port>80</port>
<bind-address>192.168.1.51</bind-address>
</listen-socket>
<listen-socket>
<port>8000</port>
<bind-address>192.168.1.51</bind-address>
</listen-socket>
<listen-socket>
<port>443</port>
<ssl>1</ssl>
<bind-address>192.168.1.51</bind-address>
</listen-socket>
|
Works fine after startup it says:
| Code: |
dev:~# /etc/init.d/icecast2-dev start
Starting icecast2-dev: Starting icecast2
Detaching from the console
icecast2-dev.
dev:~# Changed groupid to 110.
Changed userid to 105. |
But, when reloading the config using the command:
| Code: |
| dev:~# /etc/init.d/icecast2-dev reload |
Two Icecast error.log entries, draw my attention:
1.
| Code: |
| WARN slave/slave_startup process has 4096 max file descriptor limit |
2:
| Code: |
[2014-09-04 12:19:23] INFO connection/connection_setup_sockets 2 listening sockets already open
[2014-09-04 12:19:23] EROR connection/connection_setup_sockets Could not create listener socket on port 443 bind 192.168.1.51
[2014-09-04 12:19:23] INFO connection/connection_setup_sockets listener socket on port 8000 address 192.168.1.51
[2014-09-04 12:19:23] EROR connection/connection_setup_sockets Could not create listener socket on port 80 bind 192.168.1.51
[2014-09-04 12:19:23] INFO connection/connection_setup_sockets 3 listening sockets setup complete
|
Icecast keeps working and sources and listeners can still connect.
My question; what does these messages mean, do they need to be resolved and if so; how can i do that.
Thanks for the help!
Icecast version:
| Code: |
dev:/var/log/icecast2# icecast2-dev -v
Icecast 2.3.3-kh10-17-ga5260a6 |
|
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Thu Sep 04, 2014 7:34 pm Post subject: |
|
|
not a concern as far as I can see, ports 80 and 443 were left open as you generally cannot re-open them over reload, but 8000 was. After that, the 2 you already had opened naturally failed (already in use) and port 8000 was re-opened.
karl. |
|
| Back to top |
|
|
sven
Joined: 09 Apr 2014
Posts: 34
|
| Posted: Fri Sep 05, 2014 10:08 am Post subject: |
|
|
Thanks for your quick reply Karl.
Ok, I will just ignore the messages about the sockets.
And what about the other entry:
| Code: |
| WARN slave/slave_startup process has 4096 max file descriptor limit |
What does that mean? |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Fri Sep 05, 2014 12:21 pm Post subject: |
|
|
each process has hard/soft limits for a few resource, the file descriptor one is the limit of all open file/sockets/pipes handles. so if you wanted up to say 10000 clients, then you could only have at most about ~4090 as that is only what the process is allowed to have. you could try to change that with the limits.conf or prlimit utility.
karl. |
|
| Back to top |
|
|
sven
Joined: 09 Apr 2014
Posts: 34
|
| Posted: Fri Sep 05, 2014 2:02 pm Post subject: |
|
|
Alright, thanks for the explanation.
I will leave it unchanged for now. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
