Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1651688 - red herring messages SQL Warning Code: 0, SQLState: 00000 several times per second in candlepin.log and error.log
Summary: red herring messages SQL Warning Code: 0, SQLState: 00000 several times per s...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Candlepin
Version: 6.3.4
Hardware: All
OS: All
medium
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: jcallaha
URL:
Whiteboard:
Depends On: 1667149
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-20 15:10 UTC by Jan Jansky
Modified: 2021-08-30 12:39 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1667149 (view as bug list)
Environment:
Last Closed: 2019-10-22 15:03:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2184801 0 None None None 2019-10-15 08:35:11 UTC

Description Jan Jansky 2018-11-20 15:10:03 UTC 
Description of problem:
Hello one of our customers contact us about messages like

WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Warning Code: 0, SQLState: 00000
WARN  org.hibernate.engine.jdbc.spi.SqlExceptionHelper - bind <unnamed> to S_2


several times per second. It is not causing any troubles with Satellite itself, but it is filling quickly logs error.log and candlepin.log

Version-Release number of selected component (if applicable):
Satellite 6.3.5 (not an option in selection)
candlepin-2.1.24-1.el7.noarch
candlepin-selinux-2.1.24-1.el7.noarch


How reproducible:
Not sure, never saw this and it looks like red herring to me, also customer claimed that he is not observing any issue, only filling up logs


Actual results:
WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Warning Code: 0, SQLState: 00000
WARN  org.hibernate.engine.jdbc.spi.SqlExceptionHelper - bind <unnamed> to S_2

Expected results:
none

or 

DEBUG org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Warning Code: 0, SQLState: 00000
DEBUG  org.hibernate.engine.jdbc.spi.SqlExceptionHelper - bind <unnamed> to S_2


Additional info: If you will need any details, please let us know... also adding owner of the case as CC.
Comment 1 Barnaby Court 2018-11-24 04:39:20 UTC 
First I have seen this, what version of postgres is installed on the system?
Comment 7 ojanus 2019-10-22 15:03:50 UTC 
SQL Warning Code: 0, SQLState: 00000 is not an error. As you see in the [Postgresql Documentation](https://www.postgresql.org/docs/10/errcodes-appendix.html), code 00000 indicates successful completion.

These logs can be turned ON/OFF in /var/lib/pgsql/data/postgresql.conf in the section "When to Log". Below is the relevant section. There are multiple levels and level "debug2" logs successful completion as a warning.

```
# - When to Log -

client_min_messages = debug2
                                        #   debug5
                                        #   debug4
                                        #   debug3
                                        #   debug2
                                        #   debug1
                                        #   log
                                        #   notice
                                        #   warning
                                        #   error

log_min_messages = debug2
                                        #   debug5
                                        #   debug4
                                        #   debug3
                                        #   debug2
                                        #   debug1
                                        #   info
                                        #   notice
                                        #   warning
                                        #   error
                                        #   log
                                        #   fatal
                                        #   panic

log_min_error_statement = debug2
                                        #   debug5
                                        #   debug4
                                        #   debug3
                                        #   debug2
                                        #   debug1
                                        #   info
                                        #   notice
                                        #   warning
                                        #   error
                                        #   log
                                        #   fatal
                                        #   panic (effectively off)

#log_min_duration_statement = -1        # -1 is disabled, 0 logs all statements
                                        # and their durations, > 0 logs only
                                        # statements running at least this number
                                        # of milliseconds

```
Note You need to log in before you can comment on or make changes to this bug.