Resolve an “Execution error (EOFException)” error message in Puppet Enterprise with disaster recovery

Your replica Puppet Server won’t start, and you get an error message in the pe-puppet-server.log file on the agent in Puppet Enterprise.

Error message

Execution error (EOFException) at org.eclipse.jgit.util.IO/readFully (IO.java:235). 

You get this error message in the pe-puppet-server.log file on the Puppet agent in PE.

Version and installation information

PE version: All supported

Solution

The puppet-server.log file on the replica Puppet server shows the file-sync-client-service got corrupted in PE. For example:

2022-11-22T08:58:37.582-05:00 INFO  [async-dispatch-2] [p.e.s.f.file-sync-client-service] Initializing file sync client service 

2022-11-22T08:58:37.595-05:00 INFO  [async-dispatch-2] [p.t.s.s.status-service] Registering status callback function for service 'file-sync-client-service', version 2019.8.0.84 

2022-11-22T08:58:37.605-05:00 INFO  [async-dispatch-2] [p.e.s.f.file-sync-client-service] Registering file sync client HTTP API 

2022-11-22T08:58:37.721-05:00 ERROR [async-dispatch-2] [p.t.internal] Error during service init!!! 

org.eclipse.jgit.api.errors.JGitInternalException: Short read of block. 

To resolve the error message and get your pe-puppet-server running in PE, follow these steps:

1. Stop running the replica Puppet server: systemctl stop pe-puppetserver.
2. Move the file-sync-client-service to a new location: mv /opt/puppetlabs/server/data/puppetserver/filesync/client/ /opt/puppetlabs/server/data/puppetserver/filesync/client_old/
3. Restart the Puppet server: systemctl start pe-puppetserver.

Are you still seeing issues with the Puppet server? Then, submit a Support ticket and attach a copy of the /var/log/puppetlabs/puppetserver/puppetserver.log.