pacman not exiting properly from my wrapper

jrussell · 2013-06-01 18:34:25

Im playing around with a little bash wrapper for pacman and everynow and again I come across:

:: 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

Im calling pacman from my script like this:

pacman $*
wait

I think I know what is going on, but Im very new to bash and shell scripty things.
Is it because my script is listening to ctl+C as opposed to pacman getting ctl+C?
This doesnt make sense to me because when I ctl+C I see:

Interrupt signal received

from pacan

How can I prevent this?

Any help would be appreciated.

Last edited by jrussell (2013-06-01 18:36:14)

msthev · 2013-06-01 18:46:52

$* is probably not what you want. Use "$@" (with quotes). Google why.
The execution of the script is synchronous, meaning `wait` will be invoked only after pacman is finished.
What are you trying to do? What's the point of this wrapper?
The code would be helpful, there is no way to tell what's going on without it.

jrussell · 2013-06-01 18:50:13

Thanks,
Its doing nothing at the moment

#!/bin/bash

operation=0



lastCommand=$(grep '\[PACMAN\] Running' /var/log/pacman.log | tail -n 1)
echo "Last command:"$lastCommand

logTime()  # datetime : seconds
{
    local stamp=$(echo "$1 $2" | grep -o -E "[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}")
    date -d "$stamp" +%s
}
logTime $lastCommand

checkPac () {
	find / -path /home/ -prune -o -regextype posix-extended -regex ".+\.pac(new|save|orig)" 2> /dev/null
}


if [[ "$1" = \-S* ]]; then
	if [[ "$1" = *'y'* ]]; then
		operation=$((msg+1))
	fi
	if [[ "$1" = *'u'* ]]; then
		operation=$((msg+2))
	fi
	if [[ "$1" = *'w'* ]]; then
		operation=$((msg+4))
	fi
	if [[ -n "$2" && "$2" != '-'* ]]; then
		operation=$((msg+8))
	fi
fi



#GOOD - no problem
#CHECK - check db vs system
#RERUN - you should run a specific pacman command next
#BAD - bad

case $operation in
	1) 
	#	echo $'RERUN - syncing\n rerun next with \'-Su'\'
	;;
	2) 
	#	echo $'CHECK - upgrading'
	;;
	3) 
	#	echo $'GOOD - syncing upgrading'
	;;
	4) 
	#	echo $'download_only' #useless?
	;;
	5) 
	#	echo $'syncing download_only' #useless?
	;;
	6) 
	#	echo $'RERUN - upgrading download_only\n rerun next with \'-Su'\'
	;;
	7) 	
	#	echo $'RERUN - syncing upgrading download_only\n rerun next with \'-Su'\'
	;;
	8) 
	#	echo $'CHECK - installing'
	;;
	9) 
	#	echo $'BAD - syncing installing'
	;;
	10) 
	#	echo $'CHECK - upgrading installing'
	;;
	11) 
	#	echo $'GOOD - syncing upgrading installing'
	;;
	12) 
	#	echo $'RERUN - download_only installing\n rerun next with \'-S package'\'
	;;
	13) 
	#	echo $'RERUN - syncing download_only installing\n rerun next with \'-Su package'\'
	;;
	14) 
	#	echo $'RERUN - upgrading download_only installing\n rerun next with \'-Su package'\'
	;;
	15) 
	#	echo $'RERUN - syncing upgrading download_only installing\n rerun next with \'-Su package'\'
	;;
esac

pacman $*
wait
echo "looking for pacfiles..."
checkPac

I want to make something like pacmatic just for fun

https://github.com/keenerd/pacmatic/blo … r/pacmatic

*Edit

just happened again

jason@jason-pc ~ % sudo autopac -Syu
Last command:[2013-06-01 20:30] [PACMAN] Running 'pacman -Syu'
1370111400
:: 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
looking for pacfiles...
jason@jason-pc ~ % sudo rm /var/lib/pacman/db.lck
jason@jason-pc ~ % sudo autopac -Syu
Last command:[2013-06-01 20:31] [PACMAN] Running 'pacman -Syu'
1370111460
:: Synchronizing package databases...
^C
Interrupt signal received

looking for pacfiles...
jason@jason-pc ~ % sudo autopac -Syu
[sudo] password for jason: 
Last command:[2013-06-01 20:35] [PACMAN] Running 'pacman -Syu'
1370111700
:: Synchronizing package databases...
 core is up to date
^C
Interrupt signal received

looking for pacfiles...
jason@jason-pc ~ % sudo autopac -Syu
Last command:[2013-06-01 20:51] [PACMAN] Running 'pacman -Syu'
1370112660
:: 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
looking for pacfiles...
^C%                                                                                                                                                                                                                                           jason@jason-pc ~ %

There doesn't seem to be any consistency

Last edited by jrussell (2013-06-01 19:10:00)

msthev · 2013-06-01 20:24:40

Does it happen at all with plain pacman?

Also, when pacman says the db is locked, is there maybe some wild pacman process still running?

Last edited by msthev (2013-06-01 20:27:46)

jrussell · 2013-06-01 20:39:06

Not that I can recall, but I dont ctl+c all the time with pacman, Im ctl+c'ing alot when I change things in my script. (while pacman is busy running)

And no, Ive had htop running to check that.

I can't seem to reproduce it, it seems random.

Last edited by jrussell (2013-06-01 20:40:27)

cfr · 2013-06-01 21:42:42

If pacman is interrupted so that it does not exit cleanly, it may not clean up after itself and may leave its lock file behind. Next time it runs, it will check for the lock file and refuse to run because it will look as if another instance may already be running. Basically, you are forcing it to exit uncleanly, I think, and this is one of the symptoms. Doing this is probably not a great idea...

jrussell · 2013-06-01 22:16:19

cfr wrote:

If pacman is interrupted so that it does not exit cleanly, it may not clean up after itself and may leave its lock file behind. Next time it runs, it will check for the lock file and refuse to run because it will look as if another instance may already be running. Basically, you are forcing it to exit uncleanly, I think, and this is one of the symptoms. Doing this is probably not a great idea...

But what's the difference between me ctl+c'ing from my script vs from pacman? I don't think pacman is ment to be able to exit in the middle of something.

I can spam ctl+c during a straight pacman command and from my script, and I won't get the error, I think it might be a bug. It just seems so random, and it does not happen very often.

I have posted the terminal of when it occurred last on a previous post
https://bbs.archlinux.org/viewtopic.php … 4#p1281034

It has my little script too

Last edited by jrussell (2013-06-01 22:24:55)

ewaller · 2013-06-01 22:19:41

I am not an expert on the internals of pacman, but the other day, the devs did mention that pacman disables the ability to C-c at times when things need to not stop lest "Bad things" happen.

jrussell · 2013-06-01 22:27:37

ewaller wrote:

I am not an expert on the internals of pacman, but the other day, the devs did mention that pacman disables the ability to C-c at times when things need to not stop lest "Bad things" happen.

My other post https://bbs.archlinux.org/viewtopic.php … 6#p1271736

ewaller · 2013-06-01 23:22:34

See, I knew I had seen it somewhere

Xyne · 2013-06-02 00:17:17

jrussell wrote:

ewaller wrote:
I am not an expert on the internals of pacman, but the other day, the devs did mention that pacman disables the ability to C-c at times when things need to not stop lest "Bad things" happen.
My other post https://bbs.archlinux.org/viewtopic.php … 6#p1271736

No hand-holding my ****. Arch users should be able to tell from system I/O and active memory exactly what Pacman is doing and know the internals of their system well enough to be able to precisely time a keyboard interrupt. I can't believe the Pacman devs have turned into such officious little system nannies.

/sarcasm

cfr · 2013-06-02 00:27:53

But is leaving a stray lock file behind "a bad thing happening"? It is hardly disastrous and pacman then helpfully explains what to do the next time you run it.

EDIT: I guess it depends on what the devs included when they trade marked their Bad Idea™ concept...

EDIT 2: How do you type ™?

Last edited by cfr (2013-06-02 00:42:57)

msthev · 2013-06-02 01:20:54

Depends on your layout. For me it's Alt+Shift+T. Check /usr/share/X11/xkb/symbols/.

@topic
I just did some "testing" (pacman -Syu → Ctrl+C → repeat), and after 12 times pacman *did* leave the lock uncleaned.

jrussell · 2013-06-02 08:15:22

cfr wrote:

But is leaving a stray lock file behind "a bad thing happening"? It is hardly disastrous and pacman then helpfully explains what to do the next time you run it.
EDIT: I guess it depends on what the devs included when they trade marked their Bad Idea™ concept...
EDIT 2: How do you type ™?

I would think it is a bad thing? It's just not exiting cleanly like it should perhaps do.

I'll file a bug report?

cfr · 2013-06-02 16:14:20

I do not want to guess the devs thinking. However, there are disadvantages to ignoring ctrl-C as well as advantages. One possible policy would be to ignore control-C when something really nasty may result from honouring it e.g. system won't boot, pacman database fails to match installed packages, filesystem corruption, leaving a system with an old package uninstalled but without the update installed etc. but to honour control-C when something merely inconvenient or untidy will result e.g. leaving a stray lock file, updating the database without updating installed packages etc. This means that users who suddenly realised they've asked pacman to do something they really don't want (and have said "y" when asked to confirm) can potentially stop that happening if doing so will only create untidiness/inconvenience rather than risking madness and mayhem.

I'm just saying there's obviously a balance to be struck. What would your preferred policy be? That pacman *never* honour control-C? (At least when run with options which are not merely information-providing.)

Last edited by cfr (2013-06-02 16:15:30)

jrussell · 2013-06-02 18:01:57

caught it again

jason@jason-laptop ~ % sudo pacman -Syu
[sudo] password for jason: 
:: Synchronizing package databases...
^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
^C^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C
Interrupt signal received

jason@jason-laptop ~ % 
jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
^C extra                      0.0   B  0.00B/s 00:00 [----------------------]   0%
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
^C^C
Interrupt signal received

jason@jason-laptop ~ % 
jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C^C^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C^C^C
Interrupt signal received

jason@jason-laptop ~ % 
jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
^C^C^C                      0.0   B  0.00B/s 00:00 [----------------------]   0%
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C
Interrupt signal received

jason@jason-laptop ~ % 
jason@jason-laptop ~ % 
jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
^C^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C^C
Interrupt signal received

jason@jason-laptop ~ % 
jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: Synchronizing package databases...
^C
Interrupt signal received

jason@jason-laptop ~ % sudo pacman -Syu
:: 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 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
jason@jason-laptop ~ % 
jason@jason-laptop ~ %

Ill file a bug report and see what comes of it

*Edit
bug reported:
https://bugs.archlinux.org/task/35603

Last edited by jrussell (2013-06-02 18:09:52)

Allan · 2013-06-03 00:51:18

To clarify, pacman only ignores ctrl+c during the installation/removal/update of a package. It waits until that package is finished and then aborts. (well, at least that is what I think is done...)

Anyway - if people run this using --debug and try and see if that provides information on when it leaves the lock file, I can look into it.

jrussell · 2013-06-03 07:21:04

Allan wrote:

To clarify, pacman only ignores ctrl+c during the installation/removal/update of a package. It waits until that package is finished and then aborts. (well, at least that is what I think is done...)
Anyway - if people run this using --debug and try and see if that provides information on when it leaves the lock file, I can look into it.

Thanks, I'll fiddle and report back.

jrussell · 2013-06-03 08:33:01

got it

jason@jason-laptop ~ % sudo pacman -Syu --debug         
debug: pacman v4.1.1 - libalpm v8.0.1
debug: parseconfig: options pass
debug: config: attempting to read file /etc/pacman.conf
debug: config: finish section '(null)'
debug: config: new section 'options'
debug: config: HoldPkg: pacman
debug: config: HoldPkg: glibc
debug: config: arch: x86_64
debug: config: SigLevel: Required
debug: config: SigLevel: DatabaseOptional
debug: config: LocalFileSigLevel: Optional
debug: config: finish section 'options'
debug: config: new section 'core'
debug: config file /etc/pacman.conf, line 75: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'core'
debug: config: new section 'extra'
debug: config file /etc/pacman.conf, line 78: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'extra'
debug: config: new section 'community'
debug: config file /etc/pacman.conf, line 84: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'community'
debug: config: finished parsing /etc/pacman.conf
debug: setup_libalpm called
debug: option 'logfile' = /var/log/pacman.log
debug: option 'gpgdir' = /etc/pacman.d/gnupg/
debug: option 'cachedir' = /var/cache/pacman/pkg/
debug: parseconfig: repo pass
debug: config: attempting to read file /etc/pacman.conf
debug: config: finish section '(null)'
debug: config: new section 'options'
debug: config: finish section 'options'
debug: config: new section 'core'
debug: config file /etc/pacman.conf, line 75: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'core'
debug: registering sync database 'core'
debug: database path for tree core set to /var/lib/pacman/sync/core.db
debug: "/var/lib/pacman/sync/core.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/core.db.sig could not be opened
debug: missing optional signature
debug: adding new server URL to database 'core': http://mirror.de.leaseweb.net/archlinux/core/os/x86_64
debug: config: new section 'extra'
debug: config file /etc/pacman.conf, line 78: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'extra'
debug: registering sync database 'extra'
debug: database path for tree extra set to /var/lib/pacman/sync/extra.db
debug: "/var/lib/pacman/sync/extra.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/extra.db.sig could not be opened
debug: missing optional signature
debug: adding new server URL to database 'extra': http://mirror.de.leaseweb.net/archlinux/extra/os/x86_64
debug: config: new section 'community'
debug: config file /etc/pacman.conf, line 84: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'community'
debug: registering sync database 'community'
debug: database path for tree community set to /var/lib/pacman/sync/community.db
debug: "/var/lib/pacman/sync/community.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/community.db.sig could not be opened
debug: missing optional signature
debug: adding new server URL to database 'community': http://mirror.de.leaseweb.net/archlinux/community/os/x86_64
debug: config: finished parsing /etc/pacman.conf
:: Synchronizing package databases...
debug: url: http://mirror.de.leaseweb.net/archlinux/core/os/x86_64/core.db
debug: maxsize: 26214400
debug: using time condition: 1370227821
debug: opened tempfile for download: /var/lib/pacman/sync/core.db.part (wb)
debug: curl returned error 0 from transfer
debug: response code: 304
debug: file met time condition
 core is up to date
debug: url: http://mirror.de.leaseweb.net/archlinux/extra/os/x86_64/extra.db
debug: maxsize: 26214400
debug: using time condition: 1370123804
debug: opened tempfile for download: /var/lib/pacman/sync/extra.db.part (wb)
downloading extra.db...
^Cdebug: curl returned error 42 from transfer

Interrupt signal received
debug: returning error 24 from alpm_trans_interrupt : transaction not initialized
debug: returning error 24 from alpm_trans_release : transaction not initialized

debug: unregistering database 'local'
debug: unregistering database 'core'
debug: unregistering database 'extra'
debug: unregistering database 'community'
jason@jason-laptop ~ % 
jason@jason-laptop ~ % sudo pacman -Syu --debug
debug: pacman v4.1.1 - libalpm v8.0.1
debug: parseconfig: options pass
debug: config: attempting to read file /etc/pacman.conf
debug: config: finish section '(null)'
debug: config: new section 'options'
debug: config: HoldPkg: pacman
debug: config: HoldPkg: glibc
debug: config: arch: x86_64
debug: config: SigLevel: Required
debug: config: SigLevel: DatabaseOptional
debug: config: LocalFileSigLevel: Optional
debug: config: finish section 'options'
debug: config: new section 'core'
debug: config file /etc/pacman.conf, line 75: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'core'
debug: config: new section 'extra'
debug: config file /etc/pacman.conf, line 78: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'extra'
debug: config: new section 'community'
debug: config file /etc/pacman.conf, line 84: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'community'
debug: config: finished parsing /etc/pacman.conf
debug: setup_libalpm called
debug: option 'logfile' = /var/log/pacman.log
debug: option 'gpgdir' = /etc/pacman.d/gnupg/
debug: option 'cachedir' = /var/cache/pacman/pkg/
debug: parseconfig: repo pass
debug: config: attempting to read file /etc/pacman.conf
debug: config: finish section '(null)'
debug: config: new section 'options'
debug: config: finish section 'options'
debug: config: new section 'core'
debug: config file /etc/pacman.conf, line 75: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'core'
debug: registering sync database 'core'
debug: database path for tree core set to /var/lib/pacman/sync/core.db
debug: "/var/lib/pacman/sync/core.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/core.db.sig could not be opened
debug: missing optional signature
debug: adding new server URL to database 'core': http://mirror.de.leaseweb.net/archlinux/core/os/x86_64
debug: config: new section 'extra'
debug: config file /etc/pacman.conf, line 78: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'extra'
debug: registering sync database 'extra'
debug: database path for tree extra set to /var/lib/pacman/sync/extra.db
debug: "/var/lib/pacman/sync/extra.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/extra.db.sig could not be opened
debug: missing optional signature
debug: adding new server URL to database 'extra': http://mirror.de.leaseweb.net/archlinux/extra/os/x86_64
debug: config: new section 'community'
debug: config file /etc/pacman.conf, line 84: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'community'
debug: registering sync database 'community'
debug: database path for tree community set to /var/lib/pacman/sync/community.db
debug: "/var/lib/pacman/sync/community.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/community.db.sig could not be opened
debug: missing optional signature
debug: adding new server URL to database 'community': http://mirror.de.leaseweb.net/archlinux/community/os/x86_64
debug: config: finished parsing /etc/pacman.conf
:: Synchronizing package databases...
debug: url: http://mirror.de.leaseweb.net/archlinux/core/os/x86_64/core.db
debug: maxsize: 26214400
debug: using time condition: 1370227821
debug: opened tempfile for download: /var/lib/pacman/sync/core.db.part (wb)
debug: curl returned error 0 from transfer
debug: response code: 304
debug: file met time condition
 core is up to date
^C
Interrupt signal received
debug: returning error 24 from alpm_trans_interrupt : transaction not initialized
debug: returning error 24 from alpm_trans_release : transaction not initialized

debug: unregistering database 'local'
debug: unregistering database 'core'
debug: unregistering database 'extra'
debug: unregistering database 'community'
jason@jason-laptop ~ % sudo pacman -Syu --debug
debug: pacman v4.1.1 - libalpm v8.0.1
debug: parseconfig: options pass
debug: config: attempting to read file /etc/pacman.conf
debug: config: finish section '(null)'
debug: config: new section 'options'
debug: config: HoldPkg: pacman
debug: config: HoldPkg: glibc
debug: config: arch: x86_64
debug: config: SigLevel: Required
debug: config: SigLevel: DatabaseOptional
debug: config: LocalFileSigLevel: Optional
debug: config: finish section 'options'
debug: config: new section 'core'
debug: config file /etc/pacman.conf, line 75: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'core'
debug: config: new section 'extra'
debug: config file /etc/pacman.conf, line 78: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'extra'
debug: config: new section 'community'
debug: config file /etc/pacman.conf, line 84: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'community'
debug: config: finished parsing /etc/pacman.conf
debug: setup_libalpm called
debug: option 'logfile' = /var/log/pacman.log
debug: option 'gpgdir' = /etc/pacman.d/gnupg/
debug: option 'cachedir' = /var/cache/pacman/pkg/
debug: parseconfig: repo pass
debug: config: attempting to read file /etc/pacman.conf
debug: config: finish section '(null)'
debug: config: new section 'options'
debug: config: finish section 'options'
debug: config: new section 'core'
debug: config file /etc/pacman.conf, line 75: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'core'
debug: registering sync database 'core'
debug: database path for tree core set to /var/lib/pacman/sync/core.db
debug: "/var/lib/pacman/sync/core.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/core.db.sig could not be opened
debug: missing optional signature
debug: adding new server URL to database 'core': http://mirror.de.leaseweb.net/archlinux/core/os/x86_64
debug: config: new section 'extra'
debug: config file /etc/pacman.conf, line 78: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'extra'
debug: registering sync database 'extra'
debug: database path for tree extra set to /var/lib/pacman/sync/extra.db
debug: "/var/lib/pacman/sync/extra.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/extra.db.sig could not be opened
debug: missing optional signature
debug: adding new server URL to database 'extra': http://mirror.de.leaseweb.net/archlinux/extra/os/x86_64
debug: config: new section 'community'
debug: config file /etc/pacman.conf, line 84: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'community'
debug: registering sync database 'community'
debug: database path for tree community set to /var/lib/pacman/sync/community.db
debug: "/var/lib/pacman/sync/community.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/community.db.sig could not be opened
debug: missing optional signature
debug: adding new server URL to database 'community': http://mirror.de.leaseweb.net/archlinux/community/os/x86_64
debug: config: finished parsing /etc/pacman.conf
:: Synchronizing package databases...
debug: returning error 10 from alpm_db_update : unable to lock database
error: failed to update core (unable to lock database)
debug: returning error 10 from alpm_db_update : unable to lock database
error: failed to update extra (unable to lock database)
debug: returning error 10 from alpm_db_update : unable to lock database
error: failed to update community (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
debug: unregistering database 'local'
debug: unregistering database 'core'
debug: unregistering database 'extra'
debug: unregistering database 'community'
jason@jason-laptop ~ % 
jason@jason-laptop ~ %

PatronMaster · 2014-04-21 20:17:43

Hi,

I have this problem.
I solved like that

sudo rm /var/lib/pacman/db.lck
pacman -Syu

jasonwryan · 2014-04-21 21:41:51

Please don't necrobump: https://wiki.archlinux.org/index.php/Fo … Bumping.27

Closing

Arch Linux

#1 2013-06-01 18:34:25

pacman not exiting properly from my wrapper

#2 2013-06-01 18:46:52

Re: pacman not exiting properly from my wrapper

#3 2013-06-01 18:50:13

Re: pacman not exiting properly from my wrapper

#4 2013-06-01 20:24:40

Re: pacman not exiting properly from my wrapper

#5 2013-06-01 20:39:06

Re: pacman not exiting properly from my wrapper

#6 2013-06-01 21:42:42

Re: pacman not exiting properly from my wrapper

#7 2013-06-01 22:16:19

Re: pacman not exiting properly from my wrapper

#8 2013-06-01 22:19:41

Re: pacman not exiting properly from my wrapper

#9 2013-06-01 22:27:37

Re: pacman not exiting properly from my wrapper

#10 2013-06-01 23:22:34

Re: pacman not exiting properly from my wrapper

#11 2013-06-02 00:17:17

Re: pacman not exiting properly from my wrapper

#12 2013-06-02 00:27:53

Re: pacman not exiting properly from my wrapper

#13 2013-06-02 01:20:54

Re: pacman not exiting properly from my wrapper

#14 2013-06-02 08:15:22

Re: pacman not exiting properly from my wrapper

#15 2013-06-02 16:14:20

Re: pacman not exiting properly from my wrapper

#16 2013-06-02 18:01:57

Re: pacman not exiting properly from my wrapper

#17 2013-06-03 00:51:18

Re: pacman not exiting properly from my wrapper

#18 2013-06-03 07:21:04

Re: pacman not exiting properly from my wrapper

#19 2013-06-03 08:33:01

Re: pacman not exiting properly from my wrapper

#20 2014-04-21 20:17:43

Re: pacman not exiting properly from my wrapper

#21 2014-04-21 21:41:51

Re: pacman not exiting properly from my wrapper

Board footer