WordPress.org

Plugin Directory

Changeset 753414


Ignore:
Timestamp:
08/08/13 09:15:12 (9 months ago)
Author:
Strictly Software
Message:

Updated the readme.txt file with debug information and checked the system is working on Wordpress 3.6

Location:
strictly-system-check/trunk
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • strictly-system-check/trunk/readme.txt

    r730538 r753414  
    66Requires at least: 2.0.2 
    77Tested up to: 3.5.2 
    8 Stable tag: 1.0.3 
     8Stable tag: 1.0.5 
     9 
    910 
    1011Strictly System Check is a plugin that periodically checks your site checking your database and server and reporting if any problems are found. 
     
    1617the ability to regularly check the status of their site and to be notified if the site goes down or becomes overloaded. 
    1718 
    18 I created this plugin initially for my own use as on one of my sites I regularly import content from XML feeds and I noticed that occasionally 
    19 after a large update my site would suffer problems such as: 
     19I created this plugin initially for my own use as on one of my sites I regularly import content from XML feeds and I noticed that occasionally after a large update my site would suffer problems such as: 
    2020    * Error establishing a database connection, error appearing when I tried to access the site even though the configuration was correct. 
    2121    * All my articles and other content disappearing from the site. 
    2222    * A high server load that didn't reduce quick enough after the import had finished 
    2323 
    24 I soon realised that this was down to one or more of the MyISAM database tables in the MySQL database becoming corrupted which meant that the tables 
    25 were out of action, data couldn't be retrieved and requests to the system were quickly building up. Running a REPAIR statement on the database 
    26 always seemed to fix the problem. Therefore as I wasn't always able to catch this problem when it occurred I thought I would automate a process that would 
    27 check the homepage at regular intervals and on finding the database connection error it would then check the database for corrupt tables and 
    28 automatically repair them.  
     24I soon realised that this was down to one or more of the MyISAM database tables in the MySQL database becoming corrupted which meant that the tables were out of action, data couldn't be retrieved and requests to the system were quickly building up. Running a REPAIR statement on the database always seemed to fix the problem. Therefore as I wasn't always able to catch this problem when it occurred I thought I would automate a process that would check the homepage at regular intervals and on finding the database connection error it would then check the database for corrupt tables and automatically repair them.  
    2925 
    3026This was the primary reason for the plugin and I soon extended it to offer some more features such as 
     
    4036whenever these limits are reached or if the site is inaccessible. 
    4137 
    42 The report will return details of the response time it took to load the page, the current server load, the current database load and whether or not 
    43 there were connection problems, issues with corrupt tables that needed repairing or fragmented indexes that were optimized. 
     38The report will return details of the response time it took to load the page, the current server load, the current database load and whether or not there were connection problems, issues with corrupt tables that needed repairing or fragmented indexes that were optimized. 
    4439 
    45 Whilst not a replacement for professional server monitoring tools it is a nice easy to use plugin that can help notify you when your site is down 
    46 as well as rescuing your system from corrupt database tables before you even realise there has been an issue. 
     40Whilst not a replacement for professional server monitoring tools it is a nice easy to use plugin that can help notify you when your site is down as well as rescuing your system from corrupt database tables before you even realise there has been an issue. 
    4741 
    4842== Installation == 
     
    56505. Use the newly created Admin option within Wordpress titled Strictly System Check to set the configuration options for the plugin. 
    57516. Use the Test Configuration button to ensure that your plugin will work correctly. 
    58 7. Set up a CRON job or WebCron job to run the system checker at intervals of your choice. The plugin will display the correct code and URL's to use 
    59    for any CRON job. 
     527. Set up a CRON job or WebCron job to run the system checker at intervals of your choice. The plugin will display the correct code and URL's to use for any CRON job. 
    6053 
    6154 
    6255Help  
    6356 
    64 1. You may need to grant write/execute permission for the plugin folder to the website so that the configuration file and report can be written out correctly. 
    65    The plugin will give you the correct CHMOD code to run to grant these permissions. 
     571. You may need to grant write/execute permission for the plugin folder to the website so that the configuration file and report can be written out correctly. The plugin will give you the correct CHMOD code to run to grant these permissions. 
    6658 
    67 2. To access the current webserver load averages the website will need to be able to run system functions such as e.g shell_exec, system, passthru. 
    68    If you are running you own server or virutal server this shouldn't be a problem but if you are on a shared server you might have to ask your systme administrator 
    69    to set the relevant permissions for you to be able to do this. The Test Configuration button will tell you whether or not this is a problem. Even if you cannot 
    70    run system functions the plugin will still be able to report on key info such as whether the site is up or down and whether the database is overloaded or not. 
     592. To access the current webserver load averages the website will need to be able to run system functions such as e.g shell_exec, system, passthru. If you are running you own server or virutal server this shouldn't be a problem but if you are on a shared server you might have to ask your systme administrator to set the relevant permissions for you to be able to do this. The Test Configuration button will tell you whether or not this is a problem. Even if you cannot run system functions the plugin will still be able to report on key info such as whether the site is up or down and whether the database is overloaded or not. 
     60 
     613. If you have problems with the plugin then please read the help section and do not contact me. This plugin is free and if you are not willing to pay for support or features then use the help forums for any issues. The plugin works perfectly well on my server a LINUX Virtual Server with the latest version of WordPress. If you are having problems then you need to do the obvious things to resolve them such as: 
     62    -Rule out other plugins causing problems by only running this plugin. Uninstall all others and run this on it's own, then re-install the others one by one until you rule out either this or another plugin as the problem. 
     63    -Turn the WP_DEBUG contant on in wp-config.php and check for error messages 
     64    -Turn on my own DEBUGSYSCHECK constant in strictly-system-check.php to show my own messages on the screen and work out whats wrong from that. 
     65    -Ensure that you have granted all your files permissions, that your site can make HTTP requests, access system information etc. However the "Test Config" button would check all these anyway.  
     66    -If you cannot run the "Test Config" button then you have a different problem and sending me a screenshot of a white page isn't going to help in any shape or form. If that is the problem then you can either debug the issue yourself or choose to pay me to do it, but I would need full access to your site and server. However my time is expensive. 
     67 
    7168 
    7269 
     
    8683= 1.0.3 = 
    8784* Added code to handle REPAIRS if the database is overloaded 
    88 * Added extra logging for the REPAIRS if they are carried out OR not carried out 
     85* Added extra logging for the REPAIRS e.g if they are carried out OR not carried out 
    8986* Tested with latest version of Wordpress 3.5.2 
     87 
     88= 1.0.4 = 
     89* Added code to only OPTIMIZE if the server load is above a certain level 
     90* Added code to run DB checks if the page load is too slow 
     91* Added nonces and is_admin checks to the admin page 
     92 
     93= 1.0.5 = 
     94* Ensured the system works with Wordpress 3.6 
     95* Updated Readme.txt with information on how to debug any problems 
  • strictly-system-check/trunk/strictly-system-check.class.php

    r730537 r753414  
    44class StrictlySystemCheck{ 
    55 
    6     protected $version              = "1.0.3"; 
     6    protected $version              = "1.0.5"; 
    77 
    88    private static $instance; 
  • strictly-system-check/trunk/strictly-system-check.php

    r730537 r753414  
    33/** 
    44 * Plugin Name: Strictly System Check 
    5  * Version: 1.0.3 
     5 * Version: 1.0.5 
    66 * Plugin URI: http://www.strictly-software.com/plugins/strictly-system-check/ 
    77 * Description: This plugin will enable you to setup a cron job to periodically check the status of your wordpress site and auto fix any database related issues. This is useful for sites that import articles reguarly from feeds as you can experience corrupt tables on a regular basis especially after large bulk updates. 
Note: See TracChangeset for help on using the changeset viewer.