NetXMS Support Forum

Hi,

could you please provide desktop client log (usually in <home directory>/.nxmc/data/.metadata/.log) and server log file with debug level set to 6 for tags client.* and userdb?

Best regards,
Victor

Quote from: andrey_D on November 29, 2020, 10:12:22 AM
Подскажите пожалуйста
Есть графический линк между оборудованием и необходимо что бы на линке было значение из таблицы как это сделать?

Табличные данные на карте не поддерживаются сейчас. Странно что он дает выбрать таблицу в списке. Сейчас единственный вариант - сделать скриптовый DCI, который будет доставать нужную ячейку из таблицы, и его уже добавлять на карту.

Quote from: andrey_D on November 29, 2020, 10:12:22 AM
Как добавить к значению единицу измерения к примеру выбираю источник скорость передачи данных, на линке появляется значение 100, как добавить мбит/с?

В свойствах источника есть строка форматированию, это стандартный Java формат с одним дополнением - можно использовать %*s для автоматической подстановки мультипликаторов. Если надо просто поставить суффикс мбит/с, то строка формата может быть

%s мбит/с


А если значение всегда в битах, и надо автоматически подставлять к, м, и т.д., то строка будет

%*sбит/с


Попробуйте поставить уровень дебага 6 для тэгов client.* и userdb и пришлите лог сервера после неуспешного подклчения. Еще может помочь лог клиента (обычно в <user home>/.nxmc/data/.metadata/.log).

Quote from: Staj on November 26, 2020, 12:55:42 PM
Can you explain how https://github.com/openssl/openssl/issues/12859 affects nxagentd and the downgrade to TLS 1.1?

If certificate has exportable private key then agent will get the private key and use standard OpenSSL mechanisms instead of CNG engine for session authentication. In that case TLS 1.3 will be used if server supports it. If private key cannot be exported then agent will switch to TLS 1.1 and use CNG engine for authentication.

Quote from: Staj on November 26, 2020, 12:55:42 PM
Looking at the code, it will find a Certificate in the SYSTEM Personal Certificate based on matching Friendly Name, Email, Subject, Template, Common Name, Org or Device Serial (in that order)? How does one specify what the agent should consider a match?

EDIT:
Tunnel::createFromConfig and ParseTunnelList seems to have the answer:

QuoteRecord format is address[:port][,certificate[,password]]

Records meaning the configured MasterServers, ControlServers and Servers. So I guess an example would be:

Code Select Expand

MasterServers = 10.0.0.1,ADCSTemplNetXMS
Assuming ADCSTemplNetXMS was the name of a Certificate Template (Eg: Certificate issued by ADCS)?

Not exactly. Tunnel connections configured using ServerConnection parameters, so it will be


ServerConnection = 10.0.0.1, certificate_matching_string


Certificate matching string consists of selector and value separated by :. Possible selectors are:
name - certificate's friendly name (display name) in store
email - EMail portion of certificate DN
subject - certificate's subject
template - template OID (not template name!)
cn - CN part of certificate's DN
org - ORG part of certificate's DN
deviceSerial - device serial number

so for example for certificate with friendly name "NetXMS Server" it will be

ServerConnection = 10.0.0.1, name:NetXMS Server


If you are interested, relevant code is in file src/agent/core/cng_engine.cpp, function MatchWindowsStoreCertificate.

Best regards,
Victor

Hi,

automatic maps only include nodes, you can only build custom map with containers manually.

Best regards,
Victor

Seems that you have too old management console (server uses newer protocol version). You have to upgrade it to version 3.6.

Best regards,
Victor

Hi all!

We just published another patch for the server (version 3.6.264) - it fixes regression in handling agent connections through proxy. If you are not using agent proxy functionality you may stay on 3.6.262.

Best regards,
Victor

This issue should be fixed by server 3.6.264. Source and Windows packages already updated, deb packages are building right now and should be in repository in few hours.

Best regards,
Victor

I was able to reproduce this issue. We are working on fix now.

Best regards,
Victor

А у вас устройство точно ждет SHA512 а не SHA1? Это не самый распространенный вариант аутентификации.

А какую ошибку дает клиент? На какой ОС установлен сервер?

Hi,

looks like you just need to run DB upgrade:

nxdbmgr upgrade

Best regards,
Victor

Sorry, read to fast - didn't notice that it is about proxy agent. Can you show logs from both proxy and target agents for period during connection setup?
Also, did you try to downgrade proxy agent?

Best regards,
Victor

We just found and fixed critical bug in server communication code, all users currently running server version 3.6.252 are encouraged to upgrade to 3.6.262 as soon as possible.

Best regards,
Victor

Hi all!

We just found and fixed critical bug in server communication code. It is fixed in version 3.6.262. All users currently running server 3.6.252 are encouraged to upgrade as soon as possible. Only server part should be upgraded, there are no changes in agents and UI.

Best regards,
Victor