ePO Repository pull fails with error

[cdinet]

That doesn't make sense, as neither servers have those keys.  I don't know how the pkgcatalog.z is signed with a key that doesn't exist.  Do you have any other epo servers?

[TobbeFlybring]

Exactly my point! It seems impossible!
No, I do not have any more ePO's in the system

[cdinet]

The only thing I can suggest is to possibly rebuild the master repository completely on the master server. You would need to note what products you have checked in, versions and branches.  To rebuild the repo, you would turn off the server service, rename the software directory and create a new blank one.  Then start service back up and start checking in products.  That would also require replication to any distributed repositories, if you have any.

Did you ever at one point reinstall epo?

[TobbeFlybring]

Master server have been upgraded from 5.32 through 5.9 up til 5.10 update 6

Slave server is new install

[cdinet]

Do you happen to have any backups of epo install folder from any of the installs, including the older ones?  There may be a key in there.  You can check the hashes of them by opening up the zip file and look at the properties file in notepad.

Otherwise you are at a rebuild.

[TobbeFlybring]

Think I need to try a rebuild.
Is there any documentation available for doing that?

[cdinet]

Yes, KB53736

[TobbeFlybring]

Tried rebuilding the Master Repository on the Master,.

Same error: 

(Failed to verify site catalog, no repository public key matches signature.)

Noticed another thing in EpoAPSvr.log:

20200205072948 W #04952 RMANJNI
No agent handler assignments or assignment groups found in the database

20200205072948 I #04952 RMANJNI
Adding Master-Epo from specified agent handlers to site list

This repeats continously at the end of the log file. Is there any connection between this and the error I'm getting?

[cdinet]

Are you getting that error on the master epo logs or the slave for the no repository public key matches signature?  I will send you a private message with my email address, I need to see some screenshots that should not be here publicly.

For No agent handler assignments or assignment groups found in the database error, that may be if you have no agent handlers and have not created any agent handler assignment rules.  To verify, just go ahead and create one under agent handlers and assign it to my org and let me know if that goes away.

[TobbeFlybring · Accepted solution]

I managed to get this to work using another approach.

I removed the Slave ePO and installed an Agent Handler instead and connected all nodes to the Master ePO.

This works for the environment I am working in at the moment, so I will not spend any more time on trying to fix the issue.

But to answer your question:  I got key error in the Slave ePO.