NetXMS Support Forum

Quote from: nichky on August 05, 2025, 02:07:09 PMhave you spotted anything?

Sorry, I can't help you any further.

Your log literally says that connection with PostgreSQL server can't be established on localhost, port 5432 (default).

2025.08.05 15:09:23.447 *I* [logger            ] Log file opened (rotation policy 2, max size 16777216)
2025.08.05 15:09:23.447 *I* [startup            ] Starting NetXMS server version 5.2.4 build tag 5.2-396-gbe46bc94fe
2025.08.05 15:09:23.452 *I* [startup            ] System time zone is AUS+10AUSEDT
2025.08.05 15:09:23.452 *I* [logger            ] Debug level set to 3
2025.08.05 15:09:23.454 *I* [config            ] Main configuration file: C:\NetXMS\etc\netxmsd.conf
2025.08.05 15:09:23.454 *I* [config            ] Configuration tree:
2025.08.05 15:09:23.454 *I* [config            ] config
2025.08.05 15:09:23.455 *I* [config            ]  +- server
2025.08.05 15:09:23.455 *I* [config            ]      +- DBDriver
2025.08.05 15:09:23.455 *I* [config            ]      |    value: pgsql.ddr
2025.08.05 15:09:23.455 *I* [config            ]      +- DBServer
2025.08.05 15:09:23.456 *I* [config            ]      |    value: 127.0.0.1
2025.08.05 15:09:23.456 *I* [config            ]      +- LogFile
2025.08.05 15:09:23.456 *I* [config            ]          value: C:\NetXMS\log\netxmsd.log
2025.08.05 15:09:23.457 *D* [startup            ] LIB directory set to C:\NetXMS\lib
2025.08.05 15:09:23.458 *I* [startup            ] System hardware ID 7769846E7CDDD8444067E3FFB9220D396182B9A6
2025.08.05 15:09:23.465 *I* [db.drv            ] Database driver "pgsql.ddr" loaded and initialized successfully
2025.08.05 15:09:23.469 *D* [comm.listener      ] SocketListener/LocalAdmin: Trying to bind on 127.0.0.1:21784/tcp
2025.08.05 15:09:23.469 *D* [comm.listener      ] SocketListener/LocalAdmin: Trying to bind on [::1]:21784/tcp
2025.08.05 15:09:23.470 *I* [comm.listener      ] SocketListener/LocalAdmin: listening on 127.0.0.1:21784
2025.08.05 15:09:23.470 *I* [comm.listener      ] SocketListener/LocalAdmin: listening on [127.0.0.1]:21784
2025.08.05 15:09:23.470 *D* [localadmin        ] Local administration interface listener initialized
2025.08.05 15:10:00.783 *E* [db                ] Unable to establish connection with database (could not connect to server: Connection refused (0x0000274D/10061)
 Is the server running on host "127.0.0.1" and accepting
 TCP/IP connections on port 5432?)


please read logs you've shared.

SSH - you are mixing up ssh monitoring (when port from node properties is used) and object tools. Pre-configured object tool for SSH open default ssh client without specifying port. Tools are configurable in Settings -> Object Tools.

rest of the issues is not a bug report, we can't help you with this input, without proper details. I've already recommended you to read documentation, it's all covered there in details.
Regarding core "crash" - you need to configure logging to the file, and check why it's stopped and not starting.

System is working fine for years for our customers, in different environments, and with wire range of versions (oldest is still 3.9, if I remember correctly). But if you'll find condition which actually crash core or agents - please share minidump and logs, we'll look into it.

Yes, you can either request another admin user to reset it for you, or unlock and login as system.

But regarding TOTP - check server's time, maybe NTP stopped working and there is a drift.

As I mentioned before - set log file location to a file and check why it's not staring. Or run "netxmsd -D3" from the command line to keep it in the foreground, in debug mode. Reinstall is never a solution.

Check core logs. If required, increase debug level.

https://netxms.org/documentation/adminguide/appendix.html#server-configuration-file-netxmsd-conf

Quote from: nichky on August 01, 2025, 03:34:09 PMAlex - let we make it easy

from here:

https://netxms.com/downloads

what i need to install,  in order to be able to login by using the container?

YOU CAN'T LOGIN INTO CONTAINER.

Container does not contain neither server components, nor web.

Please read this: https://netxms.org/documentation/adminguide/concepts.html

Quote from: nichky on August 01, 2025, 03:26:06 PMyes the one that i'm using is
/netxms-agent-mikrotik , so i need to install WebUI and acces :expose :8080/:8443.

are we on the same page?

you need to install server + web somewhere.
then you can add mikrotok to the system and collect data over SNMP.
agnet on the mikrotik is required only if you want to install it on the customer's firewall, for example (so you can get access to the NATed network)

Quote from: nichky on August 01, 2025, 03:06:27 PMThansk Alex

so this is i'm expecting.
Since the container is running i should be able to log in to netxms (similar to how i'm doing on windows) via web using ip:8080 , ip:4700 or ip:4701

You are mixing up monitoring server, web, and agent.

Monitoring server (netxmsd, "NetXMS Core" service) listens on port 4701, you connect there using desktop client.
Server do all the scheduling, data collection, and processing. Collection can be done via multiple procorols - SNMP, native agent, SSH, etc.

WebUI - expose :8080/:8443, you connect there with the browser. WebUI transparently connects to the monitoring server.

Agents listen on port 4700 (they can go in reverse as well). Server connects to the agents to collect data / perform tasks.



So no, you do not connect to the agent with the browser. You could register it in the monitoring instead, and configure metrics you want to monitor.

what do you mean "can't login"? it's an agent, not a server.

Quote from: nichky on August 01, 2025, 01:09:40 PMpls, how to fix the the accessing to ssh from NetXMS?

check that:
1) you saved and applied properties before test
2) you are running latest version of the system.

I've just checked, and custom port works just fine.

Quote from: nichky on August 01, 2025, 08:46:24 AMbut we have options that we can run netxms on MikroTik container?

yes, you can run agent on the mikrotiks. normally, it's enough to collect information via SNMP. Agent is mostly used for running zone proxies (e.g. with network behind NATs). Full instructions are on the GitHub page.

Quote from: nichky on August 01, 2025, 12:52:40 AMthis is what im gettign

C:\NetXMS\bin>nxsnmpwalk IP 1.3.6.1.2.1.2.2.1.2
Unable to create UDP transport: Invalid hostname or IP address

Replace "IP" with actual IP of the router in question.

That's the whole command. Replace "IP" with actual IP of the router in question.

C:\NetXMS\bin\nxsnmpwalk IP 1.3.6.1.2.1.2.2.1.2


.1.3.6.1.2.1.2 is a base OID for IF-MIB.

something like "nxsnmpwalk IP 1.3.6.1.2.1.2.2.1.2" should fetch list of interfaces.