Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-4642

Puppet 2019.3 upgrade failure from 2019.2.2

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: PuppetDB
    • Labels:
    • Template:
    • Team:
      PuppetDB
    • Method Found:
      Needs Assessment
    • CS Priority:
      Major
    • Zendesk Ticket IDs:
      37911,38027
    • Zendesk Ticket Count:
      2
    • CS Rank:
      1,500
    • QA Risk Assessment:
      Needs Assessment

      Description

      During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist. Please refer to the attached log file for more details.

      [m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event
      2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed!
      journalctl log for pe-puppetdb:
      -- Logs begin at Mon 2019-12-23 23:25:01 AEDT, end at Fri 2020-01-31 12:44:13 AEDT. --
      Jan 31 12:43:02 puppetlabs.com systemd[1]: Starting pe-puppetdb Service...
      Jan 31 12:43:37 puppetlabs.com puppetdb[124158]: WARNING: An illegal reflective access operation has occurred
      Jan 31 12:43:37 puppetlabs.com puppetdb[124158]: WARNING: Illegal reflective access by dynapath.defaults$eval24067$fn__24068 to method java.net.URLClassLoader.addURL(java.net.URL)
      Jan 31 12:43:37 puppetlabs.com puppetdb[124158]: WARNING: Please consider reporting this to the maintainers of dynapath.defaults$eval24067$fn__24068
      Jan 31 12:43:37 puppetlabs.com puppetdb[124158]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
      Jan 31 12:43:37 puppetlabs.com puppetdb[124158]: WARNING: All illegal access operations will be denied in a future release
      Jan 31 12:43:52 puppetlabs.com puppetdb[124158]: The [database] classname config option has been retired and will be ignored.
      Jan 31 12:43:52 puppetlabs.com puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.
      Jan 31 12:43:52 puppetlabs.com puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.
      Jan 31 12:44:04 puppetlabs.com puppetdb[124158]: The [database] classname config option has been retired and will be ignored.
      Jan 31 12:44:04 puppetlabs.com puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.
      Jan 31 12:44:04 puppetlabs.com puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.
      Jan 31 12:44:13 puppetlabs.com puppetdb[124158]: Execution error (PSQLException) at org.postgresql.core.v3.QueryExecutorImpl/receiveErrorResponse (QueryExecutorImpl.java:2497).
      Jan 31 12:44:13 puppetlabs.com puppetdb[124158]: ERROR: relation "resource_events_20200123z" does not exist
      Jan 31 12:44:13 puppetlabs.com puppetdb[124158]: Position: 13
      Jan 31 12:44:13 puppetlabs.com puppetdb[124158]: Full report at:
      Jan 31 12:44:13 puppetlabs.com puppetdb[124158]: /tmp/clojure-9861888815849128723.edn
      Jan 31 12:44:13 puppetlabs.com systemd[1]: pe-puppetdb.service: control process exited, code=exited status=1
      Jan 31 12:44:13 puppetlabs.com systemd[1]: Failed to start pe-puppetdb Service.
      Jan 31 12:44:13 puppetlabs.com systemd[1]: Unit pe-puppetdb.service entered failed state.
      Jan 31 12:44:13 puppetlabs.com systemd[1]: pe-puppetdb.service failed.
      
      2020-01-31T12:44:13.545+11:00 - [Error]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Service[pe-puppetdb]/ensure: change from 'stopped' to 'running' failed: Systemd start for pe-puppetdb failed!
      journalctl log for pe-puppetdb: 

       

      after truncating the resource_event table, the upgrade was successful and all the services are up and running. 

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              selvakumar.subburaj Selvakumar Azhagarsami
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support