You are not logged in.
When running my ansible-playbooks, ansible is hanging. A strace shows it's trying to locate a "sudo.mo" file but is unsuccessul:
~ $ sudo strace -fp 2111
Process 2111 attached
select(18, [15 17], [], [15 17], {0, 643768}) = 0 (Timeout)
stat("/usr/share/locale/en_AU.UTF-8/LC_MESSAGES/sudo.mo", 0x7fff6f9338f0) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en_AU/LC_MESSAGES/sudo.mo", 0x7fff6f9338f0) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en.UTF-8/LC_MESSAGES/sudo.mo", 0x7fff6f9338f0) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en/LC_MESSAGES/sudo.mo", 0x7fff6f9338f0) = -1 ENOENT (No such file or directory)
wait4(2298, 0x7fff6f933cfc, WNOHANG, NULL) = 0
select(18, [15 17], [], [15 17], {1, 0}) = 0 (Timeout)
stat("/usr/share/locale/en_AU.UTF-8/LC_MESSAGES/sudo.mo", 0x7fff6f9338f0) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en_AU/LC_MESSAGES/sudo.mo", 0x7fff6f9338f0) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en.UTF-8/LC_MESSAGES/sudo.mo", 0x7fff6f9338f0) = -1 ENOENT (No such file or directory)
stat("/usr/share/locale/en/LC_MESSAGES/sudo.mo", 0x7fff6f9338f0) = -1 ENOENT (No such file or directory)
wait4(2298, 0x7fff6f933cfc, WNOHANG, NULL) = 0
Did this file go missing in a recent sudo package or something?
Last edited by fukawi2 (2014-04-18 14:27:31)
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
sudo 1.8.5.p2-1 from june 2 2012 is the oldest version i have in my /var/cache/pacman/pkg folder, and that one doesn't have that file also.
ansible was updated on 2014-04-14 22:56 UTC, does it work if you downgrade ansible ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I've downgraded ansible to the previous version I had, and no change -- it hangs after the Gathering Facts stage.
Further digging, it appears to be related to one host that is running SSH on a non-standard port. It accidentally ended up in my inventory file multiple times, some with and some without the port specification. Fixing that has resolved the issue -- not sure why strace showed it looping over the sudo file, or why it hasn't been a problem before
Thanks for your input
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline