Update Ubuntu, NO_PUBKEY, GPG error, The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3C9356BBA2E41F10

-

If you get the following NO_PUBKEY error

sjam@kh:~# sudo apt update
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu bionic-security InRelease
Get:2 http://debian.koha-community.org/koha stable InRelease [49.7 kB]
Err:2 http://debian.koha-community.org/koha stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3C9356BBA2E41F10
Reading package lists... Done
W: GPG error: http://debian.koha-community.org/koha stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3C9356BBA2E41F10
E: The repository 'http://debian.koha-community.org/koha stable InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

sjam@kh:~# sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3C9356BBA2E41F10


Comments

Post a Comment

Popular posts from this blog

ACTION_FAILED:OU_INVALID: Solution for GoogleApps bulk user upload issue, username@domainname.com:ACTION_FAILED:OU_INVALID. This error is because you have not specified the Org Unit Path properly.

-
To upload bulk users to GoogleApps, you will require a following required fileds, other fields are optional:-               First Name               Last Name               Email Address               Password               Org Unit Path What is 'Org Unit Path'? This field was not their earlier. This is the path to place users in an organizational unit. For example if your domain has different organization unit like , staff, students, guest etc.. then the Org Unit Path would be just :  /
Read more

Email Notification in Koha! How to configure Email Notification in Koha 20.11 with postfix?

-
Image
Here is the steps to configuring Koha 20.11 & postfix for sending notices/slips through email. 1. First install postfix             #sudo apt-get update             #sudo apt-get install postfix          Click on OK.    Tab and select No configuration. 2.  Copy the configuration file     #  cp /usr/share/postfix/main.cf.debian /etc/postfix/main.cf 3. Install the other required packages.     #apt-get install libsasl2-2     #apt-get install libsasl2-modules     #apt-get install ca-certificates 4.  Open the following file and add few lines.     # vim /etc/postfix/main.cf and add the following lines at the bottom of the page and save the file.     relayhost = [smtp.gmail.com]:587     smtp_sasl_auth_enable = yes     smtp_sasl_password_...
Read more

Solution to Moodle Error: Coding error detected, it must be fixed by a programmer: Failed to unserialise data from file. Either failed to read, or failed to write.

-
Image
Did you ever come across the following error when you try to access Moodle, "Coding error detected, it must be fixed by a programmer: Failed to unserialise data from file. Either failed to read, or failed to write." This usually happens when cache files are corrupted, one probable cause can be improper shutdown of Moodle system. Here is the solution to fix the issue. 1. Go to Moodle root directory     #cd /var/www/html/moodle   2. Run the command      #php admin/cli/purge_caches.php 3. Go to moodledata/cache directory   #cd /var/moodledata/cache    4. Remove the cache store directory, DO NOT remove of change the core_component.php file    # rm -rf cachestore_file/ 5. Refresh the Moodle Page. Its should work.
Read more