NetXMS Support Forum

Попробуйте запустить агента как процесс с командной строки. Кстати, если есть Telegram, то будет быстрее общаться в нашем Telegram канале.

What is current version of NetXMS agent that you are trying to upgrade?

Ошибся в названии параметра, правильно будет CreateCrashDumps:

CreateCrashDumps = yes

еще желательно поставить

FullCrashDumps = yes

Задается параметрами DumpDirectory и EnableCrashDumps, например:

EnableCrashDumps = yes
DumpDirectory = C:\

По умолчанию это C:\

What is DCI data type?

Hi,

we are checking this.

Best regards,
Victor

Пришлите хотя-бы один crash dump для агентов.

Да, в 2.2.1 вошло соответствующее исправление. Надо смотреть какие цифры получает сервер с этого конкретного устройства - возможно сделать рядом DCI для того-же параметра без трансформаций и смотреть raw значения.

Quote from: iGodunoff on December 08, 2017, 10:16:43 AM
All the netxms agents had stopped working right after upgrade to 2.2.1. Config files of all agents contain the following lines:

RequireEncryption = yes
RequireAuthentication = yes
EncryptedSharedSecret = B/Cx9iK3RpLCpgp+8SvHuMKmCn7xK8e4wqYKfvErx7g=

It worked fine with all previous agent versions but causes 2.2.1 agents to crash soon after they started. Very sad What should I do now to get NetXMS working again? I've lost connection with all network nodes...

P.S. Error in Windows logs:

H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems

Right after this NetXMS Agent service crushes.

From the context I assume it is Windows. Do you have crash dumps from agent? If not, please enable crash dump generation in agent config and send them to us. As a workaround I recommend to rollback to agent version 2.1.2 (they will work with new server).

Best regards,
Victor

Quote from: StanHubble on December 07, 2017, 11:55:03 PM
p.s. Why the number shift (2.2.1 vs 2.1.3)?

We had internal build with version number 2.2.0 distributed to our support clients with some important changes backported from 3.0 branch. Before this release we decide to make it new stable branch - because changes are important. To avoid version clashes and uderscore that there are significant changes inside we decide to number this release 2.2.1.

Best regards,
Victor

Hi,

you could stop server, then run the following SQL query on NetXMS database:

DELETE FROM items WHERE template_id=255;

then run nxdbmgr check, fix any possible errors, and start server again.

Best regards,
Victor

Hi all!

NetXMS version 2.2.1 is officially released. Changes since previous release:

- Implemented separate access rights for each DCI object
- Option to read log files using VSS snapshots on Windows
- Per stage confirmation in database manager during database check
- Fixed file download cancelation
- HTTPS support in SMSEagle driver
- New network map element - text box
- New debug log format with tags
- Ability to set debug level per tag or tag mask
- Improved audit logging on object creation
- NXSL function "GeoLocation" replaced with "GeoLocation" class constructor
- Optimized object updates in database (to reduce load on database in large installations)
- Thread pool used for data collection instead of fixed number of poller threads
- Optimized data collection from agents
- Configurable number of records per transaction for writing DCI data
- Fixed issues:
   NX-662 (New network map element - text box)
   NX-703 (Export/Import actions)
   NX-757 (Instance discovery - grace period for removed instances before deleting DCIs)
   NX-801 (Deleted nodes not removed from trusted nodes lists of other objects)
   NX-1045 (Add rack/chassis diagram as dashboard element)
   NX-1142 (Back view for racks)
   NX-1201 (Discovered node links on map should automatically be set to color based on the status of the interfaces shown in co
nnector names)
   NX-1252 (Fix automatically generated transformation scripts for 64 bit interface counters)
   NX-1268 (Do DNS resolve for node names via zone proxy)
   NX-1289 (Override PollCountForStatusChange at Node level)
   NX-1292 (Option for line charts to not always use 0 as base)
   NX-1336 (Cluster DCI Max/Min aggregation returns value from last node instead of expected max/min)
   NX-1339 (JIRA restricts subject field to 254 chars, helpdesk integration should trim alarm text or move reset of the message
to issue description)
   NX-1341 (Scheduled tasks enabled/disabled indicator)
   NX-1342 (Increase text length limit in SMS sender)
   NX-1343 (Server crash on re-enabling temporary disabled user)
   NX-1344 (Search Bar for Agent Tunnel Manager)
   NX-1345 (Add rule number to EPP export)
   NX-1347 (New agent parameter File.LineCount)
   NX-1348 (Continuous warnings in server log: seed object 0 cannot be found)
   NX-1357 (Line chart is now opened on double clicking a Performance Chart)
   NX-1359 (Last location in World Map is now saved)
   NX-1361 (Data type of transformation script's input value can be incorrect)

Best regards,
Victor

Hi,

from my experience it's usually done via VPNs to remote sites. In many cases we seen Raspberry Pi or similar devices acting as both VPN gateway and proxy agent for remote site.

Best regards,
Victor

Hi,

it seems like a bug to me. Could you provide more detailed information about one such device (how it looks like in the system, log file parts and events related to that device)?

Best regards,
Victor

Quote from: Millenium7 on December 06, 2017, 01:11:17 AM
1) Is there a better slack addon than the SMS system? providing a bit more flexibility i.e. categories (centreon can mark with low/medium/high priority with colors)

Currently no. We plan to replace current model when everything except email implemented as SMS drivers with more flexible "communication channels". Then we will be able to make Slack connector more flexible.

Quote from: Millenium7 on December 06, 2017, 01:11:17 AM
2) Setting dependencies on devices so that i.e. if a main router goes down, don't send notifications for everything behind that router because obviously everything behind it will also be unreachable. We only want a message that the router is down, then suppress all notifications for devices behind it

Server supposed to do this automatically if it knows IP path from itself to device. Please check if server has necessary IP topology information. If it does, then it's a bug. If not, and you cannot add intermediate devices to monitoring, then you can use filtering scripts to check router status when handling node down event and skip event processing if router is down.

Quote from: Millenium7 on December 06, 2017, 01:11:17 AM
3) Dependencies for DCI's on devices. Obviously if a client radio loses connection then I don't need notifications about 0 SNR, 0 signal strength, etc

You probably can use persistent storage and/or custom properties to set certain flags, and then check them in other thresholds or event processing rules. For example, set flag when client disconnects and check it when process signal strength 0 event - and if set, ignore it. Or create script threshold and don't even trigger it if client is disconnected.

Quote from: Millenium7 on December 06, 2017, 01:11:17 AM
4) Is there a way to buffer the messages for i.e. 2 minutes then sends all of them at the same time, So if we do have a few separate devices all go down at around about the same time, at least we don't have spam every second

No.

Quote from: Millenium7 on December 06, 2017, 01:11:17 AM
5) Re-sending notifications for some core devices. At the moment if a node goes down we only ever get one message. I want important devices such as core routers or radio links to keep sending a notification that it is down every 10 minutes until it comes back up

You can create script DCI that will return 1 if node is down (script can get it from $node->flags) and 0 if not, and setup threshold as usual with repeat interval set as needed.

Quote from: Millenium7 on December 06, 2017, 01:11:17 AM
6) Notification schedule? I havn't found it in NetXMS yet. We do want monitoring to continue, but we don't want any slack messages after 10pm or before 6am

You can use filtering script in notification rules. Simple script that allow actions to be executed only between 6am and 10pm could look like this:

now = localtime();
return (now->hour >= 6) && (now->hour <= 22);


Best regards,
Victor