Hi I am Posting this message here after posting it on comp.os.qnx
assuming that some of you have moved from there to this server.
We run a QNX 4.25 server here. I tried to run a back up server
and for trying out stuff. Since I have started operation on the second
test server, the syslog file of the main server is giving this following
error.
Sep 28 10:51:24 localhost inetd[2651]: pop3/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: phrelay/tcp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: chargen/udp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: chargen/tcp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: daytime/udp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: daytime/tcp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: discard/udp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: discard/tcp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: echo/udp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: echo/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: time/udp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: time/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: netstat/tcp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: systat/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: tftp/udp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: exec/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: login/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: shell/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: telnet/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: ftp/tcp: bind: Address already in
use
Sep 28 11:01:24 localhost inetd[2651]: pop3/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: phrelay/tcp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: chargen/udp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: chargen/tcp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: daytime/udp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: daytime/tcp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: discard/udp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: discard/tcp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: echo/udp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: echo/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: time/udp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: time/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: netstat/tcp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: systat/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: tftp/udp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: exec/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: login/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: shell/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: telnet/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: ftp/tcp: bind: Address already in
use
This is a part of the file that the server writes every 10 minutes. I
thought it was probably because the test server was running on the same
LAN (though both have different IPs attached to them), I shutdown the
test server but the same error continuously exist. THe wierd thing is
that the server is running just fine… performing all its
operations… However the test server is not running a couple of
processes and thats what made me look into this stuff. I would
appreciate a detailed response if someone figures out what might the
problem be…
Do you have both systems with the same hostname and thus using the same IP
from /etc/hosts?
See your netstart file for changing your hostname.
Many times the netstart uses “node$NODE” as the hostanme and if both nodes
are 1 then they’ll have the same hostname. You’ll need to change the
/etc/netstart script, or the IP in /etc/hosts, or both.
If they both use the same hostname other computers will get confused trying
to talk to them…
-Paul
Hi I am Posting this message here after posting it on comp.os.qnx
assuming that some of you have moved from there to this server.
We run a QNX 4.25 server here. I tried to run a back up server
and for trying out stuff. Since I have started operation on the second
test server, the syslog file of the main server is giving this following
error.
Sep 28 10:51:24 localhost inetd[2651]: pop3/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: phrelay/tcp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: chargen/udp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: chargen/tcp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: daytime/udp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: daytime/tcp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: discard/udp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: discard/tcp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: echo/udp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: echo/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: time/udp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: time/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: netstat/tcp: bind: Address
already in use
Sep 28 10:51:24 localhost inetd[2651]: systat/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: tftp/udp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: exec/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: login/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: shell/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: telnet/tcp: bind: Address already
in use
Sep 28 10:51:24 localhost inetd[2651]: ftp/tcp: bind: Address already in
use
Sep 28 11:01:24 localhost inetd[2651]: pop3/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: phrelay/tcp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: chargen/udp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: chargen/tcp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: daytime/udp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: daytime/tcp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: discard/udp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: discard/tcp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: echo/udp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: echo/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: time/udp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: time/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: netstat/tcp: bind: Address
already in use
Sep 28 11:01:24 localhost inetd[2651]: systat/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: tftp/udp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: exec/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: login/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: shell/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: telnet/tcp: bind: Address already
in use
Sep 28 11:01:24 localhost inetd[2651]: ftp/tcp: bind: Address already in
use
This is a part of the file that the server writes every 10 minutes. I
thought it was probably because the test server was running on the same
LAN (though both have different IPs attached to them), I shutdown the
test server but the same error continuously exist. THe wierd thing is
that the server is running just fine… performing all its
operations… However the test server is not running a couple of
processes and thats what made me look into this stuff. I would
appreciate a detailed response if someone figures out what might the
problem be…