Could not connect to the AUR

[lucacerone]

In the last few days pacaur always shows this message:

:: Package(s) usb-creator not found in repositories, trying AUR...
:: Starting AUR upgrade...
:: Could not connect to the AUR

I have seen this has happened in the past. I have no idea how to help you debug the issue, but if you let me know how to get information that is relevant for you, I will gladly run the commands and post the output here.

Thanks for the help!

[lucacerone]

I can confirm that building the package manually works.

makepkg -si works fine.

Up to the latest update pacaur was working so I would exclude permissions with sudoers and so on.

I have posted the output of

bash -x pacaur -Syu usb-creator

here: http://pastebin.com/kJ60BJFt

[rmarquis]

I cannot reproduce, and the debug output doesn't give much useful information. It seems curl has trouble connecting to the AUR RPC interface on your machine. Does the error always happen? Does it happen with any package, or just usb-creator?

Check "cower -u" and see if it has troubles connecting to the AUR too. You might want to check your dns server too. Also, using Google primary DNS servers might help here.

[lucacerone]

Hi, it didn't happen before, but now happens with all the packages (not only usb-creator). Cower -u connects fine to the AUR (it actually tells me that pacaur can be updated).

I will try to use google dns and see if that improves things. Thanks for the help!

2014-08-24 16:01 GMT+02:00 Spyhawk notifications@github.com:

I cannot reproduce, and the debug output don't give much useful information. It seems curl has trouble connecting to the AUR RPC interface on your machine. Does the error always happen? Does it happen with any package, or just usb-creator?

Check "cower -u" and see if it has troubles connecting to the AUR too. You might want to check your dns server too. Also, using Google primary DNS servers might help here.

— Reply to this email directly or view it on GitHub https://github.com/Spyhawk/pacaur/issues/264#issuecomment-53194127.

[lucacerone]

I also tried to change dns and install some package like yaourt. The problem persists. I forgot to mention that I still have v. 4.2.8 installed.

[lucacerone]

The problem persists after upgrading to 4.2.9

[rmarquis]

The command that fails is the following:

curl -sfg --compressed -C 0 'https://aur.archlinux.org/rpc.php?type=multiinfo&v=3&arg[]=chromium-pepper-flash&arg[]=cower&arg[]=ctemplate&arg[]=dropbox&arg[]=gcc44&arg[]=gnash-common&arg[]=gnash-gtk&arg[]=google-talkplugin&arg[]=ido&arg[]=jre6-compat&arg[]=libindicator-gtk3&arg[]=libiodbc&arg[]=mysql-connector-c%2b%2b&arg[]=mysql-utilities&arg[]=mysql-workbench-gpl&arg[]=nepomuk-core&arg[]=pacaur&arg[]=qbittorrent&arg[]=rstudio-desktop-bin&arg[]=samsung-unified-driver&arg[]=shared-desktop-ontologies&arg[]=soprano&arg[]=soundfont-fluid&arg[]=ttf-ms-fonts&arg[]=ubuntu-wallpapers&arg[]=usb-creator&arg[]=virtuoso-base&arg[]=vsqlite%2b%2b' -o /tmp/pacaurtmp-luca/rpc.json

Does a simple curl command fails too? The following should return a json response:

curl -sfg --compressed -C 0 'https://aur.archlinux.org/rpc.php?type=multiinfo&v=3&arg[]=pacaur'

Last time curl was updated was a month ago (24/07/14), and there is little I can do since this is not directly related to pacaur.

[lucacerone]

Thanks, curl fails with the following error:

* About to connect() to aur.archlinux.org port 443 (#0)
*   Trying 5.9.250.164...
* Adding handle: conn: 0x1be2ce0
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x1be2ce0) send_pipe: 1, recv_pipe: 0
* Connected to aur.archlinux.org (5.9.250.164) port 443 (#0)
* error setting certificate verify locations:
  CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* Closing connection 0

it seems something related to the certificate...

[lucacerone]

Creating a symbolic link to /etc/ssl/certs/ca-certificates.crt called /etc/pki/tls/certs/ca-bundle.crt fixes the issue. I would be interested in understanding why I had the issue in the first place.

I'll close the bug since it is clearly not pacaur related. Thanks for helping me!

[rmarquis]

You're welcome. I'm not sure why this happened in the first place. Checking the package that owns the /etc/pki/tls/certs/ca-bundle.crt file (using pacman -Qo) might give more useful information.

[lucacerone]

..it is weird, apparently no package owns the file :

pacman -Qo /etc/pki/tls/certs/ca-bundle.crt
error: No package owns /etc/pki/tls/certs/ca-bundle.crt

Thanks a lot again for all the help (I have posted my solution in the comments in the AUR page for pacaur since I have seen other people complaining for the same issue, hopefully it will help them as well).

[rmarquis]

For the records, here is the associated forum thread and the cause of the issue.