Wamp not working, Can I close svchost.exe and LPOC.exe permanently? - wamp

My wamp always stays in yellow rather than green, I've found the cause by command httpd.exe -e debug and netstat -ano, the result shows the port 80 be occupied by System who's PID is 4.
Then I checked the stat of http service and found there are two request queues without name, then I checked their process ID and found they are svchost.exe and LPOC.exe
There is my Windows task manager
I could close the two process to release port 80, but the next day it will bu occupied by the same reason.
So how could I "really" close the two request queues?
wish I express clearly, thanks a lot.

Related

How to free a port locked by a killed process?

I have problem same as in this question.
PID exists in netstat but does not exist in task manager
I have discovered a running process with PID 26376 listening on port
9001 and 9002 as when I try to run my program(as a service) which
binds to that port it fails.
But when I try to kill it using taskkill /PID it says that the process
26376 is not found. Similarly when I try to find the process in task
manager with "Show processes from all users" selected, I couldn't find
it anywhere.
And the accepted answer says:
What may be happening is that your process had a TCP port open when it
crashed or otherwise exited without explicitly closing it. Normally
the OS cleans up these sorts of things, but only when the process
record goes away.
I am working on a C++ code and to fix an unknown/unresolved issue I am doing taskkill which sometimes locks the port. How do I free it on next use without restarting the whole OS? Is there any way to free such ports?
The TCP TIME-WAIT state will remain for 2MSL , so that the port will still be held open. You can set socketopt SO_REUSEADDR, it will work.
See this.

Why netstat -o option does not list the chrome tab pid but only its parent browser pid?

Can somebody tell me why netstat -o is listing down only the one browser pid for all the network connections happening inside chrome...what I mean is even if I have 2 or more tabs opened up in chrome and each tab is sending packets , netstat command
netstat -o-b is showing the following.
PROTO LOCAL ADDRESS FOREIGN ADDRESS STATE PID
TCP a.a.a.a b.b.b.b ESTABLISHED 2240 [chrome.exe]
TCP a.a.a.a c.c.c.c ESTABLISHED 2240 [chrome.exe]
2240 is the chrome browser pid.
But the two connections are established
by 2 chrome tabs having distinct pid's of
there own,but are not being listed. Please shed some light.
And more importantly how to get the pid's of each chrome tab programatically?
Note: I am using windows c++.
PID is a Process ID (read: identifier of a running program), not a "Tab ID". The fact that your browser uses tabs is completely irrelevant - your browser (a single program = single PID) may establish many connections. The HTML downloadded by those connections is presented to you in different tabs - that's all. BTW the connections may be terminated after the whole content has been downloaded, but the tab(s) may be still kept open (untill you close them manually). Whether the connections are kept open or not depends on many different factors: the content of the page (if it uses any AJAX, etc.), browser settings.

Process terminated, but its network resource remained

My program has a TCP server and always has several longlived connections. Sometimes I close the program without closing all the connections and then I execute netstat -ano in command line, amazingly all the connections remained with the state of "ESTABLISHED" with a pid that doesn't exist in the task-manager! Restarting the network card doesn't do any help. The only solution is logout/logon or restarting the computer. Anybody ever met this problem?
This may be the sockets in a 'half-closed' state.
They usually disappear after some timeout which may be pretty big (from 5 to 30 minutes), depending on your system.

Putting wamp online prob

Alright, so I've downloaded wamp server before an hour. I was trying to put it online and I just couldn't. I'm getting the following exception: "could not execute menu item internal error exception could not perform service action". I was googling it and I found 2 solutions.
1 of them is to change the ports of the skype, and other programs from port 80 to another one.
I don't have any of these programs, so it's should be OK.
The second solution is to change the port of the wamp to 8080 or whatever, I tried this also and it's still not working.(The icon of the wamp is orange).
What am I doing wrong? Am I missing anything?
I use WampDeveloper Pro, so it's a bit different, but I'll assume that your problem is that Apache will not start.
You'll need to get the specific Apache error message to understand what the problem is.
Open the command line (run cmd.exe), and within type in: httpd t.
This will perform a syntax check. If it's okay, then type in: httpd -k start.
This will attempt to start Apache, and if unsuccessful, will print out the error.
If the error is something like "can't bind to 0.0.0.0:80, port already in use" (the error will be a bit more clinical than that) then you are right, something else is already taking up port 80.
In which case, type in: netstat -aon. Look for the line that says "0.0.0.0:80" and note the PID number. Then get in your Windows Task Manager (ctrl-alt-del), into the Processes Tab, click "Show process from all". Find the process that has the same PID number. This is what you need to shut down or reconfigure to listen on another port.
hey have you tried to put off any othe installed server like IIS for example ?? if you have IIS turned on go to services and stop world wide publishing service and than try restart all wamp services and then put it online it sould work :)
Mostly its Apache problem.
I had the same problem. The problem is that the port Apache is trying to use is actually being used by some other application. Either
Change the port no. from the file http.conf or httpd.conf from 80 to smething else Listen 8080 change 8080 to something else.
check out which application is using the port and shut it down. Check the port status using "cports" aplication or any other that you prefer. Then it will work just fine.

Jrun ColdFusion service intermittently fails to start

We occasionaly have a problem where we attempt to start the Jrun service and it fails with the following two errors:
error JRun Naming Service unable to start on port 2902
java.net.BindException: Port in use by another service or process: 2902
info No JDBC data sources have been configured for this server (see jrun-resources.xml)
error java.net.BindException: Port in use by another service or process: 8300
We then have to reboot the machine and Jrun comes up with no problem. This is very intermittent - happens perhaps one out of every 10 times we restart Jrun services.
I saw another reference on StackOverflow that if Windows Services take longer than 30 seconds to restart Windows shuts down the startup proccess. Perhaps that is the issue here? The logs indeed indicate that these errors are thrown about 37+ seconds after the restart command is issued.
We are on a 64bit platform on WinServer 2008.
Thanks!
We've been experiencing a similar problem on some of our servers. Unfortunately, netstat never indicated any sort of actual port conflict for us. My suspicion is that it's related to our recent deployment of a ColdFusion "cumulative hotfix" to our servers. We use the multi-server edition of CF 8.0.1 enterprise with a large number of instances on each machine -- each with its own JVM and its own distinct set of ports. Each CF instance is attached to its own IIS website and runs as its own Windows Service.
Within the past few weeks, we started getting similar "port in use" exceptions on startup, on our 32-bit machines as well as our 64-bit machines, all of which are running Windows Server 2003. I found several possible culprits and tried the following:
In jrun-jms.xml for each CF instance, there's an entry for the RMI transport layer that reads <port>0</port> -- which, according to the JRun documentation, means "choose a random port." I made that non-random and distinct per instance (in the 2600-2650 range) and restarted each instance. Things improved temporarily, perhaps coincidentally.
In the same file, under the entry for the TCPIP transport later, every instance defaulted to <port>2522</port> -- so I changed those to distinct ports per instance in the 2500-2550 range and restarted each instance. That didn't seem to help at all.
I tried researching whether ports in the 2500-3000 range might be used for any other purpose, and I couldn't find anything obvious, and besides, netstat wasn't telling me that any of my choices were in use.
I found something online about Windows designating ports from 1024 to 5000 as the "dynamic port" range, so I added 10000 to the port numbers I had set in jrun-jms.xml and restarted each instance again. Still didn't help.
I tried changing the port in jndi.properties, also by adding 10000 to the port numbers. Unfortunately this meant wiping out all my wsconfig connections to IIS and creating them again from scratch. I had to edit wsconfig_jvm.config as well, adding -DWSConfig.PortScanStartPort=12900 to java.args, so it could detect my CF instances. (By default it only scans ports 2900-3000. See bpurcell.org for details. It's an old post but still relevant.) So far so good!
My best guess is that Adobe (or MS Windows) changed the way some of its code grabs "random" ports. But all I know for sure so far is that the steps outlined above appear to have fixed the problem.
Have you verified that the services are in fact stopping? Task manager should show no instances of jrun.exe. You can also check to see what is bound to that port by opening a command window and running
netstat -a -b
This will list all your open ports, plus what program is using them. You can also use
netstat -a -o
Which does the same thing as the above, but will list the process id instead of the program name. You can then cross-reference those with task manager. You'll need to enable showing the PIDs in task manager by going to View->Select Columns and making sure PID is checked. My guess would be that the jrun processes are not shutting down in a timely fashion.