This usually improves server performance, but must be turned off when serving from networked-mounted filesystems or if support for these functions is otherwise broken on your system. Improve this question. Lakshya sharma Lakshya sharma 21 2 2 bronze badges. Add a comment. Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.
Email Required, but never shown. The Overflow Blog. Podcast Explaining the semiconductor shortage, and how it might end. Does ES6 make JavaScript frameworks obsolete? Featured on Meta. Now live: A fully responsive profile. Linked 2. A "file not found" type of condition is a perfectly normal, if somewhat notable, operation of any Web server and should not be logged at an error level on par with internal Web server problems. I'm attaching a new diff fixing all the places I can find.
In context, in case it helps this be recognized as a real bug: Mozilla, IE, et al. If it's generating an HTTP error, as is the case in all the instances in your patch, then it's an error and should be logged as such.
I think there's a question of priorities here, which is why this bug was submitted in the first place. Certainly I can't be the only site admin seeing bazillions of logged messages simply because of missing static content, which flood out all the other truly important errors.
That's just Wrong. It is an error and from an admin perspective I want to see it at the error level and I do not want to be forced to increase the loglevel verbosity for doing this.
If I do not want to see these "file not found messages" for further analysis I filter them out with grep -v.
Furthermore it is important to keep this message at the error level for backwards compatibility to avoid breaking error analysis scripts. I give up. Comment 9 Jay Freeman UTC Let me rephrase this problem: the fact that this error setting works this way is an opening for a denial of service attack on the disk space of the server.
When you are dealing with a high traffic site it is very important that nothing an end user can do can cause disk space to get used in proportion to activities they perform. On my server, I get tens of thousands of s every day, and I'm not even a "large" website I only have a couple million users. If a user wanted to mess with me, they'd just start requesting s off my server until I run out of disk space.
Connect and share knowledge within a single location that is structured and easy to search. I have a Bugzilla 4. It was able to send email without issue up until about a month ago after about three months without issue. If someone posts a comment, a new bug or anything else that should generate an email, after they hit submit the following page takes forever to time out but eventually comes back with "Internal Server Error".
Whatever they happen to be trying to do succeeds bug gets created, file attached, comment posted, etc , so it appears that the problem is solely with generating the email.
Following the official guide 's advice for troubleshooting I've created any errorlog but the output is nebulous at best:. I've verified that SELinux isn't the issue by switching it into Permissive for the full duration of this troubleshooting, and I've created simple perl scripts that send my personal email account when invoked over Apache httpd.
Basically, I'm unsure where to take it from here, I don't know how to get Bugzilla to give me more descriptive error information. I know that administratively I didn't change anything, there's plenty of processor time and storage space available, so I'm not sure why it all of a sudden broke. Look for the biggest file s generated by strace, they will likely be the strace of the apache process es in question:.
Can you increase the logging level within Apache? As follows: LogLevel info. Details are here. Can you send email from the box?
But Bugzilla is unable to send emails. It always reports "Could not authenticate user". How to know the details of the error? Everything we configured are working fine when used in another system. Can you please point out the location of the log file. If you're only having problems sending emails and you're getting authentication issues, the most probable cause for this is that your SMTP server requires authentication before it will let the server use it as a relay.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more.
0コメント