Tag Info

Hot answers tagged

6

If you're running a default configuration of Apache on Ubuntu (or have used the default config as a blind template for other virtualhost directives) you'll likely find that you have a ScriptAlias directive mapping /cgi-bin/ (relative to the apache document root) to the filesystem location of /usr/lib/cgi-bin/ - so what they're actually trying to load is ...


5

There are the locations in these popular operating systems: RHEL / Red Hat / CentOS / Fedora Linux Apache error file location - /var/log/httpd/error_log Debian / Ubuntu Linux Apache error log file location - /var/log/apache2/error.log FreeBSD Apache error log file location - /var/log/httpd-error.log The detailed answer about the Apache log files is here: ...


5

Apache keeps its log files open so deleting a log file stops apache from logging to it, since the old file descriptor now points to a deleted inode. You should rotate/delete/truncate the log file, re-create it with the correct ownership and permissions, and then issue an apachectl graceful to reload. Alternatively, apache can log errors to syslog; this ...


5

This clearly shows there are read errors on a hard drive, due to media errors. See what e.g. # smartctl --all /dev/sda turns up.


4

I have a small doubt that its related to my HDD. I have no doubt that it is related to your hard disk. The error messages say so in about as many ways as they can (naming ata1.00 & dev sda). Your drive is throwing media errors. This almost certainly means it is dying (which you can confirm using the SMART information Jeff's answer mentioned). Make ...


4

The clamd server doesn't appear to be running. Try starting it.


4

The boot messages come in two parts: those that come from the kernel (loading drivers, detecting partitions, etc) and those that come from the services starting up ([ OK ] Starting Apache...). The kernel messages are stored in /var/log/kern.log and can also be accessed from the kernel's own log buffer with the dmesg program. The userspace messages are not ...


4

From some researching I did, these are some possibilities leading to 408 message. You can test each to identify the relevant one for your case. 1) Very low Apache TIMEOUT value - your web server could be ending the session before the client even get the chance to send a request. too many 408 error codes in access log 2) browser predictive optimization - ...


3

This tool called logrotate, which is designed to ease administration of systems that generate large numbers of log files. It allows automatic rotation, compression, removal, and mailing of log files. Each log file may be handled daily, weekly, monthly, or when it grows too large. With this tool you keep logs longer with less disk space. for more details you ...


3

It appears that you have exposed your SQL Server to the internet, and now you are seeing brute-force attempts from the internet to log in with the well-known SQL account sa. I don't know your business needs, but consider adjusting your firewall so that the only IP that is able to reach your database server is your web server, for instance. Edit: If your ...


3

Somebody is trying to exploit a PHP weakness to execute system commands. The results of these will end up in the apache error log, since that is where stderr points for the PHP processes. If you see them occuring live(-ish), investigate the named PID and see what it is; though it's probably apache, if you're running the prefork MPM you can see precisely ...


3

It's telling you that mod_aspdotnet has loaded v2 of the .NET framework. It's not an error - unless you were expecting it to load in a different version of .NET, of course!


3

The ErrorLog directive can not be used multiple times. You should configure syslog to keep a local copy.


3

If there is no harm in making the apache error log readable by all others on your system you chmod o+r /var/log/apache2/error.log Edit /etc/logrotate.d/apache2 and look for or add a line that says create 640 root adm and change that also to something appropriate like create 644 root adm. It would be less secure to put everyone in the group of the ...


3

If I understand your question correctly, you want to send the errors (not output) to a logfile, and also send them via email. To do this, use a combination of tee and stdout/stderr redirection. According to the cron(8) manpage, cron can handle the email for you. No need to duplicate this effort needlessly. When executing commands, any output is mailed ...


3

To get that question out of the unanswered list: @BHare: The problem was a combination of not having the right privledges to /var/log/apache2 and also not using integers for a local error_reporting


2

I mostly use EventID.net to check event log entries, have you used EventID.net already?


2

Edit: nano /etc/lighttpd/lighttpd.conf And put: fastcgi.debug = 1


2

grep "CRON" /var/log/syslog


2

Use tee: MBPro-ABustardo:~ abustardo$ echo foo |tee tmp foo MBPro-ABustardo:~ abustardo$ cat tmp foo in your case: [your script] 2>&1 |tee [some local local file] |mail -s [subject] foo@example.com


2

The location of the error log is in your config file, which is probably located at /etc/lighttpd/lighttpd.conf. Look for the server.errorlog line. If it's still set to default, the log is probably at /var/log/lighttpd/error.log.


2

Try this: error_reporting = E_ALL | E_STRICT error_log = /var/log/php_errors.log Create log file manually touch /var/log/php_errors.log chown www-data: /var/log/php_errors.log chmod +rw /var/log/php_errors.log Now you can view PHP errors by this way tail /var/log/php_errors.log


2

sed -i '/favicon.ico/d' error_log But you can get rid of this error appearing in Apache error log by creating an empty favicon.ico file in document root or putting the following in the httpd.conf file: Redirect 404 /favicon.ico <Location /favicon.ico> ErrorDocument 404 "No favicon" </Location>


2

there is a field on pingdom with the details of the previous error; you can get the content of the error message; that should give you a clue as to whether the requests are 4xx/5xx errors, or whether it was some network problem for your ISP or Hosting company


2

You want to tune /proc/sys/kernel/printk if you need the messages off your console. And yes, these messages means your hard drive or hard drive cabling are severely bust.


2

If you don't get an ASP.NET error page ("Yellow Screen of Death"), then that typically suggests that IIS encountered an error before it managed to fire up the ASP.NET engine. IIS will usually show a more elaborate error page if you access the site from a browser running on the server running the site (i.e. from a non-remote client). Often, this is a problem ...


2

You're going to need to reinstall the old libraries somehow, either by finding the SSL package online (like here) and downloading it to the server somehow (good luck with that), then running dpkg -i libssl0.9.8_0.9.8o-4squeeze13_amd64.deb to install the package again.


2

Well, most of this is moot because the original question is a mess, but the StorageWorks MSA 50 is an HP device and looks to be accessed using an HP controller (probably a Smart Array P600 or P800 SAS RAID controller)... This is denoted by the CCISS block device naming; /dev/cciss/cXdYpZ In this case, your MSA 50's storage is presented at ...


2

Bootup messages pass by so fleetingly that, for some, one might not be sure what they say. You may wish to check all the files where they might be logged, in addition to the usual (well-known) log files, for verification purposes (at least). On Debian, logs generally are kept in directory /var/log. After booting, what changed there today (which files) can ...


2

Error logging should not have significant impact on your MySQL performance, as there shouldn't be many of them. If you've got enough errors for logging to impact performance, the solution is to fix the errors, not ignore them. You have relatively low CPU load and low memory usage. Do some benchmarking to find out what's making your site slow instead of ...



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