NetXMS Support Forum

openldap/ldap already done, as being present in the current release?

ah, thanks marco!

Thanks for the reply.

Seems it doesn't work that way for me. See the attached photos. Perhaps I've configured the checks incorrectly? What's confusing is that graphs rendered on the mobile client show up correctly.

I've noticed in the last couple of releases that the check I have for disk space percentage shows up as "0". However, If I generate graphs the real values are plotted correctly. Is it just me or is it occurring for others as well?

Yes, you're correct. Sorry about the confusion. Looking forward to your new release. Cheers.

Since this version has segmentation faults which could be devastating for mission critical environments - perhaps it's not a good idea to let 1.2.12 be available for download..

Don't understand any of this, but I have also had segmentation fault with the latest release.

Current workaround is an ugly hourly check.


#!/bin/bash
ps cax | grep netxmsd > /dev/null
if [ $? -eq 0 ]; then
  echo "Process is running." >> /var/log/netxms
else
  echo "Process is not running. Attempting restart" >> /var/log/netxms
  /etc/init.d/netxmsd start
fi

the config file is not included in the package. read the manual and learn to install a database and create the config file.

Posted this in general, but it might be more suitable in this thread as it did not occur on the previous version of netxms.

I've had netxms die on me two times. Not much in logs except this;

Apr  4 09:52:07 netxms kernel: [6647577.566437] netxmsd[29596]: segfault at 0 ip 00007f2a203a8f96 sp 00007f2a152bc9e0 error 4 in libnetxms.so.1.0.0[7f2a20382000+39000]

After upgrading to the latest version of netxms, I've experienced two cases of the netxms-server process dying.

The only error is found in /var/log/messages;

Apr  4 09:52:07 netxms kernel: [6647577.566437] netxmsd[29596]: segfault at 0 ip 00007f2a203a8f96 sp 00007f2a152bc9e0 error 4 in libnetxms.so.1.0.0[7f2a20382000+39000]

Please advice. I'll throw in a cron ps-check in the meanwhile.

Victor, thanks for fixing the debian package.

Jeff, my guess is that the issue is _not_ netxms related, but in fact postgresql related. I'd downgrade postgresql instead of running bleeding edge. I'm running the latest netxms release on postgresql 9.1 and having no issues.

I believe I already tried what you suggested, but I'll give it another go.

Thanks for the feedback.

sounds good. Thanks!

We have a few hosts that are not capable of running netxms agents. VMware ESX for instance.

Is there a simple way of utilizing a netxms agent on a remote host that does cli checks on the ESX hosts, and tie these values to the ESX host in netxms?

Currently I have the ESX values stored on the host that is running the netxms-agent, along with its own checks. Not a pretty sight. I tried the proxy functionality but I guess that's just for relaying agent traffic.

Seems like <<ERROR>> values are not raised by netxms. Not out of the box anyway.

I'd like to get some sort of warning when checks fail. Any tips would be greatly appreciated.