Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

I have a large class of devices (perhaps mostly Cisco?) that are failing discovery in an odd way.

1) Devices are detected with isSNMP=Yes, GENERIC driver, and added to db
2) Manual inspection shows that devices were added with SNMP 'public' community
3) Devices respond to a snmpwalk using 'public' with the following:
iso.3.6.1.2.1 = No more variables left in this MIB View (It is past the end of the MIB tree)
Note that this is a different response than with an invalid string; with an invalid string, queries just time out. With this (ACLed) string, 'public' simply has no allowed views.
4) Devices (and discovery) are configured with a *different* SNMP string which does actually work via a walk, but not via discovery.

Is there a way to change discovery behavior to try 'public' *last*? There doesn't appear to be an order in the SNMP Configuration that's relevant.

Is there a way to batch change configured SNMP communities on nodes? Batch 'properties' change doesn't seem to exist in the UI. Better yet, can I do this with NXSL? I'm not seeing an attribute that lets me check or set the SNMP community.

Thanks

I believe we were simply running out of memory overall. In this dev environment it's sharing space with postgresql. In the latest release, my best guess is that netxms behavior changed, resulting in more concurrent database queries. I dramatically lowered the number of database pools in use, and so far netxms has been stable with no reduction in performance. (I am monitoring threads via DCIs.)

Ran with 1000 threads. Exited. Output log contains only six lines, a splash message from Memcheck (as launched by valgrind).

I'm running netxms 3.x with Postgresql 10 (timescaledb). Occasionally the database crashes and automatically restarts/recovers. However, netxmsd does not reconnect to the database. Are there any settings to tweak this? My understanding (reading old forum messages) is that netxms *should* reconnect, but it does not, and requires a full restart of netxmsd to reconnect to the db.

As for the first problem with executing an agent´s action via EPP, it was fixed and should work in version 3.1.261 that was released yesterday. Could you please confirm that it works for you?

There is currently no way to pass script arguments that have spaces from GUI's Server Console (and also from nxadm -c). Possible workarounds:
- use some special character, e.g. _ and replace it in the script
- you can use nxscript command line utility, but it can not run scripts from server script library, the script should be in a file.

Code: [Select]

nxscript 1.nxs "1" "2 3"

Проблема решена. Сработали ограничения SQL Express на размер базы в 10Gb. .
Подскажите средства миграции с SQL Express на Postgres.

Hmm,
maybe related to the problem (or i'm too stupid to use parameters correctly).

If i execute a internal script via GUI's Server Console and pass multiple parameters, strings are split at blanks, even if enquoted by "".

Example:

Code: [Select]

exec myScript 123 456 "Hello World"So for this i get $1 = 123, $2 = 456, $3 = "Hello, $4 = World", i was expecting to get the complete string for $3.

Any thoughts on this?

Andreas

Доброго времени и с наступающим!
Обозначилась следующая проблема при изменении политики обработки событий.
База на SQL Express 14.0.2027 , NetXMS Database Manager Version 3.1.261, Консоль управления 3.1.260 на Win10

Выполняется добавление группы рассылки, но изменения не сохраняются. Появляется окно предупреждения - Произошла неполадка. 
nxdbmgr check и nxdbmgr check -d -f ошибок не находит.

Awesome work, thanks guys

Just fixed this. Bug is actually in source code parser - it is not related to custom attributes but rather to negative constant passed as function parameter. Fix will be included into next patch release.

Best regards,
Victor