• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Daily update check errors

dgarcia90

Basic Pleskian
Server operating system version
Ubuntu 20.04 LTS
Plesk version and microupdate number
18.0.57 Update#4
Hello everyone,

The last couple of days my server has been having issues when trying to find system updates at the scheduled time. This has happened to me in the past but it got fixed by itself and now it has started happening again.

Yesterday I got the first error message which was:

Reason: 2023-12-13 06:27:34 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2023-12-13 06:27:34 ERROR: Failed to lock directory /var/lib/apt/lists/: E:Could not get lock /var/lib/apt/lists/lock. It is held by process 2514634 (apt-get)
2023-12-13 06:27:34 ERROR: Exited with returncode 1.

Today I got a new error message:

Reason: 2023-12-14 06:25:48 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2023-12-14 06:25:49 ERROR: Apt cache fetch failed:
2023-12-14 06:25:49 ERROR:
2023-12-14 06:25:49 ERROR: Exited with returncode 1.

The strange thing is the fact that I can go to Plesk and check for system updates manually and it does not give any error at all

Any idea of what could be happening?

Thanks a lot for your help!
 
Just a quick update, after today I cannot check updates manually and I have an error in the logs:

Err:4 Index of linux/ubuntu/ focal InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7EA0A9C3F273FCD8
Err:12 Index of /ubuntu focal-security InRelease
Could not connect to security.ubuntu.com:80 (185.125.190.39), connection timed out
Hit:13 Index of /ubuntu focal InRelease
Get:14 Index of /ubuntu focal-updates InRelease [114 kB]
Hit:15 Index of /ubuntu focal-backports InRelease
Get:16 Index of /ubuntu focal-updates/main amd64 Packages [3020 kB]
Get:17 Index of /ubuntu focal-updates/main i386 Packages [918 kB]
Get:18 Index of /ubuntu focal-updates/universe amd64 Packages [1140 kB]
Get:19 Index of /ubuntu focal-updates/universe i386 Packages [762 kB]
Fetched 5955 kB in 32s (189 kB/s)
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of linux/ubuntu/ focal InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7EA0A9C3F273FCD8
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease Could not connect to security.ubuntu.com:80 (185.125.190.39), connection timed out
W: Failed to fetch https://download.docker.com/linux/ubuntu/dists/focal/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7EA0A9C3F273FCD8
W: Some index files failed to download. They have been ignored, or old ones used instead.
autoinstaller: read output of apt-cache policy
 
Update: I've been able to add the public key and now it does not give any error, let's hope that tomorrow with the scheduled check does not give any error
 
Back
Top