Bug 1667149 - 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: Candlepin
Classification: Community
Component: candlepin
Version: 2.5
Hardware: All
OS: All
medium
low
Target Milestone: ---
: ---
Assignee: candlepin-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 1651688
TreeView+ depends on / blocked
 
Reported: 2019-01-17 15:02 UTC by Kevin Howell
Modified: 2019-10-22 15:03 UTC (History)
3 users (show)

Fixed In Version:
Clone Of: 1651688
Environment:
Last Closed: 2019-10-22 15:03:17 UTC
Embargoed:


Attachments (Terms of Use)

Comment 1 ojanus 2019-10-22 15:03:17 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.