[SOLVED] error: failed to commit transaction (wro..) v4.0.3

Caliburn · 2012-05-04 21:43:05

Using the latest Pacman v4.0.3, I'm seeing this error [error: failed to commit transaction (wrong or NULL argument passed)] continuously on larger files. After doing some research ( https://bugs.archlinux.org/task/26764 ) and clicking the last link in the post ( http://projects.archlinux.org/pacman.gi … id=44f146f ), seeing it's committed on 1/23, I'm wondering if slower connections are no longer allowed in Arch setups.

The description for the commit reads as follows: "This is particularly important in the case of FTP control connections, which may be closed by rogue NAT/firewall devices detecting idle connections on larger transfers which may take 5-10+ minutes."

I have a connection that is only 10-15kb/s and I'm in no way able to upgrade. Is Arch no longer feasible for connections such as mine? The only time this error happens is during larger file transfers w/ Pacman.

Last edited by Caliburn (2012-05-04 22:46:26)

Trilby · 2012-05-04 21:47:03

I don't know if it's relevant, but that description refers to FTP connections. Are you using ftp mirrors, or just http? Try the latter.

Caliburn · 2012-05-04 22:45:26

Thank you for the reply, Trilby. Good suggestion, too. After commenting out the ftp servers in the mirrorlist and using only the http ones, the problem looks to be solved after grabbing some pretty large files (10~mb).

I'll update again if the problem persists, but for now: it's solved. Thanks!

Arch Linux

#1 2012-05-04 21:43:05

[SOLVED] error: failed to commit transaction (wro..) v4.0.3

#2 2012-05-04 21:47:03

Re: [SOLVED] error: failed to commit transaction (wro..) v4.0.3

#3 2012-05-04 22:45:26

Re: [SOLVED] error: failed to commit transaction (wro..) v4.0.3

Board footer