Discussion:
[Sks-devel] Missing peers on status page
Kiss Gabor (Bitman)
2017-10-04 04:02:23 UTC
Permalink
Dear Kristian,

I've noticed that page
https://sks-keyservers.net/status/ks-status.php?server=keyserver.searchy.nl
does not list any peers.
However according to
http://keyserver.searchy.nl:11371/pks/lookup?op=stats
server has 13+2 gossip partners.

I wonder if the two pure IP addresses make your supervisor
software confused? :-)

Regards

Gabor
Kristian Fiskerstrand
2017-10-04 07:16:45 UTC
Permalink
Post by Kiss Gabor (Bitman)
Dear Kristian,
I've noticed that page
https://sks-keyservers.net/status/ks-status.php?server=keyserver.searchy.nl
does not list any peers.
However according to
http://keyserver.searchy.nl:11371/pks/lookup?op=stats
server has 13+2 gossip partners.
I wonder if the two pure IP addresses make your supervisor
software confused? :-)
Only IP addresses are [listed], and IPs are filtered in the front (in
particular internal ones are excluded altogether). It might be a
misconfigured cluster where the stats requests hits a secondary node
instead of the primary.

Unless it is the starting point for a mesh walk it doesn't really
matter, though, and the peer display is only informational.

References:
[listed]
Loading Image...
--
----------------------------
Kristian Fiskerstrand
Blog: https://blog.sumptuouscapital.com
Twitter: @krifisk
----------------------------
Public OpenPGP keyblock at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
----------------------------
"We all die. The goal isn't to live forever, the goal is to create
something that will."
(Chuck Palahniuk)
Frank de Bot
2017-10-04 12:32:09 UTC
Permalink
Hi All,
Post by Kristian Fiskerstrand
Post by Kiss Gabor (Bitman)
Dear Kristian,
I've noticed that page
https://sks-keyservers.net/status/ks-status.php?server=keyserver.searchy.nl
does not list any peers.
However according to
http://keyserver.searchy.nl:11371/pks/lookup?op=stats
server has 13+2 gossip partners.
I wonder if the two pure IP addresses make your supervisor
software confused? :-)
Only IP addresses are [listed], and IPs are filtered in the front (in
particular internal ones are excluded altogether). It might be a
misconfigured cluster where the stats requests hits a secondary node
instead of the primary.
Unless it is the starting point for a mesh walk it doesn't really
matter, though, and the peer display is only informational.
It seems ausing some confusion, so I've adjusted the loadbalancer to
route the pks/lookup?op=stats to the 'outward facing' sks instance.
(Because of the only difference with queries was the query string, it
was quite some trying and failing with rewrite in apache)


Regards,

Frank de Bot
Post by Kristian Fiskerstrand
[listed]
https://download.sumptuouscapital.com/tmp/Screenshot_2017-10-04-08-52-45.png
_______________________________________________
Sks-devel mailing list
https://lists.nongnu.org/mailman/listinfo/sks-devel
Kristian Fiskerstrand
2017-10-04 12:37:51 UTC
Permalink
Post by Frank de Bot
It seems ausing some confusion, so I've adjusted the loadbalancer to
route the pks/lookup?op=stats to the 'outward facing' sks instance.
(Because of the only difference with queries was the query string, it
was quite some trying and failing with rewrite in apache)
Don't know the syntax in apache, but for others trying to do the same
using nginx it is along the lines of
map $arg_op $upstream_server {
"stats" sks_servers_primary;
default sks_servers;
}

where sks_servers and sks_server_primary are defined as upstream
--
----------------------------
Kristian Fiskerstrand
Blog: https://blog.sumptuouscapital.com
Twitter: @krifisk
----------------------------
Public OpenPGP keyblock at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
----------------------------
"At 18 our convictions are hills from which we look; At 45 they are
caves in which we hide."
(F. Scott Fitzgerald)
Frank de Bot
2017-10-04 12:52:54 UTC
Permalink
Post by Kristian Fiskerstrand
Post by Frank de Bot
It seems ausing some confusion, so I've adjusted the loadbalancer to
route the pks/lookup?op=stats to the 'outward facing' sks instance.
(Because of the only difference with queries was the query string, it
was quite some trying and failing with rewrite in apache)
Don't know the syntax in apache, but for others trying to do the same
using nginx it is along the lines of
map $arg_op $upstream_server {
"stats" sks_servers_primary;
default sks_servers;
}
where sks_servers and sks_server_primary are defined as upstream
Wouldn't this cause to also route a search with 'stats' only to the
primary server? ;-)
Post by Kristian Fiskerstrand
_______________________________________________
Sks-devel mailing list
https://lists.nongnu.org/mailman/listinfo/sks-devel
Kristian Fiskerstrand
2017-10-04 12:56:44 UTC
Permalink
Post by Frank de Bot
Wouldn't this cause to also route a search with 'stats' only to the
primary server? ;-)
$arg_op in this case actually means "?op" as key, its not an arbitrary
key in the querystring :)
--
----------------------------
Kristian Fiskerstrand
Blog: https://blog.sumptuouscapital.com
Twitter: @krifisk
----------------------------
Public OpenPGP keyblock at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
----------------------------
Aquila non capit muscas
The eagle does not hunt flies
Alain Wolf
2017-10-04 13:46:30 UTC
Permalink
Post by Frank de Bot
Hi All,
Post by Kristian Fiskerstrand
Post by Kiss Gabor (Bitman)
Dear Kristian,
I've noticed that page
https://sks-keyservers.net/status/ks-status.php?server=keyserver.searchy.nl
does not list any peers.
However according to
http://keyserver.searchy.nl:11371/pks/lookup?op=stats
server has 13+2 gossip partners.
I wonder if the two pure IP addresses make your supervisor
software confused? :-)
Only IP addresses are [listed], and IPs are filtered in the front (in
particular internal ones are excluded altogether). It might be a
misconfigured cluster where the stats requests hits a secondary node
instead of the primary.
Unless it is the starting point for a mesh walk it doesn't really
matter, though, and the peer display is only informational.
It seems ausing some confusion, so I've adjusted the loadbalancer to
route the pks/lookup?op=stats to the 'outward facing' sks instance.
(Because of the only difference with queries was the query string, it
was quite some trying and failing with rewrite in apache)
Regards,
Frank de Bot
Really strange, but searchy.nl now completely vanished from the status
page list, from the list of my peers on [1] and if I open the url
directly it shows another server [2].


[1] https://sks-keyservers.net/status/ks-status.php?server=pgpkeys.urown.net
[2] https://cloud.urown.net/s/fuJPFG9JY53Voaj
--
# pgpkeys.urown.net 11370 # Alain Wolf <***@urown.net> 0x27A69FC9A1744242
Kristian Fiskerstrand
2017-10-04 13:58:54 UTC
Permalink
Post by Alain Wolf
Really strange, but searchy.nl now completely vanished from the status
page list, from the list of my peers on [1] and if I open the url
directly it shows another server [2].
[1] https://sks-keyservers.net/status/ks-status.php?server=pgpkeys.urown.net
[2] https://cloud.urown.net/s/fuJPFG9JY53Voaj
I'm a bit curious what happened here myself, but don't have time for
proper debugging. I flushed some caches and started an update run that
should complete within the next few minutes, though, hopefully that
sorts it.
--
----------------------------
Kristian Fiskerstrand
Blog: https://blog.sumptuouscapital.com
Twitter: @krifisk
----------------------------
Public OpenPGP keyblock at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
----------------------------
Nil desperandum
Never give up
Loading...