Bug 64538
| Summary: | Web based update process does not appear to log errors | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Michael Waite <mwaite> |
| Component: | up2date | Assignee: | Adrian Likins <alikins> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fanny Augustin <fmoquete> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | CC: | cturner, gafton, mihai.ibanescu, pjones, taw |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2002-05-15 19:40:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Michael Waite
2002-05-07 17:37:42 UTC
Is this kind of information being captured by the client and not passed along by server code, or not being captured by the client? It does not appear to be captured by the client. Here is a snippet from /var/log/up2date you will see that is is tryi8ng to resolve dependancies for libpisock.so.4 and then does not return any errors. [Mon May 6 17:37:30 2002] up2date successfully retrieved authentication token from up2date server [Mon May 6 17:37:30 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:37:30 2002] up2date getAvailablePackageList from network [Mon May 6 17:37:30 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:37:30 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:38:13 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:38:13 2002] up2date updating login info [Mon May 6 17:38:13 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:38:13 2002] up2date logging into up2date server [Mon May 6 17:38:13 2002] up2date successfully retrieved authentication token from up2date server [Mon May 6 17:38:13 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:38:13 2002] up2date getAvailablePackageList from network [Mon May 6 17:38:13 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:38:13 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:38:13 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:38:13 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:38:13 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:38:13 2002] up2date solving dep for: ['libpisock.so.4', 'libpisock.so.4'] [Mon May 6 17:40:10 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:40:10 2002] up2date updating login info [Mon May 6 17:40:10 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:40:10 2002] up2date logging into up2date server [Mon May 6 17:40:10 2002] up2date successfully retrieved authentication token from up2date server [Mon May 6 17:40:10 2002] up2date Opening rpmdb in /var/lib/rpm/ with option 0 [Mon May 6 17:40:10 2002] up2date getAvailablePackageList from network Can you try this with the version of the client in 7.3 or the current 7.2 errata? Those versions should be much better about reporting errors. I am running this on my laptop which is my primary workstation. I can't udgrade it to 7.3 right now as I have it exactly the way I want it. Unless you think that a 7.3 "upgrade" will work. Generally I shy away from doing that. what version of the client are you using? the current erratad version for up2date should report this info as well. No followup for 6 months, closing. |