Informix - Problem description
Problem IT41845 | Status: Closed |
ONBAR BACKUP TO AMAZON S3 EXITS WITH 0X0(SUCCESS) EVEN THOUGH THE CLOUD HOST IS NOT REACHABLE. | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
Onbar(PSM) backup to Amazon S3 exits with 0x0(Success) even though the cloud host is not reachable. > onbar -b -w -L 0 ; echo $? 0 [bar_act.log] 2022-08-20 03:47:56 7632 7622 /opt/informix/IBM/12.10.FC13/bin/onbar_d -b -w -L 0 ... 2022-08-20 03:47:58 7632 7622 /opt/informix/IBM/12.10.FC13/bin/onbar_d complete, returning 0 (0x00) [bar_debug.log] 2022-08-20 03:47:57 7632 7622 bar_read_archive: enter 2022-08-20 03:47:57 7632 7622 bar_read_archive: input buf 0xad5fb400 2022-08-20 03:47:57 7632 7622 bar_read_archive: output buf nbytes events dbspace lolog hilog errtxt 2022-08-20 03:47:57 7632 7622 bar_read_archive: output 0xad60b400 63488 0x0 81 81 2022-08-20 03:47:57 7632 7622 bar_read_archive: return 0 (0x00) 2022-08-20 03:47:57 7632 7622 barSendData: enter 2022-08-20 03:47:57 7632 filter write_to_filter: enter 2022-08-20 03:47:57 7632 filter write_to_filter: return 0 (0x00) ... 2022-08-20 03:47:58 7632 7622 bar_main complete, returning 0 (0x00) [psm_debug.log] 2022-08-20 03:47:57 7637 7632 sm_rest.c:1618 S3 URL = 'https:///ids1210FC13/rootdbs/0/rootdbs.20284.1', ... 2022-08-20 03:47:57 7637 7632 sm_rest.c:1751 curl_easy_perform() failed(6): Couldn't resolve host name. 2022-08-20 03:47:57 7637 7632 sm_rest.c:1847 Writing status file /tmp/s3_status.7637.7641 2022-08-20 03:47:57 7637 7632 sm_rest.c:1853 WRITING STATUS 0 2022-08-20 03:47:57 7637 7632 sm_rest.c:1858 cloudS3ClientStart is returning 0 2022-08-20 03:47:57 7637 7632 sm_rest.c:1359 cloudS3ClientStart: return 0 (0x00) * Could not resolve host: * Closing connection | |
Problem Summary: | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.08.2022 18.05.2023 18.05.2023 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |