News:

We really need your input in this questionnaire

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Victor Kirhenshtein

#586
Самое простое - увеличить размер колонки vendor в таблице node_components. Например так:

ALTER TABLE node_components MODIFY COLUMN vendor varchar(127) NULL;

Увеличит размер до 127 с текущих 63.

Или подождать до следующего патч релиза - я добавил контроль длины значения при записи в эту таблицу, слишком длинные значения будут обрезаться.
#587
Hi,

log file just states that service cannot be started. Is there any other log files?

Best regards,
Victor
#588
Hi,

it should work, although we didn't test it specifically on that version. Just report here if you will encounter any issues.

Best regards,
Victor
#589
General Support / Re: 3.8 reporting server
April 12, 2021, 10:08:38 PM
Hi,

it was supposed to be in separate deb package, but it was not published. We will publish it in a few days.

Best regards,
Victor
#590
Announcements / NetXMS 3.8 version 3.8.267
April 12, 2021, 10:02:26 PM
Hi all!

We just published new patch release for version 3.8 (3.8.267). Only server and web API are affected. Changes since release 3.8.262:

- Fixed server crash during scheduled task processing
- Fixed issues:
        NX-2009 (Add notification channel driver "Shell command")
        NX-2035 (Instance discovery using ICMP.Targets list crashes server)
        NX-2037 (Save IP address of client connecting via WebAPI to audit log)

Best regards,
Victor
#591
Hi,

most likely you have hit RAM limit when allow thread pool to grow to 4000 threads. Could also be other memory-related issue (memory leak in server, slow database causing DB writer queues to grow, etc. Do you have pre-crash data on number of threads, queues, and memory consumption?

Also, 4000 nodes is not that much, it is quite strange that 500 threads is not enough. Such high load on poller pool indicates that there are lot of polls taking long time to complete.  Could it be that you have many nodes that timeout when polled?

Best regards,
Victor
#592
Announcements / NetXMS version 3.8.262
April 09, 2021, 11:31:14 AM
Hi all!

New patch release for version 3.8 - 3.8.262 - is just published. Changes since version 3.8.250:

- Fixed server crash when accessing NXSL class metadata
- Fixed agent crash when parsing log files
- Fixed file handle leak in log parser subagent
- DCI Editor filter now search by description, parameter, and DCI ID
- Long polling can be disabled in Telegram driver
- Fixed Log Parser Policy save with empty agent action field
- Fixed issues:
        NX-1770 (Add ability to filter by DCI name in DCI list)
        NX-2033 (Incorrect interface name displayed in MAC address table for Mikrotik routers)
        NX-2036 (Filter in DCI editor should search both description and parameter)

Best regards,
Victor
#593
Hi,

we likely found the issue. New patch release will be available in a next few days, please re-test this issue then.

Best regards,
Victor
#594
В списке файлов очень много раз встречается /var/log/auth.log.1, /var/log/mail.log.1, и /var/log/apcupsd.events. На агенте не настроен мониторинг этих файлов через logwatch?
#595
General Support / Re: nxdbmgr failes to repair
April 07, 2021, 05:51:17 PM
Hi,

that one looks like PostgreSQL problem - server drops connection for some reason. Check in Postgres or system log if it was restarted.

Best regards,
Victor
#596
General Support / Re: nxdbmgr failes to repair
April 06, 2021, 03:28:07 PM
Hi,

looks like bug in nxdbmgr. Somebody from dev team will check.

Best regards,
Victor
#597
Default path for source install is /usr/local/bin and /use/local/lib. It looks like old version is in your path, so command

which nxdbmgr

should show it's location.

Best regards,
Victor
#598
Hi,

looks like you have older version of NetXMS (3.4.178) somewhere in the path as well. Make sure that you don't have old version installed from sources for example.

Best regards,
Victor
#599
Hi,

looks like call to Cipher.getInstance("AES/CBC/PKCS5Padding") sometimes is very slow. To test it, please create the following Java file:


import javax.crypto.Cipher;

class CipherTest
{
   public static final void main(String[] args)
   {
      long start = System.currentTimeMillis();
      try
      {
         Cipher.getInstance("AES/CBC/PKCS5Padding");
      }
      catch(Exception e)
      {
         e.printStackTrace();
      }
      long elapsed = System.currentTimeMillis() - start;
      System.out.println("Elapsed time " + elapsed + " milliseconds");
   }
}


call it CipherTest.java, then compile as

javac CipherTest.java


and run as

java CipherTest


It should print elapsed time for cipher initialization. On my machine it is around 60 milliseconds. If it will take many seconds during some run then this is problem with local JVM (likely with entropy collection, maybe with /dev/random or /dev/urandom).

Best regards,
Victor
#600
Там где агент падает - поставьте пожалуйста еще -dbg пакеты (netxms-agent-dbg, netxms-dbdrv-sqlite-dbg, и т.д.) - тогда дамп будет сильно более полезным.

По поводу дескрипторов - пришлите пожалуйста вывод lsof -p для процесса агента.