FS#8936 - pacman segfaults on new Arch64 install

Attached to Project: Pacman
Opened by James Rayner (iphitus) - Saturday, 15 December 2007, 11:05 GMT
Last edited by Aaron Griffin (phrakture) - Wednesday, 06 February 2008, 18:50 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 3.0.6
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
First boot on new 2007.08-2 FTP install
Pacman 3.0.6-2

Steps to Reproduce:
Installed from FTP
Logged in as root
Removed all mirrors except australian mirror
pacman -Syu

Output:
[root@desktop ~]# pacman -Syu
:: Synchronizing package databases...
Internal pacman error: Segmentation faults 00:00:00 [---------] 0%
Please submit a full bug report, with the given package if appropriate.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Wednesday, 06 February 2008, 18:50 GMT
Reason for closing:  Works for me
Additional comments about closing:  No one else in our whole userbase has complained
Comment by James Rayner (iphitus) - Saturday, 15 December 2007, 11:10 GMT
I used a different mirror post install then I used for the install. I changed my mirror to the install mirror and it works.

Problematic mirror: ftp://mirror.pacific.net.au/linux/archlinux/
Working mirror: ftp://mirror.aarnet.edu.au/pub/archlinux/

Can reproduce currently.
Comment by Dan McGee (toofishes) - Saturday, 15 December 2007, 18:34 GMT
Interesting. Can you get us output with --debug=3 (or whatever the most verbose setting is for pacman 3.0.X)?
Comment by James Rayner (iphitus) - Saturday, 15 December 2007, 23:51 GMT
long, so it's here:
http://share.iphitus.org/pacman-debug1

edit: wrong log. oops. Seems it only errors out when the db has update... will post a proper log when there's some updates.
Comment by Aaron Griffin (phrakture) - Monday, 17 December 2007, 22:40 GMT
Hmm do you use a proxy?

If this only happens when there is a db update, perhaps you could set the /var/lib/pacman/*/.lastupdate down a bit to force an update
Comment by James Rayner (iphitus) - Tuesday, 18 December 2007, 21:06 GMT
No proxy, straight standard router + dhcp. I'll give it a test tonight, sorry for the delay, had a busy few days.
Comment by Roman Kyrylych (Romashka) - Thursday, 10 January 2008, 12:15 GMT
James, you can force database update with -Syy (double -y)

I remember at least one case in past when some mirror crashed pacman. I couldn't find that report even after long searching, so I'm not sure if that was not the same mirror.

P.S.: probably not related, but:
debug: connected to mirror.pacific.net.au successfully
debug: mtimes are identical, skipping core.db.tar.gzWaiting for final status
<<< 426 Failure writing network stream.
Huh, what exactly this error means? (same for extra & community from mirror.aarnet.edu.au)
Comment by James Rayner (iphitus) - Thursday, 10 January 2008, 13:08 GMT
Syy didnt cause it. It hasnt happened for a while now, so i don't think I can reproduce this any more. Maybe it was an oddly corrupted file or something.
Comment by Dan McGee (toofishes) - Thursday, 10 January 2008, 14:05 GMT
Up to you James, but I wouldn't mind closing this if you don't think it is a problem anymore, especially now that pacman has changed quite a bit since the 3.0.X series.
Comment by James Rayner (iphitus) - Thursday, 10 January 2008, 20:40 GMT
I'll install 3.1 tonight and see if I can reproduce. If I can't, then I figure we can close this.
Comment by Dan McGee (toofishes) - Wednesday, 06 February 2008, 02:32 GMT
James- I haven't heard back from you so I assume I can close this?

Loading...