How To Generate PHP Error.log Files In The Directory Of Error
Jun 15, 2008
unable to get any php5 error logs
Here are my settings in the /etc/php5/apache2/php.ini file:
display_errors = On
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
error_log = /var/log/php5/error.log
However unfortunately I never see any error log being generated in the /var/log/php5/error.log file?
Also with my shared hosting site one thing which I noticed was, due to some configurations set by them, the error.log used to generate in the folder where the error occured. This is a cool thing which they used to do, but I just dont understand how did they do that.
When deploying new server/servergroup/cluster to your IT infrastructure, deployment (simplified) consist of following steps:
OS installation: to do it over network, boot server must be configured for this new server/servergroup/cluster,
configuration/package management: configuration server has to be aware of the newcomer(s),
monitoring and alerting: monitoring software must be reconfigured,
performance metrics: a tool for collecting data must be reconfigured.
There are many excellent software solutions for those particular jobs, say configuration management (Puppet, Chef, cfengine, bcfg2), monitoring hosts and services (Nagios, Zabbix, OpenNMS, Zenoss, etc) and performance metrics (Ganglia, etc). But each of these tools has to be configured independently or at least configuration has to be generated. What tools do you use to achieve this?
For example, when you have to deploy a new server, how do you create configs for, let's say, PXE boot server, Puppet, Nagios and Ganglia, at once?
I switched over a new host and everything was working perfectly. I then uploaded one last directory but it had a weird internal server error when trying to access the index.php file. I then googled it and changed directory permissions to 755, and I am not sure if it is a coincidence but now every site on my server with php files displays that error but html pages are fine.
I have moved my sites from old server with Apache 1.3 to new one with Apache 2.2.4. Since that time, the error log is full of these lines:
Code: [Wed Jul 04 05:36:32 2007] [error] [client 188.8.131.52] File does not exist: /home/domain/public_html/russia [Wed Jul 04 05:36:39 2007] [error] [client 184.108.40.206] File does not exist: /home/domain/public_html/russia [Wed Jul 04 05:36:45 2007] [error] [client 220.127.116.11] File does not exist: /home/domain/public_html/italy [Wed Jul 04 05:36:57 2007] [error] [client 18.104.22.168] File does not exist: /home/domain/public_html/mexico The access logs show even more accesses, so sometimes the same page is ok, sometimes it is logged here. The strange thing is that these files (pages) exist! They are accessible through the browser without any problem.
Do you have any idea where could be the problem? It would helped me lot, I am unable to find any real problem now, when error log is full of these.
My OS is Ubuntu 6.06. I use mod_rewrite through .htaccess. I can provide list of apache modules, if it helps.
I seem to have an error with backing up to my personal FTP repository. I have only just noticed the issue, but i believe it originated when I upgraded Plesk Panel 11 to Plesk Panel 12. I am currently running version 12.0.18 on Cent OS 6.5.
Note whether i check the "Use passive mode" option makes no difference to my problem.Below is what I get from the panel.log under /usr/local/psa/admin/logs
Since Microupdate 11.0.9 #52/#53 I get the following error from my scheduled backup:
<description>Failed to pack files back__domainname_mn_1306110314 in /var/lib/psa/dumps/xy/clients/xy/domains/domainname [ 945838637056 bytes free of 980876906496 bytes total on mount point 0]</description>
Some related problems have already been discussed here in the forum (e.g.: [URL] .... or this one: [URL] ...., but it all did not quite match with my problem.
--> Populating transaction set with selected packages. Please wait. ---> Package cadaver.i386 0:0.22.5-1.el5.rf set to be updated ---> Package mtr.i386 2:0.72-1.el5.rf set to be updated ---> Package rsync.i386 0:3.0.2-1.el5.rf set to be updated ---> Package nmap.i386 2:4.20-1.el5.rf set to be updated ---> Package lftp.i386 0:3.7.1-1.el5.rf set to be updated ---> Package syslinux.i386 0:3.63-1.el5.rf set to be updated ---> Package dkms.noarch 0:2.0.19-2.el5.rf set to be updated ---> Package subversion.i386 0:1.4.6-0.1.el5.rf set to be updated --> Running transaction check --> Processing Dependency: perl(Crypt:asswdMD5) for package: syslinux --> Finished Dependency Resolution Error: Missing Dependency: perl(Crypt:asswdMD5) is needed by package syslinux
Other Details: eth0: error fetching interface information: Device not found cp: cannot stat `/etc/apf.bk.last/vnet/*.rules': No such file or directory Imported options from 9.7-1 to 9.7-1. Note: Please review /etc/apf/conf.apf for consistency, install default backed up to /etc/apf/conf.apf.orig my host has said Code: edit the apf.conf file to venet0:0 instead of eth0 which ive done and im still getting the error, Ive pasted my current conf.apf config below
Code: #!/bin/sh # # APF 9.7 [email@example.com] # Copyright (C) 1999-2007, R-fx Networks <firstname.lastname@example.org> # Copyright (C) 2007, Ryan MacDonald <email@example.com> # This program may be freely redistributed under the terms of the GNU GPL # # NOTE: This file should be edited with word/line wrapping off, # if your using pico/nano please start it with the -w switch # (e.g: pico -w filename) # NOTE: All options in this file are integer values unless otherwise # indicated. This means value of 0 = disabled and 1 = enabled.
## # [Main] ## # !!! Do not leave set to (1) !!! # When set to enabled; 5 minute cronjob is set to stop the firewall. Set # this off (0) when firewall is determined to be operating as desired. DEVEL_MODE="1"
# The installation path of APF; this can be changed but it is not recommended. INSTALL_PATH="/etc/apf"
# Untrusted Network interface(s); all traffic on defined interface will be # subject to all firewall rules. This should be your internet exposed # interfaces. Only one interface is accepted for each value. IFACE_IN="venet0" IFACE_OUT="venet0"
# Trusted Network interface(s); all traffic on defined interface(s) will by-pass # ALL firewall rules, format is white space or comma separated list. IFACE_TRUSTED=""
# This option will allow for all status events to be displayed in real time on # the console as you use the firewall. Typically, APF used to operate silent # with all logging piped to $LOG_APF. The use of this option will not disable # the standard log file displayed by apf --status but rather compliment it. SET_VERBOSE="1"
# The fast load feature makes use of the iptables-save/restore facilities to do # a snapshot save of the current firewall rules on an APF stop then when APF is # instructed to start again it will restore the snapshot. This feature allows # APF to load hundreds of rules back into the firewall without the need to # regenerate every firewall entry. # Note: a) if system uptime is below 5 minutes, the snapshot is expired # b) if snapshot age exceeds 12 hours, the snapshot is expired # c) if conf or a .rule has changed since last load, snapshot is expired # d) if it is your first run of APF since install, snapshot is generated # - an expired snapshot means APF will do a full start rule-by-rule SET_FASTLOAD="0"
Usually everything has been working fine with this .htaccess-file until today. There hasn't been any change on the system.
If you click on the hyperlink to the restricted area the login window appears where you need to type in your username and a password. After typing in these data the following message appears in the browser:
500 Internal Server Error
The server encountered an internal error or misconfigruation and was unable to complete your request. (…)
The apache error log file contains the following message:
Request exceeded the limit of 10 sub request nesting levels due to probable configuration error.
Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
The increase of the LimitInternalRecursion does not solve the problem. So I switched the LogLevel in the httpd.conf file from warn to debug and looked again on the entries of the error log.
The following appeared (I have replaced ip addresses, usernames and URL by xyz or <URL>) :
[error] [client xyz] mod_digest_apple: Client is using a nonce not issued by this server for this context:/rb/Vorlesung/WS12/Downloads/, referer: http:<URL>