Debian Lenny Php Error Log
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more debian squeeze php about Stack Overflow the company Business Learn more about hiring developers or posting
Php 5.4 Debian Squeeze
ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site debian squeeze php update for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise
Ubuntu Php Error Logs
to the top Where are the PHP error logs stored on a Debian 8 “Jessie” server? up vote 0 down vote favorite I know this question has been asked many times before, and I've looked at all the answers but they don't seem to work for me. I am trying to check if the error log is turned on for PHP, so I went to the php.ini file and uncommented php error log location the line in the picture seen below. I tried using the "whereis" command to find where php_error.log is but it returned a line that had "php_error: " and nothing else. Is that the correct way to view/turn on the php error logs? If not how do I and can I redirect them to an easier folder to access such as my home folder? Also, I understand that there are many different types of errors, but do I need to configure all of their paths or do they automatically go to the same error log? As a side note I have apache2 installed. I've seen a lot of questions relating php and apache2 and I'm not sure why so does the way to handle error logging? Thanks linux debian php error-logging share|improve this question edited May 17 at 15:48 kostix 1,6801614 asked May 17 at 13:08 Michael 1306 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote The problem is that there are multiple ways to run PHP scripts when they are accessed via a web server, and logging depends on that. To rephrase, whatever runs PHP, maintains the logging. On my Jessie (Debian 8) systems I run PHP using php5-fpm and
Powered by phpBB Forum Software © phpBB Group
times disabling logging on a busy websites is quite beneficial, especially if more than few Gigabytes are written in Apache visitors log (access.log) every http://www.pc-freak.net/blog/disable-apache-accesslog-errorlog-logging-debian-linux-freebsd/ day. Too much visitors to Apache webserver could pose significantly increase disk writes and be negative for overall server performance. Disabling the log is handy also for websites which already integrate a https://wiki.davical.org/index.php/Problems_and_Solutions different type of visitors logging lets say - via MySQL, PostgreSQL (SQL) … From security perspective disabling logging is a very stupid idea thought, however on systems which are experiencing high load error log and you need to sacrifice logging to reduce a bit the load (especially if you cannot afford to get a new server hardware), disabling it is an option. 1. Disabling access.log and error on Debian Linux a) Disabling access.log logging As most Debian users already know on Debian GNU Linux Apache logs all incoming (port 80) Apache requests to /var/log/apache2/access.log and /var/log/apache2/error.log Disabling php error log logging is very simple, just comment out line in /etc/apache2/sites-enabled/000-default:
CustomLog ${APACHE_LOG_DIR}/access.log combined
to
#CustomLog ${APACHE_LOG_DIR}/access.log combined
Then restart the webserver to re-read new config value:
# /etc/init.d/apache2 restart
....
Of course this is one of the ways to disable access.log logging. Other ways are to make logging gets logged in good old /dev/null. To use /dev/null forwardingp put Customlog /dev/null in /etc/apache2/sites-enabled/000-default
CustomLog /dev/null
In Debian Lenny and older Debian releases Customlog Apache directive is found in /etc/apache2/apache2.conf. b) Disabling error.log logging Same procedure applies for disabling error.log, comment out default ErrorLog directive, restart Apache and you're done:
ErrorLog ${APACHE_LOG_DIR}/error.log
should become:
ErrorLog /dev/null
Usually just comming ErrorLog ${APACHE_LOG_DIR}/error.log is supposed to work, unfortunately for reason on Debian Squeeze this worked not commenting it and restarting Apache failed to restart apache with error:
# /etc/init.d/apache2 restart
Restarting web server: apache2 ... waiting (2)No such file or directory: apache2: could not open error log file /etc/apache2/logs/error_log.
Unable to open logs
Action 'start' failed.
Rights 1.3.1 Database on Local Server 1.3.2 Database on Remote Server or non-default port 1.4 I have to log in to every page 1.5 I get a blank page 2 Authentication 2.1 HTTP authentications fails on me 3 DB Errors During Upgrade 3.1 Permission Denied errors during Upgrade 4 Upgrading from Debian Lenny to Squeeze Installation Database-script fails because of missing libraries (No Perl YAML) During the installation process DAViCal runs the database upgrade script in order to apply the correct permissions for the application and dba users to the database tables and sequences. The most common reason that this program might not work is that you don't have the YAML library for Perl installed. For Debian and related distributions you should install the libyaml-perl and libdbd-pg-perl packages - they should arealdy be there if you installed the .deb because it is a dependency. For RedHat and related distributions there should be a simple way to find an RPM of the package. Otherwise you should visit CPAN and install the YAML libraries manually. Note: this error can also occur on Fedora systems even though YAML and DBD::Pg are installed. Type "yum install -y perl-YAML perl-DBD-Pg" (as root) to install them if they're not already present. Note: on OpenBSD 4.8 the DBI module may need to be installed along with YAML and DBD::Pg. Unix Socket Directory The PostgreSQL default for the unix_socket_directory variable is /tmp. DAViCal expects the Debian path of /var/run/postgresql. Other distributions and bugs in Debian/Ubuntu can lead you to get the wrong path. Change the unix_socket_directory variable in /etc/postgresql/8.4/main/postgresql.conf. The error message that would be triggered by this would look something like: DBI connect('dbname=davical','davical_dba',...) failed: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? at /usr/share/davical/dba/update-davical-database line 244 Can't connect to database davical at /usr/share/davical/dba/update-davical-database line 244 You will see this error if the user you are trying to run the dba/create_database.sh script as cannot access the database in order to create database users for the application and create the 'davical' database. No Database Rights There are several variations on resolving the issue: Database on Local Server (you need to grant access to it) Database on Remote Server (you need to tell the scr