NetXMS Support Forum

Aga, a mi parsim (v osnovnom dlja togo chtobi svjazat' s ob'ektom node), bol'she intellekta - bol'she problem Zaregistriroval v bugtracker'e kak issue #199, budu ispravljat'.

Citata iz RFC3164 (The BSD syslog Protocol), napisana chelovekom iz Cisco:

Quote
The HEADER contains two fields called the TIMESTAMP and the HOSTNAME.
   The TIMESTAMP will immediately follow the trailing ">" from the PRI
   part and single space characters MUST follow each of the TIMESTAMP
   and HOSTNAME fields.  HOSTNAME will contain the hostname, as it knows
   itself.  If it does not have a hostname, then it will contain its own
   IP address.  If a device has multiple IP addresses, it has usually
   been seen to use the IP address from which the message is
   transmitted.  An alternative to this behavior has also been seen.  In
   that case, a device may be configured to send all messages using a
   single source IP address regardless of the interface from which the
   message is sent.  This will provide a single consistent HOSTNAME for
   all messages sent from a device.

   The TIMESTAMP field is the local time and is in the format of "Mmm dd
   hh:mm:ss" (without the quote marks) where:

         Mmm is the English language abbreviation for the month of the
         year with the first character in uppercase and the other two
         characters in lowercase.  The following are the only acceptable
         values:

         Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec

         dd is the day of the month.  If the day of the month is less
         than 10, then it MUST be represented as a space and then the
         number.  For example, the 7th day of August would be
         represented as "Aug  7", with two spaces between the "g" and
         the "7".

         hh:mm:ss is the local time.  The hour (hh) is represented in a
         24-hour format.  Valid entries are between 00 and 23,
         inclusive.  The minute (mm) and second (ss) entries are between
         00 and 59 inclusive.

   A single space character MUST follow the TIMESTAMP field.

Ni slova pro vozmoznost' takogo formata.

Esli po setke soobschenija prihodjat tochno takie-ze, to pohoze ponjatno. NetXMS server ne rasschitivaet poluchit' timestamp v vide hh:mm:ss.xxx, shitaet chto timestamp plohoj i otbrasivaet soobschenie. A eto standartnij variant kstati? Ja vrode po RFC delal parsing... No v ljubom sluchae dobavlju obrabotku takogo varianta timestamp'a.

Ponjal. NAdo zamenit' faili v src/agent/subagents/sunos na prilozennie - vse dolzno zarabotat'. U menja Solarisa sejchas net pod rukoj, tak chto ispravil chisto teoreticheski - esli ne skompiliruetsja, budem ispravljat' dal'she.

Poka nel'zja. No misl' horoshaja, objazatel'no sdelaju.

A v logah servera nichego net pro oshibki pri starte (naprimer chto ne udalos' sdelat' bind na port 514)? I esche - mozno li prislat' neskol'ko obrazcov soobschenij - esli server ih prinimaet to edinstvennaja prichina po kotoroj oni mogut ne pojavljatsja v loge eto oshibka pri parsinge.

Sudja po logu, configure otrabotal normal'no. A gde vse lomaetsja? Esche odin obschij sovet, inogda pomogaet na komercheskih UNIX'ah - poprobovat' sobrat' s --disable-iconv.

Znachit netxms_ip ne propisan v parametre Servers. Nado ego tam propisat' (zelatel'no kak MasterServers).

Esli ExternalParameter opredelen kak SipOrig(*), to v Parameter nado pisat'

SipOrig(192.168.100.22)

Ostal'noe vrode vse pravil'no. Dolzen rabotat.
Mozno eshe zapustit' agenta s kljuchom -D i posmotret' na kakoj parametr prihodjat zaprosi.

Vilozil promezutochnij reliz 0.2.20-dev2 na https://www.netxms.org/download/rc/ . Nado delat' upgrade i serveru, i consoli. VNIMANIE: esli posle upgrade'a redaktirovat' DCI konsol'ju ot versii 0.2.19, to nastroiki "proxy node" budut sbrosheni v znachenie po umolchaniju.

Uze pochti pojavilas' Ja sdelal novij attribut u DCI - "proxy node" - t.e. DCI konfiguritsja na odnoj node a znachenie real'no sprashivaetsja u nodi vistavlennoj kak proxy. Protestiruju i vilozu promezutochnij reliz - mozno budet probovat'.

Quote from: drew on October 15, 2007, 12:37:50 PM

Рассылка по нескольким e-mail адресам, разделённым ";" или пробелом. Можно, конечно, сделать несколько экшенов, как я сейчас и делаю, но была бы фича полезна.

Sdelal, v CVS versii uze est'. Adresa nado razdeljat' ";". Toze samoe rabotaet i v rassilke SMS-ov. Esli ochen' hochetsja etu funkcional'nost' v tekushej versii, to mozno zamenit' fail src/server/core/actions.cpp na tot kotorij v attache i peresobrat' server.

T.e. nuzno chtobi script ispolnjalsja na hoste A no znachenie shlo v DCI dlja hosta B? Esli tak, to normal'nogo reshenija poka net. Edinstvenno chto mogu predlozit' - eto ispol'zovat' push DCI i ne vizivat' script s servera, a zapuskat' ego po cron'u i ispol'zovat' nxpush dlja peredachi novogo znachenija DCI na server monitoringa.

I'll try to setup Microsoft SQL Server 2005 Express Edition to chek it myself. Please wait till Monday's evening.

Best regards,
Victor

Standartnimi sredstvami NetXMS poka nel'zja. Odnako mozno delat' selecti prjamo iz bazi na usnovje polja platform_name i/ili snmp_oid v tablice nodes.