RE: WARNING: mt_aio_wait: errno == EINVAL

Hi. Apply patch 108993(108993-27 or higher) under Solaris. You will sovle "WARNING: mt_aio_wait: errno == EINVAL". Regards. -- Tsutomu Ogiwara from Tokyo Japan. ICQ#:168106592 >From: try_and_err@web.de (try_and_err) >Reply-To: try_and_err@web.de (try_and_err) >To: informix-list@iiug.org >Subject: WARNING: mt_aio_wait: errno == EINVAL >Date: 21 Mar 2005 12:06:07 -0800 > >Hello, > >another question: >From time to time i receive the following info from my alarmprogram: >EVENT_SEVERITY: 3 >EVENT_CLASS : 6 >EVENT_MSG : Internal Subsystem failure: 'AIO' >EVENT_ADD_TEXT: WARNING: mt_aio_wait: errno == EINVAL >EVENT_FILE : > >Oh, i think 'bad thing', but when i look in the online.log: >- WARNING: mt_aio_wait: errno == EINVAL >- listener-thread: err = -951: oserr = 2: errstr = testx: Incorrect >password or user testx is not known on the database server. System >error = 2. > >It seems, that this only arises when the user is really unknown. For >example, when the user is known but the password is false (no >alarmprogram notification): >- Password Validation for user [test] failed! >- Check for password aging/account lock-out. >- listener-thread: err = -952: oserr = 0: errstr = test: User (test)'s > password is not correct for the database server. > >We use NIS for the user identification, is this a NIS or a generally >Informix problem ? Possibly someone knows a solution ? >We use 9.30.UC5 on Solaris 8. > >Regards, >try_and_err sending to informix-list