Problemem z wdrożeniem baz danych

Instalacja i tematy techniczne
1

Korzystam z Instrukcja instalacji aplikacji EZD RP – środowisko do 150 użytkowników – Podręcznik użytkownika systemu EZD RP

Dotarłem do Instalacja baz danych, konfiguruje jak jest opisane, następnie klikam install.

StatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:00 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:02 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:04 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:06 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:08 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:10 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:12 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:14 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:16 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:18 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:20 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:22 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:24 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:26 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:28 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:30 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:32 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:34 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:36 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:38 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:40 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:42 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:44 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:46 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:48 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:50 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:52 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:54 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:56 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:44:58 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:00 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:02 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:04 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:06 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:08 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:10 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:12 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:14 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:16 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:18 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:20 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:22 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:24 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:26 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:28 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:30 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:32 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:34 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:36 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:38 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:40 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:42 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:44 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:46 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:48 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:50 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:52 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:54 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:56 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:45:58 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:00 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:02 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:04 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:06 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:08 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:10 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:12 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:14 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:16 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:18 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:20 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:22 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:24 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:26 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:28 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:30 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:32 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:34 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:36 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:38 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:40 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:42 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:44 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:46 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:48 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:50 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:52 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:54 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:56 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:46:58 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:00 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:02 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:04 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:06 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:08 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:10 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:12 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:14 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:16 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:18 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:20 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:22 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:24 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:26 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:28 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:30 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:32 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:34 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:36 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:38 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:40 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:42 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:44 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:46 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:48 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:50 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:52 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:54 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:56 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:47:58 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:00 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:02 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:04 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:06 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:08 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:10 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:12 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:14 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:16 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:18 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:20 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:22 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:24 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:26 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:28 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:30 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:32 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:34 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:36 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:38 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:40 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:42 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:44 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:46 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:48 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:50 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:52 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:54 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:56 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:48:58 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:00 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:02 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:04 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:06 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:08 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:10 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:12 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:14 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:16 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:18 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:20 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:22 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:24 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:26 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:28 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:30 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:32 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:34 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:36 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:38 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:40 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:42 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:44 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:46 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:48 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:50 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:52 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:54 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:56 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:49:58 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:00 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:02 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:04 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:06 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:08 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:10 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:12 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:14 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:16 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:18 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:20 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:22 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:24 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:26 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:28 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:30 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:32 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:34 pmStatefulSet is not ready: ezd2/database4-postgresql. 0 out of 1 expected pods are ready

Sat, Dec 9 2023 9:50:36 pmError: INSTALLATION FAILED: timed out waiting for the condition

Czy ktoś może podpowiedzieć jak rozwiązać powyższy problem??

2

Dzień dobry,

Powodów może być wiele.
Prosiłbym o wykonanie paru komend i zaznajomienie się z outputem podczas instalacji:

kubectl -n (namespace) describe po

kubectl -n (namespace) logs

Jak i również warto sprawdzić czy wszystkie pvc się “zbondowały”:
kubectl -n (namespace) get pvc

Również warto sprawdzić zawartość StatefulSet
kubectl -n (namespace) get StatefulSet
(z listy wybrać odpowiedni)
kubectl -n (namespace) get StatefulSet (nazwa StatefulSet) -o yaml

Ewentualnie warto też sprawdzić co się wydarzyło w eventach:
kubectl -n (namespace) get events --sort-by=‘{.lastTimestamp}’

Pozdrawiam

3

Panie Dariuszu problem opisałem Instalacja baz - aplikacja ezdrp-db-dev-single:1.0.16 w stanie pending-install - #3 przez tomcic

Problemem jest ilość zasobów, proszę spróbować wdrożyć bazy danych na vm z 4 vCPU i 8GB RAM. Natknie się Pan na ten sam problem. Rke nie obsługuje over-provisioning, czyli jeżeli wdrożenie w pliku yaml wymaga odpowiedniej ilości zasobów, która przekracza możliwości VM, to bazy się nie wdrożą. Rozwiązania są dwa:

  • usunąć lub zmniejszyć rezerwacje CPU i RAM w pliku yaml
  • zwiększyć zasoby CPU i RAM dla wirtualnej maszyny.
4

Witam,
Na chwilą obecną mam konfigurację jak w instrukcji (24 VCPU i 32GB RAM) i pojawił mi się problem jak w pierwszym poście. Co mam zmienić w Rancherze aby to ruszyło dalej?
----------------------------AKTUALIZACJA---------------------------------------------------------------------------------------

Zauważyłem, że w zakładce Storage-> PersistentVolumes miałem prawidłowe powiązanie tylko dla bazy mongodb, a reszta miała status “pending”. Po sprawdzeniu konfiguracji, jedyna różnica była taka, że mongodb wskazywało na “local-path”, a reszta baz nie miała tam nic wpisanego. Po wyedytowaniu YALM i dopisaniu “storageClassName: local-path”, kolejne bazy zaczęły normalnie się meldować na zielono.
Sprawdziłem trzy razy i podczas zakładania baz zawsze zmieniałem opcję "Write Persistent Storage Class Name " na “local-path”, ale chyba nie zapisywało tej opcji dla baz innych niż mongodb.

Bazy więc świecą na zielono ale aplikacja “database” już nie. Błąd jaki się wyświetla to:

helm upgrade --history-max=5 --install=true --namespace=ezd --timeout=10m0s --values=/home/shell/helm/values-ezdrp-db-dev-single-1.0.16.yaml --version=1.0.16 --wait=true database /home/shell/helm/ezdrp-db-dev-single-1.0.16.tgz
Error: UPGRADE FAILED: execution error at (ezdrp-db-dev-single/charts/rabbitmq/templates/NOTES.txt:165:4): 
2024-03-20T07:12:29.984296407Z PASSWORDS ERROR: You must provide your current passwords when upgrading the release.
2024-03-20T07:12:29.984306449Z                  Note that even after reinstallation, old credentials may be needed as they may be kept in persistent volume claims.
2024-03-20T07:12:29.984327608Z                  Further information can be obtained at https://docs.bitnami.com/general/how-to/troubleshoot-helm-chart-issues/#credential-errors-while-upgrading-chart-releases
2024-03-20T07:12:29.984335296Z 
2024-03-20T07:12:29.984344192Z     'auth.erlangCookie' must not be empty, please add '--set auth.erlangCookie=$RABBITMQ_ERLANG_COOKIE' to the command. To get the current value:
2024-03-20T07:12:29.984350131Z 
        export RABBITMQ_ERLANG_COOKIE=$(kubectl get secret --namespace "ezd" database-rabbitmq -o jsonpath="{.data.rabbitmq-erlang-cookie}" | base64 --decode)

Coś mu nie pasuje z bazą RABBIT, ale nie wiem co.

Podczas kolejnej reinstalacji aplikacji “database” przeszedłem pełną ścieżkę z instrukcji zmieniając hasła oraz “Storage Class” na “local-path” ale po przejściu w konfigurację YAML dla bazy rabbit, “local-path” nie było pod zmienną objętości bazy. Doklejone, install i tym razem wszystko poszło.
Nie wiem czy to wina instalatora czy moje wcześniejsze działania z Storage-> PersistentVolumes, ale to podziałało i może komuś się przyda.

5

Dzień dobry,

Podczas upgradu komponentów w przypadku Rabbitmq trzeba podać stare credentiale. Mówimy tu o erlangCookie.
W komunikacie błędu jest podane w jaki sposób wyeksportować wartość potrzebną ażeby upgrade poszedł prawidłowo. Exportujemy wartość RABBITMQ_ERLANG_COOKIE przed rozpoczęciem upgradu poprzez:

export RABBITMQ_ERLANG_COOKIE=$(kubectl get secret --namespace "ezd" database-rabbitmq -o jsonpath="{.data.rabbitmq-erlang-cookie}" | base64 --decode)

I dokonujemy instalacji/upgradu wraz z parametrem

--set auth.erlangCookie=$RABBITMQ_ERLANG_COOKIE

Kolejnym sposobem jest podanie wartości dla erlangCookie poprzez zdefiniowanie jej w pliczku z values dla instalacji/upgradu backendu. Wykonujemy to poprzez:

export RABBITMQ_ERLANG_COOKIE=$(kubectl get secret --namespace "ezd" database-rabbitmq -o jsonpath="{.data.rabbitmq-erlang-cookie}" | base64 --decode)

i tu mamy dwie opcje albo definiujemy w values dla rabbitmq:

rabbitmq:
  auth:
    password: < hasło >
    erlangCookie: $RABBITMQ_ERLANG_COOKIE

albo z exportu wyciągamy zmienną i w miejsce $RABBITMQ_ERLANG_COOKIE w pliku z values definiujemy.

rabbitmq:
  auth:
    password: < hasło >
    erlangCookie: < wartość >

Pozdrawiam,
Dariusz Bółkowski
Linux Polska.

1 polubienie
6

Dzięki za wskazanie i pewnie gdybym nie przeszedł na nowo instalacji baz to pewnie bym poszedł zgodnie z Twoim wpisem.
Obecnie przeszedłem całą ścieżkę i pozostało mi się zalogować … tylko że latają kulki, a ekranu logowania ani widu ani słychu.

7

Dzień dobry,

Często podczas powtórnych instalacji natrafiałem na podobny problem.
Czasami warto wyczyścić cookies/dane w przeglądarce. Odpalić w trybie incognito.
Kolejną sprawą jest sprawdzenie ingressu.
Proszę wylistować sobie ingress dla ezdrp poprzez:

kubectl -n < nazwa namespace dla ezdrp > get ingress

I sprawdzić czy dla ingresów w kolumnie HOSTS dostaje Pan odpowiedź dla:

sso-identityserver
sso-customexternalproviders
kuip-web
ezdrp-web

Można wkleić w przeglądarkę(proszę pamiętać o https)
.
Można też curlem sprawdzić odpowiedź dla część sso i kuip.
curl < HOSTS ingressu z httpsem > - insecure
przykład:

[root@normandia ~]# curl https://sso-idp.nazwa.domeny --insecure
200 - OK

Pozdrawiam,
Dariusz Bółkowski
Linux Polska