[uyuni-users] Wrong data displayed
Hi, after an accidental (rpm-) update to 2020.03 (with errors about a missing column) I rolled back the machine to an older snapshot before the update. Finally most things are running fine again but there are still some issues: 1.) The URI https://<FQDN>/rhn/manager/notification-messages shows a blank white "frame" (top bar and side bar are fine), although there should be more than 40 messages according to the "bell" in the top bar. Pressing the "bell" the tomcat log shows the following lines: "GET /rhn/manager/notification-messages HTTP/1.1" 200 34729 "POST /rhn/manager/frontend-log HTTP/1.1" 200 16 "GET /rhn/manager/notification-messages/data-unread HTTP/1.1" 200 10089 (I stripped IP and time code) Calling /rhn/manager/notification-messages/data-unread directly delivers a JSON page with all unread notifications. 2.) One of the 3 servers (actually the first SLES machine that had been registered) in "System Overview" shows 30 Patches and 53 Packages. Triggering an Patch is executed without error but afterwards the "system overview" still shows the missing patches and packages. On the respective system calling "zypper up" shows "Nothing to do.". 3.) At the WebUI under Salt / Keys a blank white "frame" is shown, too. Under Salt / Formula Catalog a white "frame" with the text "Something wrong happened. Please reload the page. If the problem persist, please check log files". Tomcat-Logs show: "GET /rhn/manager/formula-catalog HTTP/1.1" 200 34636 "GET /rhn/manager/api/formula-catalog/data HTTP/1.1" 200 142 "POST /rhn/manager/frontend-log HTTP/1.1" 200 16 "POST /rhn/manager/frontend-log HTTP/1.1" 200 16 Again a direct call of the 2nd URI with the "api" delivers a JSON document with a list of the catalogs available. Any idea what is going wrong there (and how to fix it)? All pages worked fine in the beginning after the base installation of Uyuni (Uyuni 2020.01 on openSUSE 15.1) I wonder if Uyuni provides some tools for testing and/or aligning a system? Thanks in advance! Regards, Tobias. -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Hi, On 4/2/20 7:44 PM, Tobias Crefeld wrote:
Hi,
after an accidental (rpm-) update to 2020.03 (with errors about a missing column) I rolled back the machine to an older snapshot before the update.
Finally most things are running fine again but there are still some issues:
1.) The URI https://<FQDN>/rhn/manager/notification-messages shows a blank white "frame" (top bar and side bar are fine), although there should be more than 40 messages according to the "bell" in the top bar. Pressing the "bell" the tomcat log shows the following lines:
"GET /rhn/manager/notification-messages HTTP/1.1" 200 34729 "POST /rhn/manager/frontend-log HTTP/1.1" 200 16 "GET /rhn/manager/notification-messages/data-unread HTTP/1.1" 200 10089 (I stripped IP and time code)
Calling /rhn/manager/notification-messages/data-unread directly delivers a JSON page with all unread notifications.
did you check - `/var/log/rhn/rhn_web_ui.log` - `/var/log/rhn/rhn_web_frontend.log` both log files? The first one will tell you more about what could went wrong on the server side when the webUI is used, and the second one can tell you about any possible error in the webUI itself directly (frontend code related). Because you mentioned you updated some package and then rolled back, maybe you have to clean the cache of your browser while loading those "blank pages". It should not really happen a browser cache problem (there is a mechanism in place to prevent it), but maybe you still have a dirty packages version on your machine. Moreover: any visible error in the browser console tab development tools?
2.) One of the 3 servers (actually the first SLES machine that had been registered) in "System Overview" shows 30 Patches and 53 Packages. Triggering an Patch is executed without error but afterwards the "system overview" still shows the missing patches and packages. On the respective system calling "zypper up" shows "Nothing to do.".
3.) At the WebUI under Salt / Keys a blank white "frame" is shown, too. Under Salt / Formula Catalog a white "frame" with the text "Something wrong happened. Please reload the page. If the problem persist, please check log files". Tomcat-Logs show: "GET /rhn/manager/formula-catalog HTTP/1.1" 200 34636 "GET /rhn/manager/api/formula-catalog/data HTTP/1.1" 200 142 "POST /rhn/manager/frontend-log HTTP/1.1" 200 16 "POST /rhn/manager/frontend-log HTTP/1.1" 200 16 Again a direct call of the 2nd URI with the "api" delivers a JSON document with a list of the catalogs available.
Any idea what is going wrong there (and how to fix it)? All pages worked fine in the beginning after the base installation of Uyuni (Uyuni 2020.01 on openSUSE 15.1)
The fact you see a "blank frame" on the "Notification Messages" and on the "Salt > Keys" pages, but you can see the "System Overview" page correctly, this partially rings a bell because the first two pages are built with a technology (ReactJS) but the third one is built with another technology (JSP). This seems to confirm the possibility of a browser cache problem (which could affect ReactJS technology only) or a dirty package version on the machine.
I wonder if Uyuni provides some tools for testing and/or aligning a system?
Thanks in advance!
Regards, Tobias.
Hth, -- Dario Leidi SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Am Sun, 5 Apr 2020 21:25:16 +0200
schrieb Dario Leidi
did you check - `/var/log/rhn/rhn_web_ui.log` - `/var/log/rhn/rhn_web_frontend.log` both log files? The first one will tell you more about what could went wrong on the server side when the webUI is used, and the second one can tell you about any possible error in the webUI itself directly (frontend code related).
Thanks, I wasn't aware about this log directory at all. Found some interesting stuff about "taskomatic" in this directory, too.
Because you mentioned you updated some package and then rolled back, maybe you have to clean the cache of your browser while loading those "blank pages". It should not really happen a browser cache problem (there is a mechanism in place to prevent it), but maybe you still have a dirty packages version on your machine.
As the "blank frame" disappeared at another web browser I deleted the cache for this site and actually your right - the respective pages look fine now, thanks! Which packages do you mean with being dirty?
2.) One of the 3 servers (actually the first SLES machine that had been registered) in "System Overview" shows 30 Patches and 53 Packages. Triggering an Patch is executed without error but afterwards the "system overview" still shows the missing patches and packages. On the respective system calling "zypper up" shows "Nothing to do.".
This issue didn't disappear. It's a little bit strange that I cannot find a log file with corresponding warnings or errors. -- Gruss, Tobias Crefeld. xmpp (no email): crefeld@xabber.de -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
On Thu, 2 Apr 2020 19:44:43 +0200 Tobias Crefeld
2.) One of the 3 servers (actually the first SLES machine that had been registered) in "System Overview" shows 30 Patches and 53 Packages. Triggering an Patch is executed without error but afterwards the "system overview" still shows the missing patches and packages. On the respective system calling "zypper up" shows "Nothing to do.".
There is way to fix this issue. At the WebUI there is a possibility to let Uyuni learn the patch status of a system: Systems / System Set Manager / Misc / Update package profiles Regards, Tobias. -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
participants (2)
-
Dario Leidi
-
Tobias Crefeld