- 论坛徽章:
- 0
|
每次把wap那台服务器启动就会导致数据库服务器出现以下情况的。
就算数据库刚起来，再启动wap服务器也是这样。，，立即处于
22:59:37 Informix Dynamic Server Stopped.
22:59:44 Informix Dynamic Server Started.
Fri Mar 23 22:59:45 2007
22:59:45 Event alarms enabled. ALARMPROG = '/usr/informix/etc/alarmprogram.sh'
22:59:45 Booting Language <c> from module <>
22:59:45 Loading Module <CNULL>
22:59:45 Booting Language <builtin> from module <>
22:59:45 Loading Module <BUILTINNULL>
22:59:50 Informix Dynamic Server Version 9.40.UC1 Software Serial Number AAA#B000000
22:59:50 Informix Dynamic Server Initialized -- Shared Memory Initialized.
22:59:50 Physical Recovery Started at Page (2:2273).
22:59:50 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored.
22:59:50 Logical Recovery Started.
22:59:50 10 recovery worker threads will be started.
22:59:53 Logical Recovery has reached the transaction cleanup phase.
22:59:53 Logical Recovery Complete.
0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks
22:59:54 Dataskip is now OFF for all dbspaces
22:59:54 Checkpoint Completed: duration was 0 seconds.
22:59:54 Checkpoint loguniq 18, logpos 0x4b46018, timestamp: 618458860
22:59:54 Maximum server connections 0
22:59:54 On-Line Mode
23:00:23 Checkpoint Completed: duration was 0 seconds.
23:00:23 Checkpoint loguniq 18, logpos 0x4b47018, timestamp: 618461043
23:00:23 Maximum server connections 1
23:10:23 Checkpoint Completed: duration was 0 seconds.
23:10:23 Checkpoint loguniq 18, logpos 0x4b48018, timestamp: 618461048
23:10:23 Maximum server connections 1
Sat Mar 24 00:03:31 2007
00:03:31 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
00:04:03 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
00:10:00 Booting Language <spl> from module <>
00:10:00 Loading Module <SPLNULL>
00:10:01 Checkpoint Completed: duration was 0 seconds.
00:10:01 Checkpoint loguniq 18, logpos 0x4b49018, timestamp: 618461115
00:10:01 Maximum server connections 1
00:10:01 Level 0 Archive started on rootdbs, phydbs, logdbs, pordbs, jpldbs, datadbs1
00:11:26 Archive on rootdbs, phydbs, logdbs, pordbs, jpldbs, datadbs1 Completed.
00:11:27 Process 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:07 listener-thread: err = -408: oserr = 0: errstr = : Invalid message type received from the sqlexec process.
00:20:23 Checkpoint Completed: duration was 0 seconds.
00:20:23 Checkpoint loguniq 18, logpos 0x4b4b018, timestamp: 618461147
00:20:23 Maximum server connections 1
00:42:13 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
00:57:24 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:08:06 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:09:24 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:11:03 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:11:17 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:11:32 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:19:09 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:20:23 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:20:31 listener-thread: err = -408: oserr = 0: errstr = : Invalid message type received from the sqlexec process.
01:21:54 listener-thread: err = -408: oserr = 0: errstr = : Invalid message type received from the sqlexec process.
01:22:30 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:25:29 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:26:41 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:27:43 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:29:04 listener-thread: err = -25580: oserr = 0: errstr = : System error occurred in network function.
01:30:16 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:31:11 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:34:20 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:35:41 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
01:35:46 listener-thread: err = -27001: oserr = 0: errstr = : Read error occurred during connection attempt.
02:10:24 I/O read chunk 1, pagenum 7, pagecnt 1 --> errno = 9
02:10:24 Assert Failed: Checkpoint Page Write Error. (1)
02:10:24 Informix Dynamic Server Version 9.40.UC1
02:10:24 Who: Session(1, informix@dbser, 0, 0x423b801
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:24 stack trace for pid 14791 written to /tmp/af.3ee1810
02:10:24 See Also: /tmp/af.3ee1810, shmem.3ee1810.0
03:30:37 Error writing '/tmp/shmem.3ee1810.0' errno = 28
03:30:38 rsrecvr.c, line 1551, thread 6, proc id 14791, Checkpoint Page Write Error. (1).
03:30:38 invoke_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:38 invoke_alarm(): mt_exec failed, status 32512, errno 0
03:30:39 The Master Daemon Died
03:30:39 invoke_alarm(): /bin/sh -c '/usr/informix/etc/alarmprogram.sh 5 6 "Internal Subsystem failure: 'MT'" "The Master Daemon Died" '
03:30:39 invoke_alarm(): mt_exec failed, status 32512, errno 0
03:30:39 PANIC: Attempting to bring system down
03:46:27 Informix Dynamic Server Started.
Sat Mar 24 03:46:28 2007
03:46:28 Event alarms enabled. ALARMPROG = '/usr/informix/etc/alarmprogram.sh'
03:46:28 Booting Language <c> from module <>
03:46:28 Loading Module <CNULL>
03:46:28 Booting Language <builtin> from module <>
03:46:28 Loading Module <BUILTINNULL>
03:46:32 Informix Dynamic Server Version 9.40.UC1 Software Serial Number AAA#B000000
03:46:32 Informix Dynamic Server Initialized -- Shared Memory Initialized.
03:46:32 Physical Recovery Started at Page (2:2273).
03:46:32 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored.
03:46:32 Logical Recovery Started.
03:46:32 10 recovery worker threads will be started.
03:46:35 Logical Recovery has reached the transaction cleanup phase.
03:46:35 Logical Recovery Complete.
0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks
03:46:36 Dataskip is now OFF for all dbspaces
03:46:36 Checkpoint Completed: duration was 0 seconds.
03:46:36 Checkpoint loguniq 18, logpos 0x4b4d018, timestamp: 618461171
03:46:36 Maximum server connections 0
03:46:36 On-Line Mode
03:51:52 listener-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.
[informix@dbser informix]$ 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. |
|
免费注册
发表于 2007-03-22 12:34
