I've started a new instance (i-d23f3a5c) 2 months ago and it's becoming inaccessible every day.
Looking at /var/log/messages I can see the dhcp client is requesting a lease quite often and at some point the message "dhclient1306: fork: Cannot allocate memory" appears.
From there the server is not accessible anymore and needs to be rebooted (I suppose it has lost it's internal ip).
Aug 19 08:47:19 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 (xid=0x7daf4b5c)
Aug 19 08:47:37 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 (xid=0x7daf4b5c)
Aug 19 08:48:02 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 (xid=0x7daf4b5c)
Aug 19 08:48:37 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21 (xid=0x7daf4b5c)
Aug 19 08:49:24 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=0x7daf4b5c)
Aug 19 08:49:43 ip-172-31-16-179 dhclient[2144]: No DHCPOFFERS received.
Aug 19 08:50:11 ip-172-31-16-179 dhclient[2144]: No working leases in persistent database - sleeping.
Aug 19 08:51:09 ip-172-31-16-179 dhclient[2144]: fork: Cannot allocate memory
Aug 19 08:59:09 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0x322ab770)
Aug 19 08:59:46 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 (xid=0x322ab770)
Aug 19 09:00:15 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 (xid=0x322ab770)
Aug 19 09:01:14 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14 (xid=0x322ab770)
Aug 19 09:01:47 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0x322ab770)
Aug 19 09:02:26 ip-172-31-16-179 dhclient[2144]: No DHCPOFFERS received.
Aug 19 09:03:12 ip-172-31-16-179 dhclient[2144]: No working leases in persistent database - sleeping.
Aug 19 09:04:17 ip-172-31-16-179 dhclient[2144]: fork: Cannot allocate memory
Aug 19 09:14:10 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x1c2c358)
Aug 19 09:14:55 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 (xid=0x1c2c358)
Aug 19 09:15:30 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 (xid=0x1c2c358)
Aug 19 09:16:22 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0x1c2c358)
Aug 19 09:17:01 ip-172-31-16-179 dhclient[2144]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 (xid=0x1c2c358)
Aug 19 09:17:43 ip-172-31-16-179 dhclient[2144]: No DHCPOFFERS received.
And so on until I reboot it from the EC2 console.
What would be the best course of action ?
remove DHCP - is that possible ?
restart dhcp client on regular basis ?
increase the number of possible fork (issue will probably arise at some point)
change the renew time to a longer time ?
fix the dhcp client ?
Thanks,
Ankit
Related
Also I have infinity loading at https://remotedesktop.google.com/access
System Ubuntu 20.04
(zh;sd h;fghdfghidfzghuid ghfdh pugzpoum ifdioug(for edit)
Logs:
Feb 19 09:41:01 instance-20210501-1727 chrome-remote-desktop[1927244]: [0219/094101.848763:INFO:chromoting_host.cc(108)] Starting host
Feb 19 09:41:01 instance-20210501-1727 chrome-remote-desktop[1927244]: [0219/094101.851095:INFO:remoting_me2me_host.cc(1137)] Policy sets host domains:
Feb 19 09:41:01 instance-20210501-1727 chrome-remote-desktop[1927244]: [0219/094101.851123:INFO:remoting_me2me_host.cc(1240)] Policy does not require host username match.
Feb 19 09:41:01 instance-20210501-1727 chrome-remote-desktop[1927244]: [0219/094101.851129:INFO:remoting_me2me_host.cc(1159)] Policy allows remote access connections: 1
Feb 19 09:41:01 instance-20210501-1727 chrome-remote-desktop[1927244]: [0219/094101.851320:INFO:ftl_signaling_connector.cc(137)] Attempting to reconnect signaling.
Feb 19 09:41:03 instance-20210501-1727 chrome-remote-desktop[1927244]: [0219/094103.048669:INFO:ftl_signaling_connector.cc(94)] Signaling connected. New JID: eed268b131894fa78cdcc0268abfebb5#chromoting.gserviceaccount.com/chromoti>Feb 19 09:41:03 instance-20210501-1727 chrome-remote-desktop[1927244]: [0219/094103.048720:INFO:heartbeat_sender.cc(172)] Sending outgoing heartbeat.
Feb 19 09:41:03 instance-20210501-1727 chrome-remote-desktop[1927244]: [0219/094103.378292:INFO:remoting_me2me_host.cc(956)] Host ready to receive connections.
Feb 19 09:41:03 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:03,379:INFO:Host ready to receive connections.
Feb 19 09:41:05 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:05,048:INFO:wait() returned (1927242,139)
Feb 19 09:41:05 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:05,048:INFO:Session process terminated
Feb 19 09:41:05 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:05,149:INFO:Failure count for 'session' is now 1
Feb 19 09:41:05 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:05,149:INFO:Terminating X server
Feb 19 09:41:05 instance-20210501-1727 chrome-remote-desktop[1927244]: [0219/094105.152972:ERROR:connection.cc(66)] X connection error received.
Feb 19 09:41:05 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:05,488:INFO:Terminating host
Feb 19 09:41:05 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:05,489:INFO:Failure count for 'X server' is now 0
Feb 19 09:41:05 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:05,489:INFO:Failure count for 'host' is now 0
Feb 19 09:41:05 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:05,489:INFO:Launching X server and X session.
Feb 19 09:41:05 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:05,518:INFO:Starting Xvfb on display :20
Feb 19 09:41:05 instance-20210501-1727 chrome-remote-desktop[1927350]: xdpyinfo: unable to open display ":20".
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:06,027:INFO:X server is active.
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:06,148:INFO:Launching X session: ['/bin/sh', '/etc/chrome-remote-desktop-session']
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:06,158:INFO:Launching host process
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:06,159:INFO:['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/ubuntu/.config/chrome>Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.258905:WARNING:resource_bundle.cc(406)] locale_file_path.empty() for locale
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.258987:INFO:remoting_me2me_host.cc(1776)] Starting host process: version 96.0.4664.9
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.478209:INFO:file_host_settings.cc(31)] Host settings file /home/ubuntu/.config/chrome-remote-desktop/host#4790dcd5b0eb6c774388357f3e52ea98.setting>Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.478483:INFO:remoting_me2me_host.cc(1344)] Policy does not require curtain-mode.
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.478497:INFO:remoting_me2me_host.cc(1267)] Policy enables NAT traversal.
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.478502:INFO:remoting_me2me_host.cc(1285)] Policy enables use of relay server.
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.478507:INFO:remoting_me2me_host.cc(1306)] Policy restricts UDP port range to: <no port range specified>
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.478514:INFO:remoting_me2me_host.cc(1355)] Policy sets third-party token URLs: <no 3rd party auth config specified>
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.478519:INFO:remoting_me2me_host.cc(1377)] Policy enables client pairing.
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.478524:INFO:remoting_me2me_host.cc(1393)] Policy enables security key auth.
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.478528:INFO:remoting_me2me_host.cc(1412)] Policy enables file transfer.
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.478532:INFO:remoting_me2me_host.cc(1435)] Policy enables user interface for non-curtained sessions.
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.478537:INFO:remoting_me2me_host.cc(1458)] Policy does not set a maximum session duration.
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.478547:INFO:remoting_me2me_host.cc(617)] Processing new host configuration.
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.479442:INFO:chromoting_host.cc(108)] Starting host
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.549653:INFO:remoting_me2me_host.cc(1137)] Policy sets host domains:
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.549669:INFO:remoting_me2me_host.cc(1240)] Policy does not require host username match.
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.549674:INFO:remoting_me2me_host.cc(1159)] Policy allows remote access connections: 1
Feb 19 09:41:06 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094106.549836:INFO:ftl_signaling_connector.cc(137)] Attempting to reconnect signaling.
Feb 19 09:41:07 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094107.950526:INFO:ftl_signaling_connector.cc(94)] Signaling connected. New JID: eed268b131894fa78cdcc0268abfebb5#chromoting.gserviceaccount.com/chromoti>Feb 19 09:41:07 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094107.954376:INFO:heartbeat_sender.cc(172)] Sending outgoing heartbeat.
Feb 19 09:41:08 instance-20210501-1727 chrome-remote-desktop[1927382]: [0219/094108.249860:INFO:remoting_me2me_host.cc(956)] Host ready to receive connections.
Feb 19 09:41:08 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:08,250:INFO:Host ready to receive connections.
Feb 19 09:41:08 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:08,748:INFO:wait() returned (1927376,139)
Feb 19 09:41:08 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:08,749:INFO:Session process terminated
Feb 19 09:41:08 instance-20210501-1727 chrome-remote-desktop[1927195]: 2022-02-19 09:41:08,755:INFO:Failure count for 'session' is now 2
lines 1-74
zh;sd h;fghdfghidfzghuid ghfdh pugzpoum ifdioug(for edit)
The line:
Feb 19 09:41:05 instance-20210501-1727 chrome-remote-desktop[1927350]: xdpyinfo: unable to open display ":20".
tell you you do not have X server Display 20 on your desktop. Set it or configure it to use existing display. Also firewall on your computer can be the reason for this problem so you can open the port for display 20 (if its available on your computer.).
I've installed pptpd on CentOS 7 with AWS EC2 and I can connect to vpn with windows client but I have no internet access while the server has full internet access. In pptpd log I noticed the error "Cannot determine ethernet address for proxy ARP".
I've changed the dns in /etc/ppp/options.pptpd as below:
ms-dns 8.8.8.8
ms-dns 8.8.4.4
I've also created users in /etc/ppp/chap-secrets and clients can connect without problem (but with no internet access.)
I've also enabled IP forwarding in /etc/sysctl.conf
net.ipv4.ip_forward = 1
and execute this command:
sudo sysctl -p
I changed local and remote IPs in /etc/pptpd.conf as below:
localip 192.168.10.1
remoteip 192.168.20.10-100
I configured firewall for IP masquerading:
sudo iptables -t nat -A POSTROUTING -o ens5 -j MASQUERADE
This is the ifconfig result:
ens5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9001
inet 172.31.28.246 netmask 255.255.240.0 broadcast 172.31.31.255
inet6 fe80::4e6:11ff:fed8:bb4a prefixlen 64 scopeid 0x20<link>
ether 06:e6:11:d8:bb:4a txqueuelen 1000 (Ethernet)
RX packets 3668 bytes 347939 (339.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3111 bytes 385009 (375.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 6 bytes 416 (416.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6 bytes 416 (416.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ppp0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1396
inet 192.168.10.1 netmask 255.255.255.255 destination 192.168.20.10
ppp txqueuelen 3 (Point-to-Point Protocol)
RX packets 40 bytes 3158 (3.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 104 (104.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
And this is the pptpd status (I could connect to the VPN successful but could not access the internet):
[root#ip-172-31-28-246 ~]# systemctl status pptpd
● pptpd.service - PoPToP Point to Point Tunneling Server
Loaded: loaded (/usr/lib/systemd/system/pptpd.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2021-08-22 09:24:41 UTC; 2min 9s ago
Main PID: 1476 (pptpd)
CGroup: /system.slice/pptpd.service
├─1476 /usr/sbin/pptpd -f
├─1505 pptpd [171.213.14.133:ED5A - 0000]
└─1506 /usr/sbin/pppd local file /etc/ppp/options.pptpd 115200 192.168.10.1:192.168.20.10 ipparam 171.213.14.133 plugin /usr/lib64/pptpd/pptpd-logwtmp.so pptpd-original-ip 171.213.14.133 remote...
Aug 22 09:25:28 ip-172-31-28-246.ap-east-1.compute.internal pptpd[1505]: CTRL: Starting call (launching pppd, opening GRE)
Aug 22 09:25:28 ip-172-31-28-246.ap-east-1.compute.internal pppd[1506]: Plugin /usr/lib64/pptpd/pptpd-logwtmp.so loaded.
Aug 22 09:25:28 ip-172-31-28-246.ap-east-1.compute.internal pppd[1506]: pppd 2.4.5 started by root, uid 0
Aug 22 09:25:28 ip-172-31-28-246.ap-east-1.compute.internal pppd[1506]: Using interface ppp0
Aug 22 09:25:28 ip-172-31-28-246.ap-east-1.compute.internal pppd[1506]: Connect: ppp0 <--> /dev/pts/1
Aug 22 09:25:32 ip-172-31-28-246.ap-east-1.compute.internal pppd[1506]: peer from calling number 171.213.14.133 authorized
Aug 22 09:25:32 ip-172-31-28-246.ap-east-1.compute.internal pppd[1506]: MPPE 128-bit stateless compression enabled
Aug 22 09:25:34 ip-172-31-28-246.ap-east-1.compute.internal pppd[1506]: Cannot determine ethernet address for proxy ARP
Aug 22 09:25:34 ip-172-31-28-246.ap-east-1.compute.internal pppd[1506]: local IP address 192.168.10.1
Aug 22 09:25:34 ip-172-31-28-246.ap-east-1.compute.internal pppd[1506]: remote IP address 192.168.20.10
When I running a fluentd td-agent to read the data from the tcp port 514 using tcp plugin but I find the error as,
2015-05-25 15:32:18 +0000 [info]: adding match pattern="tcp.events" type="stdout"
2015-05-25 15:32:18 +0000 [info]: adding source type="tcp"
2015-05-25 15:32:18 +0000 [error]: unexpected error error_class=Errno::EACCES error=#<Errno::EACCES: Permission denied - bind(2) for "0.0.0.0" port 514>
When I try to read the data from TCP port I find the data as
nc -l 514
<30>May 25 21:15:11 5gws056 docker/34cead996122[1865]: Hello Mon May 25 15:45:11 UTC 2015
<30>May 25 21:15:12 5gws056 docker/34cead996122[1865]: Hello Mon May 25 15:45:12 UTC 2015
<30>May 25 21:15:13 5gws056 docker/34cead996122[1865]: Hello Mon May 25 15:45:13 UTC 2015
<30>May 25 21:15:14 5gws056 docker/34cead996122[1865]: Hello Mon May 25 15:45:14 UTC 2015
<30>May 25 21:15:15 5gws056 docker/34cead996122[1865]: Hello Mon May 25 15:45:15 UTC 2015
Thanks in advance
Any port number under 1024 requires root permission. It's called privileged ports. Could you try with bigger port number?
Jmeter is taking always the same time to finish remote test. The jmx script is simple and there is no time configured on it, and there are just one request (only 84ms in local test).
It happens only on remote test, in local test is ok.
Starting the test on host x.x.x.x # Thu Aug 14 09:31:43 BRT 2014 (1408019503091)
Finished the test on host x.x.x.x # Thu Aug 14 09:34:43 BRT 2014 (1408019683082)
Starting the test on host x.x.x.x # Thu Aug 14 09:35:53 BRT 2014 (1408019753107)
Finished the test on host x.x.x.x # Thu Aug 14 09:38:53 BRT 2014 (1408019933091)
Starting the test on host x.x.x.x # Thu Aug 14 09:40:33 BRT 2014 (1408020033110)
Finished the test on host x.x.x.x # Thu Aug 14 09:43:33 BRT 2014 (1408020213100)
Starting the test on host x.x.x.x # Thu Aug 14 10:03:23 BRT 2014 (1408021403158)
Finished the test on host x.x.x.x # Thu Aug 14 10:06:23 BRT 2014 (1408021583154)
Starting the test on host x.x.x.x # Thu Aug 14 10:07:53 BRT 2014 (1408021673181)
Finished the test on host x.x.x.x # Thu Aug 14 10:10:53 BRT 2014 (1408021853164)
Starting the test on host x.x.x.x # Thu Aug 14 10:25:23 BRT 2014 (1408022723204)
Finished the test on host x.x.x.x # Thu Aug 14 10:28:23 BRT 2014 (1408022903204)
Starting the test on host x.x.x.x # Thu Aug 14 10:33:13 BRT 2014 (1408023193224)
Finished the test on host x.x.x.x # Thu Aug 14 10:36:53 BRT 2014 (1408023413225)
I can't make Apache/WAMP start after I removed a vhost, and it doesn't start after I restored the config. This is driving me nuts :)
Starting it from the command line doesn't give me anything.
C:\wamp\bin\apache\Apache2.2.11\bin>httpd.exe
C:\wamp\bin\apache\Apache2.2.11\bin>
Tried debug mode:
C:\wamp\bin\apache\Apache2.2.11\bin>httpd.exe -e debug
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module actions_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module alias_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module asis_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module auth_basic_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module authn_default_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module authn_file_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module authz_default_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module authz_groupfile_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module authz_host_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module authz_user_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module autoindex_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module cgi_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module dir_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module env_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module include_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module isapi_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module log_config_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module mime_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module negotiation_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module rewrite_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module setenvif_module
[Fri Sep 13 13:26:23 2013] [debug] mod_so.c(246): loaded module php5_module
C:\wamp\bin\apache\Apache2.2.11\bin>
But if I try to start it from Services, it actually says it fails. From the Windows Event log:
The Apache2.2 service terminated with service-specific error Incorrect function..
My first thought was that something (Skype) was using port 80, so I scanned open ports, but don't see it is being used:
C:\wamp\bin\apache\Apache2.2.11\bin>netstat -ano | findstr 80
TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING 980
TCP 127.0.0.1:4380 0.0.0.0:0 LISTENING 3768
TCP 192.168.1.18:1289 108.160.162.51:80 ESTABLISHED 3920
TCP 192.168.1.18:1677 204.62.114.180:443 ESTABLISHED 4608
TCP 192.168.1.18:1678 204.62.114.180:443 ESTABLISHED 4608
TCP 192.168.1.18:1679 204.62.114.180:443 ESTABLISHED 4608
TCP 192.168.1.18:1680 204.62.114.180:443 ESTABLISHED 4608
TCP 192.168.1.18:1681 204.62.114.180:443 ESTABLISHED 4608
TCP 192.168.1.18:2125 38.123.7.203:80 ESTABLISHED 4608
TCP 192.168.1.18:2126 38.123.7.203:80 ESTABLISHED 4608
TCP 192.168.1.18:2127 38.123.7.203:80 ESTABLISHED 4608
TCP 192.168.1.18:2128 76.74.254.123:80 ESTABLISHED 4608
TCP 192.168.1.18:2131 173.194.32.45:80 ESTABLISHED 4608
TCP 192.168.1.18:2136 173.194.32.57:80 ESTABLISHED 4608
TCP 192.168.1.18:2137 173.194.32.38:80 ESTABLISHED 4608
TCP 192.168.1.18:2138 66.155.9.250:80 ESTABLISHED 4608
TCP 192.168.1.18:2141 173.194.32.57:80 ESTABLISHED 4608
TCP 192.168.1.18:2143 23.3.90.208:80 ESTABLISHED 4608
TCP 192.168.1.18:2144 173.241.240.153:80 TIME_WAIT 0
TCP 192.168.1.18:2152 184.169.176.87:80 ESTABLISHED 4608
TCP 192.168.1.18:2161 107.21.38.221:80 ESTABLISHED 4608
TCP 192.168.1.18:2162 193.149.47.98:80 ESTABLISHED 4608
TCP 192.168.1.18:2166 66.155.9.250:80 ESTABLISHED 4608
TCP 192.168.1.18:2170 74.121.138.232:80 TIME_WAIT 0
TCP 192.168.1.18:2172 23.21.44.43:80 ESTABLISHED 4608
TCP 192.168.1.18:2173 173.192.220.64:80 ESTABLISHED 4608
TCP 192.168.1.18:2174 63.251.249.49:80 TIME_WAIT 0
TCP 192.168.1.18:2179 23.3.90.171:80 ESTABLISHED 4608
TCP 192.168.1.18:2180 23.3.91.115:80 ESTABLISHED 4608
TCP 192.168.1.18:2181 66.119.33.141:80 ESTABLISHED 4608
TCP 192.168.1.18:2182 63.251.249.50:80 TIME_WAIT 0
TCP 192.168.1.18:2186 23.21.44.43:80 ESTABLISHED 4608
TCP [::]:1026 [::]:0 LISTENING 980
UDP 169.254.129.250:60880 *:* 4724
UDP [fe80::212e:6fdb:926d:bd2a%10]:546 *:* 980
UDP [fe80::212e:6fdb:926d:bd2a%10]:1900 *:* 4724
UDP [fe80::212e:6fdb:926d:bd2a%10]:60876 *:* 4724
UDP [fe80::8835:6af0:18df:81fa%22]:546 *:* 980
UDP [fe80::8835:6af0:18df:81fa%22]:1900 *:* 4724
UDP [fe80::8835:6af0:18df:81fa%22]:5353 *:* 1820
UDP [fe80::8835:6af0:18df:81fa%22]:60877 *:* 4724
Sorry for the super long question. Hope somebody knows what might be going on!