• cnchi.log: command failed to execute correctly


    I just installed Antergos on a notebook and everything went apparently smooth, but when I looked into cnchi.org I saw the following errors:

    2015-10-12 10:10:51 [DEBUG] pac.py(504) cb_log(): updating database
    2015-10-12 10:10:51 [DEBUG] pac.py(504) cb_log(): adding database entry 'lightdm’
    2015-10-12 10:10:51 [DEBUG] pac.py(504) cb_log(): writing lightdm-1:1.16.3-1 DESC information back to db
    2015-10-12 10:10:51 [DEBUG] pac.py(504) cb_log(): writing lightdm-1:1.16.3-1 FILES information back to db
    2015-10-12 10:10:51 [DEBUG] pac.py(504) cb_log(): adding entry ‘lightdm’ in ‘local’ cache
    2015-10-12 10:10:51 [DEBUG] pac.py(504) cb_log(): executing ". /tmp/alpm_UmvepG/.INSTALL; post_install 1:1.16.3-1"
    2015-10-12 10:10:51 [DEBUG] pac.py(504) cb_log(): executing “/usr/bin/bash” under chroot "/install/"
    2015-10-12 10:10:51 [INFO] slides.py(224) manage_events_from_cb_queue(): Installing gnome-shell (484/822)
    2015-10-12 10:10:51 [INFO] slides.py(224) manage_events_from_cb_queue(): Installing gnome-shell-extensions (485/822)
    2015-10-12 10:10:51 [INFO] slides.py(224) manage_events_from_cb_queue(): Installing lightdm (486/822)
    2015-10-12 10:10:51 [DEBUG] pac.py(504) cb_log(): call to waitpid succeeded
    2015-10-12 10:10:51 [ERROR] pac.py(493) cb_log(): command failed to execute correctly

    2015-10-12 10:11:25 [DEBUG] pac.py(504) cb_log(): adding database entry 'antergos-keyring’
    2015-10-12 10:11:25 [DEBUG] pac.py(504) cb_log(): writing antergos-keyring-20150806-1 DESC information back to db
    2015-10-12 10:11:25 [DEBUG] pac.py(504) cb_log(): writing antergos-keyring-20150806-1 FILES information back to db
    2015-10-12 10:11:25 [DEBUG] pac.py(504) cb_log(): adding entry ‘antergos-keyring’ in ‘local’ cache
    2015-10-12 10:11:25 [DEBUG] pac.py(504) cb_log(): executing ". /tmp/alpm_TUMmPp/.INSTALL; post_install 20150806-1"
    2015-10-12 10:11:25 [DEBUG] pac.py(504) cb_log(): executing “/usr/bin/bash” under chroot "/install/"
    2015-10-12 10:11:25 [DEBUG] pac.py(504) cb_log(): call to waitpid succeeded
    2015-10-12 10:11:25 [ERROR] pac.py(493) cb_log(): command failed to execute correctly

    2015-10-12 10:11:32 [DEBUG] pac.py(504) cb_log(): adding database entry 'linux’
    2015-10-12 10:11:32 [DEBUG] pac.py(504) cb_log(): writing linux-4.2.2-1 DESC information back to db
    2015-10-12 10:11:32 [DEBUG] pac.py(504) cb_log(): writing linux-4.2.2-1 FILES information back to db
    2015-10-12 10:11:32 [DEBUG] pac.py(504) cb_log(): adding entry ‘linux’ in ‘local’ cache
    2015-10-12 10:11:32 [DEBUG] pac.py(504) cb_log(): executing ". /tmp/alpm_io02kN/.INSTALL; post_install 4.2.2-1"
    2015-10-12 10:11:32 [DEBUG] pac.py(504) cb_log(): executing “/usr/bin/bash” under chroot "/install/"
    2015-10-12 10:11:33 [DEBUG] pac.py(504) cb_log(): call to waitpid succeeded
    2015-10-12 10:11:33 [ERROR] pac.py(493) cb_log(): command failed to execute correctly

    2015-10-12 10:11:34 [DEBUG] chroot.py(136) run(): Created symlink from /etc/systemd/system/multi-user.target.wants/haveged.service to /usr/lib/systemd/system/haveged.service.
    2015-10-12 10:11:34 [DEBUG] install.py(647) enable_services(): Service ‘haveged’ has been enabled.
    2015-10-12 10:11:34 [DEBUG] chroot.py(136) run(): Failed to create bus connection: No such file or directory

  • Dear @developers is there a way to know which commands “failed to execute correctly”, so that I can run then manually if needed?

  • Hi,

    I’m positive you can safely ignore those pac.py errors. I’ve never experienced any problem. Having said that, I promise I’ll check them out asap.

    Cheers!

command failed1 Posts 3Views 760
Log in to reply