I am trying to use Squid's (its 2.7STABLE8 version) reverse proxy service on Windows 7. When I try to start squid from "cmd" (as administrator) I get an error message such as;
"The Squid service could not be started
A system error has occurred
System error 1067 has occurred message
The process terminated unexpectedly"
To solve it I tried:
setting "http_port" to 80 and 8080
disabling user account control settings.
and followed the instructions on this website: Configuring a Basic Reverse Proxy in Squid on Windows
However, none of the solutions worked. Therefore if there is any other solution you might know it would be great.
Thanks
I checked my cache.log file, and it was reporting to;
"FATAL: ipcache_init: DNS name lookup tests failed"
Therefore, in the squid.conf file I set my dns_testname to;
"dns_testnames 0.0.0.0"
and it solved my problem.
Try this to check:
squid -k check
I had the same issue.
Just in case it helps someone, I got the same problem and was low disk space.
I made some cleanup and went back on in seconds.
Thanks.
when I check logs, I saw there is not "logs" folder under "c:\squid\var". after I create "logs" folder under there, it starts working. please make sure you have "c:\squid\var\logs"
My error it was the same.
My solution was: check the log in C:\squid\var\logs in the file chache, and i found this;
commBind: Cannot bind socket FD 14 to 192.168.3.12:3128: (10049) WSAEADDRNOTAVAIL, Cannot assign requested address.
FATAL: Cannot open HTTP Port
In a last time, i change the dir IP of my server, this was the origin of my trouble. In the file C:\squid\etc\squid.conf i change it again, and it solve of my.
Related
I've been struggling with this issue for 2 days now and it's starting to be a big problem.
we have 2 LB on which HAproxy is installed,
I've tried to change the certificats on the first one and it fell down and couldn't restart it even when getting back the old haproxy.cfg file.
after a while I tried to restart the server and it did the job. I had my Haproxy running on the failed node. and I successfully changed the ssl certificats on that one.
Then, I tried to do the same on the second, and then it went down and nothing seem to be correcting the problem; not restarting haproxy on the old haproxy.cfg file nor restarting the whole server.
the error I get is like this :
Starting frontend PAGEMAINTENANC_GUN: cannot bind socket [10.168.10.16:80]
Can you please give me some little help?
thank you all in advance.
It seems that I've been trying to bind to an IP address that is not local. That's why the HAproxy fails to start. The solution was to set ip_nonlocal_bind to 1.
To get info:
sysctl net.ipv4.ip_nonlocal_bind
Set net.ipv4.ip_nonlocal_bind to 1
sysctl -w net.ipv4.ip_nonlocal_bind=1
Restart HAproxy works
So I created a new Cpanel using WHM I set the quota to 50MB and the bandwidth to 50MB as well. And I also uploaded the web files to public_html on cpanel successfully but when I load the website, an error that says This webpage is not available ERR_CONNECTION_TIMED_OUT appear.
Here's the status screenshot.
And here's the screenshot of the files I uploaded.
But still I get the error. Did I missed something?
Since it is connection timed out, definitely it is related to firewall. Do you have any firewall installed like CSF ? If so please try to check if your ISP IP (you can get ISP IP from http://whatismyip.com ) is blocked in the firewall.
Another possiblity is your server is having Selinux enabled. To disable that please try to
setenforce 0
Another possiblity is server is having some default iptables rules
iptables -L -n
If the above command is showing rules, then try to stop it
service iptables stop
Let me know how it goes
I'm trying to set up Apache directory studio in my mac, but however when i try to create a connection i get this error "Apache directory studio 'Open connection' has encountered a problem".
I'm following this tutorial, http://directory.apache.org/studio/users-guide/ldap_browser/gettingstarted_create_connection.html. Any help is really appreciated.
A connection being refused will likely mean that either the address and port you are connecting to is being blocked or filtered for whatever reason, or nothing is running on the specified address and port.
I had the same issue with the error,
ldap: error code 49 - INVALID_CREDENTIALS: Bind failed
The cause for this issue is, I had changed the port from 10389 to 10390. Hence, it is trying to connect to old port.
When I changed the 'Connections' port to update value (Ex: 10390) and start the server, the issue resolved.
I got the same error of shutdown unexpectedly. I tried everything.
I uninstalled skype.
I tried changing the ports to 81,444 / 81,443 / 88/443 / 80,443(default).
I went to services and tried killing required one.
I went to windows firewall and created the new inbound rule too.
I uninstalled old apache and installed new one too. This worked for 1 day.
I checked whether the port 80 is busy or not but none of the services is using port
80,443. I used netstat -a command to check all the list of port for Win-8.
I tried stopping windows http services by "NET STOP HTTP".
I unchecked "Internet Information Services" from program and features.
I checked "Resource Monitor" for port usage. Port 80 is being used by HTTP server only
but not responding to xampp control panel.
In all of the above cases, I made the changes and restarted the laptop every time to take the effect. But nothing has worked. Each time i got the same error i.e "XAMPP, Apache - Error: Apache shutdown unexpectedly".
Please give me the solution for this error. I am very much frustrated now. Please help me. Any help would be appreciable. Thank you in advance.
It would be good if you enable Apache Logs in debug mode.
LogLevel debug
Also you can get easily notified for syntax issues with help of below command.
httpd -t
For your skype, go to Tools -> Options -> Advanced -> connection. Disable the "Use port 80 and 443 for alternatives for incoming connections"
Sign Out and Close all Skype windows. Try restart your Apache again.
Everything was going alright, no edits have been done on the configurations, suddenly the httpd stopped running on start up, and another service made by me as well.
one information that the hard disk reached his full space so I had to delete some files.
the result of chkconfig --list is
httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
If httpd fails to start up, you should be able to find an error message in the error-log (/var/log/httpd/error_log or wherever you have configured its errors to). Check what gets logged when you manually try to start the service ("service httpd start") and get back with more information if you don't understand what it is trying to tell you.
If hard disk was full that would be the first reason of apache service not starting. Did you try restarting httpd service after freeing up some sufficient disk space and please also check the httpd error logs in /var/log/httpd/error.log. I think the major problem would have been due to disk space got full.
Try to free up some log files also to free up some more space in /var/log directory.
In my case it was a problem in log configuration:
AH00015: Unable to open logs
(1)Operation not permitted: AH00091: httpd: could not open error log file /usr/teste.localhost-error.log.
I Changed my log path, created the file into my path setted and it worked after restarting.