Hi EMS admins
When I update from EMS 7.4.4 to EMS 7.4.5 I have the following error.
Upgrade EMS: Err:1 http://apt.postgresql.org/pub/repos/apt noble-pgdg InRelease
Upgrade EMS: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7FCC7D46ACCC4CF8
The upgrade finishes successfully however. And I think you have seen similar error if you performed the same EMS update operation.
The question is:
Did it bypass the signature check and installed PostgreSQL update? Or did it just abort PostgreSQL update and performed the other package updates?
Hi AEK,
what version of pgsql are you running after the update to 7.4.5 ? i'm still at 7.4.4 and have psql (PostgreSQL) 15.15 (Ubuntu 15.15-1.pgdg22.04+1) , but did a apt upgrade previously.
Hi Funky
But how can I get this info? With the new versions we are blind on what happens inside.
oh I see , you are using EMS installed as a VM Image ... i'm using the installation on top of Ubuntu Server, since I'm a nerd :) that's why I can find it.
I know you did well and I may do the same in my future integrations. However for regular admins the hardened system (VM install) should be the best choice for security, right?
sure. the VM is good as it implements best practices, removes unnecessary users/services and has only the required ports opened.
but to be honest, if you have some linux skills and the time/willingness to do, you can do those things also by yourself and on the plus side you have better control of the OS/packages/debug etc.
| User | Count |
|---|---|
| 2862 | |
| 1445 | |
| 829 | |
| 820 | |
| 455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.