Menu

error.log is very large - how do i clean it

Help
2011-11-01
2013-05-30
  • George Scott

    George Scott - 2011-11-01

    my error.log file has become quite large.  How do I refresh it or clean it?

     
  • Gerry Kroll

    Gerry Kroll - 2011-11-02

    What error.log?  There's no such file in the PGV system itself.

    PGV does, however, have a log file that records certain activity, such as logins, hack attempts, etc.  You can configure PGV to start a new log file every day or every week.  This is part of the site configuration.

     
  • George Scott

    George Scott - 2011-11-13

    The file is in /public_html/phpgedview/error_log 
    The current size is 237.59 Mb and shows as active every time I log in.  It just keeps growing.  I certainly haven't created it, so it must somehow be part of the system.  I also have small error.log files in :
    /public_html/phpgedview/media/Global/custPage/error_log  and
    /public_html/phpgedview/pages/error_log

     
  • George Scott

    George Scott - 2011-11-13

    Note.  message should be error_log not error.log  The error_log has not file type when I look at it with cPanel File manager

     
  • Gerry Kroll

    Gerry Kroll - 2011-11-13

    Sorry, I still can't help you.  There's absolutely NO reference to a file called "error_log" anywhere in PhpGedView.  What version of PGV are you running?

    You'll have to download that error_log file and then inspect it to see what sort of error messages are being recorded in that file.  It looks as if the server's software, other than PhpGedView, is recording or creating that file.

    Why don't you use cPanel file manager to rename the file (while PGV is not running, of course), and then launch PGV.  If there are legitimate error messages in the file, the server's OS should recreate the error_log file before recording anything.  This should result in a much smaller file with more meaningful messages in it.

     
  • George Scott

    George Scott - 2011-11-14

    renaming and restarting caused the system to build a new error_log file.  Contents look like this:
    PHP Warning:  session_start() :

    open(/tmp/sess_xxGOOGLEBOTfsHTTPcffWWWdGOOGLxx, O_RDWR) failed: Permission denied (13) in

    /home/hestonsc/public_html/phpgedview/includes/session.php on line 368
    PHP Stack trace:
    PHP   1. {main}() /home/hestonsc/public_html/phpgedview/individual.php:0
    PHP   2. require() /home/hestonsc/public_html/phpgedview/individual.php:30
    PHP   3. require_once() /home/hestonsc/public_html/phpgedview/config.php:76
    PHP   4. session_start() /home/hestonsc/public_html/phpgedview/includes/session.php:368
    PHP Warning:  session_start() : Cannot send session cookie -

    headers already sent by (output started at /home/hestonsc/public_html/phpgedview/includes/functions/functions.php:500) in

    /home/hestonsc/public_html/phpgedview/includes/session.php on line 368

    I have no idea where this is coming from, but I'll just clear it out every now and then.  Thanks.

     
  • Gerry Kroll

    Gerry Kroll - 2011-11-15

    This is BAD.

    Your problem is that the /tmp directory does not have proper permissions.  The PHP system is not able to create any temporary files there.  You need to report this problem to the support folks at your hosting provider.

    You can work around this problem by changing the configuration of PhpGedView to point at an alternative directory where the session files can be created and stored.

    Launch PGV and sign in as a user with site admin rights.  Click on the "Admin" menu option, and then within that menu click on "Configuration" to launch the Install wizard.  The wizard should start at step 4:  "Site Configuration".  Click on the "Advanced Settings" tab.  The "Session save path" option is normally blank.  Change this to "./index/" and then click "Next" until the configuration file has been saved.

    Note that this is a work-around.  The correct solution is to fix the system configuration by setting the permissions on the Session Save path directory mentioned in php.ini.  777 permission (universal read/write/modify) is required.

     

Log in to post a comment.