Illumos might have getpeerucred, which can also set errno to ENOTSUP.
On Sun, Jul 26, 2020 at 3:25 AM Reid Wahl wrote:
> Hmm. If it's reading PCMK_ipc_type and matching the server type to
> QB_IPC_SOCKET, then the only other place I see it could be coming from is
> qb_ipc_auth_creds.
>
> qb_ipcs
Hmm. If it's reading PCMK_ipc_type and matching the server type to
QB_IPC_SOCKET, then the only other place I see it could be coming from is
qb_ipc_auth_creds.
qb_ipcs_run -> qb_ipcs_us_publish -> qb_ipcs_us_connection_acceptor ->
qb_ipcs_uc_recv_and_auth -> process_auth -> qb_ipc_auth_creds ->
s
Sorry, actually the problem is not gone yet.
Now corosync and pacemaker are running happily, but those IPC errors are coming
out of heartbeat and crmd as soon as I start it.
The pacemakerd process has PCMK_ipc_type=socket, what's wrong with heartbeat or
crmd?
Here's the env of the process:
so
Sorry, I was using wrong hostnames for that networks, using debug log I found
it was not finding "this node" in conf file.
Gabriele
Sonicle S.r.l.
:
http://www.sonicle.com
Music:
http://www.gabrielebulfon.com
Quantum Mechanics :
http://www.cdbaby.com/cd/gabrielebulfon
Da:
Gabriele Bulfon
Thanks, I ran it manually so I got those errors, running from service script it
correctly set PCMK_ipc_type to socket.
But now I see these now:
Jul 26 11:08:16 [4039] pacemakerd: info: crm_log_init: Changed active directory
to /sonicle/var/cluster/lib/pacemaker/cores
Jul 26 11:08:16 [4039] pace