пятница, 13 ноября 2015 г.
четверг, 12 ноября 2015 г.
среда, 11 ноября 2015 г.
вторник, 10 ноября 2015 г.
У линукс своя атмосфера.
у линукс своя атмосфера :-/
nagios@fs:~$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +36.0°C (high = +80.0°C, crit = +100.0°C)
Core 1: +39.0°C (high = +80.0°C, crit = +100.0°C)
coretemp-isa-0003
Adapter: ISA adapter
Core 0: +35.0°C (high = +86.0°C, crit = +100.0°C)
Core 1: +34.0°C (high = +86.0°C, crit = +100.0°C)
плагин nagios парсит построчно и обстановку видит как:
nagios@fs:~$ /usr/lib/nagios/plugins/check_lm_sensors --list
found sensor Core 0 (36.0)
found sensor Core 1 (39.0)
found sensor Core 0 (35.0)
found sensor Core 1 (34.0)
а мониторит так:
nagios@fs:~$ /usr/lib/nagios/plugins/check_lm_sensors --high Core_0=50,60
LM_SENSORS OK - Core 0=36.0|Core 0=36.0;50;60;;
ну вы поняли =)
Как исправить:
nagios@fs:~$ cat /etc/sensors.d/coretemp.cfg
chip "coretemp-isa-0000"
label temp2 "P0_Core0"
label temp3 "P0_Core1"
chip "coretemp-isa-0003"
label temp2 "P1_Core0"
label temp3 "P1_Core1"
БЛЖАД! почему, почему у нулевого кора параметр temp2???
итого:
nagios@fs:~$ sensors
coretemp-isa-0000
Adapter: ISA adapter
P0_Core0: +36.0°C (high = +80.0°C, crit = +100.0°C)
P0_Core1: +39.0°C (high = +80.0°C, crit = +100.0°C)
coretemp-isa-0003
Adapter: ISA adapter
P1_Core0: +35.0°C (high = +86.0°C, crit = +100.0°C)
P1_Core1: +34.0°C (high = +86.0°C, crit = +100.0°C)
nagios@fs:~$ /usr/lib/nagios/plugins/check_lm_sensors --list
found sensor P0_Core0 (36.0)
found sensor P0_Core1 (39.0)
found sensor P1_Core0 (36.0)
found sensor P1_Core1 (35.0)
nagios@fs:~$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +36.0°C (high = +80.0°C, crit = +100.0°C)
Core 1: +39.0°C (high = +80.0°C, crit = +100.0°C)
coretemp-isa-0003
Adapter: ISA adapter
Core 0: +35.0°C (high = +86.0°C, crit = +100.0°C)
Core 1: +34.0°C (high = +86.0°C, crit = +100.0°C)
плагин nagios парсит построчно и обстановку видит как:
nagios@fs:~$ /usr/lib/nagios/plugins/check_lm_sensors --list
found sensor Core 0 (36.0)
found sensor Core 1 (39.0)
found sensor Core 0 (35.0)
found sensor Core 1 (34.0)
а мониторит так:
nagios@fs:~$ /usr/lib/nagios/plugins/check_lm_sensors --high Core_0=50,60
LM_SENSORS OK - Core 0=36.0|Core 0=36.0;50;60;;
ну вы поняли =)
Как исправить:
nagios@fs:~$ cat /etc/sensors.d/coretemp.cfg
chip "coretemp-isa-0000"
label temp2 "P0_Core0"
label temp3 "P0_Core1"
chip "coretemp-isa-0003"
label temp2 "P1_Core0"
label temp3 "P1_Core1"
БЛЖАД! почему, почему у нулевого кора параметр temp2???
итого:
nagios@fs:~$ sensors
coretemp-isa-0000
Adapter: ISA adapter
P0_Core0: +36.0°C (high = +80.0°C, crit = +100.0°C)
P0_Core1: +39.0°C (high = +80.0°C, crit = +100.0°C)
coretemp-isa-0003
Adapter: ISA adapter
P1_Core0: +35.0°C (high = +86.0°C, crit = +100.0°C)
P1_Core1: +34.0°C (high = +86.0°C, crit = +100.0°C)
nagios@fs:~$ /usr/lib/nagios/plugins/check_lm_sensors --list
found sensor P0_Core0 (36.0)
found sensor P0_Core1 (39.0)
found sensor P1_Core0 (36.0)
found sensor P1_Core1 (35.0)
Description of Tape Alerts and code definitions
Article URL:http://www.veritas.com/docs/000005226
---------------------------------------------------------
A "tape alert" message is a critical, warning, or informational alert that occurs due to a tape drive or robotic library hardware event. These "tape alert" messages are stored on the tape drive or robotic library. Applications like NetBackup query the tape device or robotic library for these "tape alert" messages and display the "tape alerts" to the user. "Tape alert" messages are reported in the NetBackup bptm log. The tape alert technology detects and logs hardware and media errors.
It is important to remember that while NetBackup displays these "tape alerts," the alerts occur due to a tape drive or robotic library hardware event. Check the Event Viewer for any hardware related errors. Please contact the Original Equipment Manufacturer (OEM) for support.
The "errors" file may also contain specific Tape Alert information:
\Veritas\Netbackup\db\media\errors
TapeAlert is a standard for devices to report diagnostic messages to the controlling application. A "No TapeAlert Messages" response is a good thing. Here's the list of codes and definitions as it exists today.
(from the ANSI T10 Specifications):
tapealert_codes = {
0x01: 'Having problems reading (slowing down)',
0x02: 'Having problems writing (losing capacity)',
0x03: 'Uncorrectable read/write error',
0x04: 'Media Performance Degraded, Data Is At Risk',
0x05: 'Read Failure',
0x06: 'Write Failure',
0x07: 'Media has reached the end of its useful life',
0x08: 'Cartridge not data grade',
0x09: 'Cartridge write protected',
0x0A: 'Initiator is preventing media removal',
0x0B: 'Cleaning media found instead of data media',
0x0C: 'Cartridge contains data in an unsupported format',
0x0D: 'Recoverable mechanical cartridge failure (broken tape?)',
0x0E: 'Unrecoverable mechanical cartridge failure (broken tape?)',
0x0F: 'Failure of cartridge memory chip',
0x10: 'Forced eject of media',
0x11: 'Read only media loaded',
0x12: 'Tape directory corrupted on load',
0x13: 'Media nearing end of life',
0x14: 'Tape drive neads cleaning NOW',
0x15: 'Tape drive needs to be cleaned soon',
0x16: 'Cleaning cartridge used up',
0x17: 'Invalid cleaning cartidge used',
0x18: 'Retension requested',
0x19: 'Dual port interface failed',
0x1A: 'Cooling fan in drive has failed',
0x1B: 'Power supply failure in drive',
0x1C: 'Power consumption outside specified range',
0x1D: 'Preventative maintenance needed on drive',
0x1E: 'Hardware A: Tape drive has a problem not read/write related',
0x1F: 'Hardware B: Tape drive has a problem not read/write related',
0x20: 'Problem with SCSI interface between tape drive and initiator',
0x21: 'The current operation has failed. Eject and reload media',
0x22: 'Attempt to download new firmware failed',
0x23: 'Drive humidity outside operational range',
0x24: 'Drive temperature outside operational range',
0x25: 'Drive voltage outside operational range',
0x26: 'Failure of drive predicted soon',
0x27: 'Diagnostics required',
# 0x28 to 0x2E are obsolete, but some vendors still have them listed.
0x28: 'Loader Hardware A: Changer having problems communicating with tape drive',
0x29: 'Loader Stray Tape: Stray tape left in drive from prior error',
0x2A: 'Loader Hardware B: Autoloader mechanism has a fault',
0x2B: 'Loader Door: Loader door is open, please close it',
# 0x2F to 0x31 are reserved
0x32: 'Media statistics lost',
0x33: 'Tape directory invalid at unload (reread all to rebuild)',
0x34: 'Tape system area write failure',
0x35: 'Tape system area read failure',
0x36: 'Start of data not found',
0x37: 'Media could not be loaded/threaded',
0x38: 'Unrecoverable unload failed',
0x39: 'Automation interface failure',
0x3A: 'Firmware failure',
# 0x3B to 0x40 are reserved
}
---------------------------------------------------------
---------------------------------------------------------
A "tape alert" message is a critical, warning, or informational alert that occurs due to a tape drive or robotic library hardware event. These "tape alert" messages are stored on the tape drive or robotic library. Applications like NetBackup query the tape device or robotic library for these "tape alert" messages and display the "tape alerts" to the user. "Tape alert" messages are reported in the NetBackup bptm log. The tape alert technology detects and logs hardware and media errors.
It is important to remember that while NetBackup displays these "tape alerts," the alerts occur due to a tape drive or robotic library hardware event. Check the Event Viewer for any hardware related errors. Please contact the Original Equipment Manufacturer (OEM) for support.
The "errors" file may also contain specific Tape Alert information:
TapeAlert is a standard for devices to report diagnostic messages to the controlling application. A "No TapeAlert Messages" response is a good thing. Here's the list of codes and definitions as it exists today.
(from the ANSI T10 Specifications):
tapealert_codes = {
0x01: 'Having problems reading (slowing down)',
0x02: 'Having problems writing (losing capacity)',
0x03: 'Uncorrectable read/write error',
0x04: 'Media Performance Degraded, Data Is At Risk',
0x05: 'Read Failure',
0x06: 'Write Failure',
0x07: 'Media has reached the end of its useful life',
0x08: 'Cartridge not data grade',
0x09: 'Cartridge write protected',
0x0A: 'Initiator is preventing media removal',
0x0B: 'Cleaning media found instead of data media',
0x0C: 'Cartridge contains data in an unsupported format',
0x0D: 'Recoverable mechanical cartridge failure (broken tape?)',
0x0E: 'Unrecoverable mechanical cartridge failure (broken tape?)',
0x0F: 'Failure of cartridge memory chip',
0x10: 'Forced eject of media',
0x11: 'Read only media loaded',
0x12: 'Tape directory corrupted on load',
0x13: 'Media nearing end of life',
0x14: 'Tape drive neads cleaning NOW',
0x15: 'Tape drive needs to be cleaned soon',
0x16: 'Cleaning cartridge used up',
0x17: 'Invalid cleaning cartidge used',
0x18: 'Retension requested',
0x19: 'Dual port interface failed',
0x1A: 'Cooling fan in drive has failed',
0x1B: 'Power supply failure in drive',
0x1C: 'Power consumption outside specified range',
0x1D: 'Preventative maintenance needed on drive',
0x1E: 'Hardware A: Tape drive has a problem not read/write related',
0x1F: 'Hardware B: Tape drive has a problem not read/write related',
0x20: 'Problem with SCSI interface between tape drive and initiator',
0x21: 'The current operation has failed. Eject and reload media',
0x22: 'Attempt to download new firmware failed',
0x23: 'Drive humidity outside operational range',
0x24: 'Drive temperature outside operational range',
0x25: 'Drive voltage outside operational range',
0x26: 'Failure of drive predicted soon',
0x27: 'Diagnostics required',
# 0x28 to 0x2E are obsolete, but some vendors still have them listed.
0x28: 'Loader Hardware A: Changer having problems communicating with tape drive',
0x29: 'Loader Stray Tape: Stray tape left in drive from prior error',
0x2A: 'Loader Hardware B: Autoloader mechanism has a fault',
0x2B: 'Loader Door: Loader door is open, please close it',
# 0x2F to 0x31 are reserved
0x32: 'Media statistics lost',
0x33: 'Tape directory invalid at unload (reread all to rebuild)',
0x34: 'Tape system area write failure',
0x35: 'Tape system area read failure',
0x36: 'Start of data not found',
0x37: 'Media could not be loaded/threaded',
0x38: 'Unrecoverable unload failed',
0x39: 'Automation interface failure',
0x3A: 'Firmware failure',
# 0x3B to 0x40 are reserved
}
---------------------------------------------------------
понедельник, 9 ноября 2015 г.
SPAM-ерское
из спама:
------------------------------
From: Administrator mail@faraero.ru
Subject: АСТ - подарок всем автомобилистам
Date: Mon, 9 Nov 2015 02:21:12 -0500
X-Mailer: PHPMailer 5.2.1 (http://code.google.com/a/apache-extras.org/p/phpmailer/)
Чего сам не испытаешь, того не поймешь!
Речь идет о смазочной композиции НАНОУГЛЕРОД, о здоровье двигателя Вашего автомобиля и об экономии Ваших денег!
Влей наноуглерод в бензобак любого двигателя (бензин, газ, дизель) и нажми на педаль газа, чтобы увидеть как мгновенно увеличится мощность, двигатель станет работать тише. Сначала кратковременно из глушителя пойдет белый дым - это наноуглерод очищает Ваши поршни, клапана и стенки цилиндра от нагара. Послу чего Вы тут же резко почуствуете что у Вас уже новый двигатель.
------------------------------
Белый дым верная примета, к новому двигателю =)
------------------------------
From: Administrator mail@faraero.ru
Subject: АСТ - подарок всем автомобилистам
Date: Mon, 9 Nov 2015 02:21:12 -0500
X-Mailer: PHPMailer 5.2.1 (http://code.google.com/a/apache-extras.org/p/phpmailer/)
Чего сам не испытаешь, того не поймешь!
Речь идет о смазочной композиции НАНОУГЛЕРОД, о здоровье двигателя Вашего автомобиля и об экономии Ваших денег!
Влей наноуглерод в бензобак любого двигателя (бензин, газ, дизель) и нажми на педаль газа, чтобы увидеть как мгновенно увеличится мощность, двигатель станет работать тише. Сначала кратковременно из глушителя пойдет белый дым - это наноуглерод очищает Ваши поршни, клапана и стенки цилиндра от нагара. Послу чего Вы тут же резко почуствуете что у Вас уже новый двигатель.
------------------------------
Белый дым верная примета, к новому двигателю =)
2008R2 DFSR
про глюки: http://habrahabr.ru/post/245075/
Q&A: https://technet.microsoft.com/ru-ru/library/cc773238%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
dfsrdiag: http://blogs.technet.com/b/filecab/archive/2009/05/28/dfsrdiag-exe-replicationstate-what-s-dfsr-up-to.aspx
ограничения (https://technet.microsoft.com/ru-ru/magazine/gg690154.aspx)
Каждый сервер может быть членом не более 256 репликационных групп.
В каждой репликационной группе может быть не более 256 реплицируемых папок.
У каждого сервера может быть не более 256 подключений (например, 128 входящих и столько же исходящих).
На каждом сервере произведение числа репликационных групп на число реплицируемых папок и на количество одновременно активных подключений не может превышать 1024.
В каждой репликационной группе может быть не более 256 членов.
На томе может размещаться не более 8 млн реплицируемых файлов, а на сервере может храниться не более 1 ТБ таких файлов.
Максимальный размер файла — 64 ГБ.
DFS-R не поддерживает связь с FRS.
Подписаться на:
Сообщения (Atom)