You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a Uyuni 2024.12 system, I have noticed that the update scripts are not being executed, or at least the return value cannot be determined. As an error, I receive the following:
29-01-2025 13:15:58 | ldaptest.domain.de | INFO | Execute begin update scripts
29-01-2025 13:16:29 | ldaptest.domain.de | WARNING | There has been an problem to get the event status, retry in 10 seconds. The error is:
EOF occurred in violation of protocol (_ssl.c:2427)
29-01-2025 13:16:39 | ldaptest.domain.de | INFO | Still Running
29-01-2025 13:17:09 | ldaptest.domain.de | WARNING | There has been an problem to get the event status, retry in 10 seconds. The error is:
EOF occurred in violation of protocol (_ssl.c:2427)
29-01-2025 13:17:19 | ldaptest.domain.de | INFO | Still Running
29-01-2025 13:17:49 | ldaptest.domain.de | WARNING | There has been an problem to get the event status, retry in 10 seconds. The error is:
EOF occurred in violation of protocol (_ssl.c:2427)
29-01-2025 13:17:59 | ldaptest.domain.de | INFO | Still Running
29-01-2025 13:18:29 | ldaptest.domain.de | WARNING | There has been an problem to get the event status, retry in 10 seconds. The error is:
EOF occurred in violation of protocol (_ssl.c:2427)
29-01-2025 13:18:39 | ldaptest.domain.de e | INFO | Still Running
29-01-2025 13:19:09 | ldaptest.domain.de | WARNING | There has been an problem to get the event status, retry in 10 seconds. The error is:
EOF occurred in violation of protocol (_ssl.c:2427)
29-01-2025 13:19:19 | ldaptest.domain.de | INFO | Still Running
The text was updated successfully, but these errors were encountered:
On a Uyuni 2024.12 system, I have noticed that the update scripts are not being executed, or at least the return value cannot be determined. As an error, I receive the following:
The text was updated successfully, but these errors were encountered: