NetXMS Support Forum

Hi!

Can you please run configuration poll manually and see if anything changes? Also, please try to get data from agent from command line using nxget:

nxget -I agent_ip_addr

Best regards,
Victor

Quote from: doki on May 14, 2013, 04:48:22 AM
Is the h3C & shoretel driver included on this release?

No, I completely forgot about them. I'll do this for next release.

Best regards,
Victor

Hi!

You can use portcheck subagent to check that network service is actually responds. There is short documentation: http://wiki.netxms.org/wiki/Subagent:PortCheck. There are no FTP support, so you can only check that TCP connection can be established.

Another option is to define external parameter on one of the agents to connect and check FTP server. It could be something like this:


ExternalParameter = FTP.Status(*):echo quit | nc -q1 $1 21 | grep '^220 .*' | wc -l


After you add this line to nxagentd.conf and restart agent, it will provide new paraneter FTP.Status, which will take server DNS name or IP address as argument, and return 1 if 220 got in response, and 0 otherwise.

Best regards,
Victor

А это случайно не был upgrade поверх не-UNICODE версии? Или инсталляция на чистую систему?

Уменьшил в схеме размеры полей, так что в будущем эта ошибка вылезать не должна.

С функцией wgetenv совсем странно - это нормально, что ее нет - configure это обнаруживает, и используется имплементация из libnetxms. У меня на Debian 6 собирается без проблем в UNICODE без libcommons-exec-java. Можете свой config.h прислать, и вывод ldd nxdbmgr?

Hi!

Dial charts available only in dashboards. Steps to create dashboard with single dial chart:

1. Right-click on "Dashboards" tree, select "Create dashboard".
2. Open properties for new dashboard object.
3. Open "Dashboard Elements" page.
4. Press "Add" button, select "Dial chart" as element type.
5. Double click on new element in list, dashboard element properties dialog will open.
6. Open "Data Sources" page.
7. Press "Add" to add DCI you want to show.
8. Open "Dial Chart" page.
9. Enter desired values for maximum value and values for red and yellow zones.
10. Press OK to close dashboard element properties.
11. Press OK to close dashboard properties.
12. Double click on dashboard object - you should see dashboard with single dial chart element.

You can also see this screencast on dashboard creation: https://www.youtube.com/watch?v=ZfJQiUIDHY4.

Best regards,
Victor

Looks like problem is found: if you have installed gpp (general-purpose preprocessor), and don't have installed g++ (GNU C++ compiler), configure script mistakenly detects gpp as C++ compiler. Solution is to install g++ package.

Best regards,
Victor

Hi!

From the log I can see that agent successfully find new record in log and tries to send it to server:

[17-May-2013 23:14:08.683]   matched
[17-May-2013 23:14:08.683] SendTrap(): event_code=100008, event_name=(null), num
_args=1, arg[0]="Recibido comando de inicio de IIS del usuario HPCDSES\administr
ador. El dato registrado es el c¾digo de estado. " arg[1]="(null)" arg[2]="(null
)"

What I didn't see in the log is communications with the server. Please check that server can communicate with agent. You can run configuration poll and see if agent is detected. If not, check network connectivity and firewalls between server and agent.

Best regards,
Victor

Судя по логу, configure вместо C++ компилятора (g++) нашел некий gpp. Проверьте, что установлен пакет g++, и удалите gpp, если он реально не используется.

В новой консоли тоже можно делать автоматический логин. Вот документ с описанием параметров командной строки: http://wiki.netxms.org/wiki/Autologin_for_Management_Console.

Hi!

Did you try to configure any custom attributes for some object?

Best regards,
Victor

Hi!

Parser looks correct. It should generate an event for each critical event in Windows system event log. I suggest to check the following:

1. Agent config - you should have logwatch subagent, and you should have parser definition set in LOGWATCH section.
2. Check event log on NetXMS server - do you see events coming?
3. Check that there really was new critical events.
4. Run agent in debug mode and see if there are any errors/warnings related to log monitoring.

Also, don't be confused by syslog view in NetXMS - agent send events to server, not syslog records - and so you should see them in event log in NetXMS.

Best regards,
Victor

Hi!

Looks like there was some remnants from previous version. I encounter similar situation on Tomcat - you have to re-deploy application while Tomcat is running. If you stop Tomcat, copy over new war file, and start Tomcat, some packages from old version can remain in temporary directories.

Best regards,
Victor

Попробуйте запустить агент с полным дебагом (ключ -D9). И пришлите пожалуйста конфиг агента.

С тех пор сообщения менялись, я лучше соберу новый архив. Был человек, который начал перевод на русский, но от него давно ничего не слышно...