Re: [Sks-devel] Need help with clustered setup

[Danny Horne]

On 07/09/2016 1:24 pm, Kristian Fiskerstrand wrote:
>
> And you can manually access 10.78.100.5:11371 and do post on
> /pks/hashquery or a regular get like /pks/lookup?op=stats from the slave?

Sorry, didn't really understand this bit
> As this is accessed internally, is it using spearate listening IP than
> you're configured for using nginx, and sks listens loopback only, etc?
>
>
There is a separate internal virtual network on my setup

This is the master -

recon_address:  164.132.220.24 2001:41d0:1:f41f:24::1 10.78.100.10
hkp_address:    127.0.0.1 ::1 10.78.100.10

This is the slave -

recon_address:                  10.78.100.5
hkp_address:                    10.78.100.5

This is the relevant part of my Nginx config (sks-peer1..... resolves to
10.78.100.5)

        upstream sks_servers
                {
                server localhost:11371;
                server sks-peer1.lockmail.net:11371;
                }

I've also noticed that the master (in this configuration) only seems to
be trying to peer with the slave and is ignoring external peers (even
though they're still in the membership file), which means no new keys
will be added to the database

I'm thinking I should remove the 10.* address from the master, but would
that stop them peering?

signature.asc
Description: OpenPGP digital signature