Thinkphp3.1 cache failure think3.1 + dwz system cache meaning write failed, permission and disk space check are no problem.
Deleting the cache can run normally for a period of time, and then this error occurs.
Porting to the new ubuntu system is normal for half a month.
Reply to discussion (solution)
This is clearly a failure to connect to mysql.
Restart ubuntu.
Check the error log
It should be because your mysql service is stopped or occupied by another program.
Mysql error log information
140807 9:44:59 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.140807 9:44:59 [Note] Plugin 'FEDERATED' is disabled.140807 9:44:59 InnoDB: The InnoDB memory heap is disabled140807 9:44:59 InnoDB: Mutexes and rw_locks use GCC atomic builtins140807 9:44:59 InnoDB: Compressed tables use zlib 1.2.3.4140807 9:44:59 InnoDB: Initializing buffer pool, size = 128.0M140807 9:44:59 InnoDB: Completed initialization of buffer pool140807 9:44:59 InnoDB: highest supported file format is Barracuda.140807 9:44:59 InnoDB: Waiting for the background threads to start140807 9:40:10 InnoDB: 5.5.38 started; log sequence number 2477014140807 9:40:10 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306140807 9:40:10 [Note] - '127.0.0.1' resolves to '127.0.0.1';140807 9:40:10 [Note] Server socket created on IP: '127.0.0.1'.140807 9:40:10 [Note] Event Scheduler: Loaded 0 events140807 9:40:10 [Note] /usr/sbin/mysqld: ready for connections.Version: '5.5.38-0ubuntu0.12.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
It should be because your mysql service is stopped or occupied by another program.
Check that mysql is started. this happens again in the morning, and it is restarted once.
Apache error log
[Thu Aug 07 09:44:29 2014] [warn] child process 1331 still did not exit, sending a SIGTERM[Thu Aug 07 09:44:29 2014] [warn] child process 2069 still did not exit, sending a SIGTERM[Thu Aug 07 09:44:29 2014] [warn] child process 2070 still did not exit, sending a SIGTERM[Thu Aug 07 09:44:31 2014] [notice] caught SIGTERM, shutting down[Thu Aug 07 09:44:59 2014] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.13 with Suhosin-Patch configured -- resuming normal operations[Thu Aug 07 09:45:59 2014] [error] [client 116.22.142.9] File does not exist: /var/www/dx/default, referer: http://218.20.201.217/index/system2.html[Thu Aug 07 09:46:00 2014] [error] [client 116.22.142.9] File does not exist: /var/www/dx/default, referer: http://218.20.201.217/index/system2.html[Thu Aug 07 09:46:08 2014] [error] [client 116.22.142.9] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 40961 bytes) in /var/www/dx/Library/Common/common.php on line 684, referer: http://218.20.201.217/index/system2.html[Thu Aug 07 09:46:22 2014] [error] [client 116.22.142.9] File does not exist: /var/www/dx/default, referer: http://218.20.201.217/index/system2.html[Thu Aug 07 09:51:37 2014] [error] [client 116.22.142.9] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 40961 bytes) in /var/www/dx/Library/Common/common.php on line 684, referer: http://218.20.201.217/index/system2.html[Thu Aug 07 09:51:48 2014] [error] [client 116.22.142.9] File does not exist: /var/www/dx/default, referer: http://218.20.201.217/index/system2.html
Is it a legendary false death.
It should be because your mysql service is stopped or occupied by another program.
Check that mysql is started. this happens again in the morning, and it is restarted once.
The best solution to reinstall mysql
Insufficient Memory
Find the reason, find the disk is deleted by the mysql-bin.00001 file occupies a lot of space, delete these files, restart mysql this situation, and then delete the mysql-bin.index to restart it will be okay