Pakfire stalled

Just had a look into pakfire to check for updates and saw those line.s velow. Obviously pakfire tries to do sthg. since 1.30 am.

Can I restart pakfire?

I am guessing not. With pakfire I only see a start command and no stop or reload:

[root@ipfire ~]# /etc/rc.d/init.d/pakfire
Usage: /etc/rc.d/init.d/pakfire {start}

[root@ipfire ~]# cat /etc/rc.d/init.d/pakfire
#!/bin/sh
########################################################################
# Begin $rc_base/init.d/pakfire
#
# Description : Imports the keyring to make Pakfire operational
#
########################################################################

. /etc/sysconfig/rc
. ${rc_functions}

export GNUPGHOME="/opt/pakfire/etc/.gnupg"

case "${1}" in
	start)
		boot_mesg "Setting up Pakfire Package Manager..."
		gpg --import /opt/pakfire/pakfire-2018.key &>/dev/null
		evaluate_retval

		# Try to import the old key, too
		gpg --import /opt/pakfire/pakfire-2007.key &>/dev/null
		;;

	*)
		echo "Usage: ${0} {start}"
		exit 1
		;;
esac

# End $rc_base/init.d/pakfire
[root@ipfire ~]# 

So it might be better to just reboot the IPFire.

@hellfire

does pakfire status give you output?

Output is

core-list.db 100.00% |=============================>| 903.00 B
Core-Version: 2.25-x86_64
Core-Update-Level: 152
Last update: 9d 5h 47m 49s ago
Last core-list update: 21h 18m 41s ago
Last server-list update: 21h 18m 43s ago
Last packages-list update: 21h 18m 42s ago
Core-Update available: no
Package-Updates available: 0
Reboot required: no

I now had the chance to reboot ipfire. After refreshing Pakfire in WUI, Isee this log. At the time of writing 7:51,the screen in browser constantly refreshes but the log still shows the very same entries.

Dec 19 07:45:08 ipfire pakfire: DOWNLOAD STARTED: 2.25-x86_64/lists/server-list.db
Dec 19 07:45:08 ipfire pakfire: DOWNLOAD INFO: Host: pakfire.ipfire.org (HTTPS) - File: 2.25-x86_64/lists/server-list.db
Dec 19 07:45:09 ipfire pakfire: DOWNLOAD INFO: 2.25-x86_64/lists/server-list.db has size of 2459 bytes
Dec 19 07:45:09 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
Dec 19 07:45:09 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature…
Dec 19 07:45:09 ipfire pakfire: DOWNLOAD INFO: Signature of server-list.db is fine.
Dec 19 07:45:09 ipfire pakfire: DOWNLOAD FINISHED: 2.25-x86_64/lists/server-list.db
Dec 19 07:45:09 ipfire pakfire: DB INFO: packages_list.db is 83 seconds old. - DEBUG: force
Dec 19 07:45:09 ipfire pakfire: DOWNLOAD STARTED: lists/packages_list.db
Dec 19 07:45:09 ipfire pakfire: MIRROR INFO: 28 servers found in list
Dec 19 07:45:09 ipfire pakfire: DOWNLOAD INFO: Host: ftp.nluug.nl (HTTPS) - File: os/Linux/distr/ipfire/pakfire2/2.25-x86_64/lists/packages_list.db
Dec 19 07:45:10 ipfire pakfire: DOWNLOAD INFO: os/Linux/distr/ipfire/pakfire2/2.25-x86_64/lists/packages_list.db has size of 4931 bytes
Dec 19 07:45:11 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
Dec 19 07:45:11 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature…
Dec 19 07:45:11 ipfire pakfire: DOWNLOAD INFO: Signature of packages_list.db is fine.
Dec 19 07:45:11 ipfire pakfire: DOWNLOAD FINISHED: os/Linux/distr/ipfire/pakfire2/2.25-x86_64/lists/packages_list.db
Dec 19 07:45:11 ipfire pakfire: CORE INFO: core-list.db is 83 seconds old. - DEBUG: force
Dec 19 07:45:11 ipfire pakfire: DOWNLOAD STARTED: lists/core-list.db
Dec 19 07:45:11 ipfire pakfire: MIRROR INFO: 28 servers found in list
Dec 19 07:45:11 ipfire pakfire: DOWNLOAD INFO: Host: mirror.uta.edu.ec (HTTPS) - File: ipfire/pakfire2/2.25-x86_64/lists/core-list.db

So what are my options to get Pakfire working again? Btw, until the reboot I checked the log everyday and each time I did the log entries changed to a new date and time but the outcome was the same, an obviously frozen log or Pakfire.

Updated the WUI by pressing the blue refresh button reveiled some new lines though. Those lines are the sam I saw every time while checking the logs. Does IPfire have some issues while checking signatures of the downloaded packages? Can I verify the process myself manually in shell?

Dec 19 07:45:09 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature…
Dec 19 07:45:09 ipfire pakfire: DOWNLOAD INFO: Signature of server-list.db is fine.
Dec 19 07:45:09 ipfire pakfire: DOWNLOAD FINISHED: 2.25-x86_64/lists/server-list.db
Dec 19 07:45:09 ipfire pakfire: DB INFO: packages_list.db is 83 seconds old. - DEBUG: force
Dec 19 07:45:09 ipfire pakfire: DOWNLOAD STARTED: lists/packages_list.db
Dec 19 07:45:09 ipfire pakfire: MIRROR INFO: 28 servers found in list
Dec 19 07:45:09 ipfire pakfire: DOWNLOAD INFO: Host: ftp.nluug.nl (HTTPS) - File: os/Linux/distr/ipfire/pakfire2/2.25-x86_64/lists/packages_list.db
Dec 19 07:45:10 ipfire pakfire: DOWNLOAD INFO: os/Linux/distr/ipfire/pakfire2/2.25-x86_64/lists/packages_list.db has size of 4931 bytes

Just had a look into sysmlogs of pakfire and saw at totally different picture. So what’s the deal? For me it seems that the pakfire process never finishes properly, and stalled in a kind of loop.

08:08:03 pakfire: CORE INFO: core-list.db is 1455 seconds old. - DEBUG: noforce
08:08:03 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25-x86_64 started!
08:04:03 pakfire: CORE INFO: core-list.db is 1215 seconds old. - DEBUG: noforce
08:04:03 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25-x86_64 started!
08:00:05 pakfire: CORE INFO: core-list.db is 977 seconds old. - DEBUG: noforce
08:00:05 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25-x86_64 started!
07:56:03 pakfire: CORE INFO: core-list.db is 735 seconds old. - DEBUG: noforce
07:56:03 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25-x86_64 started!
07:52:05 pakfire: CORE INFO: core-list.db is 497 seconds old. - DEBUG: noforce
07:52:05 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25-x86_64 started!
07:48:05 pakfire: CORE INFO: core-list.db is 257 seconds old. - DEBUG: noforce
07:48:05 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25-x86_64 started!
07:45:11 pakfire: DOWNLOAD INFO: Host: mirror.uta.edu.ec (HTTPS) - File: ipfire/pakfire2/2.25-x86 _64/lists/core-list.db
07:45:11 pakfire: MIRROR INFO: 28 servers found in list
07:45:11 pakfire: DOWNLOAD STARTED: lists/core-list.db
07:45:11 pakfire: CORE INFO: core-list.db is 83 seconds old. - DEBUG: force
07:45:11 pakfire: DOWNLOAD FINISHED: os/Linux/distr/ipfire/pakfire2/2.25-x86_64/lists/packages_li st.db
07:45:11 pakfire: DOWNLOAD INFO: Signature of packages_list.db is fine.
07:45:11 pakfire: DOWNLOAD INFO: File received. Start checking signature…
07:45:11 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK

Below is the system log of pakfire from Dec 17th. It seems the complete update process is taking forever, at least over an hour, but finished at the end. The WUI page, however, definitely has a bug while showing the latest lines from the logs. At least on my side.

01:26:10 pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
01:26:10 pakfire: DOWNLOAD FINISHED: pub/ipfire/pakfire2/2.25-x86_64/lists/core-list.db
01:26:10 pakfire: DOWNLOAD INFO: Signature of core-list.db is fine.
01:26:10 pakfire: DOWNLOAD INFO: File received. Start checking signature…
01:26:10 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
01:26:10 pakfire: DOWNLOAD INFO: pub/ipfire/pakfire2/2.25-x86_64/lists/core-list.db has size of 9 03 bytes
01:26:09 pakfire: DOWNLOAD INFO: Host: mirror.datacenter.by (HTTPS) - File: pub/ipfire/pakfire2/2 .25-x86_64/lists/core-list.db
01:26:09 pakfire: MIRROR INFO: 27 servers found in list
01:26:09 pakfire: DOWNLOAD STARTED: lists/core-list.db
01:26:09 pakfire: CORE INFO: core-list.db is 3789 seconds old. - DEBUG: force
01:26:09 pakfire: DOWNLOAD FINISHED: ipfire/pakfire2/2.25-x86_64/lists/packages_list.db
01:26:09 pakfire: DOWNLOAD INFO: Signature of packages_list.db is fine.
01:26:09 pakfire: DOWNLOAD INFO: File received. Start checking signature…
01:26:09 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
01:26:09 pakfire: DOWNLOAD INFO: ipfire/pakfire2/2.25-x86_64/lists/packages_list.db has size of 4 931 bytes
01:26:08 pakfire: DOWNLOAD INFO: Host: ftp.fau.de (HTTPS) - File: ipfire/pakfire2/2.25-x86_64/lis ts/packages_list.db
01:26:08 pakfire: MIRROR INFO: 27 servers found in list
01:26:08 pakfire: DOWNLOAD STARTED: lists/packages_list.db
01:26:08 pakfire: DB INFO: packages_list.db is 3788 seconds old. - DEBUG: force
01:26:07 pakfire: DOWNLOAD FINISHED: 2.25-x86_64/lists/server-list.db
01:26:07 pakfire: DOWNLOAD INFO: Signature of server-list.db is fine.
01:26:07 pakfire: DOWNLOAD INFO: File received. Start checking signature…
01:26:07 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
01:26:07 pakfire: DOWNLOAD INFO: 2.25-x86_64/lists/server-list.db has size of 2403 bytes
01:26:07 pakfire: DOWNLOAD INFO: Host: pakfire.ipfire.org (HTTPS) - File: 2.25-x86_64/lists/serve r-list.db
01:26:07 pakfire: DOWNLOAD STARTED: 2.25-x86_64/lists/server-list.db
01:26:07 pakfire: MIRROR INFO: server-list.db is 3789 seconds old. - DEBUG: force
01:25:08 pakfire: CRON INFO: Waiting for 59 seconds.
01:25:08 pakfire: CRON INFO: Running an update
01:25:08 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25-x86_64 started!
00:23:00 pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
00:23:00 pakfire: DOWNLOAD FINISHED: pakfire2/2.25-x86_64/lists/core-list.db
00:23:00 pakfire: DOWNLOAD INFO: Signature of core-list.db is fine.
00:23:00 pakfire: DOWNLOAD INFO: File received. Start checking signature…
00:23:00 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
00:23:00 pakfire: DOWNLOAD INFO: pakfire2/2.25-x86_64/lists/core-list.db has size of 903 bytes
00:22:59 pakfire: DOWNLOAD INFO: Host: mirror7.ipfire.org (HTTPS) - File: pakfire2/2.25-x86_64/li sts/core-list.db
00:22:59 pakfire: MIRROR INFO: 27 servers found in list
00:22:59 pakfire: DOWNLOAD STARTED: lists/core-list.db
00:22:59 pakfire: CORE INFO: core-list.db is 73530 seconds old. - DEBUG: force
00:22:59 pakfire: DOWNLOAD FINISHED: os/Linux/distr/ipfire/pakfire2/2.25-x86_64/lists/packages_li st.db
00:22:59 pakfire: DOWNLOAD INFO: Signature of packages_list.db is fine.
00:22:59 pakfire: DOWNLOAD INFO: File received. Start checking signature…
00:22:59 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
00:22:59 pakfire: DOWNLOAD INFO: os/Linux/distr/ipfire/pakfire2/2.25-x86_64/lists/packages_list.d b has size of 4931 bytes
00:22:58 pakfire: DOWNLOAD INFO: Host: ftp.nluug.nl (HTTPS) - File: os/Linux/distr/ipfire/pakfire 2/2.25-x86_64/lists/packages_list.db
00:22:58 pakfire: MIRROR INFO: 27 servers found in list
00:22:58 pakfire: DOWNLOAD STARTED: lists/packages_list.db
00:22:58 pakfire: DB INFO: packages_list.db is 73531 seconds old. - DEBUG: force
00:22:58 pakfire: DOWNLOAD FINISHED: 2.25-x86_64/lists/server-list.db
00:22:58 pakfire: DOWNLOAD INFO: Signature of server-list.db is fine.
00:22:58 pakfire: DOWNLOAD INFO: File received. Start checking signature…
00:22:58 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
00:22:58 pakfire: DOWNLOAD INFO: 2.25-x86_64/lists/server-list.db has size of 2403 bytes
00:22:57 pakfire: DOWNLOAD INFO: Host: pakfire.ipfire.org (HTTPS) - File: 2.25-x86_64/lists/serve r-list.db
00:22:57 pakfire: DOWNLOAD STARTED: 2.25-x86_64/lists/server-list.db
00:22:57 pakfire: MIRROR INFO: server-list.db is 73532 seconds old. - DEBUG: force
00:22:57 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25-x86_64 started!

So a ps -eF reveils:

root 17880 1 0 2819 1564 0 07:45 ? 00:00:00 /usr/local/bin/pakfire update --force --no-colors
root 17882 17880 0 8054 27404 1 07:45 ? 00:00:02 /usr/bin/perl /opt/pakfire/pakfire update --force --no-colors

As you can see it’s running since 7:45 o’clock and does not finish. By any chance, is this a access issue with some files or similar.

Unfortunately a kill 17880 or kill 17882 does not stop pakfire at all.

Files in /opt/pakfire/db/lists:

-rw-r–r-- 1 root root 903 Dec 19 10:52 core-list.db
-rw-r–r-- 1 root root 4931 Dec 19 07:45 packages_list.db
-rw-r–r-- 1 root root 2459 Dec 19 07:45 server-list.db
Anything wrong with these?

Two old files in /opt/pakfire:

-rw-r–r-- 1 root root 1814 Apr 27 2018 pakfire-2007.key
-rw-r–r-- 1 root root 1648 Apr 27 2018 pakfire-2018.key

Some questions:

  1. How to stop pakfire now?
  2. Should I, or can I clear the cache in /opt/pakfire/cache? There are lots of (old) packages, may be they are the cause of this issue?
  3. Should I, or can I clear the logs in /opt/pakfire/logs?
  4. Can I clear /opt/pakfire/db/lists and restart pakfire, when I get pakfire stopped?
  5. Can I delete those key-files in /opt/pakfire?

Update: just used htop and managed to kill pakfire using F9 and selected option 9 (SIGKILL). After this the WebIF of Pakfire is normal again.

When pressing the refresh list button again, all is well now - don’t know if ths is by luck or a final fix. I will check tomorrow.

Until then, is clearing up the files, as mentioned above, points 2), 3), 4= and 5) a good option to do some hous keeping?

Well, apart from being presented in reverse order, everything in the log seems to be ok. It shows two separate update events, one starting at 00:22:57 and the other at 01:25:08. The earlier update took around 3 seconds to complete and the later update took around 3 seconds but with a wait of 59 seconds:

01:26:10 pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
...
01:25:08 pakfire: CRON INFO: Waiting for 59 seconds.
....
01:25:08 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25-x86_64 started!
...
00:23:00 pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
...
00:22:57 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25-x86_64 started!

Yes, but so far it never finished and did not return to the starting page. The website just stuck with showing the logs.

After killing the process and pressing the refresh button several times all is well for the moment. However, as mentioned above, I did reboot which did not affect the WebIF and the log still did not update nor did pakfire finish and return to its normal state. .

I will monitor the process the next days, though…

Just so the Devs know: I ran into something similar (but definitely not the same). I did an update from core 144 to testing core 153 on an older computer I use for testing.

I didn’t pay any attention to the duration of the update until today (after reading Michael posts).

The single click of the pakfire upgrade button took over 2 hours to complete.

The IPFire box was not rebooted during the wait.

Dec 15 17:39:44 ipfire pakfire: CORE UPGR: Upgrading from release 144 to 152
. . .
Dec 15 19:13:12 ipfire pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
. . .
Dec 15 19:54:20 ipfire pakfire: CORE UPGR: Upgrading from release 151 to 153
. . .
Dec 15 19:54:55 ipfire pakfire: PAKFIRE INFO: Pakfire has finished. Closing.

The only thing similar to Michael’s issue is the wait on the pakfire update page for a l-o-n-g time.

0

IPFire version	IPFire 2.25 (x86_64) - core153 Development Build: master/eaa90321
Pakfire version	2.25.1-x86_64
Kernel version	Linux ipfire153t.localdomain 4.14.211-ipfire #1 SMP Tue Dec 8 23:54:50 GMT 2020 x86_64 Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz GenuineIntel GNU/Linux

PS - I can post the message log if needed.

Little update:

Right now, when pressing the “Refresh list” button in WebIF, it takes some seconds and the web page is back again after showing some logs.

So, it works as expected but it did not before. At least the log display in WebIF was not up to date and it seems the whole process took about an hour the days before.