Document Type | Troubleshooting
Category | Patch/Upgrade
Applicable Product Version | 6FS07
Error Code | 18017
Document Number | TPATS007
Issue
The symptom is that โERROR_IO(-18017) : during a user authentication process.โ appears in the sys.log.
[2025-04-04T14:10:55.645821] [FRM-104] [I] ERROR_IO(-18017) : during a user authentication process. client ip: 172.31.34.100, port:55876, prog_name:, user_name:, osuser_name:, terminal:
Cause
Tibero only allows connections from clients (such as jdbc) recognized by Tibero, and when a normal Tibero client connects, prog_name, user_name, osusername, etc. all appear in the slog along with the 18017 error.
NoteSince this is a case of connecting directly to the port, such details are not recorded, and only the client IP and port are shown. This can occur during server Health Check.
Solutions
To prevent errors from occurring even when the message format differs or there is no message, or in cases where there is only a connect to the port, apply the patch to resolve the issue. (Applied Patch: 188701)
After applying patch 188701b, the ERROR_IO output issue can be resolved by setting โAUTHENTICATION_FOR_HEALTH_CHECK=Yโ.
CautionApply the patch through technical support provided by Tmax Tibero.
NoteYou can identify the process name that accessed ERROR_IO(-18017) : during a user authentication process. client ip: 172.31.34.100 by using the auditd package.(Meaning: Using the auditd framework provided by Linux, it dumps all information and time of the process that requested the 'connect' system call on Linux, to identify the process name that connected to Tibero.)1. Install auditdSince it is a daemon provided by the Linux kernel, it may already be installed depending on the distribution.2. Start audit recording by running the command as root user$ sudo auditctl -a exit,always -F arch=b64 -S connect -k MYCONNECTFrom the time this command is executed, all records of 'connect' calls will be logged in /var/log/audit/audit.log.
3. Stop recording after completion$ sudo auditctl -d exit,always -F arch=b64 -S connect -k MYCONNECTBecause a large amount of data can be recorded, stop recording with the above command after completion.
4. Interpret audit.log contents (using ausearch)sudo ausearch --start 03/16/21 '16:01:42' --end 03/16/21 '16:01:47'When entered as above, the audit.log recorded from 16:01:42 to 16:01:47 on March 16, 2021, is converted into a more readable format and displayed on the screen.