禅道没两周左右，会无法登陆，需要重启服务器已解决悬赏5积分

提问者雷宇答案数1 阅读数3326 发表时间2016-07-06 16:17:19

每次报错的原因，查看log：

commonModel::loadConfigFromDB(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "post_max_size" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in D:\xampp\htdocs\zentaopms\module\common\model.php on line 99 when visiting

禅道版本：8.0.1

安装包类型：源码包

操作系统：Windows Server 2008

客户端浏览器：Chrome

答案列表

禅道软件 2016-07-07 10:30:42

你通过<?php phpinfo();?>，看看post_max_size项，把这个改大一些试试。

10条回复

🍨

雷宇 2016/07/15

我将50M更改为300M，然后今天上午还是报了，有没有什么办法可以规避这个问题，主要是让数据库不要死掉。
下面是几次报错的log：
6月14日：
15:05:59 Trying to get property of non-object in D:\xampp\htdocs\zentaopms\module\mail\control.php on line 320 when visiting cron-ajaxExec

15:10:20 Creating default object from empty value in D:\xampp\htdocs\zentaopms\module\testtask\control.php on line 957 when visiting testtask-results-0-128398

15:10:59 Trying to get property of non-object in D:\xampp\htdocs\zentaopms\module\mail\control.php on line 320 when visiting cron-ajaxExec

15:16:00 Trying to get property of non-object in D:\xampp\htdocs\zentaopms\module\mail\control.php on line 320 when visiting cron-ajaxExec

15:17:38 commonModel::loadConfigFromDB(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "post_max_size" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in D:\xampp\htdocs\zentaopms\module\common\model.php on line 99 when visiting

7月6日：
14:54:16 Creating default object from empty value in D:\xampp\htdocs\zentaopms\module\testtask\control.php on line 959 when visiting testtask-results-104332

14:54:26 Creating default object from empty value in D:\xampp\htdocs\zentaopms\module\testtask\control.php on line 959 when visiting testtask-results-104331

14:54:45 Creating default object from empty value in D:\xampp\htdocs\zentaopms\module\testtask\control.php on line 959 when visiting testtask-results-104329

14:54:58 commonModel::loadConfigFromDB(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "post_max_size" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in D:\xampp\htdocs\zentaopms\module\common\model.php on line 99 when visiting

7月15日：
09:55:13 Only variables should be passed by reference in D:\xampp\htdocs\zentaopms\module\testtask\control.php on line 225 when visiting testtask-view-135

09:55:13 Only variables should be passed by reference in D:\xampp\htdocs\zentaopms\module\testtask\control.php on line 225 when visiting testtask-view-135

09:55:32 Undefined offset: 1 in D:\xampp\htdocs\zentaopms\module\user\control.php on line 706 when visiting user-login-L215Lmh0bWw=

09:56:08 commonModel::loadConfigFromDB(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "post_max_size" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in D:\xampp\htdocs\zentaopms\module\common\model.php on line 99 when visiting

石洋洋 2016/07/15

300M 附件太大了，上传需要的时间肯定比较多，很容易超时的，超过50M就不推荐用网页上传，可以放到一个公共硬盘上，把访问方式写在禅道上。

🍨

雷宇 2016/07/15

之前默认是50M，300M是7月8日改的。
传超过限制的文件，应该会有提示，所以我不太确定是不是由于上传附件过大引起的我反馈的这个问题。
目前的主要问题是会导致数据库挂掉，需要重启服务，然后又不知道出现这个问题的原因，最终的目的是询问下出现数据库挂掉的原因的原因和解决方法。
PS：目前我司有大概100多个人员同时使用，且在多个部门，所以不太好调查时什么操作引发的这个问题

石洋洋 2016/07/15

找一下mysql的日志，看有什么错误记录。

🍨

雷宇 2016/07/18

没有看到有出错前的记录，都是出错后，我重启的信息:
6月14日：
2016-06-14 15:19:58 3148 [Note] d:\xampp\mysql\bin\mysqld.exe: Normal shutdown
2016-06-14 15:19:58 3148 [Note] Event Scheduler: Purging the queue. 0 events
2016-06-14 15:19:58 5056 [Note] InnoDB: FTS optimize thread exiting.
2016-06-14 15:19:58 3148 [Note] InnoDB: Starting shutdown...
2016-06-14 15:20:00 3148 [Note] InnoDB: Shutdown completed; log sequence number 1858505
2016-06-14 15:20:00 3148 [Note] d:\xampp\mysql\bin\mysqld.exe: Shutdown complete
2016-06-14 15:20:03 1ec InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2016-06-14 15:20:03 492 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-06-14 15:20:03 492 [Note] InnoDB: The InnoDB memory heap is disabled
2016-06-14 15:20:03 492 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-06-14 15:20:03 492 [Note] InnoDB: Memory barrier is not used
2016-06-14 15:20:03 492 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-06-14 15:20:03 492 [Note] InnoDB: Using generic crc32 instructions
2016-06-14 15:20:03 492 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-06-14 15:20:03 492 [Note] InnoDB: Completed initialization of buffer pool
2016-06-14 15:20:03 492 [Note] InnoDB: Highest supported file format is Barracuda.
2016-06-14 15:20:04 492 [Note] InnoDB: 128 rollback segment(s) are active.
2016-06-14 15:20:04 492 [Note] InnoDB: Waiting for purge to start
2016-06-14 15:20:04 492 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-76.0 started; log sequence number 1858505
2016-06-14 15:20:04 3096 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-06-14 15:20:04 492 [Note] Plugin 'FEEDBACK' is disabled.
2016-06-14 15:20:04 492 [Note] Server socket created on IP: '::'.
2016-06-14 15:20:04 492 [Note] d:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.10-MariaDB' socket: '' port: 3306 mariadb.org binary distribution

7月6日：
2016-07-06 15:05:47 3776 [Note] d:\xampp\mysql\bin\mysqld.exe: Normal shutdown
2016-07-06 15:05:47 3776 [Note] Event Scheduler: Purging the queue. 0 events
2016-07-06 15:05:48 3748 [Note] InnoDB: FTS optimize thread exiting.
2016-07-06 15:05:48 3776 [Note] InnoDB: Starting shutdown...
2016-07-06 15:05:50 3776 [Note] InnoDB: Shutdown completed; log sequence number 1879531
2016-07-06 15:05:50 3776 [Note] d:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2016-07-06 15:06:20 684 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2016-07-06 15:06:20 1668 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-07-06 15:06:20 1668 [Note] InnoDB: The InnoDB memory heap is disabled
2016-07-06 15:06:20 1668 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-07-06 15:06:20 1668 [Note] InnoDB: Memory barrier is not used
2016-07-06 15:06:20 1668 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-07-06 15:06:20 1668 [Note] InnoDB: Using generic crc32 instructions
2016-07-06 15:06:20 1668 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-07-06 15:06:20 1668 [Note] InnoDB: Completed initialization of buffer pool
2016-07-06 15:06:21 1668 [Note] InnoDB: Highest supported file format is Barracuda.
2016-07-06 15:06:29 1668 [Note] InnoDB: 128 rollback segment(s) are active.
2016-07-06 15:06:29 1668 [Note] InnoDB: Waiting for purge to start
2016-07-06 15:06:29 1668 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-76.0 started; log sequence number 1879531
2016-07-06 15:06:30 1668 [Note] Plugin 'FEEDBACK' is disabled.
2016-07-06 15:06:30 2264 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-07-06 15:06:30 1668 [Note] Server socket created on IP: '::'.
2016-07-06 15:06:30 1668 [Note] d:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.10-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2016-07-06 15:25:38 3188 [ERROR] mysqld.exe: Table '.\zentao\zt_taskestimate' is marked as crashed and should be repaired
2016-07-06 15:25:38 3188 [Warning] Checking table: '.\zentao\zt_taskestimate'

7月15日：
2016-07-15 10:01:39 3184 [Note] d:\xampp\mysql\bin\mysqld.exe: Normal shutdown

2016-07-15 10:01:39 3184 [Note] Event Scheduler: Purging the queue. 0 events
2016-07-15 10:01:39 3156 [Note] InnoDB: FTS optimize thread exiting.
2016-07-15 10:01:39 3184 [Note] InnoDB: Starting shutdown...
2016-07-15 10:01:41 3184 [Note] InnoDB: Shutdown completed; log sequence number 1884350
2016-07-15 10:01:41 3184 [Note] d:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2016-07-15 10:02:06 7b0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2016-07-15 10:02:06 1968 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-07-15 10:02:06 1968 [Note] InnoDB: The InnoDB memory heap is disabled
2016-07-15 10:02:06 1968 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-07-15 10:02:06 1968 [Note] InnoDB: Memory barrier is not used
2016-07-15 10:02:06 1968 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-07-15 10:02:06 1968 [Note] InnoDB: Using generic crc32 instructions
2016-07-15 10:02:06 1968 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-07-15 10:02:06 1968 [Note] InnoDB: Completed initialization of buffer pool
2016-07-15 10:02:06 1968 [Note] InnoDB: Highest supported file format is Barracuda.
2016-07-15 10:02:07 1968 [Note] InnoDB: 128 rollback segment(s) are active.
2016-07-15 10:02:07 1968 [Note] InnoDB: Waiting for purge to start
2016-07-15 10:02:07 1968 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-76.0 started; log sequence number 1884350
2016-07-15 10:02:07 3904 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-07-15 10:02:07 1968 [Note] Plugin 'FEEDBACK' is disabled.
2016-07-15 10:02:07 1968 [Note] Server socket created on IP: '::'.
2016-07-15 10:02:07 1968 [Note] d:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.10-MariaDB' socket: '' port: 3306 mariadb.org binary distribution

石洋洋 2016/07/18

mysql开启 InnoDB 引擎了？

🍨

雷宇 2016/07/18

之前用的Xampp3.2.1的集成包，但是出现Apache服务挂掉的问题，所以后来更新到Xampp3.2.2，里面的设置基本上没有改过，我看了mysql.ini里面，有关innoDB是这么写的：
# Comment the following if you are using InnoDB tables
#skip-innodb
innodb_data_home_dir = "D:/xampp/mysql/data"
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = "D:/xampp/mysql/data"
#innodb_log_arch_dir = "D:/xampp/mysql/data"
## You can set .._buffer_pool_size up to 50 - 80 %
## of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 16M
innodb_additional_mem_pool_size = 2M
## Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

石洋洋 2016/07/18

推荐用禅道的windows一键安装包试试。

🍨

雷宇 2016/07/18

之前用的时候，正式上线之后1~2天内高频率发生Apache服务挂掉的情况（Apache error log：AH00354: Child: Starting 1920 worker threads，事件查看器：错误应用程序名称: httpd.exe，版本: 2.4.4.0，时间戳: 0x5128aa4a，错误模块名称: php5ts.dll，版本: 5.5.0.0，时间戳: 0x51c24cf8），用了很多种方法尝试更改，都没效果，最后有论坛说是Apache和php版本兼容的问题，所以就更新到刚刚发的那个版本了，然后这个问题就没有了。
就怕换回去，上面那个问题又出来了。
本人对数据库这块不熟，有没有办法在哪些地方加一些调试信息，可以看出来是哪个用户做了哪些操作触发的这个问题，方便做下规避。

石洋洋 2016/07/19

这个比较难调试，你用的这个xampp不是我们的一键安装包，是xampp官方发布的版本，可以到xampp官方的论坛上提问一下问题看是否能给出解答方案。

联系我们