You are not logged in.
When I initiate pacman -Syu, during the "Synchronizing package database..." dialogue it lags for way too long. This is not related to the mirrorlist as I've updated the mirrorlist and tried several mirrors and the network is fast but this happens to be related to the local database. Just a few days ago it was really fast but I am not sure what could be causing this lag. I tried "pacman-optimize && sync" as well as "pacman -Scc" and I get the same results. Has anyone else experienced this problem?
Last edited by rg_arc (2014-11-07 22:17:30)
Offline
Run pacman in verbose or debug mode to see if there are any errors...
Offline
Offline
it lags for way too long.
How long is way too long?
Offline
At the "Synchronizing package database..." stage, it accesses the remote server and three files on your harddrive... have you tried changing mirrors?
Offline
Isn't there a tool for cleaning up the database? Ah-yes pacman-optimize.
Last edited by nomorewindows (2014-11-07 16:26:40)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
At the "Synchronizing package database..." stage, it accesses the remote server and three files on your harddrive... have you tried changing mirrors?
"...This is not related to the mirrorlist as I've updated the mirrorlist and tried several mirrors and the network is fast but this happens to be related to the local database...."
Isn't there a tool for cleaning up the database? Ah-yes pacman-optimize.
"..I tried "pacman-optimize && sync" as well as "pacman -Scc" and I get the same results..."
Did you actually read my post?
rg_arc wrote:it lags for way too long.
How long is way too long?
Typically that dialogue lasts for like half a second before going straight to the mirror. This lags for about 15-20 seconds or so. I'm using a SSD too, which is why I think its so strange.
Offline
Allan wrote:At the "Synchronizing package database..." stage, it accesses the remote server and three files on your harddrive... have you tried changing mirrors?
"...This is not related to the mirrorlist as I've updated the mirrorlist and tried several mirrors and the network is fast but this happens to be related to the local database...."
Did you actually read my post?
In Allan's defense, he is the lead developer of pacman, so if anyone knows what might be going on it would be him...
Last edited by drcouzelis (2014-11-07 19:59:35)
Offline
Where does the lag occur? In the original post you say it's after
When I initiate pacman -Syu, during the "Synchronizing package database..." dialogue it lags for way too long.
but then later you say
Typically that dialogue lasts for like half a second before going straight to the mirror. This lags for about 15-20 seconds or so.
Offline
Where does the lag occur? In the original post you say it's after
When I initiate pacman -Syu, during the "Synchronizing package database..." dialogue it lags for way too long.
but then later you say
Typically that dialogue lasts for like half a second before going straight to the mirror. This lags for about 15-20 seconds or so.
I'm referring to the same "Synchronizing package database..." dialogue. I'm watching the internet monitor to see if during that time its pinging the mirrors, but there is no internet activity for a good while. Which suggests it could be related to a lag in accessing the local database on my desktop.
rgedit: I should be more specific. Typically the Synchronizing package database dialogue would take maybe .5 of a second but since about three days ago it is taking much longer. Even after changing the mirrorlist (even switching the top mirror in the mirrorlist file) and issuing the "pacman-optimize && sync" command I still get the same results.
Last edited by rg_arc (2014-11-07 21:42:39)
Offline
pacman does not access the local database until after it has finished checking the sync databases. If "Synchronizing package database..." is the last message you see before the lag you have a network/mirror problem not a local database problem.
Offline
Ok I solved it by switching to NetworkManager. I was using the systemd-networkd.service.
Offline
so this was a DNS issue?
Offline
so this was a DNS issue?
I can't be sure exactly what it was. I am assuming networkd was having trouble resolving ipv4/ipv6 maybe? I was using the same DNS NetworkManager is using now Google's DNS servers.
Here is my systemd-networkd service:
[Match]
Name=enp3s0
[Network]
DNS=8.8.8.8
DNS=8.8.4.4
#DNS=109.69.8.34
#DNS=185.16.40.143
[Address]
Address=10.0.0.2/24
[Route]
Gateway=10.0.0.1
Last edited by rg_arc (2014-11-07 22:50:00)
Offline