数据库有连接时候就报错
数据库平时是很好的，，现在有个应用要连接数据库就会报错
麻烦帮忙看看
10:10:38mt_aio_wait(423d8688)
10:10:38chunkio(3, 0x183b0000, 0x7, 0, 0x1, 1109682472, 33) errno 1
AIOREQ *a
429261a8: 00000000 00000000 00000000 00000000 ........ ........
429261b8: 00000000 00000000 d0873d42 70ee3c42 ........ ..=Bp.<B
429261c8: 00000000 00000000 b40c0000 41494f72 ........ ....AIOr
429261d8: 65710000 00000000 d1070000 00000000 eq...... ........
429261e8: 03000000 01080000 01000000 02000000 ........ ........
429261f8: 01000000 00000000 01000000 08873d42 ........ ......=B
42926208: 00000000 01000000 09000000 01000000 ........ ........
42926218: 00000000 00000000 00000000 ........ ....
10:10:38
10:10:38Informix Dynamic Server Version 9.40.UC1 Software Serial Number AAA#B000000
10:10:38Assert Failed: Checkpoint Page Write Error. (1)
10:10:38 Who: Session(1, informix@dbser, 0, 0x423b8018)
Thread(6, main_loop(), 42387018, 1)
File: rsrecvr.c Line: 1551
10:10:38 Results: Dynamic Server must abort
10:10:38 Action: Please notify Informix Technical Support.
10:10:38Stack for thread: 6 main_loop()
base: 0x42916000
len: 69632
pc: 0x085cfa2b
tos: 0x42925fc0
state: running
vp: 1
0x085cfa2b (oninit)afstack (0x429042a0, 0x4601e59e, 0x429265c8, 0x85cefd2, 0x88746c0, 0x3b3)
429261a8: 00000000 00000000 00000000 00000000 ........ ........
429261b8: 00000000 00000000 d0873d42 70ee3c42 ........ ..=Bp.<B
429261c8: 00000000 00000000 b40c0000 41494f72 ........ ....AIOr
429261d8: 65710000 00000000 d1070000 00000000 eq...... ........
429261e8: 03000000 01080000 01000000 02000000 ........ ........
429261f8: 01000000 00000000 01000000 08873d42 ........ ......=B
42926208: 00000000 01000000 09000000 01000000 ........ ........
42926218: 00000000 00000000 00000000 ........ ....
10:10:38
10:10:38Informix Dynamic Server Version 9.40.UC1 Software Serial Number AAA#B000000
10:10:38Assert Failed: Checkpoint Page Write Error. (1)
10:10:38 Who: Session(1, informix@dbser, 0, 0x423b8018)
Thread(6, main_loop(), 42387018, 1)
File: rsrecvr.c Line: 1551
10:10:38 Results: Dynamic Server must abort
10:10:38 Action: Please notify Informix Technical Support.
10:10:38Stack for thread: 6 main_loop()
base: 0x42916000
len: 69632
pc: 0x085cfa2b
tos: 0x42925fc0
state: running
vp: 1
0x085cfa2b (oninit)afstack (0x429042a0, 0x4601e59e, 0x429265c8, 0x85cefd2, 0x88746c0, 0x3b3)
0x085cefe0 (oninit)afhandler(0x3, 0x42926698, 0x42b51fa0, 0x4213afa8, 0x601, 0x1)
0x085cea65 (oninit)afcrash_interface(0x42926698, 0x42b51fa0, 0x4213afa8, 0x8833333, 0x60f, 0x42b51f60)
0x083dc17f (oninit)ckptwrite(0x4601e59e, 0x0, 0x42926728, 0x83db3c2, 0x7, 0x61a8)
0x083db478 (oninit)checkpoint(0xa, 0x6, 0x0, 0x0, 0x0, 0x10084380)
0x080f3e13 (oninit)main_loop(0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
0x085b4980 (oninit)startup (0x0, 0x42927670, 0x42927058, 0x670, 0x8524ed39, 0x0)
0x00000000 (*nosymtab*)0x0
10:10:38 See Also: /tmp/af.3eee59e, shmem.3eee59e.0
---------------------------------
Begin System Alarm Program Output
---------------------------------
Assertion Failure Type: CRASH
Host Name: dbser
Database Server Name: dbser
Time of failure: Thu Mar 22 10:10:38 CST 2007
AF file: /tmp/af.3eee59e
Shared memory file: None
System Blocking: OFF finderr -27001
好象是说client的连接太多导致的，，
hen you encounter this error on the client side, it indicates that a
network I/O error occurred when the client tried to connect to a
database server. Probably the connection attempt timed out because the
database server or the network was very busy, too many clients were
attempting to connect to the database server simultaneously, or the
database server was taken off-line during the connection attempt.
If this error occurs frequently on a database server that runs on a
host with multiple processors, you might want to tune the database
server by increasing the number of poll threads and/or listener
threads.
那么我想问问，，怎样可以增加 threads and/or listener
threads. 和网络无关，aio写出问题了。你的磁盘没问题吧？ 每次把wap那台服务器启动就会导致数据库服务器出现以下情况的。
就算数据库刚起来，再启动wap服务器也是这样。，，立即处于
22:59:37Informix Dynamic Server Stopped.
22:59:44Informix Dynamic Server Started.
Fri Mar 23 22:59:45 2007
22:59:45Event alarms enabled.ALARMPROG = '/usr/informix/etc/alarmprogram.sh'
22:59:45Booting Language <c> from module <>
22:59:45Loading Module <CNULL>
22:59:45Booting Language <builtin> from module <>
22:59:45Loading Module <BUILTINNULL>
22:59:50Informix Dynamic Server Version 9.40.UC1 Software Serial Number AAA#B000000
22:59:50Informix Dynamic Server Initialized -- Shared Memory Initialized.
22:59:50Physical Recovery Started at Page (2:2273).
22:59:50Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored.
22:59:50Logical Recovery Started.
22:59:5010 recovery worker threads will be started.
22:59:53Logical Recovery has reached the transaction cleanup phase.
22:59:53Logical Recovery Complete.
0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks
22:59:54Dataskip is now OFF for all dbspaces
22:59:54Checkpoint Completed:duration was 0 seconds.
22:59:54Checkpoint loguniq 18, logpos 0x4b46018, timestamp: 618458860
22:59:54Maximum server connections 0
22:59:54On-Line Mode
23:00:23Checkpoint Completed:duration was 0 seconds.
23:00:23Checkpoint loguniq 18, logpos 0x4b47018, timestamp: 618461043
23:00:23Maximum server connections 1
23:10:23Checkpoint Completed:duration was 0 seconds.
23:10:23Checkpoint loguniq 18, logpos 0x4b48018, timestamp: 618461048
23:10:23Maximum server connections 1
Sat Mar 24 00:03:31 2007
00:03:31listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
00:04:03listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
00:10:00Booting Language <spl> from module <>
00:10:00Loading Module <SPLNULL>
00:10:01Checkpoint Completed:duration was 0 seconds.
00:10:01Checkpoint loguniq 18, logpos 0x4b49018, timestamp: 618461115
00:10:01Maximum server connections 1
00:10:01Level 0 Archive started on rootdbs, phydbs, logdbs, pordbs, jpldbs, datadbs1
00:11:26Archive on rootdbs, phydbs, logdbs, pordbs, jpldbs, datadbs1 Completed.
00:11:27Process exited with return code 127: /bin/sh /bin/sh -c /usr/informix/etc/alarmprogram.sh 2 16 "Archive completed: 'rootdbs, phydbs, logdbs, pordbs, jpldbs, d
00:14:07listener-thread: err = -408: oserr = 0: errstr = : Invalid message type received from the sqlexec process.
00:20:23Checkpoint Completed:duration was 0 seconds.
00:20:23Checkpoint loguniq 18, logpos 0x4b4b018, timestamp: 618461147
00:20:23Maximum server connections 1
00:42:13listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
00:57:24listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:08:06listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:09:24listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:11:03listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:11:17listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:11:32listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:19:09listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:20:23listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:20:31listener-thread: err = -408: oserr = 0: errstr = : Invalid message type received from the sqlexec process.
01:21:54listener-thread: err = -408: oserr = 0: errstr = : Invalid message type received from the sqlexec process.
01:22:30listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:25:29listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:26:41listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:27:43listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:29:04listener-thread: err = -25580: oserr = 0: errstr = : System error occurred in network function.
01:30:16listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:31:11listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:34:20listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:35:41listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:35:46listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
02:10:24I/O read chunk 1, pagenum 7, pagecnt 1 --> errno = 9
02:10:24Assert Failed: Checkpoint Page Write Error. (1)
02:10:24Informix Dynamic Server Version 9.40.UC1
02:10:24 Who: Session(1, informix@dbser, 0, 0x423b8018)
Thread(6, main_loop(), 42387018, 1)
File: rsrecvr.c Line: 1551
02:10:24 Results: Dynamic Server must abort
02:10:24 Action: Please notify Informix Technical Support.
02:10:24stack trace for pid 14791 written to /tmp/af.3ee1810
02:10:24 See Also: /tmp/af.3ee1810, shmem.3ee1810.0
03:30:37Error writing '/tmp/shmem.3ee1810.0' errno = 28
03:30:38rsrecvr.c, line 1551, thread 6, proc id 14791, Checkpoint Page Write Error. (1).
03:30:38invoke_alarm(): /bin/sh -c '/usr/informix/etc/alarmprogram.sh 5 6 "Internal Subsystem failure: 'MT'" "rsrecvr.c, line 1551, thread 6, proc id 14791, Checkpoint Page Write Error. (1)." '
03:30:38invoke_alarm(): mt_exec failed, status 32512, errno 0
03:30:39The Master Daemon Died
03:30:39invoke_alarm(): /bin/sh -c '/usr/informix/etc/alarmprogram.sh 5 6 "Internal Subsystem failure: 'MT'" "The Master Daemon Died" '
03:30:39invoke_alarm(): mt_exec failed, status 32512, errno 0
03:30:39PANIC: Attempting to bring system down
03:46:27Informix Dynamic Server Started.
Sat Mar 24 03:46:28 2007
03:46:28Event alarms enabled.ALARMPROG = '/usr/informix/etc/alarmprogram.sh'
03:46:28Booting Language <c> from module <>
03:46:28Loading Module <CNULL>
03:46:28Booting Language <builtin> from module <>
03:46:28Loading Module <BUILTINNULL>
03:46:32Informix Dynamic Server Version 9.40.UC1 Software Serial Number AAA#B000000
03:46:32Informix Dynamic Server Initialized -- Shared Memory Initialized.
03:46:32Physical Recovery Started at Page (2:2273).
03:46:32Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored.
03:46:32Logical Recovery Started.
03:46:3210 recovery worker threads will be started.
03:46:35Logical Recovery has reached the transaction cleanup phase.
03:46:35Logical Recovery Complete.
0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks
03:46:36Dataskip is now OFF for all dbspaces
03:46:36Checkpoint Completed:duration was 0 seconds.
03:46:36Checkpoint loguniq 18, logpos 0x4b4d018, timestamp: 618461171
03:46:36Maximum server connections 0
03:46:36On-Line Mode
03:51:52listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
If you are using IBM Informix Dynamic Server, IBM Informix Universal Server, or
IBM Informix OnLine Dynamic Server, verify that the database server is still
online. If you are using IBM Informix SE, verify that the sqlexecd daemon for the
database server is still running. Use either or both of the environment
variables INFORMIXCONTIME and INFORMIXCONRETRY on the client side to increase
the connection time and number of retry attempts.
When you encounter this error on the database server side, it is a
warning that a network I/O error is detected while the database server
is accepting a connection request from a client. This error usually
occurs when the database server or the network is very busy or when too
many clients are trying to connect to the database server at once. The
database server might be taking so long to respond to a client that the
client's connection request timed out before the connection is
complete. Or possibly a client terminated its connection attempt before
the connection is completely established.
If this error is seen only occasionally in the server message log, it
is just a warning. No corrective action is required on the server
side.
If this error occurs frequently on a database server that runs on a
host with multiple processors, you might want to tune the database
server by increasing the number of poll threads and/or listener
threads.
$ finderr 408
-408 Invalid message type received from the sqlexec process.
This internal error indicates a problem in the communication between the
database server and the library functions that call it. Make sure that
your program software is compatible with the database engine in use.
This error can also occur if the CSM option is enabled on the database
server side but not on the client application side, or vice versa. If you
want to use a CSM, make sure that the CSM option is set in the sqlhosts
file for both the database server and client application.
This error can also occur if the confidentiality option of the CSM is
enabled on the database server side but not on the client application
side, or vice versa. If you want to use the confidentiality option of the
CSM, make sure that the confidentiality option is set for both the
database server and client application. Check your sqlhosts file and CSS
configuration file.
If the error recurs, note all circumstances and contact
Technical Support at tsmail@us.ibm.com. 原帖由 wolfop 于 2007-3-23 15:21 发表
和网络无关，aio写出问题了。你的磁盘没问题吧？
磁盘是没有问题的，平时直接从别的机器拷贝大量数据到数据库服务器的磁盘上还是很好的。
页:
[1]