NetXMS Support Forum

Hi,

all seems going well until this point:

2020.06.02 06:04:06.788 *D* [tunnel             ] 192.168.10.6: SSL_write error (bytes=-1 ssl_err=5 errno=2)

SSL error 5 means underlying socket error, which is strange because SSL negotiation seems to be completed successfully. Are you using server version 3.3.x as well? Can you check what was logged in server log during that attempt?

Best regards,
Victor

Hi,

currently no.

Best regards,
Victor

Do you have SYS_DCI_ACTIVE events in event log for that node?

Hi,

configuration looks good. Is hybrid authentication enabled? Also, could it be that password contains some characters that could be misinterpreted (like: ; # ' ")?

Best regards,
Victor

Hi,

server should generate event SYS_DCI_ACTIVE when DCI state changes from "unsupported" to "active". Make sure that you are processing this event in EPP and use correct key to terminate alarms generated with SYS_DCI_UNSUPPORTED.

Best regards,
Victor

Actually we already decided that we have to move from libvirt to direct interaction with VMWare API (as we already did for XEN) - it's just question of available time and resources.

Best regards,
Victor

Попробуйте поставить уровень дебага 9 для тэга ncd.telegram, создать канал, попробовать послать сообщение, и пришлите лог сервера.

Hi,

probably the only way is to create script table DCI. Inside script you can use executeSSHCommand method to get your output as lines and split them into table columns.

Best regards,
Victor

Hi,

on what OS and what agent version?

Best regards,
Victor

Yes, it looks like message is too big (or rather supplied buffer is too small). I've registered an issue in our bug tracker: https://track.radensolutions.com/issue/NX-1863

Best regards,
Victor

Hi,

agent configuration file looks correct. What is set as primary host name / primary IP address in proxy node settings? Could it be that firewall itself also responds to your NetXMS server via SNMP, possibly providing different set of interfaces? Please check what is displayed in overview and interfaces tab for proxy node. Ideally please post screenshots of those two tabs along with forced configuration poll output.

For agents inside client network you should use proxy node's IP address as master server address. It is good to specify ZoneUIN in proxy agent configuration but is not necessary for each agent inside zone.

Best regards,
Victor

Hi,

this is bug in the agent that should have been fixed in version 3.3.314. Try to upgrade agent to that version if not already done, and then delete agent's local database file (usually C:\Windows\system32\config\systemprofile\AppData\Local\nxagentd\nxagentd.db) and restart agent. It should re-create database with correct structure.

Best regards,
Victor

Hello,

what is GUI version and operating system?

Best regards,
Victor

Hi,

starting with 3.2 you can also define web service and use it for data collection. For example you can define web service named TestService with correct URL and authentication options and then create DCI with origin "web service". As parameter you should use service_name:path_to_element. For example, to access number_of_pending_tasks element:

TestService:/number_of_pending_tasks


Best regards,
Victor

Hi,

this is caused by lazy object sync introduced in 3.2 - interface objects are no longer synced on login, but only when you expand node or select interfaces tab. We will add appropriate on-demand synchronization for maps as well. In the meantime as a workaround you can try to turn on option "full object synchronization on startup" in console properties (File -> Properties -> Object Browser). This is client-side setting so should be done on each client.

Best regards,
Victor