Bug 878195
| Summary: | OSA-dispatcher generating errors after troubleshooting 862058 | ||
|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | JDavis4102 |
| Component: | Server | Assignee: | Michael Mráka <mmraka> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.6 | CC: | JDavis4102, jpazdziora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-12-21 07:23:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1484117 | ||
There have been numerous fixes to Spacewalk code base since Spacewalk 1.6. Please upgrade to Spacewalk 1.8 to see if it resolves your issue. I really don't want to upgrade to 1.8 with the errors it is generating now as it wasn't before I worked that other issue. Also why tell me to upgrade to 1.8 when in the last bug you told me to create this bug report. You could have saved me some time by telling me there. This is really getting frustrating. This issue was caused by you telling me to set a setting in PostgreSQL. Please help me resolve this issue as it was caused by you telling me to change something. After changing that setting and then switching it back it generates these errors. I don't want to upgrade until this is resolved as I feel it can be resolved with the current version. (In reply to comment #2) > I really don't want to upgrade to 1.8 with the errors it is generating now > as it wasn't before I worked that other issue. Also why tell me to upgrade > to 1.8 when in the last bug you told me to create this bug report. You could > have saved me some time by telling me there. When you reopened bug 862058 today after response to comment that marked the bugzilla resolved in Spacewalk, there was no way I assumed that you have *not* upgraded to the latest Spacewalk release yet. > This issue was caused by you telling me to set a setting in PostgreSQL. This is not correct -- my first comment on bug 862058 was the one when I said that this setting is not needed. Which is true for Spacewalk 1.8. I am sorry got my names of people mixed up. It was Michael Mráka that suggested I set the PostgreSQL setting. I guess I will go ahead and upgrade to 1.8. If this was prod I wouldn't do this as I still feel this can be resolved without the upgrade. I have a Test and Prod environment that is not generating the errors with the remote command fix added from the other bug. I will upgrade and let you know if I have any issues and if the upgrade resolves the current issue. Upgrade to 1.8 resolved all issues. Sorry to have wasted your time and sorry if I came off a little harsh. That wasn't my intention at all. (In reply to comment #5) > Upgrade to 1.8 resolved all issues. Marking as such. Thank you. This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug. |
Description of problem: osa-dispatcher is generating the following errors after troubleshooting issue 862058. After switching the standard_conforming_strings setting I now get the following errors. 2012/10/03 10:16:55 -07:00 9473 0.0.0.0: rhnSQL/driver_postgresql._execute_('ERROR', 'ERROR: \n update rhnPushClient\n set state_id = %(offline_id)s\n where state_id = %(online_id)s\n and last_ping_time is not null\n and current_timestamp > next_action_time\n ') 2012/10/03 10:16:55 -07:00 9473 0.0.0.0: rhnSQL/driver_postgresql._execute_('ERROR', "PARAMS: {'online_id': 1, 'offline_id': 2}") 2012/10/03 10:16:55 -07:00 9473 0.0.0.0: rhnSQL/driver_postgresql._execute_('ERROR', 'ERROR: \n select id, name, shared_key, jabber_id\n from rhnPushClient\n where state_id = %(online_id)s\n and last_ping_time is not null\n and next_action_time is null\n and jabber_id is not null\n ') 2012/10/03 10:16:55 -07:00 9473 0.0.0.0: rhnSQL/driver_postgresql._execute_('ERROR', "PARAMS: {'online_id': 1}") 2012/10/03 10:16:55 -07:00 9473 0.0.0.0: rhnSQL/driver_postgresql._execute_('ERROR', "ERROR: \n select a.id, sa.server_id, pc.jabber_id,\n date_diff_in_days(current_timestamp, earliest_action) * 86400 delta\n from\n rhnServerAction sa,\n rhnAction a,\n rhnPushClient pc\n where pc.server_id = sa.server_id\n and sa.action_id = a.id\n and sa.status in (0, 1) -- Queued or picked up\n and not exists (\n -- This is like saying 'this action has no\n -- prerequisite or has a prerequisite that has completed\n -- (status = 2)\n select 1\n from rhnServerAction sap\n where sap.server_id = sa.server_id\n and sap.action_id = a.prerequisite\n and sap.status != 2\n )\n order by earliest_action\n ") 2012/10/03 10:16:55 -07:00 9473 0.0.0.0: rhnSQL/driver_postgresql._execute_('ERROR', 'PARAMS: {}') Even switching the setting back to default still generates the errors. Postgresql*.log doesn't show any errors other than the following: WARNING: nonstandard use of \\ in a string literal at character 1247 HINT: Use the escape string syntax for backslashes, e.g., E'\\'. There are no other logs generated that I can see. Version-Release number of selected component (if applicable): 1.6 How reproducible: Change the standard_conforming_strings setting. Actual results: Starting generating errors. Expected results: No errors generated.