Pacman error failed to synchronize all databases

#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
ILoveCandy
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
#HookDir     = /etc/pacman.d/hooks/
HoldPkg     = pacman glibc
#XferCommand = /usr/bin/curl -L -C — -f -o %o %u
#XferCommand = /usr/bin/wget —passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto

# Pacman won’t upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg   =
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
#Color
#NoProgressBar
CheckSpace
#VerbosePkgLists
#ParallelDownloads = 5

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key —init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key —populate archlinux`.

#
# REPOSITORIES
#   — can be defined here or included from another file
#   — pacman will search repositories in the order defined here
#   — local/custom mirrors can be added here or in separate files
#   — repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   — URLs will have $repo replaced by the name of the current repo
#   — URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial — it must be present and
# uncommented to enable the repo.
#

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

[testing]
#Include = /etc/pacman.d/mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

[community-testing]
#Include = /etc/pacman.d/mirrorlist

[community]
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

[multilib]
Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

Arch Linux

You are not logged in.

#1 2012-09-16 07:53:19

[SOLVED] pacman: «unable to lock database»

I have been working hard to install my Arch Linux as all of you have but now that i finally installed it i am trying to do some
postinstalation things located here.

I first opened /etc/pacman.conf file and at the end of the file added the repository [multilib], which pacman was
supposed to look for on my 1st mirror in /etc/pacman.d/mirrorlist which is this one.
Long story short, this is the code i added in my /etc/pacman.conf:

I saved the file but while mirror is available pacman still refuses to update mirror lists using command:

This produces the error:

I am currently logged in as root and i don’t know why is the database locked, as root was supposed to be able to do whatever he likes?
What can i do to resolve the «lock database» error?

Last edited by 71GA (2012-09-16 09:28:37)

C, ARM, ARM assembly, HTML, CSS, JS, Linux

#2 2012-09-16 08:04:53

Re: [SOLVED] pacman: «unable to lock database»

Did you try to remove the db.lck file? This happens when pacman is interrupted.

#3 2012-09-16 08:06:12

Re: [SOLVED] pacman: «unable to lock database»

Did you try to remove the db.lck file? This happens when pacman is interrupted.

Is it safe to do it?

C, ARM, ARM assembly, HTML, CSS, JS, Linux

#4 2012-09-16 08:26:39

Re: [SOLVED] pacman: «unable to lock database»

I did remove /var/lib/pacman/db.lck and again used command

And it partialy worked as it did update repositories [core] [extra] and [comunity]. After this it again reports
an error about [multilib]. This is the error which i get for every mirror listed in my /etc/pacman.d/mirrorlist file:

«404 Not Found» indicates that URL cant be found which could be an internet problem, but this can’t be the issue here
as other depositories are sucessfully installed and furthermore it could never have happend to all the mirrors at once.

Last edited by 71GA (2012-09-16 08:28:06)

Источник

Ошибка error: failed to synchronize all databases (unable to lock database) (РЕШЕНО)

При попытке обновить Arch Linux или дистрибутив на его основе (например, BlackArch) может возникнуть ошибка «error: failed to synchronize all databases (unable to lock database)».

Например, при вводе команды

Может быть выведено (в случае, если система с английской локалью):

С русской локалью будет написано «ошибка: failed to synchronize all databases (не удалось заблокировать базу данных)», то есть ошибка синхронизации всех баз данных из-за того, что не получилось заблокировать базу данных.

Это означает, что создан файл, который говорит о том, что база данных пакетов заблокирована для работы, поскольку в настоящее время работу с базой данной пакетов ведёт другая программа.

Если это действительно так (например, вы уже запустили pacman в другой вкладке), то рекомендуется дождаться выполнения этой команды, чтобы впоследствии не возникло ошибок в кэше и базе данных установленных пакетов.

Если вы уверены, что это сообщение выводиться исключительно по ошибке — например, вы через SSH с помощью pacman обновляли пакеты, но сессия неожиданно была прервана и вы вновь подключись к удалённому компьютеру, но при попытке использовать pacman появляется эта ошибка, то в этом случае для её исправления достаточно удалить файл /var/lib/pacman/db.lck следующим образом:

После этого вновь запустите pacman — проблема должна быть полностью решена.

Если вы не уверены, нужно ли удалять файл db.lck, то вы можете проверить дату его создания следующим образом:

Дата создания может подсказать вам, по какой причине данный файл присутствует в системе.

Если проблема не решена, то второй причиной может быть переполненность диска — на нём не осталось места чтобы записать файл блокировки. В этом случае очистите диск и повторите команду для обновления системы.

Очистку можно начать с удаления журналов. Например, для удаления логов веб-сервера:

Для удаления временных файлов:

Для удаления файлов установочных пакетов:

Близкие статьи

• Ошибка error: failed to update core (unable to lock database) (РЕШЕНО) (100%)
• Ошибка: «файл vmlinuz-linux» не найден (РЕШЕНО) (100%)
• Аналог опции —force в pacman (100%)
• Ошибка pacman «warning: failed to retrieve some files» (РЕШЕНО) (100%)
• Ошибка «ruby-bundler: /usr/share/man/man5/gemfile.5.gz exists in filesystem (owned by ruby)» (РЕШЕНО) (100%)
• Практические примеры использования pacman (RANDOM — 83.4%)

1 thought on “ Ошибка error: failed to synchronize all databases (unable to lock database) (РЕШЕНО) ”

OS: EndeavourOS Linux
`:+sssssssssso/. Host: B250M-DS3H
`-/ossssssssssssso/. Kernel: 5.19.7-zen2-1
`-/+sssssssssssssssso+:` Uptime: 22 mins
`-:/+sssssssssssssssssso+/. Packages: 853 (pacman
`.://osssssssssssssssssssso++- Shell: bash 5.1.16
.://+ssssssssssssssssssssssso++: Resolution: 1680×1050
.:///ossssssssssssssssssssssssso++: WM: i3
`:////ssssssssssssssssssssssssssso+++. Theme: Adwaita [GTK2]
`-////+ssssssssssssssssssssssssssso++++- Icons: Adwaita [GTK2]
`..-+oosssssssssssssssssssssssso+++++/` Terminal: xfce4-termi
./++++++++++++++++++++++++++++++/:. Terminal Font: Source
`. ——« CPU: Intel i7-7700 (8
GPU: NVIDIA GeForce G
Memory: 1018MiB / 320

OS: EndeavourOS Linux
`:+sssssssssso/. Host: B250M-DS3H
`-/ossssssssssssso/. Kernel: 5.19.7-zen2-1
`-/+sssssssssssssssso+:` Uptime: 22 mins
`-:/+sssssssssssssssssso+/. Packages: 853 (pacman
`.://osssssssssssssssssssso++- Shell: bash 5.1.16
.://+ssssssssssssssssssssssso++: Resolution: 1680×1050
.:///ossssssssssssssssssssssssso++: WM: i3
`:////ssssssssssssssssssssssssssso+++. Theme: Adwaita [GTK2]
`-////+ssssssssssssssssssssssssssso++++- Icons: Adwaita [GTK2]
`..-+oosssssssssssssssssssssssso+++++/` Terminal: xfce4-termi
./++++++++++++++++++++++++++++++/:. Terminal Font: Source
`. ——« CPU: Intel i7-7700 (8
GPU: NVIDIA GeForce G
Memory: 1018MiB / 320

Your advice is right. My sistem is update now . Thank you for your efforts.

Источник

error: failed to synchronize all databases (unable to lock database) (SOLVED)

January 14, 2022

When trying to update Arch Linux or a distribution based on it (for example, Manjaro or BlackArch), an error “failed to synchronize all databases (unable to lock database)”» may occur.

For example, when entering the command

It can be output:

This means that a file has been created that indicates that the package database is locked for processing, because another program is currently working with the package database.

If this is indeed the case (for example, you have already started pacman in another tab), then it is recommended that you wait for this command to complete so that there are no errors in the cache and database of installed packages later.

If you are sure that this message is displayed exclusively by mistake – for example, you updated packages via SSH using pacman, but the session was unexpectedly terminated and you reconnect to the remote computer, but this error appears when you try to use pacman, then in this case for fixing it is enough to delete the file /var/lib/pacman/db.lck file as follows:

After that, run pacman again – the problem should be completely resolved.

If you are unsure whether to delete the db.lck file, you can check its creation date as follows:

The creation date can tell you why this file is present in the system.

If the problem is not solved, then the second reason may be the disk is full – there is no space left on it to write the lock file. In this case, clean the disk and retry the command to update the system.

You can start the cleanup by deleting the logs. For example, to remove web server logs:

Источник

Pacman troubleshooting

Содержание

Various issues relating to the download and installation of software packages from the Manjaro repositories are dealt with here.

«Unrecognized archive format» Error

It has ocurred more than once, an update is issuing these messages in a seemingly never ending stream. Pacman could not open file: sync files

The error relates to a mismatch in the information contained in the db files at the mentioned location and the db files at the first mirror in your mirrorlist. Pacman checks a package in the database and sees if the signature file matches the one in the database. If it does not, then pacman will say the package is corrupted.

While it sometimes is possible to fix the issue simply by deleting the files and the running a pacman update it far from every time.

One recipe for fixing this

It is mandatory to ensure that the keyrings is current. By ensuring the keyrings are in shape and then redownloading the databases we reestablish the chain of trust between the keyrings and the packages.

You will have to find the correct names by looking at

Replace yyyymmdd and x with the info found at the above links

Remove your faulty databases

Download the databases and update the system

«Unable to lock database» Error

When downloading and installing software from the repositories, a special database lock file will be created in order to ensure that the current installation process is the only one running at that time. Otherwise, attempting to install multiple files from multiple sources simultaneously may corrupt the downloaded files, cause file conflicts — or worse still — damage your system. Once the installation has been completed, the lock file will then be automatically deleted. This error may therefore occur due to two possible reasons:

• Another installation is still taking place and has not yet finished, or
• A previous installation attempt had not finished properly (e.g. due to being aborted early)

It is therefore wise to first check to ensure that another installation is not (or had not been) in process at the time of the error. When satisfied that this is not the case, then the database lock file can be manually deleted. To do so, open up the terminal and enter the following command:

Once done, you should now be able to successfully re-attempt your intended installation.

Errors about Keys

We all have our own unique signatures which are used to authenticate who we are and to prevent fraudulent or even malicious activities by others. This is also the case with software packages available from the software repositories. They all contain encrypted codes (signature keys) unique to their developers to ensure that they are authentic and not malicious in nature.

During the installation process, once any software packages have been downloaded, your system will first check their signature keys to ensure that they are authentic prior to actually installing them. If a signature key cannot be verified for any reason, then the installation process will be aborted. This problem will usually occur due to:

• one or more signature keys contained in your system’s database being revoked, changed, corrupted, or out of date
• one or more software packages not having been signed off properly when placed in a repository

Where a package has not been signed off properly before being placed in a repository, it will be the responsibility of the developer(s) to correct this. However, as this problem will be more than likely due to a problem with your system’s verification of a signiture key, this can be solved in three easy steps. Working net connection is required. Once you have opened your terminal:

1. Remove old (and possibly broken) keys by entering this command:

2. Reinstall keyrings including the latest keys:

3. Initialize the pacman keyring:

4. Load the signature keys:

5. Refresh and update the signature keys:

6. Clear out the software packages downloaded during the aborted installation (optional):

1. Remove old (and possibly broken) keys by entering this command:

2. Initialize the pacman keyring:

3. Download the packages:

Those running ARM may also need to download archlinuxarm-keyring and manjaro-arm-keyring.

4. Remove the signatures:

5. Install the downloaded packages manually:

6. Clear out the software packages downloaded during the aborted installation (optional):

7. Remove the custom package folder: (optional):

After that try running sudo pacman -Syu to see if the errors were resolved.

Conflicting files — FILENAME exists in filesystem

If you cant can’t install or update a package because of an error like this:

Then the package manager, pacman, has detected an unexpected file that already exists on the disk.

Why is this happening?

By design pacman will not overwrite files that already exist. This is a design feature, not a flaw — package managers are designed to keep track of installed files.

This issue normally happens because you’ve manually added, copied, or created a file. It can also happen when you install software using a downloaded executable, run a make install, or use a third-party package system such as conda. It also occurs when you install an AUR package which installs files that conflict with a repo package.

When using a third-party installer you should always specify an alternative installation location, such as under your home directory, or under /opt or /usr/local/. Never install directly under / or /usr.

How can I fix this?

The first step is to identify which, if any, package owns the file. This can be easily done with:

If this identifies a conflicting package you can decide to remove it with pacman -R. If no package is identified you can delete the file (or move it to a backup location).

Where can I read more?

This post was inspired by (and adapted from):

The above post also has links to further reading.

«Configuration file. not recognized» Error

Manjaro’s package manager — pacman — uses a file called mirrorlist to tell it the internet addresses of the Manjaro servers in order to download updates and software applications from them. This error will therefore occur if one or more server addresses contained in the mirrorlist file have not been listed properly, resulting in pacman being unable to connect to them. Another tell-tale sign is that this problem will also be encountered immediately after:

• Installing Manjaro and editing the mirrorlist file during installation, or
• Editing the mirrorlist file at a later time.

See the Change to a Different Download Server guide for more detailed information on how to correctly select and enable another Manjaro server for downloading.

«GPGME error: No data» Error

The most likely cause of this issue is that an error or corruption has been detected by pacman in one or more software packages being downloaded. Package signatures and checksums are used to verify the validity of downloaded software, and should they fail, the installation attempt will be aborted to protect your system until the matter is resolved.

Option 1: Basic Resolution

To resolve this issue, first follow the basic procedure provided below. If this does not work, then there is a more comprehensive procedure available.

1. Download the package databases and update your system:

2. Clear out the software packages downloaded during the aborted installation by entering the command:

3. Re-attempt the aborted download.

Option 2: Comprehensive Resolution

If the basic proceedure still does not resolve the matter, further steps are available:

1. Resynchronise with the Manjaro servers to ensure that everything is up to date by entering the command:

2. Refresh and update the signature keys by entering the command:

3. Reload the signature keys by entering the command:

4. Clear out the software packages downloaded during the aborted installation by entering the command:

5. Re-attempt the aborted download.

If the error still persists, then it is recommended to Change to a Different Download Server.

Источник

The other day, I was about to update my Arch Linux system. When I try to update the system, I encountered with «unable to lock database» error in Arch Linux. I could not install or remove any packages.

Here is the command that I entered to update my Arch Linux system:

# pacman -Syu

And, It returned the following error:

:: Synchronizing package databases...
error: failed to update core (unable to lock database)
error: failed to update extra (unable to lock database)
error: failed to update community (unable to lock database)
error: failed to update multilib (unable to lock database)
error: failed to synchronize any databases
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
 if you're sure a package manager is not already
 running, you can remove /var/lib/pacman/db.lck

The beauty of Linux distros is sometimes they will the explicitly display the solution along with the error message. As you can see in the above output, it says: «.. you can remove /var/lib/pacman/db.lck».

So, I simply deleted the aforementioned file with command:

$ sudo rm /var/lib/pacman/db.lck

Voila! It worked. I can then able to update, install and remove without any problems.

$ pacman -Syu

Sample output:

:: Synchronizing package databases...
 core 122.8 KiB 162K/s 00:01 [######################] 100%
 extra 1771.8 KiB 249K/s 00:07 [######################] 100%
 community 3.3 MiB 256K/s 00:13 [######################] 100%
 multilib 163.5 KiB 265K/s 00:01 [######################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (8) ca-certificates-mozilla-3.22-1 coreutils-8.25-1 curl-7.47.1-1
 gcc-5.3.0-4 gcc-libs-5.3.0-4 libgcrypt-1.6.5-1 nano-2.5.2-1
 pacman-mirrorlist-20160208-2

Total Download Size: 42.79 MiB
Total Installed Size: 187.90 MiB
Net Upgrade Size: 0.91 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
 gcc-libs-5.3.0-4-x86_64 12.7 MiB 261K/s 00:50 [######################] 100%
 coreutils-8.25-1-x86_64 2.1 MiB 262K/s 00:08 [######################] 100%
 ca-certificates-moz... 363.0 KiB 241K/s 00:02 [######################] 100%
 curl-7.47.1-1-x86_64 798.3 KiB 263K/s 00:03 [######################] 100%
 gcc-5.3.0-4-x86_64 26.1 MiB 247K/s 01:48 [######################] 100%
 libgcrypt-1.6.5-1-x... 403.5 KiB 244K/s 00:02 [######################] 100%
 nano-2.5.2-1-x86_64 407.0 KiB 262K/s 00:02 [######################] 100%
 pacman-mirrorlist-2... 5.3 KiB 408K/s 00:00 [######################] 100%
(8/8) checking keys in keyring [######################] 100%
(8/8) checking package integrity [######################] 100%
(8/8) loading package files [######################] 100%
(8/8) checking for file conflicts [######################] 100%
(8/8) checking available disk space [######################] 100%
:: Processing package changes...
(1/8) upgrading gcc-libs [######################] 100%
(2/8) upgrading coreutils [######################] 100%
(3/8) upgrading ca-certificates-mozilla [######################] 100%
(4/8) upgrading curl [######################] 100%
(5/8) upgrading gcc [######################] 100%
(6/8) upgrading libgcrypt [######################] 100%
(7/8) upgrading nano [######################] 100%
(8/8) upgrading pacman-mirrorlist [######################] 100%
warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew

Hope this helps.

26 comments

This site uses Akismet to reduce spam. Learn how your comment data is processed.