Error when adding or updating an entry

[vazquezjm]

Hi.

I get the following error when I create a new entry or edit an existing one:

Not Found

The requested URL /faq/admin/index.php was not found on this server.

I doesn't happen all the time. The thing is I can not detect the cause. I'm using version 1.6.6 (it also happened with 1.6.4)

TIA

[matteo]

Hi,

I doesn't happen all the time. The thing is I can not detect the cause. I'm using version 1.6.6 (it also happened with 1.6.4)

it seems an error derived from a network hickup: is that server on internet and are you connecting to it via a dialin connection?

Regards,
Matteo

[vazquezjm]

Hi Matteo.

Yes, the server is on the Internet and I'm connecting from my office thru cablemodem.

[matteo]

Hi,

Yes, the server is on the Internet and I'm connecting from my office thru cablemodem.

Since it is a cable modem I think that that kind of hickup could be triggered only by "abusing" the bandwidth offered by your modem: try to see if the issue will be arised when many people is supposed to produce much traffic to the internet. if yes, the only solution is to prioritize your network traffic and give you the rigth to overcome others' traffic .

Ciao,
Matteo

[vazquezjm]

Tried from another location and the same thing happed. Also, this was not happening a month ago when we populated the database (manually, using the editor).

Anyway, I don't get what "network hiccups" are.

Thx

[matteo]

Hi,
just suppose that someone is disconnecting your network cable just for <1sec .

Maybe the issue is related with your hosting provider: have you a dedicated server? Have you a SLA for network availability?

Ciao,
Matteo

[vazquezjm]

Yes, I have a dedicated server with many other services running without problems.

Let's suppose it is a network hiccup, how can only this happens when updating an entry?

Thx

[matteo]

Hi,

how can only this happens when updating an entry?

we need to discover together the answer .
I'm guessing that there is no issue on PMF code: when you submit/update an entry you're using HTTP POST to deliver the data.
In my experience I've seen such issues when the client is connected to the network through a Content Filtering Proxy and when the process of filtering clients' requests is too long compared to the connection timeout of the Web Server, something similar to your issue happens.
Are you directly connected to your server?

Ciao,
Matteo

[vazquezjm]

Ok. No, I'm connecting thru a firewall (HotBrick), but I also tried it with another connection (at home) where I only have a Linksys router.

Can you guide on how to check the connection parameters? Or what information do I need to look for on the Apache config file?

Thanks

[matteo]

Hi,

Can you guide on how to check the connection parameters?

You need to check if your firewall/router has any transparent caching proxy capability, ONLY IF you don't have any proxy settings in your "LAN settings..." e.g. for IE.

Or what information do I need to look for on the Apache config file?

You need to look at the values of:

• Timeout, http://httpd.apache.org/docs/1.3/mod/core.html#timeout;
• KeepAlive;
• MaxKeepAliveRequests;
• KeepAliveTimeout, http://httpd.apache.org/docs/1.3/mod/co ... ivetimeout

Ciao,
Matteo

[vazquezjm]

Values are:

Timeout 120
KeepAlive Off
MaxKeepAliveRequests 100
KeepAliveTimeout 15

Thx

[Johannes]

For me this looks like some problem with the webserver configuration, but I can'T say for sure what the problem might be. Can you check wether you get redirected to another (virtual) host (is it the right domain name in the browser's adress bar?). Can you check the error_log of the webserver, there you should find the exact filename it tries to find and check whether a file with such a name exists?

Another idea might be that your server is running mod_Securit being configured to send such an error in case it detects an possible attack, that should be found in the error_log, too.

[matteo]

Hi,
thanks Johannes for pointing out also mod_security as the reason of the issue
I did not cite it 'cause the HTTP error seems to be something different from that usually used by this module (HTTP Status 406). BTW, the error is configurable so it could be also 404: vazquezjm, find here a topic among the others talking about mod_security effects: basically, if mod_security is causing the issue then you cannot submit any form containing content that triggers any mod_security rule regarding HTTP GET/POST payload.
It is the next check you must perform 'cause the values for timeout are reasonable and cannot be the cause of your issue.

Ciao,
Matteo