Displaying 7 results from an estimated 7 matches for "tnlp".
Did you mean:
tlp
2008 Jul 03
3
Icecast Fedora9 migration problems
Karl Heyes wrote:
> Seann Clark wrote:
>
>> The biggest being is that the server binds to whatever port it feels
>> like instead of the bind port specified. The rest of the issues I have
>
> a random port bind is a new issue. Can you show us the
> netstat -tnlp | grep icecast
> for the xml provided?
Thu Jul 03-13:54:17-root at haruhi-new:~> netstat -tnlp | grep icecast
tcp 0 0 192.168.10.5:34429
0.0.0.0:* LISTEN 3336/icecast
>
>> with Icecast are minor (stats? What stats?) so here is the startup...
2008 Jul 04
0
Icecast Fedora9 migration problems
...te:
>> Seann Clark wrote:
>>
>>> The biggest being is that the server binds to whatever port it feels
>>> like instead of the bind port specified. The rest of the issues I have
>>
>> a random port bind is a new issue. Can you show us the
>> netstat -tnlp | grep icecast
>> for the xml provided?
> Thu Jul 03-13:54:17-root at haruhi-new:~> netstat -tnlp | grep icecast
> tcp 0 0 192.168.10.5:34429
> 0.0.0.0:* LISTEN 3336/icecast
ok, that doesn't match the 8000 port and you should raise...
2008 Jul 04
1
Icecast Fedora9 migration problems
...te:
>> Seann Clark wrote:
>>
>>> The biggest being is that the server binds to whatever port it feels
>>> like instead of the bind port specified. The rest of the issues I have
>>
>> a random port bind is a new issue. Can you show us the
>> netstat -tnlp | grep icecast
>> for the xml provided?
> Thu Jul 03-13:54:17-root at haruhi-new:~> netstat -tnlp | grep icecast
> tcp 0 0 192.168.10.5:34429
> 0.0.0.0:* LISTEN 3336/icecast
ok, that doesn't match the 8000 port and you should raise...
2008 Jul 03
2
Icecast Fedora9 migration problems
Ok, First I want to start off with this isn't the first icecast I have
cloned, but it is the first where I have not only jumped Fedora release
versions, but arch types as well (i386 - x86_64) and I am having strange
problems. The Icecast versions are the same between the old and new servers.
The biggest being is that the server binds to whatever port it feels
like instead of the bind port
2008 Jul 03
0
Icecast Fedora9 migration problems
Seann Clark wrote:
> The biggest being is that the server binds to whatever port it feels
> like instead of the bind port specified. The rest of the issues I have
a random port bind is a new issue. Can you show us the
netstat -tnlp | grep icecast
for the xml provided?
> with Icecast are minor (stats? What stats?) so here is the startup
> script and config I am using:
if you have suggestions for extra stats which are shown on the web pages
like /admin/stats then feel free to mention them.
>
> Icecast 2.3.1:...
2012 Dec 24
3
puppetdb listening on TCP Ports 1099 and 58772
...22u IPv6 119118 0t0 TCP *:1099 (LISTEN)
java 30115 puppetdb 23u IPv6 117236 0t0 TCP *:58772 (LISTEN)
java 30115 puppetdb 40u IPv6 117241 0t0 TCP 127.0.0.1:8080
(LISTEN)
java 30115 puppetdb 45u IPv6 117247 0t0 TCP 127.0.0.1:8081
(LISTEN)
$ netstat -tnlp | grep java
tcp6 0 0 :::1099 :::*
LISTEN 30115/java
tcp6 0 0 127.0.0.1:8080 :::*
LISTEN 30115/java
tcp6 0 0 127.0.0.1:8081 :::*
LISTEN 30115/java...
2016 Jul 07
1
Icecast is running, but not responding
...r -->
</logging>
<security>
<chroot>0</chroot>
<changeowner>
<user>icecast</user>
<group>icecast</group>
</changeowner>
</security>
</icecast>
When I run netstat -tnlp I get
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
1358/sshd
tcp 0 0 127.0.0.1:25 0.0.0.0:*...