Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Filipp Sudanov

#1171
General Support / Re: nxdbmgr failes to repair
April 12, 2021, 12:27:45 PM
Can you have a look into log of Postgres DB. There should be a ERROR: line prior to the moment when
"current transaction is aborted, commands ignored until end of transaction block"
started to occur. This should give us some understanding of what's happened.
#1172
Hi!

Which exactly training materials, were they prepared by Raden Solutions or some third party?
I suppose disk_logger is some 3-rd party app that can send syslog messages. Not sure if it's giving any benefits over netxms agent when monitoring a system.
#1173
You need to create log parser definition in Configuration -> Syslog parser.

There could be several definitions, each is a filter that only reacts to particular conditions - syslog text, source, etc.
Each definition specifies an event that is triggered.
Then in Event Processing Policy you need to have a rules for these events. These rules can create alarms, terminate alarms, send notifications, etc.
#1174
General Support / Re: nxapush not working?
April 01, 2021, 02:40:22 AM
What's exactly netxms agent and server versions?
What kind of connection is between server and agent - is it normal or tunnel?
#1175
Если у этих коммутаторов порты называются как-то по разному, то можно в summary table в свойствах колонки включить использование регулярных выражений и написать регулярку с OR.

Второй путь, более универсальный - делать на этих нодах дополнительный скриптовый DCI. В его скрипте определять модель коммутатора, брать последнее значение DCI соответствующего нужному порту и сохранять. Если история по этому DCI нигде не требуется, то для него можно выбрать время хранения "не сохранять в базу".
Ну или тоже самое можно сделать другим путем - DCI может быть не скриптовым, а push. А скриптоваться в transformation script оригинальных DCI и оттуда делать PushDCIData(node,dciId,value). Но так, возможно, более путанно и чуть хуже по производительности.
#1176
Not sure how timeout could be set from nxshell side.

From server side:
- try checking number of connected sessions - show sessions in server console or using nxadm. Are there stuck sessions from previous nxshell connections?

- try checking with netstat if there are hanging sockets to port 4701


What is the version of netxms?
#1177
DebugLevel=6 в конфиг агента и его перезапустить.
Ну и LogFile=C:\NetXMS\log\nxagentd удобнее поставить вместо сислога, который по умолчанию.

(а на сервере можно на лету менять - команда debug в server console)
#1178
А что в логе агента при этом на 6 уровне дебага?
#1179
General Support / Re: nxapush not working?
March 30, 2021, 06:20:16 PM
DCI matching is performed by parameter, so the parameter of your DCI should be "LOCAL_TEST".

Try setting debug level for the agent and server to 6, in there anything in the logs when you execute nxapush?
#1180
Chances are that you are missing EnableWebServiceProxy=yes in config file of the agent (web services are collected via the agent that runs on the machine where the server runs, or via proxies if zoning is used).
Also make sure that "Use text parsing..." checkbox is not set.

You can use nxwsget utility to test, e.g.
nxwsget 127.0.0.1 http://api.open-notify.org/astros.json number

Ah, and there's probably the reason - json parser currently does not support arrays (the company that ordered web service functionality did not need this so it was not implemented).
This means that you can request e.g. /cellulareRssi/unit and it should return dBm, but parts in [] are not available for parsing.
#1181
Там сейчас как-то криво, на закладке Performace tab раскрывается вроде бы только {instance}, но раскрывается в то, во что обычно раскрывается {instance-name}

В 4.0 в этом планируется навести порядок.
#1182
Ага, ну нет, это не тот способ бороться с утечкой дескрипторов. Агент поставлен из пакетов, так? Попробуйте core dump файл собрать при креше.
#1183
This could be, if there's no nxagent-3.8.166-x64.exe file in the folder where nxagent-3.8.166-x64.npi resides.

The principle of operation is that console opens the .npi file and it had .exe file specified inside (.npi is simple test file, you can open it with any editor.

Only desktop console can upload packages using .npi file - in web we can not open arbitrary files from the computer where console is open - console would need this to open the .exe that is specified inside .npi.
There are plans for the future to change package format so that everything is packed into one file - in this case web console will also work.
#1184
General Support / Re: Data collection configuration
March 24, 2021, 08:07:48 PM
Do they have same settings in properties of these nodes -> Communications -> SNMP?

In View -> Object Details in Capabilities column is isSNMP flag in "Yes" state? If it's not, try running Configuration poll (full).

If no avail from the above, please share Object Details window screenshot and output of Configuration Poll.

#1185
Попробуйте версию 3.8.226, какие-то исправления на тему дескрипторов там были.

Если не поможет - что еще делает этот агент? Есть ли какие-нибудь external parameters?