NetXMS Support Forum

Da, kak-to u menja oni smeshalis'... Poprobujte vot etu versiju konsoli: https://www.netxms.org/download/patches/009/netxms-console-1.1.5.1.exe. Kstati, a cherez Java consol' rabotaet normal'no?

Problema v tom, chto v baze ostalos' znachenie DataDirectory dlja Windows servera. Nado libo pomenjat' etot parametr v baze, libo dopisat' v netxmsd.conf

DataDirectory = /path_to_server_data

Pri vozmoznosti luchshe perenesti soderzimoe data directory so starogo servera, hotja eto i ne kritichno.

Da, esli mozno, damp bazi ot versii 1.1.3 ochen' bi pomog. Mozno poslat' na [email protected].

Quote from: inspirit on October 07, 2011, 12:41:12 PM
Если можно. Хотелось бы увидеть запросы которые происходят при обновлении базы с 1.1.3 до 1.1.5. попробуем их накатить и посмотрим что изменится..

Samij prostoj sposob - zapustit' esche raz nxdbmgr s opciej -t - on togda budet pechatat' vse SQL zaprosi, kotorie delaet. No po idee s tablicami, gde hranjatsja ob'ekti, tam svjazano nichego ne dolzno bit'...

Sudja po screenshotu, k kommentarijam pripisalas' chast' SQL zaprosa - eto mesto v kode kak raz menjalos' mezdu 1.1.3 i 1.1.5, tak chto problema skoree vsego v kode samogo servera. Ja poprobuju smodelirovat' etu situaciju u sebja. I kakaja baza vse-ze - mysql?

Hi!

You have to create directory /var/opt/netxms/agent or set another location for data files by adding

DataDirectory = /path_to_data_dir

to nxagentd.conf. Currently it is only used for storing information about locally installed policies, so if you don't use them, this error does not affect anything.

Best regards,
Victor

A kakaja operacionka i baza? I chto bilo ran'she v code page servera?

Nu i sejchas ja tak ponimaju informacija v baze isporchena uze, poetomu samo po sebe tochno ne ispravitsja. A pojavolos' srazu posle upgrade, ili pri obnovlenii sootvetstvujuschih ob'ektov?

Posle konvertacii v UTF-8, pri sozdanii/pereimenovanii ob'ekta, pishetsja musor?

Peresobral package s depend >= 5.1 (zamenil suschestvujuschij package).

Viktor

All Disk.* names are deprecated and replaced with appropriate FileSystem.* parameters (so Disk.Used became FileSystem.Used). Agent still support old names to maintain compatibility with already configured DCIs, but did not report them as supported to encourage users to use new naming.

Best regards,
Victor

Hi!

Sorry for late reply. I finally do some tests on Windows 2008. Currently for me it looks like security issue - for example, agent running under local system account cannot access some shares, but if I run it under domain admin account, everything works fine.  Could you please check that account you are using for running agent service has appropriate rights to the shares you are trying to check?

Best regards,
Victor

Hi!

This message means that deleted object still referenced by some long-running internal process. If it repeats for very long time (hours or more), then most likely it's a bug in a server (reference counter for object was not properly decreased). This will not affect server operation, and such objects will be cleared after server restart.

Best regards,
Victor

Poprobujte postavit' agenta 1.0.12. Funkcional'nih otlichij na Win2K bit' ne dolzno, a rabotat' on skoree vsego budet.

Viktor

Patched legacy console available here: https://www.netxms.org/download/patches/009/netxms-console-1.1.5.1.exe

Best regards,
Victor

Hi!

It is one of top priorities for me to implement all functions presented in legacy console in the Java console. There are no much gaps left, so I expect that in few month legacy console could be completely replaced. Regarding "subordinates" tab it's not hard to implement it - I'm just not sure if it is really needed, because object tree in Java console supports multiple selection, so you can just select many objects in the tree and do manage/unmanage/delete at once.

Best regards,
Victor

There is a bug in legacy console with node creation. I'll publish patched version later today.
You should not use reindex operation in nxdbmgr. It was created long time ago for one specific case and is currently broken. It need to be either fixed or removed. But why you need to reindex database?

Best regards,
Victor

Additional question - do you use old or new console for creating nodes? I encounter same issue with old console (nxcon.exe) connected to server 1.1.5. Java console connected to same server works fine.

Best regards,
Victor