NetXMS Support Forum

Hi!

This should be fixed already in 1.2.1. Can you try version 1.2.1?

Best regards,
Victor

Hi!

Yes, you are absolutely right. I fixed that in a trunk.

Best regards,
Victor

Hi!

1. Did you enable zoning support globally (by setting EnableZoning server configuration parameter to 1)?

2. Did you enable built-in syslog server? Also, if you are running NetXMS server on Linux, it's built in syslog server may conflict with system's syslog server by attempting to use same UDP port 514. Check server's log on startup for errors.

Best regards,
Victor

Hi!

You should not prefix action name with "Action:" in action configuration on server side, use just action name, VarnishReload in your case.

Best regards,
Victor

Hi!

Good catch, thanks for detailed debugging! I'll make a fix for that in a next few days.

Best regards,
Victor

Hi!

It's actually the same. pgsql.ddr is a new naming scheme, and libnxddr_pgsql.so is old one. In fact, /usr/local/lib/libnxddr_pgsql.so is just a symbolic link to /usr/local/lib/netxms/dbdrv/pgsql.ddr, so it doesn't matter what you specify as a driver.

Best regards,
Victor

You mean object icon for map? Unfortunately it's not possible, you can only manually assign it to object.

Best regards,
Victor

Hi!

Manual is a bit outdated unfortunately Please use this: http://wiki.netxms.org/wiki/Web_Interface_Installation_Guide

Best regards,
Victor

Hi!

You can make dashboard element to span multiple rows and/or columns. For example, if you have 3 graphs, and want one of them to be fill screen wide and others two to be half screen wide, yo set number of columns to 2, and horizontal span for first graph to 2. Then first graph will took entire top half of the dashboard, and two others will be shown in two columns in bottom part of the dashboard.

Best regards,
Victor

That's bad, because I found memory leak in SNMP code (fixed in 1.2.1) and was thinking that it was the cause for your problem too. I'll do more tests next week.

Best regards,
Victor

Hi!

I plan to release 1.2.2 before 21st of June, because after that date I'll leave for 3 weeks vacation. I plan that it will be mostly bug fix release, probably with small new features/enhancements. I'll try to implement new drivers before release date.

Best regards,
Victor

Hi!

Currently it's not possible. I'll add this as feature request.

Best regards,
Victor

Hi!

It's bug in a package. As a fix, you should manually run

update-rc.d nxagentd defaults 99 01

I'll fix this in next version.

Best regards,
Victor

Hi!

I confirm that this is a bug. I'll add it to be fixed in next release.

Best regards,
Victor

Логика работы такая: когда NetXMS находит/добавляет хост с адресом из субнета, которого еще нет, то создается новый объект субнета, и маска берется из конфигурации интерфейса нового хоста. В большинстве случаев это будет правильная маска. Все остальные хосты с интерфейсами из этого субнета проверяются на соответствие маске из уже существующего объекта субнета. Проблема возникает тогда, когда первым хостом в субнете является хост с неправильной маской, либо хост, с которого информацию получить нельзя - в этом втором случае NetXMS принимает маску равной 255.255.255.0 (/24), поскольку это один из самих распространенных вариантов. Если получилась неправильная конфигурация, то надо удалить неправильний объект субнета, и сделать конфигуратион полл хосту с правильной маской из этого субнета - тогда объект субнета будет создан заново с правильной маской.