Skip to main content
Solved

" SEVERE: failed post-install: job failed: BackoffLimitExceeded"

  • January 23, 2024
  • 2 replies
  • 240 views

RWEAVER
Do Gooder (Customer)
Forum|alt.badge.img+4
  • Do Gooder (Customer)
  • 5 replies

I see this problem repeated, but I haven’t found any with a solution relevant to me.

 

[Tue Jan 23 18:08:58 UTC 2024] - SEVERE: failed post-install: job failed: BackoffLimitExceeded
[Tue Jan 23 18:08:58 UTC 2024] - SEVERE: Failed to install ifs-cloud
[Tue Jan 23 18:08:58 UTC 2024] - INFO: ifs-db-init log:
Container initiated at Tue Jan 23 18:06:45 UTC 2024
SECRETIMAGE_VERSION=Tue Mar 21 05:25:29 UTC 2023 1.0.6
ALPINE_VERSION=Tue Mar 21 05:25:29 UTC 2023 3.16.3
BASEIMAGE_VERSION=Tue Mar 21 05:25:29 UTC 2023 1.0.44
CERTIFICATE_HANDLER_VERSION=Tue Mar 21 05:27:05 UTC 2023 1.0.8
JAVAIMAGE_VERSION=Tue Mar 21 05:27:05 UTC 2023 1.0.53
DRIVER_VERSION=Tue Mar 21 06:42:06 UTC 2023 22.2.7.0.0
DBINITIMAGE_VERSION=Tue Mar 21 06:42:06 UTC 2023 22.2.7.0.0
Using API to fetch certificates
/opt/ifs/get_certs.sh: line 50: $(sed -e 's/^"//' -e 's/"$//' <<< "$(echo -e "${split[0]}" | tr -d '[:space:]')"): ambiguous redirect
No certificates are loaded for database-certs ..
Using API to fetch certificates
No certificates are loaded for ifs-db-init-certs ..
/opt/ifs/get_certs.sh: line 50: $(sed -e 's/^"//' -e 's/"$//' <<< "$(echo -e "${split[0]}" | tr -d '[:space:]')"): ambiguous redirect
Failed updating database. IO Error: The Network Adapter could not establish the connection.
Failing updating, check credentials
 

Best answer by RWEAVER

Did complete reinstall beginning to end.  Worked this time.

2 replies

RWEAVER
Do Gooder (Customer)
Forum|alt.badge.img+4
  • Author
  • Do Gooder (Customer)
  • 5 replies
  • Answer
  • January 23, 2024

Did complete reinstall beginning to end.  Worked this time.


Forum|alt.badge.img+15
  • Superhero (Employee)
  • 182 replies
  • January 23, 2024

Hi Rodney,

It seems that this is resolved now. But let me add two common causes for this:

  1. The Oracle listener is not up or port 1541 is blocked.
  2. The solutionset.yaml file is missing or not located in the right folder.

There may be other causes, but these are two that I have seen multiple times.

Best regards -- Ben