Learn & Share

To check what is blocking the DROP DATABASE command, run the following command; #mysqladmin processlist -u root -p You can see the query id 50, 200 and 207 is blocking the dropping of koha_library. Use mysql to terminate the query; #mysqladmin kill 50 Repeat the termination for other IDs.

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_...

Error : Solution : Open the file /etc/defult/grub  replace the line GRUB_CMDLINE_LINUX_DEFAULT= "quiet" with GRUB_CMDLINE_LINUX_DEFAULT= "quiet intel_iommu=on" # update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.78-2-pve Found initrd image: /boot/initrd.img-5.4.78-2-pve Found linux image: /boot/vmlinuz-5.4.73-1-pve Found initrd image: /boot/initrd.img-5.4.73-1-pve Found memtest86+ image: /boot/memtest86+.bin Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin Adding boot menu entry for EFI firmware configuration done # reboot // the VM

 Issue : #sudo koha-enable-sip library # koha-start-sip library   Deprecated script used (koha-start-sip) Solution: You can manually start and the SIP2 Server in Koha cd /usr/share/koha/lib export PERL5LIB=/usr/share/koha/lib export KOHA_CONF=/etc/koha/sites/library/koha-conf.xml perl -IC4/SIP/ -MILS C4/SIP/SIPServer.pm /etc/koha/SIPconfig.xml

 Error : An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums. Solution : First find the ip address of the api.wordpress.org C:\Users\SJ/PC-G>nslookup wordpress.org Server:  ns0.jnec.edu.bt Address:  192.168.255.222 Non-authoritative answer: Name:    wordpress.org Address:  198.143.164.252 In the Wordpress host server, run the following command: echo "198.143.164.251 api.wordpress.org" >> /etc/hosts

Here is the solution to the Proxmox update and upgrade issue. Error :  E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  401  Unauthorized [IP: 51.79.159.216 443] Error:  root@moni:~# # apt update Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://ftp.debian.org/debian buster InRelease            Hit:3 http://ftp.debian.org/debian buster-updates InRelease    Err:4 https://enterprise.proxmox.com/debian/pve buster InRelease 401  Unauthorized [IP: 51.79.159.216 443] Reading package lists... Done            | E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  401  Unauthorized [IP: 51.79.159.216 443] E: The repository 'https://enterprise.proxmox.com/debian/pve buster InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-s...

 Even if you successfully set the mysql root password, mysql(MariaDb 10.+) allows you to login without any password or with any random string.  Solution :  the default mariaDB installations plugins like  'console' or 'unix_socket' allows us to login without password. Try following commands to solve the issue.  mysql -u root -p  use mysql; SELECT host, user, password, plugin FROM mysql.user LIMIT 0,1; --------------------------------------------------------------------------------- SET PASSWORD FOR 'root' @ 'localhost' = PASSWORD ( 'MyNewPass' ); UPDATE mysql.user SET plugin = '' WHERE user = 'root' AND host = 'localhost' ; FLUSH PRIVILEGES ;

 #dpkg-reconfigure tzdata

Error or Issue : Unmet Dependencies:  # sudo apt install mariadb-server Reading package lists... Done Building dependency tree        Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies:  mariadb-server : Depends: mariadb-server-10.3 (>= 1:10.3.25-0ubuntu0.20.04.1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Solution or Fix : Remove the different version of MySQL/MariaDB. To check the version run the following command. #  dpkg -l | grep -E 'mysql|mariadb' output:  ii  libdatetime-format-mysql-perl          0.06-1        ...

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 deta...