Return-Path: <nex2@valbek.cz>
Delivered-To: pasek@valbek.cz
Received: from mail.valbek.cz (localhost.localdomain [127.0.0.1])
	by mail.valbek.cz (Postfix) with ESMTP id 6CE7E1CF8005;
	Thu, 16 Jun 2011 03:45:13 +0200 (CEST)
Received: from nex2.valbek.cz (unknown [192.168.1.191])
	by mail.valbek.cz (Postfix) with ESMTP id 61BE31CF8001
	for <it@valbek.cz>; Thu, 16 Jun 2011 03:45:13 +0200 (CEST)
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.020 (F2.74; B3.07; Q3.07)
Date: Thu, 16 Jun 2011 03:45:13 +0200
To: it@valbek.cz
From: nex2@valbek.cz
Content-Type: multipart/mixed; boundary="_----------=_130818871368280"
Content-Transfer-Encoding: binary
Subject: [NMS Report] NOTICE: host nex2
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.45/RELEASE,
	 bases: 20110616 #5534606, check: 20110616 clean

This is a multi-part message in MIME format.

--_----------=_130818871368280
Content-Disposition: inline
Content-Length: 2669
Content-Transfer-Encoding: binary
Content-Type: text/plain


FAULT: **********************************************************************
FAULT: Appliance   : nex2 (OS v3.0.5, NMS v3.0.5 (r9220))
FAULT: Machine SIG : 9BHG8AI9K
FAULT: Primary MAC : 
FAULT: Time        : Thu Jun 16 03:45:13 2011
FAULT: Trigger     : services-check
FAULT: Fault Type  : ALARM
FAULT: Fault ID    : 28
FAULT: Fault Count : 729
FAULT: Severity    : NOTICE
FAULT: Description : Service auto-sync:data-LI34-000 went into maintenance
FAULT:             : state. Corrective action applied: service state = online
FAULT: **********************************************************************

!
! For more detais on this trigger click on link below:
! http://:2000/data/runners?selected_runner=services-check
!

LOG: /var/svc/log/system-filesystem-zfs-auto-sync:data-LI34-000.log
LOG: ------------------------------------------------------------------------
LOG: [ Jun 16 03:00:34 Method "stop" exited with status 0. ]
LOG: [ Jun 16 03:00:34 Stopping for maintenance due to service_request. ]
LOG: [ Jun 16 03:15:09 Leaving maintenance because clear requested. ]
LOG: [ Jun 16 03:15:09 Enabled. ]
LOG: [ Jun 16 03:15:09 Executing start method ("/lib/svc/method/zfs-auto-sync start"). ]
LOG: [ Jun 16 03:15:10 Method "start" exited with status 0. ]
LOG: [ Jun 16 03:30:07 (zfs-auto-sync, 5990) from: root@nex1.valbek.cz:/data/LI34, to: localhost:/data/LI34, proto=zfs+netcat, dircontent, marker=...d612 ]
LOG: [ Jun 16 03:30:09 (zfs-auto-sync, 5990)     auto-sync will process every folder and every snapshot manually. See progress information below ]
LOG: [ Jun 16 03:30:21 (zfs-auto-sync, 5990) Error: failed to list marker '9798229f7db1b951c52c3314c39cd612' at source root@nex1.valbek.cz/data/LI34 ]
LOG: [ Jun 16 03:30:21 (zfs-auto-sync, 5990) WARNING: Service's saved marker is might not actual. Trying to get real marker name ]
LOG: [ Jun 16 03:30:31 (zfs-auto-sync, 5990) Fatal Error: Could not find working marker for replication. Auto-sync will not continue ]
LOG: [ Jun 16 03:30:31 (zfs-auto-sync, 5990) Moving service svc:/system/filesystem/zfs/auto-sync:data-LI34-000 to maintenance mode. ]
LOG: [ Jun 16 03:30:31 Stopping for maintenance due to service_request. ]
LOG: [ Jun 16 03:30:31 Executing stop method ("/lib/svc/method/zfs-auto-sync stop"). ]
LOG: [ Jun 16 03:30:35 Method "stop" exited with status 0. ]
LOG: [ Jun 16 03:30:35 Stopping for maintenance due to service_request. ]
LOG: [ Jun 16 03:45:09 Leaving maintenance because clear requested. ]
LOG: [ Jun 16 03:45:09 Enabled. ]
LOG: [ Jun 16 03:45:09 Executing start method ("/lib/svc/method/zfs-auto-sync start"). ]
LOG: [ Jun 16 03:45:12 Method "start" exited with status 0. ]


--_----------=_130818871368280--