I have just installed WAMPSERVER (Apache/2.4.9 (Win64) ) on my WIN 8 machine and when tried to start it, its icon is always RED / orange ( not green ). From services when tried to run the service I see following error message:
From the even log, I see following multiple errors
The wampapache64 service terminated with the following service-specific error:
Incorrect function.
The Apache service named reported the following error:
>>> (OS 10013)An attempt was made to access a socket in a way forbidden by its access permissions. : AH00072: make_sock: could not bind to address 0.0.0.0:80
The Apache service named reported the following error:
>>> (OS 10013)An attempt was made to access a socket in a way forbidden by its access permissions. : AH00072: make_sock: could not bind to address [::]:80
The Apache service named reported the following error:
>>> AH00015: Unable to open logs
The Apache service named reported the following error:
>>> AH00451: no listening sockets available, shutting down
The wampapache64 service terminated with the following service-specific error:
Incorrect function.
The Apache service named reported the following error:
>>> (OS 10013)An attempt was made to access a socket in a way forbidden by its access permissions. : AH00072: make_sock: could not bind to address [::]:80.
Okay, I figured out: my machine's port 80 was being used by IIS, not by Skype. Here is how I found that:
Left-click the WAMPManager icon to reveal the menu. Click Apache ► Service ► Test port 80.
This will launch a command window and display some information about what, if anything is using port 80. You can find more details at http://forum.wampserver.com/read.php?2,122527.
Configure Apache to listen on different port
Since I wanted to keep running IIS on the port 80, I decided to run my WAMP Server on a different port. So here is how I did it.
I had to change http.conf file which in my case is in folder C:/WAMP/bin/apache/apache2.4.9/conf/. Open it (with Notepad for example) and search for 80. I had to change the following three lines on different places:
Listen 0.0.0.0:80 # Changed to Listen 0.0.0.0:81
Listen [::0]:80 # Changed to Listen [::0]:81
ServerName localhost:80 # Changed toServerName localhost:81
Now I have got the green icon of WAMP Server on Windows 8.
More details on http://forum.wampserver.com/read.php?2,13744.
If you have Skype running, then you have to do the following within Skype: in the menu bar, click Tools ► Options ► Advanced settings ► Connection. Now uncheck the following checkbox:
Use port 80 and 443 as alternatives for incoming connections
I have gone through the same problem.
I quit the Skype application and started the wampapache64 service from task manager and that worked for me.
Related
I have installed jenkins as windows service but every time after starting the machine i have to execute it through command line using $ java -jar jenkins.war
I am not able to directly open it into web browser at http://localhost:8080/
Am i missing something? Any help will be really appreciated.
Copy original 'jenkins.war' into 'jenkins' directory and restart service
Clear the Windows event viewer logs for Application and System
Please ensure your services are running and up
Firewall Issue:The easiest way to track down firewall issues is to use tcpdump. Just run the following command on the Jenkins server, which is trying to connect to the slave.
More Info on firewall part:
By default, Windows Firewall prevents the TCP connections necessary to make this mechanism work. The firewall on the slave must allow the following exceptions (see List of TCP&UDP port numbers):
TCP Port 135 (DCE/RPC Locator service)
TCP Port 139 (NetBIOS Session Service)
TCP Port 445 (Windows shares)
C:\WINDOWS\system32\dllhost.exe (dllhost.exe seems to use a random port number)
C:\WINDOWS\system32\javaw.exe (Jenkins also uses a random port number)
File and Printer sharing (TCP 139, TCP 445, UDP 137, UDP 138 (possibly only a subset of these is required))
The issue is fixed now. I have changed the service properties. In service properties -> Log On->Select Local system account and select the checkbox for allow the service to interact with desktop
When I ran the Mosquitto (MQTT) broker for the first time there was no issue. However when running it for the second time using the default config I could not run the code successfully because of the following error on Windows 8:
1379497253: mosquitto version 1.2 (build date 2013-09-17 17:59:39+0530) starting 1379497253: Using default config. 1379497253: Opening ipv6 listen socket on port 1883. 1379497253: Error: Address already in use
How can I resolve this error, or more importantly what does this error mean?
Address already in use usually means that the port (in your case 1883) is already being used by another process. The most likely situation given your description is that another copy of mosquitto is already running. If you want to run two (or more) you'll need to configure each to use a separate port number.
You have to check the mosquitto.conf in a bin folder in which you installed the mosquitto server.
Make sure all lines are commented with '#' especially the following line,
port 1883 or listener 1883.
then, find some available port or whether the port 1883 is used by using command like netstat.
In windows, you can use this,
netstat -an| findStr 1883
You have to change your default port on mosquitto when found any message from the prompt.
Append some specific number on the line below which is indicating the port whatever you prefer to.
listener XXX
protocol mqtt
I'm developing an MQTT based application using HiveMQ, an enterprise broker. I installed it as per the instructions here- http://www.hivemq.com/docs/hivemq/2.0.1/
When I run it using ./bin/run.sh, the server connection is immediately closed due to the error - Could not bind to all interfaces and port 1883, because it is already in use. Stopping HiveMQ
As far as I'm aware, nothing else is using this port. This happens even when I restart my computer and nothing else is running. I'm running in root mode.
Why am I getting this error?
To check if something is already running on the port, please type the following into the terminal if you happen to run a Linux / BSD / OSX:
netstat -an|grep 1883
If you're running a Windows System, type the following:
netstat -an|find "1883"
After running that command you should see which application is using port 1883.
Alternatively you could edit the configuration.properties file in you conf folder of the HiveMQ installation and set the global.port property to a port of your choice.
From those results, do you have d-bus daemon installed? I don't know much about d-bus, but have you tried disabling it or modifying the config and then see if you can restart hivemq on port 1883.
I have IBM Notes 9.0.1 (Revision 20131022.1138) installed on my Windows 8.1. Whenever I start my Domino Designer and try to preview a page it does not show up. I tried to start the local HTTP process using the command nhttp.exe -preview but it gave me an error as:
HTTP Server: Error - Unable to Bind port 80, port may be in use or
user needs net_privaddr privilege
Using the command of netstat -o I was able to find Toaster.exe process bound to 80. I disabled it using instructions from here. But still I am getting the same error. Now the netstat -o command does not show any process bound to port 80.
Taking reference from this discussion I even disabled my Windows firewall but I am still unable to get it to work.
Not sure if this will work - but have you tried changing the Web Preview port in Domino Designer -> Preferences -> Domino Designer -> Web Preview Port. Change it to 8080 or something other than 80 that's not being used and see if it works.
Hi I'm receiving an SSL issue on my rails app on my local server:
An error occurred during a connection to localhost:3000.
SSL received a record that exceeded the maximum permissible length.
(Error code: ssl_error_rx_record_too_long)
and was told that opening port 443 would fix the problem. I've looked around everywhere but there doesn't seem to be an answer. Could someone go through the process of how I would open port 443?
So, someone is advising you to open that port in your firewall. I don't think this will help, since you're connecting to port 3000, but it might be that you're running a proxy on port 3000 that needs to connect to port 443.
Instead of opening that port I would suggest disabling your firewall and retrying that. If it works, then you should look into making an exception for that port. Here's how to disable the firewall: (Which will open that port)
Open System Preferences->Security->Firewall and click "Stop". Don't forget to turn it back on when you're done testing.