NetXMS Support Forum

Quote from: Victor Kirhenshtein on May 05, 2020, 04:45:32 PM
yes, Ubuntu 20 packages will be available shortly.

Hi Victor,

any news about this package ?

Thanks & regards
Detlev

Quote from: Victor Kirhenshtein on June 02, 2020, 11:32:09 AM
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?

Hi,

yes, server is latest 3.3 version.

I ran same procedure again with debuglevel 7 on server. I have cut beginning and end of the log, but it still contains a lot of waste.

I think the most relevant line is at time 12:19:10.069   - handshake failed.

I have attached a zip file containing the server log.

Regards
Detlev

Quote from: Filipp Sudanov on June 01, 2020, 05:56:45 PM
Please try the most recent nxagent-3.3.330 version, adding EnableSSLTrace=yes to agent configuration file and setting DebugLevel=7. Please share agent log for the time when the situation occurs.

Hi Filipp,

I have updated the agent as requested and started a clean attempt. Same result as before.

Please find attached agent log

Regards
Detlev

Quote from: Victor Kirhenshtein on May 25, 2020, 09:52:57 AM

What agent versions you are using, and on what platform? We've seen such issue with Windows agents and it was solved by rebuilding agent with newer OpenSSL.

Hi Victor,

I tried the 3.3.314 windows x64 agent on both Win7-x64 and server2019-x64

Regards
Detlev

Thanks for your reply...

Quote from: tfines on May 20, 2020, 10:42:10 PM
Please post your agent config file.

ServerConnection = 192.168.10.6
ConfigIncludeDir = C:\NetXMS\etc\nxagentd.conf.d
LogFile = {syslog}
FileStore = C:\NetXMS\var
SubAgent = filemgr.nsm
SubAgent = ping.nsm
SubAgent = logwatch.nsm
SubAgent = wmi.nsm
DebugLevel = 6
LogFile = c:\netxms\log\agent.log

QuoteWhat setting did you select on the server for how it handles new nodes?

New nodes need to be added manually. I have tried with manually added node and bind as well as with "create node and bind". AgentTunnel.NewNodesContainer is left empty. The node appears in the root folder.

Best...
Detlev

Hello,

I'm trying to setup a tunnel between agent and the NetXMS-server. Unfortunately without success.

Both, server and agent, are latest version at the time of writing and are running on Window. Server's IP is 192.168.10.6, the agent is at .10.70

Server is running on Win Server 2016, I have tried agent side on Win7x64 (physical machine) and server 2019 (VWware virtual machine)

Here's what I did:

- created a key (rsa 2048) and a CSR (including SAN) on a linux machine using standard open-ssl
- created a server cert using the CSR (on our windows domain ca)
- copied the root cert, the server cert and the server key to the netxms server
- edited the server's .conf to add the file pathes for key, cert and ca

after starting the test agent's log reports:

*D* [tunnel             ] Tunnel manager started
*D* [tunnel             ] 192.168.10.6: Cannot open file "C:\Windows\system32\config\systemprofile\AppData\Local\nxagentd\certificates\897A0B2402C28AD5A07199D8CDD5A37FD445FF87.crt" (No such file or directory)
*D* [tunnel             ] 192.168.10.6: Cannot open file "C:\Windows\system32\config\systemprofile\AppData\Local\nxagentd\certificates\0602060AA8C0000000000000000000000000.crt" (No such file or directory)
*D* [tunnel             ] 192.168.10.6: Server certificate subject is /C=DE/ST=NW/.....
*D* [tunnel             ] 192.168.10.6: Server certificate issuer is /DC=de/DC=.....
...
*I* [                   ] Tunnel with 192.168.10.6 established

The two "cannot open file" lines should be ok as there are no certs yet. The server's certificate subject and issuer are ok.

Checking the tunnel using the management console I see the tunnel as unbound.

I think that everything is fine until here.

Now I tried to create a node and bind the tunnel using the management console.

A key and a cert are created and copied to the agent computer, the files appear in c:\windows\system32\config....

the agent's log:

*D* [tunnel             ] 192.168.10.6: Resetting tunnel
*D* [tunnel             ] 192.168.10.6: Certificate and private key loaded
*D* [tunnel             ] 192.168.10.6: Server certificate subject is /C=DE/ST=NW/.....
*D* [tunnel             ] 192.168.10.6: Server certificate issuer is /DC=de/DC=.....
...
*D* [tunnel             ] 192.168.10.6: Receiver thread stopped (MSGRECV_COMM_FAILURE)
...
*W* [                   ] Tunnel with 192.168.10.6 closed
...
*D* [tunnel             ] 192.168.10.6: Cannot configure tunnel (request timeout)

The unbound tunnel disappears from the mangement console, but there's no bound one now.

The server's log reports:

*D* [                   ] SocketListener/AgentTunnels: Incoming connection from 192.168.10.70
*D* [                   ] SocketListener/AgentTunnels: Connection from 192.168.10.70 accepted
*D* [agent.tunnel       ] SetupTunnel(192.168.10.70): TLS handshake failed (error:00000001:lib(0):func(0):reason(1))

Whatever I have tried - same results.

Anyone out here, who have an idea what I'm missing or doing wrong?

Thanks in advance for any help!

Regards
Detlev

Hi Victor,

thanks for the upgrade 

Do you have any plan to create Ubuntu 20.04 Focal Fossa packages? An "apt-get update" currently ends up in a HTTP 404 response....

Regards
Detlev

Quote from: Victor Kirhenshtein on August 15, 2017, 03:02:41 PM
do you have any messages in server log with prefix XMPPMessageSender?

No, there's nothing like that in the server's log file. Just the hint "*action* Sending XMPP" as show in the original posting and there's the big silence.

Regards
Detlev

Hi,

I'm new to NetXMS and I'm trying to set up XMPP alerts, but - until now - without success.

What I did:

- set up a xmpp server named jabber.***.net on a vps (ejabberd)
- created two users on ejabberd : dj (admin) + srv (server)

- created an action named "xmpp test action" to send messages to user dj@jabber.***.net
- created a new event processing policy with number 1 to trigger the "xmpp test action" on any event from a specific node

After setting the DebugLevel to 6 I can see that the event processing and the action are triggered:

[12-Aug-2017 08:36:59.207] [DEBUG] *actions* Executing action 1 (XMPP Test Action) of type XMPP MESSAGE
[12-Aug-2017 08:36:59.207] [DEBUG] *actions* Sending XMPP message to dj@jabber.***.net: "NetXMS Test Message 0"

but the message is never sent. There is no more info in the netxms log. My ejabberd server's log is also not showing any attempt to deliver the message.

Netxms is properly connected to the ejabberd - I can send remote commands from a phone client and also receive the answer from netxms on the phone:

[12-Aug-2017 08:39:02.106] [DEBUG] XMPP: RECV: <message type="chat" lang="en" to="srv@jabber.***.net" from="dj@jabber.***.net/phone"><composing xmlns="http://jabber.org/protocol/chatstates"/><no-store xmlns="urn:xmpp:hints"/><no-storage xmlns="urn:xmpp:hints"/></message>
[12-Aug-2017 08:39:12.152] [DEBUG] XMPP: RECV: <message id="7fbc6fab-43ab-4ca7-b456-247347819f73" type="chat" lang="en" to="srv@jabber.***.net" from="dj@jabber.***.net/phone"><body>Show queues</body><markable xmlns="urn:xmpp:chat-markers:0"/><request xmlns="urn:xmpp:receipts"/><origin-id id="7fbc6fab-43ab-4ca7-b456-247347819f73" xmlns="urn:xmpp:sid:0"/><active xmlns="http://jabber.org/protocol/chatstates"/></message>
[12-Aug-2017 08:39:12.152] [DEBUG] XMPP: Incoming message from dj@jabber.***.net/phone: Show queues
[12-Aug-2017 08:39:12.152] [DEBUG] User admin authenticated for XMPP commands
[12-Aug-2017 08:39:12.152] [DEBUG] XMPP: SENT: <message to="dj@jabber.***.net/phone" type="chat"><body>Data collector : 0

This happened on netxms 2.0.8 and also after upgrading to 2.1. The server is running on Windows Server 2016.

I have no idea what's going on.

Any help highly appreciated Thanks in advance !

Best...
Detlev