Tag Info

Hot answers tagged

8

The documentation states that add_header "Adds the specified field to a response header provided that the response code equals 200, 204, 206, 301, 302, 303, 304, or 307. A value can contain variables." So it doesn't work with a 502. I forgot to add that you can use the third party headers more module to add headers to other codes. You'll probably have to ...


8

Take a look at IIS7's Failed Request Tracing feature: Troubleshooting Failed Requests Using Tracing in IIS 7 Troubleshoot with Failed Request Tracing The other thing I would do is tweak your <httpErrors> setting because IIS may be swallowing an error message from further up the pipeline: <configuration> <system.webServer> ...


3

Restarting IIS because of a 500 response is about the same as cracking an egg with a hefty swing of a sledgehammer. You are not going to solve this problem with a restart, you are going to have to solve your problem by figuring out what is causing the 500 and correcting it. Automatically restarting the server on a 500 is not a resolution to the problem. ...


3

It's something to do with session cookies and how the site handles them. First pass, no session cookie at my end, $ wget --load-cookies cookies --save-cookies cookies --keep-session-cookies -S http://motherscarehawaii.teamvision.biz/ --2011-07-21 21:37:05-- http://motherscarehawaii.teamvision.biz/ Resolving motherscarehawaii.teamvision.biz ...


3

We use a combination of log formats in nginx and lmon to catch things like this. An NGINX log format like: log_format main '$status:$request_time:$upstream_response_time:$pipe:$body_bytes_sent $connection $remote_addr $host $remote_user [$time_local] "$request" "$http_referer" "$http_user_agent" "$http_x_forwarded_for" $upstream_addr ...


3

error_log $filename debug; will turn on debug level logging into the error log -- this will give you lots and lots of details of nginx's internal status at the time of the error, and if compiled with --with-debug (which several distros do by default) it'll give even more. Be warned that the "debug" level really does generate lots of output, to the point ...


3

Within your virtual host conf (or httpd.conf/apache2.conf) you can use the ErrorDocument directive, as follows: ErrorDocument 500 /errordocs/500error.php It's inadvisable to do too much in your 500 error page, as you could hit the same error condition that caused the 500 response in the first place!


3

Run a2enmod rewrite /etc/init.d/apache2 restart And it will load the rewrite module for you the error you are seeing is not because you dont have permissions to use rewrite but because its not available as can be seen from the a2dismod list output you provided (its not appearing in the list)


2

7 is "time up" and 14 is "EOF", so the root cause of this is probably a read timeout during the upload. The 70000 prefix means they are APR status codes. They are logged poorly here because they the core of apache is expecting a different type of error code then what is returned -- these are APR or "filter" return codes but the core of httpd is expecting a ...


2

All you need to do is add the following to your web.config OR, for those using Classic ASP, just create a web.config file in your ROOT with this code in it. <configuration> <system.webServer> <asp scriptErrorSentToBrowser="true"/> <httpErrors errorMode="Detailed"/> </system.webServer> </configuration>


2

This is interesting because the logs state that a redirect is happening, but you do not have any rules which use the [R] flag. However, when a rule includes http://... the [R] flag is redundant, so the RewriteRule ^(.*)$ http://mydomain.com/$1 rule is the likely candidate for causing the problem. If I were you, I would try putting [R=301,L] at the end ...


2

First: tail -f /var/log/httpd/error_log not error.log Check your apache config file for a line with LogLevel I would suggest LogLevel error until you figure out the error. warn/debug might be too verbose


2

Whenever a web-server reports error 500 I look in the server's error log for a detailed reason. The following look useful http://mvolo.com/blogs/serverside/archive/2007/07/26/Troubleshoot-IIS7-errors-like-a-pro.aspx http://learn.iis.net/page.aspx/266/troubleshooting-failed-requests-using-tracing-in-iis-7/


2

The error is going into your log file, but not printed to the server error displayed. This is intentional, because it prevents possibly-sensitive information from being exposed to attackers. (Pathname information, database schemas, possibly something exploitable about the bug that caused the error itself....) You can either just look at the php error log ...


2

1) Changes to .htaccess files will take effect immediately. If you are being advised to edit the .htaccess files this suggests that your .htaccess files may contain php_values or php_flags that will need to be removed. For example your .htaccess file may contain php_value upload_max_filesize 10M This example could then be added to a php.ini file like ...


2

@Richard Holloway is correct about the .htaccess files. Changes take effect immedietly. As for the error logs, GoDaddy has a specific way of accessing them: http://help.godaddy.com/article/1197 To View Error Logs Log in to your Account Manager. In the My Products section, select Hosting. Next to the hosting account you want to modify, ...


2

Why are you using location =? I'm fairly certain that isn't what you want. On the other hand, that shouldn't be causing your redirect loop, as I understand it, but it certainly won't be helping you get what you want. Enable nginx debugging (error_log ... debug or error_log ... debug_http if you've got an nginx built correctly) to see what nginx is doing ...


2

SOLVED: Alas, there is a load balancer controlling the server, and the load balancer was set up to stop connections after 10 seconds of inactivity or so. The problem is solved now. The reason the 500 did not show up in the apache's error.log is that it was the "outer" system (the load balancer) stopping the connection, not the server itself. Thank you all ...


2

I have spoken to a Dev on httpd mailing list and he confirmed that this feature has not been implemented in the current code base. I have also reviewed the code myself. The state machine inside mod_proxy_balancer cannot retry on HTTP error but can only do so in case of connection error. I tried to implement it myself but its too complicated and I can easily ...


2

The server is running the PHP file. Execution of the PHP is stopping when it can't load something it's including. If you get it to ignore those errors, it'll simply error later on in execution, when it actually tries to use what it tried to load with the include. If you don't actually need what the include statements are loading, then remove them from ...


2

If I understand correctly, you want to catch the 500 error status in the logs while presenting a regular error looking page to your customers and scanners. Some web shops do this to "hide" the more serious errors on their website from attackers. A page which generates a 500 error status may be a good target in a DOS attack. Scan the site to find the page ...


2

Optimizing memory footprint is usually done by reducing (and limiting) these factors: count of simultaneous Apache processes (I'd recommend switching to prefork MPM, which is kindof more controllable in memory-limited environs) moving away from mod_php or php_cgi to fastcgi, mod_cfgid works fine. Reducing the count of allowed spawned php processes by ...


1

This is a general error message. Pls take a look at the event log on server to view detailed error message. Make sure the Url you specified in code is correct. Pls go through following url for more details and fix, http://miserrors.blogspot.in/2010/10/systemnetwebexception-remote-server.html


1

Drupal itself changes the error reporting and display settings which happens after the ini file (where your settings reside) is processed. To change the settings after drupal does you can add error_reporting(E_ALL); ini_set('display_errors', TRUE); ini_set('display_startup_errors', TRUE); to index.php. Drupal is complex. The blank white page is ...


1

I finally found the solution (at this page); indeed, the problem was related to rewriting. I modified my virtual host like this: RewriteEngine On RewriteCond %{REQUEST_URI} !^/error-50[0-3].html$ RewriteRule ^/(.*) http://localhost:8080/... (in my case, I get a status 503 when Zope is down; my condition is ready for more specific messages as well). Since ...


1

It's possible that there is a bug in the app which is crashing the app pool. If you don't see anything useful in the applicaiton event log the try looking in the IIS log file and see what resource the last few requests were for right before the service stops responding. That is, find the entries that have a success response code (200, 301, 304, etc) that ...


1

I would definitely argue it is possible if your 404 page was built using a dynamic language like PHP, ASP, etc. (anything beyond what is considered just markup language). The introduction of a dynamic language introduces a wealth of ways in which a page can fail (threading problems, memory management problems, resource locking problems, etc.)...some of which ...


1

My bet is that the files in that the files in /home/newuser/domains/joomlasite.com/public_html/ are owned by root. It looks like you're using suPHP which will run the PHP files as the same user as owns the files. The min_uid restriction is there to make sure that suPHP isn't run as root or another system user inadvertently. The fastest fix will probably be ...


1

The issue you're having is because of this line here: DirectoryIndex / Basically, what that says is, when you access http://localhost, display /--which will then display /, etc.. DirectoryIndex should specify a file; when you access a directory, if that file exists, then it displays that. So if you had: DirectoryIndex cgit.cgi Then when you access ...


1

The first port of call when you encounter 500 errors in PHP is to check the PHP error log; if a 500 error is not reported by apache then it is caused by PHP. To check if you're hitting resource limits, enable and watch the apache server-status.



Only top voted, non community-wiki answers of a minimum length are eligible