Roots Discourse

Warning: apt-key output should not be parsed (stdout is not a terminal) at TASK [php : Add PHP 7.3 PPA]

trellis
#1

TASK [mailhog : Copy mailhog init script into place.] **************************
skipping: [default]

TASK [mailhog : Copy mailhog systemd unit file into place (for systemd systems).] ***
changed: [default]

TASK [mailhog : Ensure mailhog is enabled and will start on boot.] *************
changed: [default]

TASK [php : Add PHP 7.3 PPA] ***************************************************
System info:
Ansible 2.7.8; Vagrant 2.2.4; Linux
Trellis 1.0.1: January 16th, 2019

Warning: apt-key output should not be parsed (stdout is not a terminal)
gpg: connecting dirmngr at ‘/tmp/apt-key-gpghome.LPhptfMTeY/S.dirmngr’
failed: IPC connect call failed
gpg: keyserver receive failed: No dirmngr
Warning: apt-key output should not be parsed (stdout is not a terminal)
gpg: connecting dirmngr at ‘/tmp/apt-key-gpghome.LPhptfMTeY/S.dirmngr’
failed: IPC connect call failed
gpg: keyserver receive failed: No dirmngr

fatal: [default]: FAILED! => {“changed”: false, “cmd”: “apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 14AA40EC0831756756D7F66C4F4EA0AAE5267A6C”, “rc”: 2, “stderr_lines”: [“Warning: apt-key output should not be parsed (stdout is not a terminal)”, “gpg: connecting dirmngr at ‘/tmp/apt-key-gpghome.LPhptfMTeY/S.dirmngr’ failed: IPC connect call failed”, “gpg: keyserver receive failed: No dirmngr”], “stdout”: “Executing: /tmp/apt-key-gpghome.LPhptfMTeY/gpg.1.sh --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 14AA40EC0831756756D7F66C4F4EA0AAE5267A6C\n”, “stdout_lines”: [“Executing: /tmp/apt-key-gpghome.LPhptfMTeY/gpg.1.sh --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 14AA40EC0831756756D7F66C4F4EA0AAE5267A6C”]}

RUNNING HANDLER [fail2ban : restart fail2ban] **********************************
changed: [default]

RUNNING HANDLER [ferm : restart ferm] ******************************************
skipping: [default]

RUNNING HANDLER [ntp : restart ntp] ********************************************
changed: [default]

RUNNING HANDLER [sshd : restart ssh] *******************************************
changed: [default]

RUNNING HANDLER [mariadb : restart mysql server] *******************************
changed: [default]
to retry, use: --limit @/home/amankapoor/development/wordpress/website.com/trellis/dev.retry

PLAY RECAP *********************************************************************
default : ok=49 changed=32 unreachable=0 failed=1

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

I get the above error when I run vagrant up. And my installation fails.

Then I run vagrant destroy and again vagrant up, and in the second run, it proceeds properly.

TASK [mailhog : Copy mailhog init script into place.] **************************
skipping: [default]

TASK [mailhog : Copy mailhog systemd unit file into place (for systemd systems).] ***
changed: [default]

TASK [mailhog : Ensure mailhog is enabled and will start on boot.] *************
changed: [default]

TASK [php : Add PHP 7.3 PPA] ***************************************************
changed: [default]

TASK [php : Install PHP 7.3] ***************************************************
changed: [default] => (item=php7.3-fpm)
changed: [default] => (item=php7.3-dev)
ok: [default] => (item=php7.3-xml)
changed: [default] => (item=php7.3-curl)
changed: [default] => (item=php7.3-mysql)
changed: [default] => (item=php7.3-gd)
changed: [default] => (item=php7.3-xmlrpc)
ok: [default] => (item=php7.3-opcache)
ok: [default] => (item=php7.3-cli)
ok: [default] => (item=php7.3-common)
changed: [default] => (item=php7.3-mbstring)
changed: [default] => (item=php7.3-zip)

TASK [php : Start php7.3-fpm service] ******************************************
ok: [default]

Why is this happening?

I generally destroy the machine and then run vagrant up.

0 Likes

#2

I’ve never seen this myself, but I did find https://github.com/ansible/ansible/issues/28820.

0 Likes

#3

Yeah, found that too but not of much help.

No idea why, but this doesn’t seem very stable.

I was getting this error that I posted, and it disappeared after several attempts of re-running it.

Then til yesterday, I was building my website in dev mode and everything was good. Then the next morning, I added new RAM and now when I run vagrant up, I get this error:

TASK [wordpress-install : Setup Permalink Structure] ***************************
System info:
Ansible 2.7.8; Vagrant 2.2.4; Linux
Trellis 1.0.1: January 16th, 2019

non-zero return code
PHP Fatal error: Uncaught Error: Call to a member function flush_rules() on
null in /srv/www/promos.neticians.com/current/web/wp/wp-
includes/rewrite.php:276
Stack trace:

I have tried running vagrant up multiple times now and same thing. I even git checkout those commits which were working good but to no avail.

This is very weird.

0 Likes

closed #4

This topic was automatically closed after 42 days. New replies are no longer allowed.

0 Likes