Optware log: xinetd started too often

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Author Message
gatorback
DD-WRT User


Joined: 04 Feb 2007
Posts: 360
Location: Fountain of Youth

PostPosted: Mon Nov 07, 2011 7:54    Post subject: Optware log: xinetd started too often Reply with quote
As you can see that this message is quickly filling up my log file, because xinetd is started more than once per second from my laptop (192.168.8.116).

I am wondering what is causing this and what corrective action can be taken. Please weigh-in if you have seen this symptom and understand its root cause. Thank you.



Quote:
Nov 6 20:33:21 athomehost authpriv.info xinetd[3546]: START: www pid=15130 from=192.168.8.116
Nov 6 20:33:22 athomehost authpriv.info xinetd[3546]: START: www pid=15131 from=192.168.8.116
Nov 6 20:33:22 athomehost authpriv.info xinetd[3546]: START: www pid=15132 from=192.168.8.116
Nov 6 20:33:22 athomehost authpriv.info xinetd[3546]: START: www pid=15133 from=192.168.8.116
Nov 6 20:33:23 athomehost authpriv.info xinetd[3546]: START: www pid=15134 from=192.168.8.116
Nov 6 20:33:23 athomehost authpriv.info xinetd[3546]: START: www pid=15135 from=192.168.8.116
Nov 6 20:33:23 athomehost authpriv.info xinetd[3546]: START: www pid=15136 from=192.168.8.116
Nov 6 20:33:24 athomehost authpriv.info xinetd[3546]: START: www pid=15137 from=192.168.8.116
Nov 6 20:33:24 athomehost authpriv.info xinetd[3546]: START: www pid=15140 from=192.168.8.116
Nov 6 20:33:24 athomehost authpriv.info xinetd[3546]: START: www pid=15141 from=192.168.8.116
Nov 6 20:33:24 athomehost authpriv.info xinetd[3546]: START: www pid=15142 from=192.168.8.116
Nov 6 20:33:25 athomehost authpriv.info xinetd[3546]: START: www pid=15143 from=192.168.8.116
Nov 6 20:33:25 athomehost authpriv.info xinetd[3546]: START: www pid=15144 from=192.168.8.116
Nov 6 20:33:25 athomehost authpriv.info xinetd[3546]: START: www pid=15145 from=192.168.8.116
Nov 6 20:33:26 athomehost authpriv.info xinetd[3546]: START: www pid=15146 from=192.168.8.116
Nov 6 20:33:26 athomehost authpriv.info xinetd[3546]: START: www pid=15147 from=192.168.8.116
Nov 6 20:33:26 athomehost authpriv.info xinetd[3546]: START: www pid=15148 from=192.168.8.116
Nov 6 20:33:27 athomehost authpriv.info xinetd[3546]: START: www pid=15149 from=192.168.8.116


root@athomehost:/opt/var/log# ls -l | grep messages
-rw-rw-rw- 1 root root 1853003 Nov 7 03:42 messages
-rw-rw-rw- 1 root root 2048082 Nov 5 20:05 messages.0
-rw-rw-rw- 1 root root 2048073 Nov 1 16:05 messages.1
-rw-rw-rw- 1 root root 453570 Oct 24 18:30 messages.10
-rw-rw-rw- 1 root root 2048019 Nov 1 14:06 messages.2
-rw-rw-rw- 1 root root 2048034 Nov 1 05:15 messages.3
-rw-rw-rw- 1 root root 2048024 Nov 1 01:02 messages.4
-rw-rw-rw- 1 root root 2048041 Oct 31 16:05 messages.5
-rw-rw-rw- 1 root root 2048027 Oct 27 20:15 messages.6
-rw-rw-rw- 1 root root 2048034 Oct 27 17:41 messages.7
-rw-rw-rw- 1 root root 2048066 Oct 24 07:45 messages.8
-rw-r--r-- 1 root root 6063287 Oct 21 21:15 messages.9

_________________
My Routers | RT-N16 Wiki | RT-N16 Mods
Peacock Flashing | Wireless N Conf | Linking Routers |
DD-WRT Wiki | DD-WRT Builds | Broadcom FAQ| QoS| OTRW


Last edited by gatorback on Mon Nov 07, 2011 19:32; edited 1 time in total
Sponsor
Bird333
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 807

PostPosted: Mon Nov 07, 2011 19:21    Post subject: Reply with quote
Yes, I haven't check the actual logs but WallWatcher is showing alot of these messages.
zoomlink
DD-WRT User


Joined: 08 May 2011
Posts: 221

PostPosted: Mon Nov 07, 2011 20:21    Post subject: Reply with quote
Guys... these messages get generated when you are on any of the router's web pages. One entry gets generated every time the router page you are on refreshes.

If you close the browser session to the router, these messages stop.
gatorback
DD-WRT User


Joined: 04 Feb 2007
Posts: 360
Location: Fountain of Youth

PostPosted: Mon Nov 07, 2011 20:37    Post subject: Reply with quote
@zoomlink: thanks for the explanation. I'm glad this is not something I need to address. Last week, I experienced a similar problem with another unix box, however, a service was generating log errors and had to be removed.
_________________
My Routers | RT-N16 Wiki | RT-N16 Mods
Peacock Flashing | Wireless N Conf | Linking Routers |
DD-WRT Wiki | DD-WRT Builds | Broadcom FAQ| QoS| OTRW
digital_janitor
DD-WRT Novice


Joined: 06 Aug 2013
Posts: 2
Location: Somewhere in Washington

PostPosted: Thu Aug 29, 2013 18:03    Post subject: Reply with quote
Sorry to dig up an ancient thread, but hopefully this might help someone else.

I am running kong mega 220000 on a linksys e4200. I have optware2 installed and am running
xinetd
pixelserv
fixtables
stophammer
asiablock
sshhack
stophack
mypage
I noticed I was getting this same xinetd spam about starting www in wallwatcher.

I also noticed even though pixelserv moves httpd to port 88, I was still listening on port 80.

using netstat -l -v --numeric-ports -p I discovered xinetd was the culprit. I don't know if this is by design, or what, I am still researching.

tcp 0 0 192.168.1.1:80 0.0.0.0:* LISTEN 12209/xinetd


Anyway, if I connected to the admin page using port 88 I don't get the xinetd messages.

However if I connect to the admin page using port 80, not only do I still get the admin page, xinetd is going nuts. (It appears it's spawning a www process that immediately dies, so in order to fulfill all the http requests it keeps starting them)

Anyhow, I am still investigating why xinetd is doing this(for all I know it's by design) I may look at just blocking port 80.



Edit:
http://linux.die.net/man/5/xinetd.conf

I'm wondering if it's something to do with this

redirect

Allows a tcp service to be redirected to another host. When xinetd receives a tcp connection on this port it spawns a process that establishes a connection to the host and port number specified, and forwards all data between the two hosts. This option is useful when your internal machines are not visible to the outside world. Syntax is: redirect = (ip address) (port). You can also use a hostname instead of the IP address in this field. The hostname lookup is performed only once, when xinetd is started, and the first IP address returned is the one that is used until xinetd is restarted. The "server" attribute is not required when this option is specified. If the "server" attribute is specified, this attribute takes priority.
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum