Jira (PDB-4509) Puppetdb 6.5, PG9.6.15, fresh install of puppetdb service will not start ERROR: invalid byte sequence for encoding "UTF8"

[Scot Kreienkamp (JIRA)]

Scot Kreienkamp created an issue

PuppetDB / PDB-4509 Puppetdb 6.5, PG9.6.15, fresh install of puppetdb service will not start ERROR: invalid byte sequence for encoding "UTF8" Issue Type: Bug Affects Versions: PDB 6.5.0 Assignee: Unassigned Components: PuppetDB Created: 2019/09/18 11:24 AM Environment: RHEL7.7, PG9.6.15, puppet-agent-6.8.1, puppetdb-6.5.0   puppetdb=# select extname from pg_extension; extname --------- plpgsql pg_trgm   Locale:  LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= Priority: Normal Reporter: Scot Kreienkamp On first start of puppetdb after install it is failing with error:  2019-09-18T13:31:10.415-04:00 INFO [p.p.s.migrate] Applying database migration version 43 2019-09-18T13:31:10.456-04:00 ERROR [p.p.s.migrate] Caught SQLException during migration java.sql.BatchUpdateException: Batch entry 1 CREATE AGGREGATE sha1_agg (BYTEA) ( sfunc = dual_sha1, stype = bytea, initcond = '\x00' ) was aborted: ERROR: invalid byte sequence for encoding "UTF8": 0x00 Call getNextException to see other errors in the batch. Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Scot Kreienkamp (JIRA)]

Scot Kreienkamp updated an issue

PuppetDB / PDB-4509 Puppetdb 6.5, PG9.6.15, fresh install of puppetdb service will not start ERROR: invalid byte sequence for encoding "UTF8"

Change By: Scot Kreienkamp Attachment: puppetdb.log

Add Comment

[Austin Blatt (JIRA)]

Austin Blatt commented on PDB-4509

Re: Puppetdb 6.5, PG9.6.15, fresh install of puppetdb service will not start ERROR: invalid byte sequence for encoding "UTF8" Robert Roland Can you take a look at this error? It's in the same realm as your md5 to sha1 migration change, so I want to check if you know what would cause this error off the top of your head.

Add Comment