Table of Contents
Administration page of your instance
Get to your administration page
The administration page of your instance is accessible via your instance's control panel at Gandi or directly at this URL:
xxxxxx is replaced by the unique number of your instance).
You will then see a username (the username is that same number), and password, which is the one you chose when you set up your instance.
You will then see a page like the following screenshot:
You may change this, however, to suit your needs. To see how to customize it, go here.
The available information
Viewing the Logs
You can view the logs of your instance in order to locate the source of a problem occurring on your website(s).
Logs available for consultation are:
- error.log: Contains all errors related to the Apache Web server. It is recommended to verify these logs regularly to detect possible configuration problems (bad directives on
.htaccess, missing index files, and so on).
admin-error.log: PHP logs executed on the admin part of your instance.
fpm.log: Logs related to the PHP interpreter. It's here that you can see if the max number of PHP processor is reached.
www-error.log:PHP logs executed on the public part of your instance.
MySQL (Database) logs:
error.log: Logs related to the MySQL server. You can view tables which have crashed and been repaired.
slow-queries.log: Here you can view the queries that take an unusually long time to execute. This can occur in the case where some tables are locked.
Understanding the logs
[Thu Jun 14 12:08:45.199853 2012] [mpm_event:notice] [pid 186:tid 3557842618176] AH00489: Apache/2.4.1 (Unix) configured -- resuming normal operations [Thu Jun 14 12:08:45.199869 2012] [core:notice] [pid 186:tid 3557842618176] AH00094: Command line: '/usr/sbin/apache2 -d /srv/data/.config/apache -f /srv/data/.config/apache/apache2.conf -D lamp0-1' [Thu Jun 14 15:08:45.213486 2012] [mpm_event:notice] [pid 186:tid
This lines indicates that the web server has been started.
This alert occurs when PHP-FPM has reached the maximum number of simultaneous processes for PHP. The maximum number of simultaneous process is defined in terms of the size of your instance (2 on a pack S, 4 on a M, 8 on a L …). If this error occurs too frequently, you should consider increasing the size of your instance Simple Hosting. When you see [pool www], it is the number of processes running on the public part of your instance, [pool admin] denotes the admin part of the proceedings.
This alert is not an error and can be ignored.
120614 16:09:59 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use GCC atomic builtins InnoDB: Compressed tables use zlib 1.2.6 120614 16:09:59 InnoDB: Initializing buffer pool, size = 8.0M 120614 16:09:59 InnoDB: Completed initialization of buffer pool 120614 16:09:59 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 120614 16:09:59 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 120614 16:10:00 InnoDB Plugin 1.0.17 started; log sequence number 2657932 120614 16:10:00 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.1.61-2' socket: '/srv/run/mysqld/mysqld.sock' port: 0 (Debian)
Indicates that MySQL has been started.
120614 16:04:45 [ERROR] /usr/sbin/mysqld: Table './wp/wp_comments' is marked as crashed and should be repaired 120614 16:04:45 [Warning] Checking table: './wp/wp_comments' 120614 16:04:45 [ERROR] /usr/sbin/mysqld: Table './wp/wp_links' is marked as crashed and should be repaired 120614 16:04:45 [Warning] Checking table: './wp/wp_links' 120614 16:04:45 [ERROR] /usr/sbin/mysqld: Table './wp/wp_options' is marked as crashed and should be repaired 120614 16:04:45 [Warning] Checking table: './wp/wp_options'
During startup of MySQL, the tables of your database are checked; if the tables seem to have crashed, MySQL tries to repair them automatically.