NetXMS Support Forum

Hi!

Server connects to agent, by default using port 4700.

It should be safe - first, agent accepts connection only for explicitly listed IP addresses (usually you will have only one address - of your NetXMS server). In addition, you can configure NetXMS to use encrypted connections between server and agent, and configure shared secret authentication on agent, so it will acccept connections not only from specific addressm but also only if valid shared secret was provided.

Best regards,
Victor

А можно запустить агента с ключом -D (debug) и прислать лог?

Again, problem with OpenSSL. You either don't have it or have some incorrect version. I use 0.9.8b, but any later version should be ok as well.

Best regards,
Victor

Looks like problem with encryption stuff. Do you have OpenSSL correctly installed?

Best regards,
Victor

1. You need flex version 2.5.33. Probably you have older one.

2. These functions defined in src/libnetxms/crypto.cpp. Did you compile this file as part of libnetxms?

Best regards,
Victor

Hi!

Do you link it with scilexer library?

Best regards,
Victor

Hi!

Yes, you need perl and wxrc to compile wxWidgets-based console.

Best regards,
Victor

Hi!

Missing files attached.

Best regards,
Victor

Hi!

You need NetXMS agent installed on target machine, and than you can get disk space information via Disk.Free, Disk.Used, etc. parameters. For example, to configure free disk space monitoring on disk C:, do the following:
1. Select node in object browser
2. Right click on it, and select Data collection
3. Add new DCI, leave origin as "NetXMS Agent", press "Select...", and select Disk.Free parameter.
4. Inside the parenthesis, enter C:. You parameter's name should look like
Disk.Free(C:)
5. Configure thresholds if necessary.

That's all - as soon as you create new DCI, NetXMS server will start collecting information.

Best regards,
Victor

Hi!

Missing file attached.

Best regards,
Victor

Sdelal event forwarding v 0.2.23. Tam esche mnogo chto nado budet uluchshat', no uze mozno nachinat' pol'zovatsja.

Quote from: Anth0ny on November 28, 2008, 04:15:20 PM
1) Прошу добавить в Event Processing policy Editor возможность менять положение Правил обработки (чтобы можно было перемещать Правила, менять их расположение относительно друг друга и их очерёдность применения).

Sdelal, teper' rabotajut operacii cut, copy, i paste - sootvetstvenno pri pomoshi cut i paste mozno dvigat' pravila.

Quote from: Anth0ny on November 28, 2008, 04:15:20 PM
2) Если возможно, было бы неплохо отключить первичное срабатывание NXMS при перезапуске core-сервиса NXMS. А то при каждом таком перезапуске все, кто подписан на получение почтой извещений о состоянии отслеживаемых систем, получают почему-то список - перечень кластеров (!? я так и не понял почему и причём тут кластера) и порцию извещений о последних неудачных тестах (текущие не закрытые варнинги).

Mozno bolee razvernutij primer? A to ja ne sovsem ponjal o chem rech'.

Quote from: Anth0ny on November 28, 2008, 04:15:20 PM
3) прошу увеличить объём, выделенный для внесения текста в поле "Message Template" у События (Event). а то нельзя туда запихнуть столько информации, сколько бы хотелось...

Sejchas maksimal'naja dlinna teksta soobschenija - 255 simvolov. Uvelichit' mozno, no eto budet ne ochen' prosto - nado ochen' mnogie mesta v kode proverit' i popravit' - naprimer, nado sootvetstvenno uvelichivat' maks. dlinnu soobschenij v alarmah, etc. V blizajshem relize tochno ne sdelaju, poskol'ku nado budet mnogo testirovat' posle takih izmenenij. Potom mozno budet.

Quote from: Anth0ny on November 28, 2008, 04:15:20 PM
4) в Actions нельзя создавать Действия, давая им русские имена. не принимаются. это можно поправить?

Ispravil.

В версии 0.2.23 можно мониторить логи - https://www.netxms.org/forum/index.php/topic,483.0.html

Hi!

I highly recommend you to try to convert existing VC6 projects (as far as I know, Visual Studio 2005 has built-in conversion functionality for VC6 projects). Currently, there are 59 separate projects in VC6 workspace, each compiling in separate executable or DLL. They are not intended to be compiled into a single executable. The only exception is that it is possible to build monolithic agent with all subagents compiled into it, like static agent on UNIX platforms, but it will require some additional efforts.

Best regards,
Victor

Hi!

MSG00001.bin is a file generated by message compiler from messages.mc, so it should be generated during compilation.
All other missing files will appear in 0.2.23 release. I suggest you to wait a few days for it.

Best regards,
Victor