Question

I'm getting a "The page cannot be displayed" randomly throughout my website intermittently. I cannot figure out the cause of the problem and it is driving me insane. It seems to frequently happen when I am submitting an edit or creating a username and confirming the registration. If I simply refresh the "The page cannot be displayed" page I am brought to the intended destination/page. Any ideas?

Environment

-- BrianMahoney - 06 Jul 2007

Answer

If you answer a question - or have a question you asked answered by someone - please remember to edit the page and set the status to answered. The status is in a drop-down list below the edit box.

What does the apache log say?

-- ArthurClemens - 06 Jul 2007

I'm not getting anything useful out of the apache log - all it says is that some images do not exist, once i inserted the images I still run into the same blank page / page cannot be displayed issues.

Some errors that I have encountered in the apache2 error log \tCGI::Carp::realdie('ERROR: \tCGI::Carp::die('ERROR: etc...

However rarely any of these errors correspond to the point in time when the blank page/ page cannot be displayed error occurs, which makes me think the TWiki code believes what is happening is in fact not an error at all. What is strange is how a simple refresh fixes the issue.

-- BrianMahoney - 09 Jul 2007

Do you have duplicate entries in Apache's access log in the cases where a refresh fixes the issue? If yes: Does the first entry return a 500 status code? Only in this case we would have to investigate TWiki internals. If both entries have a 200 status code, then apparently the first response got lost - if there's only one entry, then it looks loke the request has been lost. Some possibilities are in the network: Are there any caches / proxies / accelerators involved? Are your data on a NFS share?

If there's any chance that the die errors are related, please paste the whole stack, it may have some hints for possible error sources.

-- HaraldJoerg - 09 Jul 2007

I think I may have fixed it - it appears that the blank pages occur due to the Apache KeepAlive setting - I turned this off and I have not encountered another error - If I do I will paste the error log at the end of the day. Thank you all for your help & time!

-- BrianMahoney - 09 Jul 2007