Ao executar sudo apt-get update em um dos meus scripts, ele fica suspenso na parte Reading package lists... . Deixei ficar lá por uma hora e ainda não faz nada. Para esclarecer, estou fazendo isso diretamente após executar apt-cache policy docker-engine no processo de configuração do Docker no Ubuntu.
Como isso é diferente de outros problemas de reading package list freeze :
Ao pressionar 'enter' (ou 'return'), 20 segundos depois, continua. Parece haver alguns erros, mas continua e tudo funciona perfeitamente. Aqui está a saída ao pressionar enter :
ebconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-77-generic /boot/vmlinuz-3.13.0-77-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-77-generic /boot/vmlinuz-3.13.0-77-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-77-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-77-generic /boot/vmlinuz-3.13.0-77-generic
run-parts: executing /etc/kernel/postinst.d/x-grub-legacy-ec2 3.13.0-77-generic /boot/vmlinuz-3.13.0-77-generic
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-3.13.0-77-generic
Found kernel: /boot/vmlinuz-3.13.0-77-generic
Updating /boot/grub/menu.lst ... done
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-77-generic /boot/vmlinuz-3.13.0-77-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.13.0-77-generic
Found initrd image: /boot/initrd.img-3.13.0-77-generic
done
Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: crda iw libnl-3-200 libnl-genl-3-200 wireless-regdb The following NEW packages will be installed: crda iw libnl-3-200 libnl-genl-3-200 linux-image-extra-3.13.0-77-generic wireless-regdb 0 upgraded, 6 newly installed, 0 to remove and 72 not upgraded. Need to get 36.9 MB of archives. After this operation, 152 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/main libnl-3-200 amd64 3.2.21-1ubuntu3 [45.7 kB] Get:2 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/main libnl-genl-3-200 amd64 3.2.21-1ubuntu3 [10.2 kB] Get:3 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty/main wireless-regdb all 2013.02.13-1ubuntu1 [6,456 B] Get:4 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty/main crda amd64 1.1.2-1ubuntu2 [15.2 kB] Get:5 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty/main iw amd64 3.4-1 [51.7 kB] Get:6 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/main linux-image-extra-3.13.0-77-generic amd64 3.13.0-77.121 [36.7 MB] Fetched 36.9 MB in 14s (2,582 kB/s) Selecting previously unselected package libnl-3-200:amd64. (Reading database ... 51153 files and directories currently installed.) Preparing to unpack .../libnl-3-200_3.2.21-1ubuntu3_amd64.deb ... Unpacking libnl-3-200:amd64 (3.2.21-1ubuntu3) ... Selecting previously unselected package libnl-genl-3-200:amd64. Preparing to unpack .../libnl-genl-3-200_3.2.21-1ubuntu3_amd64.deb ... Unpacking libnl-genl-3-200:amd64 (3.2.21-1ubuntu3) ... Selecting previously unselected package wireless-regdb. Preparing to unpack .../wireless-regdb_2013.02.13-1ubuntu1_all.deb ... Unpacking wireless-regdb (2013.02.13-1ubuntu1) ... Selecting previously unselected package crda. Preparing to unpack .../crda_1.1.2-1ubuntu2_amd64.deb ... Unpacking crda (1.1.2-1ubuntu2) ... Selecting previously unselected package iw. Preparing to unpack .../archives/iw_3.4-1_amd64.deb ... Unpacking iw (3.4-1) ... Selecting previously unselected package linux-image-extra-3.13.0-77-generic. Preparing to unpack .../linux-image-extra-3.13.0-77-generic_3.13.0-77.121_amd64.deb ... Unpacking linux-image-extra-3.13.0-77-generic (3.13.0-77.121) ... Processing triggers for man-db (2.6.7.1-1ubuntu1) ... Setting up libnl-3-200:amd64 (3.2.21-1ubuntu3) ... Setting up libnl-genl-3-200:amd64 (3.2.21-1ubuntu3) ... Setting up wireless-regdb (2013.02.13-1ubuntu1) ... Setting up crda (1.1.2-1ubuntu2) ... Setting up iw (3.4-1) ... Setting up linux-image-extra-3.13.0-77-generic (3.13.0-77.121) ... Processing triggers for libc-bin (2.19-0ubuntu6.7) ...
Ign http://nova.clouds.archive.ubuntu.com trusty InRelease
Hit http://nova.clouds.archive.ubuntu.com trusty-updates InRelease
Hit http://security.ubuntu.com trusty-security InRelease
Hit http://nova.clouds.archive.ubuntu.com trusty-backports InRelease
E a partir daí, o apt-get update funciona normalmente. Alguém sabe por que eu tenho que pressionar enter para fazer com que ele não seja pendurado em Reading package lists... ? Não é como se eles mostrassem o erro e então eu tenho que pressionar enter , ou que eu fui solicitado com qualquer coisa.
Eu estou procurando uma maneira de chamar apt-get update para que eu não precise pressionar enter (ou simular pressionando isso se eu tiver que fazer isso) se esse problema não puder ser resolvido.
Basta colocar isso no topo do seu script
export DEBIAN_FRONTEND=noninteractive
que melhorará todos os problemas "incapazes de inicializar o frontend". Quando um script é executado de forma autônoma (digamos, na caixa remota ou no sistema iniciado), você não está lá para reconhecer os prompts interativos, portanto, a configuração acima informa ao sistema para fazer o padrão