Project

General

Profile

Actions

Feature #4434

open

fm/smtp-notify service fails to start if using postfix instead of sendmail on /hipster

Added by Predrag Zečević almost 8 years ago. Updated about 7 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Start date:
2013-12-27
Due date:
% Done:

0%

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

Description

Hi,

I am using postfix as default MTA, and have noticed that fm/smtp-notify service was down:

$ svcs -xv
svc:/network/sendmail-client:default (sendmail SMTP client queue runner)
 State: disabled since December 27, 2013 08:37:46 AM CET
Reason: Disabled by an administrator.
   See: http://illumos.org/msg/SMF-8000-05
   See: man -M /usr/share/man -s 1M sendmail
Impact: 1 dependent service is not running:
        svc:/system/fm/smtp-notify:default

After looking at manifest file, one can see that it REQUIRES sendmail-client:default, so I have fixed it to have it OPTIONAL (see attachment).

$ pfexec svccfg validate manifest-smtp-notify.xml
$ pfexec svccfg import manifest-smtp-notify.xml
$ pfexec svcadm refresh svc:/system/fm/smtp-notify:default
$ pfexec svcadm restart svc:/system/fm/smtp-notify:default

I guess it is not breaking anything.

Regards.


Files

manifest-smtp-notify.xml (4.73 KB) manifest-smtp-notify.xml Predrag Zečević, 2013-12-27 08:21 AM
Actions #1

Updated by Predrag Zečević almost 8 years ago

UPDATE:

on latest /hipster i got 2 mails (due to 'pkg update' and reboot action and probably fact that my box has 2 pools):

From: No Access User <predrag.zecevic@our-domain.com>
Message-Id: <201401060759.s067x0FM001255@solarix.local>
X-FMEV-HOSTNAME: solarix
X-FMEV-CLASS: list.suspect
X-FMEV-UUID: 05991ec1-cad1-c21b-e07c-e3db6b60c5b2
X-FMEV-CODE: ZFS-8000-CS
X-FMEV-SEVERITY: Major
Reply-To: predrag.zecevic@our-domain.com
Subject: Fault Management Event: solarix:ZFS-8000-CS
To: undisclosed-recipients:;

SUNW-MSG-ID: ZFS-8000-CS, TYPE: Fault, VER: 1, SEVERITY: Major
EVENT-TIME: Fri Nov 29 13:06:50 CET 2013
PLATFORM: Vostro-400, CSN: 4DCHN3J, HOSTNAME: solarix
SOURCE: zfs-diagnosis, REV: 1.0
EVENT-ID: 05991ec1-cad1-c21b-e07c-e3db6b60c5b2
DESC: A ZFS pool failed to open.  Refer to http://illumos.org/msg/ZFS-8000-CS for more information.
AUTO-RESPONSE: No automated response will occur.
IMPACT: The pool data is unavailable
REC-ACTION: Run 'zpool status -x' and attach any missing devices, follow
     any provided recovery instructions or restore from backup.

and similar to this one:
From: No Access User <predrag.zecevic@our-domain.com>
Message-Id: <201401060759.s067x1p6001316@solarix.local>
X-FMEV-HOSTNAME: solarix
X-FMEV-CLASS: list.suspect
X-FMEV-UUID: a6857ac3-215a-c087-cee5-af9172c43713
X-FMEV-CODE: ZFS-8000-D3
X-FMEV-SEVERITY: Major
Reply-To: predrag.zecevic@our-domain.com
Subject: Fault Management Event: solarix:ZFS-8000-D3
To: undisclosed-recipients:;

SUNW-MSG-ID: ZFS-8000-D3, TYPE: Fault, VER: 1, SEVERITY: Major
EVENT-TIME: Fri Nov 29 13:06:50 CET 2013
PLATFORM: Vostro-400, CSN: 4DCHN3J, HOSTNAME: solarix
SOURCE: zfs-diagnosis, REV: 1.0
EVENT-ID: a6857ac3-215a-c087-cee5-af9172c43713
DESC: A ZFS device failed.  Refer to http://illumos.org/msg/ZFS-8000-D3 for more information.
AUTO-RESPONSE: No automated response will occur.
IMPACT: Fault tolerance of the pool may be compromised.
REC-ACTION: Run 'zpool status -x' and replace the bad device.

Neither information is correct (after log in):
$ pfexec zpool status -x
all pools are healthy

To me it looks like some FM check is done to early.

Regards.

Actions #2

Updated by Ken Mays over 7 years ago

  • Tracker changed from Bug to Feature
Actions #3

Updated by Rich Lowe about 7 years ago

  • Project changed from OpenIndiana Distribution to illumos gate
  • Category deleted (PKG (Image Packaging System))
Actions

Also available in: Atom PDF