NetXMS Support Forum

Mozno prosto kak foreground process - ostanovit' servis, i zapustit'

nxagentd.exe -D 9 -c <config_file>

Chtobi zapustit' servis v debug rezime, nado v registry pomenjat' command line servisa.

Nu i zelatel'no, chtobi v kachestve loga ispol'zovalsja tekstovij fail, a ne event log.

Hi!

Looks like memory leak in netxmsd. Can you please add to monitoring memory used by netxmsd process and send me how it changes over time?

Best regards,
Victor

Hi!

Is it possible that there are low memory condition on NetXMS server? From crash dump it looks like some internal memory allocation fails.

Best regards,
Victor

Pohoze chto problema s kodirovkoj servera ili bazi. Kakoj stoit code page dlja non-UNICODE program na servere, gde rabotaet NetXMS server? I kakaja vibrana kodirovka dlja bazi NetXMS?

Ochen' pohoze na nedavno obsuzdavshujusja problemu s parserom logov na Novell NetWare. Vozmozno agent schitaet chto proizoshla rotacija loga, i perechitivaet fail s nachala. A vi mogli bi zapustit' agenta v debug rezime?

A problema s postojannimi soobschenijami "LogParser: file size differs for stat(7) and fstat(SYS:\ETC\LOGs\CONSOLE.LOG), assume file rename" toze tol'ko na 5.1?

Quote from: Dillinger on June 08, 2011, 10:05:28 AM
Если смотреть на этот файл с Windows-компьютера проводником, то он имеет нулевую длину - может в этом причина ошибки?

Eto vozmozno. AGent sravnivaet dlinnu otkritogo faila s tem, chto soobschaet OS, i esli OS soobschaet men'shuju dlinnu, schitaet chto proizoshla rotacija i nado fail otkrivat' zanogo. Ja podumaje chto zdes' mozno sdelat'.

Hi!

You can try to create custom tool for 1.3.6.1.2.1.4.22.1.2. I'm not sure that all devices supports IP-MIB, so changing default tool to it may not be a good idea. Probably another standard tool based on IP-MIB should be added.

Best regards,
Victor

Hi!

Failed SQL queries suggests that there are something wrong with DB connection, but I don't really sure that it's related. Crash dump will be very helpful.

Best regards,
Victor

Oni poka ne ochen' rabotajut. Chto-to posmotret' mozno, nado sdelat' novij query cherez menu i vipolnit' ego.

Hi!

It's not possible to use fractions for minute specification. I'll add this as feature request.

Best regards,
Victor

U menja k sozaleniju est' tol'ko 6.5, poetomu na 5.1 vozmozni esche kakie-to problemi. Versija iz attacha rabotaet na 6.5. s vashim configom, strochki so slovom Error: detektjatsja. Btw, v konfige parsera netochnost' - ukazano param="1", no net capture gruppi. Pravil'nej bi bilo kak-to tak:

<parser>
   <file>SYS:\SYSTEM\PVSW.LOG</file>
   <rules>
   <rule>
      <match>Error: (.*)</match>
      <event params="1">100017</event>
   </rule>
   </rules>
</parser>

U menja sejchas net pod rukoj NetWare servera dlja testov. Vecherom posmotrju. A kakaja versija NetWare ispol'zuetsja?

Zdes' oshibka v konfige - parser dolzen ukazivatsja v sekcii LogWatch:


MasterServers = 10.1.1.4
LogFile = SYS:/NETXMS/nxagent.log
FileStore = SYS:/NETXMS/TMP/
SubAgent = logwatch.nsm

*LogWatch
Parser = SYS:/NETXMS/pvsw.xml


Hi!

You should give disk names with colons, like this:

FileSystem.UsedPerc(C:)

Most likely this is the cause.

Best regards,
Victor