Oninit cdi / Archive
Talk to an expert →

how to fix the error "hpkaioaddseg: ASYNC_ADDSEG.

Posted in 2007

Topics: Error Codes & Troubleshooting, Platform-Specific Issues

NETSKY LIAO — — source: IIUG Forums & Mailing Lists

HP-UX11i,IDS9.4.FC8X5,with 32G mem,use kaio 22:37:14 IBM Informix Dynamic Server Version 9.40.FC8X5 22:37:14 Who: Session(6, informix@, 0, 0000000000000000) Thread(125, kaio, 0, 6) File: kaio.c Line: 2072 22:37:14 Who: Session(1, informix@hp8400_2, 0, 0000000000000000) Thread(124, kaio, 0, 12) File: kaio.c Line: 2072 22:37:14 stack trace for pid 28366 written to /tmp/af.465161a 22:37:14 stack trace for pid 28372 written to /tmp/af.464161a 22:37:14 See Also: /tmp/af.464161a, shmem.464161a.0 22:37:14 See Also: /tmp/af.465161a, shmem.465161a.0 22:37:15 hpkaioaddseg: ASYNC_ADDSEG failed, errno = 7 Arg list too long 22:37:15 Assert Failed: kaiothread() ERROR

↪ replying to NETSKY LIAO
H.G — — source: IIUG Forums & Mailing Lists

R U exporting env. variable KAIOON=1 ? Post ONCONFIG, it might help to advice. --- NETSKY LIAO <liaosnet@126.com> wrote: > HP-UX11i,IDS9.4.FC8X5,with 32G mem,use kaio > > 22:37:14 IBM Informix Dynamic Server Version 9.40.FC8X5 > 22:37:14 Who: Session(6, informix@, 0, 0000000000000000) > Thread(125, kaio, 0, 6) > File: kaio.c Line: 2072 > 22:37:14 Who: Session(1, informix@hp8400_2, 0, 0000000000000000) > > Thread(124, kaio, 0, 12) > > File: kaio.c Line: 2072 > 22:37:14 stack trace for pid 28366 written to /tmp/af.465161a > 22:37:14 stack trace for pid 28372 written to /tmp/af.464161a > 22:37:14 See Also: /tmp/af.464161a, shmem.464161a.0 > 22:37:14 See Also: /tmp/af.465161a, shmem.465161a.0 > 22:37:15 hpkaioaddseg: ASYNC_ADDSEG failed, errno = 7 Arg list too long > 22:37:15 Assert Failed: kaiothread() ERROR > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

↪ replying to NETSKY LIAO
Andreas.KUTSCHE@spar.at — — source: IIUG Forums & Mailing Lists

There seems to be a problem with KAIO (kernel asynchronous IO). When using KAIO the Server allocates some additional shared memory (additional to LOCKS, BUFFERS and SHMVIRTSIZE). Check the following: - async driver included in the HPUX kernel - /dev/async existing and mode 666 - /etc/privgroup entry for informix with MLOCK privilege - onconfig file: RESIDENT -1 (force shared memory segments resident) - enough memory/swapspace/shared memory available, enough segments available Bye Andreas Kutsche > ------------------------------------------- SPAR Österreichische Warenhandels-AG Hauptzentrale A - 5015 Salzburg, Europastrasse 3 FN 34170 a Tel: +43 662 4470 24223 Mobile: +43 664 6259575 E-Mail: Andreas.KUTSCHE@spar.at Internet: http://www.spar.at Wichtiger Hinweis: Der Inhalt dieser E-Mail kann vertrauliche und rechtlich geschützte Informationen, insbesondere Betriebs- oder Geschäftsgeheimnisse, enthalten, zu deren Geheimhaltung der Empfänger verpflichtet ist. Die Informationen in dieser E-Mail sind ausschließlich für den Adressaten bestimmt. Sollten Sie die E-Mail irrtümlich erhalten haben so ersuchen wir Sie, die Nachricht von Ihrem System zu löschen und sich mit uns in Verbindung zu setzen. Über das Internet versandte E-Mails können leicht manipuliert oder unter fremdem Namen erstellt werden. Daher schließen wir die rechtliche Verbindlichkeit der in dieser Nachricht enthaltenen Informationen aus. Der Inhalt der E-Mail ist nur rechtsverbindlich, wenn er von uns schriftlich bestätigt und gezeichnet wird. Sollte trotz der von uns verwendeten Virus-Schutzprogramme durch die Zusendung von E-Mails ein Virus in Ihre Systeme gelangen, haften wir nicht für evtl. hieraus entstehende Schäden. Wir danken für Ihr Verständnis. Important notice: The contents of this e-mail may contain confidential and legally protected information that is in particular related to operational and trade secrets, which the recipient is obliged to treat as confidential. The information in this e-mail is made available exclusively for use by the addressee. In the event that the e-mail may have been sent to you in error, we would ask you to kindly delete this communication from your system and to contact us. E-mails sent via the Internet can be easily manipulated or sent out under someone else's name. We therefore do not accept legal liability for the information contained in this communication. The contents of the e-mail are only legally binding if they have been confirmed and signed by us in writing. If, in spite of our using Antivirus protection software, a virus may have penetrated your system through the sending of this e-mail, we do not accept liability for any damage that may possibly arise as a result of this. We trust that you appreciate our position. ------------------------------------------- -----Ursprüngliche Nachricht----- > Von: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org]Im Auftrag von > NETSKY LIAO > Gesendet: Mittwoch, 25. April 2007 04:07 > An: ids@iiug.org > Betreff: how to fix the error "hpkaioaddseg: ASYNC_ADDSEG. [9005] > > > HP-UX11i,IDS9.4.FC8X5,with 32G mem,use kaio > > 22:37:14 IBM Informix Dynamic Server Version 9.40.FC8X5 > 22:37:14 Who: Session(6, informix@, 0, 0000000000000000) > Thread(125, kaio, 0, 6) > File: kaio.c Line: 2072 > 22:37:14 Who: Session(1, informix@hp8400_2, 0, 0000000000000000) > > Thread(124, kaio, 0, 12) > > File: kaio.c Line: 2072 > 22:37:14 stack trace for pid 28366 written to /tmp/af.465161a > 22:37:14 stack trace for pid 28372 written to /tmp/af.464161a > 22:37:14 See Also: /tmp/af.464161a, shmem.464161a.0 > 22:37:14 See Also: /tmp/af.465161a, shmem.465161a.0 > 22:37:15 hpkaioaddseg: ASYNC_ADDSEG failed, errno = 7 Arg > list too long > 22:37:15 Assert Failed: kaiothread() ERROR > > > ************************************************************** > ***************** > Forum Note: Use "Reply" to post a response in the discussion forum. > >

↪ replying to NETSKY LIAO
NETSKY LIAO — — source: IIUG Forums & Mailing Lists

OK, it happen as Andreas Kutsche says. - enough memory/swapspace/shared memory available, enough segments available the IDS allocates a lots of segments,so the error act.