at bottom :-
On 08/01/2017, intrigeri <intrig...@debian.org> wrote:
> shirish शिरीष:
>> ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197
>
>> gpg: keyserver receive failed: No keyserver available
>
>> Tried it multiple times but get the above failure.
>
> [...]
>
>> Any ideas what I need to do next ?
>
> Add a "debug-all" line in ~/.gnupg/dirmngr.conf, restart
> dirmngr.socket, try again and look at the logs (on my system they are
> in the systemd Journal).
>
> Cheers,
> --
> intrigeri
>
Umm.. there was no ~/.gnupg/dirmngr.conf hence had to make one
$ touch ~/.gnupg/dirmngr.conf
$ cd ~/.gnupg/
$ nano dirmngr.conf
and just added debug-all
┌─[shirish@debian] - [~/.gnupg] - [10017]
└─[$] cat dirmngr.conf
debug-all
Did the remaining bits.
And this is the result.
$ journalctl --since "1 hour ago"
While I have shared all the entries, the most pertinent might be -
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 -> # Home:
/home/shirish/.gnupg
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 -> # Config:
/home/shirish/.gnupg/dirmngr.conf
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 -> OK Dirmngr 2.1.17
at your service
Jan 08 14:46:40 debian dirmngr[1203]: connection from process 1370 (1000:1000)
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 <- GETINFO version
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 -> D 2.1.17
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 -> OK
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 <- KEYSERVER --clear
hkp://pgp.mit.edu
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 -> OK
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 <- KS_GET -- 0xDAD95197
Jan 08 14:46:40 debian dirmngr[1203]: DBG: dns: libdns initialized
Jan 08 14:46:50 debian dirmngr[1203]: DBG: dns:
getsrv(_hkp._tcp.pgp.mit.edu): Server indicated a failure
Jan 08 14:46:50 debian dirmngr[1203]: command 'KS_GET' failed: Server
indicated a failure <Unspecified source>
Jan 08 14:46:50 debian dirmngr[1203]: DBG: chan_5 -> ERR 219 Server
indicated a failure <Unspecified source>
Jan 08 14:46:50 debian dirmngr[1203]: DBG: chan_5 <- BYE
Jan 08 14:46:50 debian dirmngr[1203]: DBG: chan_5 -> OK closing connection
Jan 08 14:46:50 debian dirmngr[1203]: handler for fd 5 terminated
Please go through the attached logs and let me know if any
improvements can be made.
All any any advice would be useful.
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Jan 08 14:46:21 debian systemd[2360]: dirmngr.socket: Trying to enqueue job
dirmngr.socket/restart/replace
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: Installed new job
dirmngr.service/restart as 219
Jan 08 14:46:21 debian systemd[2360]: dirmngr.socket: Installed new job
dirmngr.socket/restart as 216
Jan 08 14:46:21 debian systemd[2360]: dirmngr.socket: Enqueued job
dirmngr.socket/restart as 216
......
......
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: Changed running ->
stop-sigterm
Jan 08 14:46:21 debian dirmngr[7477]: SIGTERM received - shutting down ...
Jan 08 14:46:21 debian dirmngr[7477]: dirmngr (GnuPG) 2.1.17 stopped
.......
.......
Jan 08 14:46:21 debian systemd[1]: Got cgroup empty notification for:
/user.slice/user-1000.slice/user@1000.service/dirmngr.service
Jan 08 14:46:21 debian systemd[2360]: Received SIGCHLD from PID 7477 (dirmngr).
Jan 08 14:46:21 debian systemd[2360]: Child 7477 (dirmngr) died (code=exited,
status=0/SUCCESS)
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: Child 7477 belongs to
dirmngr.service
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: Main process exited,
code=exited, status=0/SUCCESS
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: Changed stop-sigterm ->
dead
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: Job
dirmngr.service/restart finished, result=done
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: Converting job
dirmngr.service/restart -> dirmngr.service/start
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: cgroup is empty
.....
......
Jan 08 14:46:21 debian systemd[2360]: dirmngr.socket: Changed running -> dead
Jan 08 14:46:21 debian systemd[2360]: dirmngr.socket: Job
dirmngr.socket/restart finished, result=done
Jan 08 14:46:21 debian systemd[2360]: dirmngr.socket: Converting job
dirmngr.socket/restart -> dirmngr.socket/start
Jan 08 14:46:21 debian systemd[2360]: dirmngr.socket: Changed dead -> listening
Jan 08 14:46:21 debian systemd[2360]: dirmngr.socket: Job dirmngr.socket/start
finished, result=done
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: Failed to set pids.max:
No such file or directory
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: Passing 1 fds to service
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: About to execute:
/usr/bin/dirmngr --supervised
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: Forked /usr/bin/dirmngr
as 1203
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: Changed dead -> running
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: Job
dirmngr.service/start finished, result=done
Jan 08 14:46:21 debian systemd[2360]: Failed to send job remove signal for 219:
Connection reset by peer
Jan 08 14:46:21 debian systemd[2360]: dirmngr.socket: Changed listening ->
running
Jan 08 14:46:21 debian systemd[2360]: dirmngr.service: Failed to send unit
change signal for dirmngr.service: Transport endpoint is not connecte
Jan 08 14:46:21 debian systemd[2360]: dirmngr.socket: Failed to send unit
change signal for dirmngr.socket: Transport endpoint is not connected
Jan 08 14:46:21 debian systemd[2360]: Got cgroup empty notification for:
/user.slice/user-1000.slice/user@1000.service/dirmngr.service
Jan 08 14:46:21 debian systemd[2360]: Got disconnect on private connection.
Jan 08 14:46:22 debian dirmngr[1203]: dirmngr.service: Executing:
/usr/bin/dirmngr --supervised
Jan 08 14:46:22 debian dirmngr[1203]: dirmngr[1203]: enabled debug flags: x509
crypto memory cache memstat hashing ipc dns network lookup
Jan 08 14:46:22 debian dirmngr[1203]: dirmngr[1203]: error opening
'/home/shirish/.gnupg/dirmngr_ldapservers.conf': No such file or directory
Jan 08 14:46:22 debian dirmngr[1203]: permanently loaded certificates: 0
Jan 08 14:46:22 debian dirmngr[1203]: runtime cached certificates: 0
..........
..........
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 -> # Home:
/home/shirish/.gnupg
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 -> # Config:
/home/shirish/.gnupg/dirmngr.conf
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 -> OK Dirmngr 2.1.17 at your
service
Jan 08 14:46:40 debian dirmngr[1203]: connection from process 1370 (1000:1000)
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 <- GETINFO version
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 -> D 2.1.17
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 -> OK
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 <- KEYSERVER --clear
hkp://pgp.mit.edu
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 -> OK
Jan 08 14:46:40 debian dirmngr[1203]: DBG: chan_5 <- KS_GET -- 0xDAD95197
Jan 08 14:46:40 debian dirmngr[1203]: DBG: dns: libdns initialized
Jan 08 14:46:50 debian dirmngr[1203]: DBG: dns: getsrv(_hkp._tcp.pgp.mit.edu):
Server indicated a failure
Jan 08 14:46:50 debian dirmngr[1203]: command 'KS_GET' failed: Server indicated
a failure <Unspecified source>
Jan 08 14:46:50 debian dirmngr[1203]: DBG: chan_5 -> ERR 219 Server indicated a
failure <Unspecified source>
Jan 08 14:46:50 debian dirmngr[1203]: DBG: chan_5 <- BYE
Jan 08 14:46:50 debian dirmngr[1203]: DBG: chan_5 -> OK closing connection
Jan 08 14:46:50 debian dirmngr[1203]: handler for fd 5 terminated
