KAIO
Posted in 2003
On HP-UX 11 with IDS 9.30, enabling KAIOON caused startup failures: "hpkaioaddseg: ASYNC_ADDSEG failed, errno = 1 Not owner", an assert in kaio.c line 2010, and a server PANIC. Respondents blamed the async driver setup: make sure the asyncdsk driver is in the kernel and /dev/async exists (mknod c 101 4), set its ownership/permissions correctly (660 informix, or 666), set RESIDENT=1, and grant the informix group MLOCK privilege via /etc/privgroup plus setprivgrp. The poster later reported that only 3 of 5 instances would start with KAIO on, asking about a limit; no answer or resolution to that follow-up is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: Storage & Space Management, Error Codes & Troubleshooting, Logging & Checkpoints, Platform-Specific Issues, Versions, Editions & End-of-Life
I am trying to turn KAIOON. The system administrator has enabled the kernal parameter and says I should be able to use it but check out the message below that I get in the online log when I try to run with it turned on. Any ideas of what could be causing the problem? -------------------------------- 10:01:39 Maximum server connections 4 10:51:34 Informix Dynamic Server Stopped. 10:53:18 Informix Dynamic Server Started. Thu Jan 16 10:53:27 2003 10:53:27 Event alarms enabled. ALARMPROG = '/apps/informix/etc/log_full.sh' 10:53:28 Booting Language <c> from module <> 10:53:28 Loading Module <CNULL> 10:53:28 Booting Language <builtin> from module <> 10:53:28 Loading Module <BUILTINNULL> 10:53:33 Informix Dynamic Server Version 9.30.HC1 Software Serial Number AA D#J265205 10:53:33 HPUX Version B.11.00 -> Using flag/select style KAIO 10:53:33 HPUX KAIO Segment locked addr=0xe6b94000 size=111894528 10:53:34 Informix Dynamic Server Initialized -- Shared Memory Initialized. 10:53:34 Physical Recovery Started at Page(5:470). 10:53:34 hpkaioaddseg: ASYNC_ADDSEG failed, errno = 1 Not owner 10:53:34 Assert Failed: kaiothread() ERROR 10:53:34 Informix Dynamic Server Version 9.30.HC1 10:53:34 Who: Session(11, informix@diomede, 0, 0) Thread(36, kaio, 0, 3) File: kaio.c Line: 2010 10:53:34 stack trace for pid 18006 written to /tmp/af.40c0dbe 10:53:34 See Also: /tmp/af.40c0dbe, shmem.40c0dbe.0 10:53:35 Physical Recovery Complete: 0 Pages Examined 0 Pages Restored. 10:53:35 Logical Recovery Started. 10:53:35 10 recovery worker threads will be started. 10:53:38 Logical Recovery has reached the transaction cleanup phase. 10:53:38 Logical Recovery Complete. 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks 10:53:39 Dataskip is now OFF for all dbspaces 10:53:39 Checkpoint Completed: duration was 0 seconds. 10:53:39 Checkpoint loguniq 3024, logpos 0x603018 10:53:39 Maximum server connections 0 10:53:39 On-Line Mode 10:53:58 kaio.c, line 2010, thread 36, proc id 18006, kaiothread() ERROR. 10:53:58 Fatal error in ADM VP at mt.c:11890 10:53:58 Unexpected virtual processor termination, pid = 18006, exit = 0x100 10:53:58 PANIC: Attempting to bring system down 10:53:58 semctl: errno = 22 10:53:58 semctl: errno = 22 10:53:58 semctl: errno = 22 10:53:58 semctl: errno = 22 ---------------------------------------------------- Jane Vohden Database Administrator Fairbanks North Star Borough HP-UX 11 IDS 9.30
I didn't think you had to explicitly turn it on for HPUX 11. What do the release notes say? -- Bye now, Obnoxio "C'est pas parce qu'on n'a rien à dire qu'il faut fermer sa gueule" - Coluche >From: "Jane Vohden " <jvohden@co.fairbanks.ak.us> >To: ids@iiug.org >Subject: KAIO [285] Date: Thu, 6 Feb 2003 18:04:54 -0500 (EST) > >I am trying to turn KAIOON. The system administrator has enabled the >kernal >parameter and says I should be able to use it but check out the message >below that I get in the online log when I try to run with it turned on. >Any ideas of what could be causing the problem? >-------------------------------- >10:01:39 Maximum server connections 4 >10:51:34 Informix Dynamic Server Stopped. > >10:53:18 Informix Dynamic Server Started. > >Thu Jan 16 10:53:27 2003 > >10:53:27 Event alarms enabled. ALARMPROG = >'/apps/informix/etc/log_full.sh' >10:53:28 Booting Language <c> from module <> >10:53:28 Loading Module <CNULL> >10:53:28 Booting Language <builtin> from module <> >10:53:28 Loading Module <BUILTINNULL> >10:53:33 Informix Dynamic Server Version 9.30.HC1 Software Serial >Number AA >D#J265205 >10:53:33 HPUX Version B.11.00 -> Using flag/select style KAIO >10:53:33 HPUX KAIO Segment locked addr=0xe6b94000 size=111894528 >10:53:34 Informix Dynamic Server Initialized -- Shared Memory Initialized. > >10:53:34 Physical Recovery Started at Page(5:470). >10:53:34 hpkaioaddseg: ASYNC_ADDSEG failed, errno = 1 Not owner >10:53:34 Assert Failed: kaiothread() ERROR >10:53:34 Informix Dynamic Server Version 9.30.HC1 >10:53:34 Who: Session(11, informix@diomede, 0, 0) > Thread(36, kaio, 0, 3) > File: kaio.c Line: 2010 >10:53:34 stack trace for pid 18006 written to /tmp/af.40c0dbe >10:53:34 See Also: /tmp/af.40c0dbe, shmem.40c0dbe.0 >10:53:35 Physical Recovery Complete: 0 Pages Examined 0 Pages Restored. > >10:53:35 Logical Recovery Started. >10:53:35 10 recovery worker threads will be started. >10:53:38 Logical Recovery has reached the transaction cleanup phase. >10:53:38 Logical Recovery Complete. > 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks > >10:53:39 Dataskip is now OFF for all dbspaces >10:53:39 Checkpoint Completed: duration was 0 seconds. >10:53:39 Checkpoint loguniq 3024, logpos 0x603018 > >10:53:39 Maximum server connections 0 >10:53:39 On-Line Mode >10:53:58 kaio.c, line 2010, thread 36, proc id 18006, kaiothread() ERROR. >10:53:58 Fatal error in ADM VP at mt.c:11890 >10:53:58 Unexpected virtual processor termination, pid = 18006, exit = >0x100 > >10:53:58 PANIC: Attempting to bring system down >10:53:58 semctl: errno = 22 > >10:53:58 semctl: errno = 22 > >10:53:58 semctl: errno = 22 > >10:53:58 semctl: errno = 22 >---------------------------------------------------- > >Jane Vohden >Database Administrator >Fairbanks North Star Borough >HP-UX 11 >IDS 9.30 _________________________________________________________________ Express yourself with cool emoticons http://messenger.msn.co.uk
what are de permissions/ownership on /dev/async ?Do you have /dev/asyncdsk as well ? Change both ownership to informix and change permissions to 660 on both special files. THat should get you sorted. Assuming that the aync driver has been loaded into the kernel. You can check that with #ldsev|grep async. HTH, Peter Jane Vohden wrote: >I am trying to turn KAIOON. The system administrator has enabled the kernal >parameter and says I should be able to use it but check out the message >below that I get in the online log when I try to run with it turned on. >Any ideas of what could be causing the problem? >-------------------------------- >10:01:39 Maximum server connections 4 >10:51:34 Informix Dynamic Server Stopped. > >10:53:18 Informix Dynamic Server Started. > >Thu Jan 16 10:53:27 2003 > >10:53:27 Event alarms enabled. ALARMPROG = >'/apps/informix/etc/log_full.sh' >10:53:28 Booting Language <c> from module <> >10:53:28 Loading Module <CNULL> >10:53:28 Booting Language <builtin> from module <> >10:53:28 Loading Module <BUILTINNULL> >10:53:33 Informix Dynamic Server Version 9.30.HC1 Software Serial >Number AA >D#J265205 >10:53:33 HPUX Version B.11.00 -> Using flag/select style KAIO >10:53:33 HPUX KAIO Segment locked addr=0xe6b94000 size=111894528 >10:53:34 Informix Dynamic Server Initialized -- Shared Memory Initialized. > >10:53:34 Physical Recovery Started at Page(5:470). >10:53:34 hpkaioaddseg: ASYNC_ADDSEG failed, errno = 1 Not owner >10:53:34 Assert Failed: kaiothread() ERROR >10:53:34 Informix Dynamic Server Version 9.30.HC1 >10:53:34 Who: Session(11, informix@diomede, 0, 0) > Thread(36, kaio, 0, 3) > File: kaio.c Line: 2010 >10:53:34 stack trace for pid 18006 written to /tmp/af.40c0dbe >10:53:34 See Also: /tmp/af.40c0dbe, shmem.40c0dbe.0 >10:53:35 Physical Recovery Complete: 0 Pages Examined 0 Pages Restored. > >10:53:35 Logical Recovery Started. >10:53:35 10 recovery worker threads will be started. >10:53:38 Logical Recovery has reached the transaction cleanup phase. >10:53:38 Logical Recovery Complete. > 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks > >10:53:39 Dataskip is now OFF for all dbspaces >10:53:39 Checkpoint Completed: duration was 0 seconds. >10:53:39 Checkpoint loguniq 3024, logpos 0x603018 > >10:53:39 Maximum server connections 0 >10:53:39 On-Line Mode >10:53:58 kaio.c, line 2010, thread 36, proc id 18006, kaiothread() ERROR. >10:53:58 Fatal error in ADM VP at mt.c:11890 >10:53:58 Unexpected virtual processor termination, pid = 18006, exit = >0x100 > >10:53:58 PANIC: Attempting to bring system down >10:53:58 semctl: errno = 22 > >10:53:58 semctl: errno = 22 > >10:53:58 semctl: errno = 22 > >10:53:58 semctl: errno = 22 >---------------------------------------------------- > >Jane Vohden >Database Administrator >Fairbanks North Star Borough >HP-UX 11 >IDS 9.30 > > > >
Jane Vohden wrote: > I am trying to turn KAIOON. The system administrator has enabled the kernal > parameter and says I should be able to use it but check out the message > below that I get in the online log when I try to run with it turned on. > Any ideas of what could be causing the problem? It looks like your SA has not set appropriate permissions on the KAIO files in /dev. Check your release notes in $INFORMIXDIR/release/*/*, they usually give explicit instructions on how to setup KAIO. Cheers, -- Mark. +----------------------------------------------------------+-----------+ | Mark D. Stock mailto:mdstock@MydasSolutions.com |//////// /| | Mydas Solutions Ltd http://MydasSolutions.com |///// / //| | +-----------------------------------+//// / ///| | |We value your comments, which have |/// / ////| | |been recorded and automatically |// / /////| | |emailed back to us for our records.|/ ////////| +----------------------+-----------------------------------+-----------+
Yes this is correct, 660 /dev/async with Informix owner informix group Have to reboot server when adding the driver. Make sure RESIDENT is set to 1 in onconfig file Carl W Berner - Team Lead Informix/Oracle DBA IBM Global Services - Serving Lucent Technologies Work : (770) 750 5225 Pager: 1-800-759-8888 Pin#1615039 Email: cberner@lucent.com -----Original Message----- From: Mark D. Stock [mailto:mdstock@mydassolutions.com] Sent: Friday, February 07, 2003 5:58 AM To: ids@iiug.org Subject: Re: KAIO [292] Jane Vohden wrote: > I am trying to turn KAIOON. The system administrator has enabled the kernal > parameter and says I should be able to use it but check out the message > below that I get in the online log when I try to run with it turned on. > Any ideas of what could be causing the problem? It looks like your SA has not set appropriate permissions on the KAIO files in /dev. Check your release notes in $INFORMIXDIR/release/*/*, they usually give explicit instructions on how to setup KAIO. Cheers, -- Mark. +----------------------------------------------------------+-----------+ | Mark D. Stock mailto:mdstock@MydasSolutions.com |//////// /| | Mydas Solutions Ltd http://MydasSolutions.com |///// / //| | +-----------------------------------+//// / ///| | |We value your comments, which have |/// / ////| | |been recorded and automatically |// / /////| | |emailed back to us for our records.|/ ////////| +----------------------+-----------------------------------+-----------+
Well, I suppose that is *one* way to do it. But I'd
rather not restrict
ownership of /dev/async to informix. Here's what we did to enable kernel
async I/O on HPUX 11:
a. ensure HP KAIO driver "asyncdsk" is installed and linked into the kernel.
b. to ensure KAIO driver is up and running, check to see if
/dev/async exists; if not, then run the following commands as root:
# /usr/sbin/mknod /dev/async c 101 4
# chmod 0666 /dev/async
c. to fix the "ownership" problem, run the following commands as root:
# echo "informix: MLOCK" > /etc/privgroup
# setprivgrp -f /etc/privgroup# getprivgrp
-- should display:
global privileges: CHOWN
informix: MLOCK
HTH,
Paul Mosser
-----Original Message-----
From: Berner, Car.... [mailto:cberner@lucent.com]
Sent: Friday, February 07, 2003 8:12 AM
To: ids@iiug.org
Subject: RE: KAIO [297]
Yes this is correct, 660 /dev/async with Informix owner informix group
Have to reboot server when adding the driver.
Make sure RESIDENT is set to 1 in onconfig file
Carl W Berner - Team Lead Informix/Oracle DBA
IBM Global Services - Serving Lucent Technologies
Work : (770) 750 5225
Pager: 1-800-759-8888 Pin#1615039
Email: cberner@lucent.com
-----Original Message-----
From: Mark D. Stock [mailto:mdstock@mydassolutions.com]
Sent: Friday, February 07, 2003 5:58 AM
To: ids@iiug.org
Subject: Re: KAIO [292]
Jane Vohden wrote:
> I am trying to turn KAIOON. The system administrator has enabled the
kernal
> parameter and says I should be able to use it but check out the message
> below that I get in the online log when I try to run with it turned on.
> Any ideas of what could be causing the problem?
It looks like your SA has not set appropriate permissions on the KAIO
files in /dev. Check your release notes in $INFORMIXDIR/release/*/*,
they usually give explicit instructions on how to setup KAIO.
Cheers,
--
Mark.
+----------------------------------------------------------+-----------+
| Mark D. Stock mailto:mdstock@MydasSolutions.com |//////// /|
| Mydas Solutions Ltd http://MydasSolutions.com |///// / //|
| +-----------------------------------+//// / ///|
| |We value your comments, which have |/// / ////|
| |been recorded and automatically |// / /////|
| |emailed back to us for our records.|/ ////////|
+----------------------+-----------------------------------+-----------+
Last week I had KAIOON=1 in 4 out of our 5 instances of IDS 9.3 running successfully. We have 3 production instances and 2 test. I had modified the startup script for the 5th instance but I wasn't going to turn it on until this morning. Well - during the weekend, the system required a reboot so that instance was started up for me with the KAIOON. When the informix instances started up, only 3 out of the 5 would start. One that started was the one I was going to start up this morning. The instances came up in order as they are supposed to, the first 3 started were the 3 that worked. When I came in this morning, I noticed the other 2 instances down so I did some playing around. I took one of the up instances down and then was able to start one of the other down instance with KAIOON. I've played around a lot this morning and still can only get 3 instances with KAIOON up and running. Is there a limit set somewhere? I've included a segment of the online log so you can see the errors. Please let me know if you have any ideas as to what's causing this. Thanks. - Jane HP-UX 11.0 IDS 9.30.HC1
sorry - I forgot the messages in prior email. -----Original Message----- From: Jane Vohden [mailto:jvohden@co.fairbanks.ak.us] Sent: Monday, April 14, 2003 11:49 AM To: ids@iiug.org Subject: RE: KAIO [924] Last week I had KAIOON=1 in 4 out of our 5 instances of IDS 9.3 running successfully. We have 3 production instances and 2 test. I had modified the startup script for the 5th instance but I wasn't going to turn it on until this morning. Well - during the weekend, the system required a reboot so that instance was started up for me with the KAIOON. When the informix instances started up, only 3 out of the 5 would start. One that started was the one I was going to start up this morning. The instances came up in order as they are supposed to, the first 3 started were the 3 that worked. When I came in this morning, I noticed the other 2 instances down so I did some playing around. I took one of the up instances down and then was able to start one of the other down instance with KAIOON. I've played around a lot this morning and still can only get 3 instances with KAIOON up and running. Is there a limit set somewhere? I've included a segment of the online log so you can see the errors. Please let me know if you have any ideas as to what's causing this. Thanks. - Jane HP-UX 11.0 IDS 9.30.HC1 11:02:58 Informix Dynamic Server Started. Mon Apr 14 11:03:30 2003 11:03:30 Event alarms enabled. ALARMPROG = '/apps/informix/etc/log_full.sh' 11:03:31 Booting Language <c> from module <> 11:03:31 Loading Module <CNULL> 11:03:31 Booting Language <builtin> from module <> 11:03:31 Loading Module <BUILTINNULL> 11:03:38 Informix Dynamic Server Version 9.30.HC1 Software Serial Number AA D#J265205 11:03:39 HPUX Version B.11.00 -> Using flag/select style KAIO 11:04:54 hpkaioaddseg: ASYNC_ADDSEG failed, errno = 1 Not owner 11:04:55 Assert Failed: kaiothread() ERROR 11:04:55 Informix Dynamic Server Version 9.30.HC1 11:04:55 Who: Session(1, informix@diomede, 0, 0) Thread(43, kaio, 0, 1) File: kaio.c Line: 2010 11:04:55 stack trace for pid 9415 written to /tmp/af.4130657 11:04:57 See Also: /tmp/af.4130657, shmem.4130657.0 11:07:00 kaio.c, line 2010, thread 43, proc id 9415, kaiothread() ERROR. 11:07:00 PANIC: Attempting to bring system down