Project

General

Profile

Bug #5615

fmd should make sure it is registered with rpcbind

Added by Marcel Telka almost 6 years ago. Updated almost 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
cmd - userland programs
Start date:
2015-02-13
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:

Description

In a case the rpcbind restarts, the fmd looses its registration with it (see #5611 for the example). Since fmd is system critical service, we do not want to restart it when absolutely not needed. So we need to find another solution for fmd to make sure the fmd is still registered (or re-registered) with rpcbind in a case the rpcbind restarts.

From an email from Robert Mustacchi:

I don't have first hand knowledge of this, so I'm mostly trying to put
it together. But part of fmd's purpose is to diagnose faults that occur.
When services restart for whatever reason, that information is sent off
to fmd as part of diagnosis by startd/configd. Say you had a
pathological rpcbind, you wouldn't want those errors causing fmd to
restart and making it harder to actually diagnose the failure that's
going on.

So, in this case, it seems like given fmd's purpose, we shouldn't be
restarting and should file an RFE to implement the poll or think about
some other mechanism.

Related issues

Related to illumos gate - Bug #5611: Some RPC services do not re-register on rpcbind restartClosedMarcel Telka2015-02-11

Actions
#1

Updated by Marcel Telka almost 6 years ago

An idea from Gordon Ross: we could try to re-check (and re-register) on refresh.

Also available in: Atom PDF