NetXMS Support Forum

My guess is that DB is shutting down before the core process and netxmsd waits for connection to write cached information.

Add "After=" section to your unit override.

There are comments by systemctl:

### Editing /etc/systemd/system/netxms-server.service.d/override.conf
### Anything between here and the comment below will become the new contents of the file

...

### Lines below this comment will be discarded


Your changes were just ignored.

Proper override should be something like this:

### Anything between here and the comment below will become the new contents of the file


[Unit]
After=network.target postgresql.service
TimeoutSec=900
... more overrides

### Lines below this comment will be discarded



But I want to point out that TimeoutSec=900 is default value in the unit file (check /lib/systemd/system/netxms-server.service)

Quote from: kronicklez on February 18, 2025, 03:57:32 AMHi,

May i know where is path location this  "netxmsd.service" this file?

I'm using ubuntu 22 server.

Thanks and appreciate your feedback

you can add override by running "systemctl edit netxms-server". It's not recommended to modify unit file directly - it might be overwritten by the upgrade.

It's a leftover from really old times. We probably need to remove this option.

Web load configuration in the following order (e.g. "server" parameter, same for others):
1) from JNDI, java:comp/env/nxmc/server
2) "server" from the property file /nxmc.properties (from resources)
3) JVM property "nxmc.server" (e.g. you can run "java -Dnxmc.server=1.2.3.4")
4) environment variable NXMC_SERVER
5) then, if not found, and only for the server - try to look up the hostname "NETXMS_SERVER"

А какая версия убунту? Возможно мы под нее просто не выкладываем уже пакеты.

Second one is correct. See screenshot.

I'd check that search base is wide enough.

(&(|(objectClass=user)(objectClass=group))(department=Department1))

you can even use wildcards there:

(&(|(objectClass=user)(objectClass=group))(department=Department*))


I usually filter by the base group, but you need to use ActiveDirectory(?) extensions to do it recursively, something like this:

(&(|(objectClass=user)(objectClass=group))(memberOf:1.2.840.113556.1.4.1941:=CN=...))


Quote from: yordi on January 09, 2025, 05:46:47 PMHello,

Thanks Alex, i will (try) update to the latest Debian.
This server was wayback installed as a project for a internship, Linux is not my main server environment.

i Suppose this will not be a problem for Netxms to upgrade when i have Debian 12 installed ?

Thanks for your help !

greetings,
Yordi

Yes, there are packages for both Debian 11 and 12 in the repo.

All of the features are enabled on most systems. Some of them are packaged into separate packages (e.g. reporting) or mqtt.
There are some exceptions, you can check them in the version-specific configs: https://github.com/netxms/packages-deb/tree/stable-5.1/config

Quote from: yordi on January 09, 2025, 03:45:14 PMHello,

As a very longtime Netxms user (for our education) i am stuck at 5.0.8 (linux debian install)
if i do apt-get update it will not find the 5.1.2 version, there are no updates..

is this still the correct deb repository : https://packages.netxms.org/debian buster InRelease ?
it was added with the "wget https://packages.netxms.org/netxms-release-latest.deb" command.

I hope that PJlink (control and monitory all our projectors at school) is maybe a new feature :

thanks,
Yordi

Hello

Debian 10 LTS is ended on 30th June, 2024 (https://www.debian.org/releases/buster/).
We provide public builds only for systems which are currently in support (Debian 11 - 12, Ubuntu 20-24, etc.).

If you need binaries for Debian 10, please contact us at [email protected].

In terminal:

java -XstartOnFirstThread -jar nxmc-5.1.1-standalone.jar
I'm working on proper .app launcher, plan to release in next couple of days.

If it's intel-based, then you can use standard repositories. 
If it's arm - we currently do not provide deb packages for arm, but this will change in the near future 

Normally you setup self-monitoring (free space, required processes) and notifications and that's it. Even when backend is down (there is even an internal event for that), NetXMS keep collecting metrics and process thresholds - so notifications will be sent anyway. Once backend is recovered - queued data is written back to the database. But yes, login will fail.

Quote from: Shaun_Swale on December 06, 2024, 12:15:15 PMUbuntu 24.04.1

Currently unable to login with any account as [email protected] has now decided to die.  Think I might just try a different monitoring solution.

To be honest, I'm not sure that other monitoring solution will work fine when backend database is dead.