Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-779

postgresql warning message "nonstandard use" in logfile

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Fixed
    • Icon: Major Major
    • 1.6
    • 1.6
    • None
    • None
    • ubuntu hardy / debian etch

      Logwatchchecks (and also other checks) that return quotes with values raise this Warning Message in zabbix-server and also in postgresql.log:

      HINT: Use the escape string syntax for backslashes, e.g., E'
      '.
      WARNING: nonstandard use of
      in a string literal
      LINE 1: ....log,sshd
      []') or (h.host='vlxp01-dd' and i.key_='log[/var/...
      ^
      HINT: Use the escape string syntax for backslashes, e.g., E'
      '.
      WARNING: nonstandard use of
      in a string literal
      LINE 1: ....log,sshd
      []') or (h.host='vlxp01-dd' and i.key_='log[/var/...
      ^
      HINT: Use the escape string syntax for backslashes, e.g., E'
      '.
      WARNING: nonstandard use of
      in a string literal
      LINE 1: ....log,sshd
      []') or (h.host='vlxp01-dd' and i.key_='log[/var/...
      ^
      HINT: Use the escape string syntax for backslashes, e.g., E'
      '.
      WARNING: nonstandard use of
      in a string literal
      LINE 1: ....log,sshd
      []') or (h.host='vlxp01-dd' and i.key_='log[/var/...
      ^
      HINT: Use the escape string syntax for backslashes, e.g., E'
      '.
      WARNING: nonstandard use of
      in a string literal
      LINE 1: ....log,sshd
      []') or (h.host='vlxp01-dd' and i.key_='log[/var/...
      ^
      HINT: Use the escape string syntax for backslashes, e.g., E'
      '.

      This concerns changes in postgresql 8.x that are discussed here:

      It bulks the logfile a lot in both postgresql and zabbix-server, please fix.

            sasha Alexander Vladishev
            tekknokrat Gunnar Thielebein
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: