NetXMS Support Forum

V versii 1.0.13 net tablici images. Pri upgrade skoree vsego vilezet ta-ze oshibka, kogda nxdbmgr popitaetsja sozdat' etu tablicu.

A chto v loge agenta? Poprobujte esche agenta zapustit' v debug mode - s kljuchom -D 9. Pered etim log luchshe postavit' v fail.

Dobrij den'!

1.0.14 ja esche ne sobral. Na dnjah sdelaju, vilozu na sait kak obichno. Read-only dostup k svn est':

https://svn.netxms.org/public/netxms/trunk - vetka 1.1.x
https://svn.netxms.org/public/netxms/branches/1.0.x - vetka 1.0.x

Eto mozet bit', esli postavlen 32bit agent na 64bit server.

Hi!

Old versions ccan be downloaded from here: https://www.netxms.org/download/archive/.

Best regards,
Victor

Hi!

I have changed system default locale in call to EvtOpenPublisherMetadata to LANG_NEUTRAL. It's very good to know that this was a solution.

Best regards,
Victor

Hi!

In nxmc we use Eclipse viewers, so code to got parent/child relations is actually decoupled into separate pieces. Simple code to print object tree, which you can use as an example:



private void printObject(GenericObject object, int level)
{
for(int i = 0; i < level; i++)
System.out.print(' ');
System.out.println(object.getObjectName());

for(GenericObject o : object.getChildsAsArray())
printObject(o, level + 2);
}

public void main() throws Exception
{
final NXCSession session = connect();  // obtain session somehow

session.syncObjects();

GenericObject object = session.findObjectById(1, EntireNetwork.class);

printObject(object, 0);

session.disconnect();
}


Best regards,
Victor

Hi!

You can install test agent on same machine, using the following procedure:

1. Stop netxms agent service
2. Remove agent service by running nxagentd.exe -R
3. Install test agent into separate directory. This is most important! You will have to copy nxagentd.conf.

To recover after test agent uninstall, do the following:

1. Ensure that uninstall has removed agent service
2. Install agent service by running nxagentd -I -c <full_path_to_nxagentd.conf>

Best regards,
Victor

A kakaja imenno versija Windows?

It general, it is not possible to distinguish from outside if node was shut down or cable was disconnected. The only situation where it can be distinguished that I can think of is following:

Assumptions:

1. If node is off (shutdown), it still have power and link on NIC is up
2. Node is connected to managed switch and port is known

Then you can check port state on switch - if it is down, then most likely cable is disconnected (or node was completely powered off). If it is up, but node is not responding, then node was shutdown.

Also, if node in question is a server with management board (like HP iLO), you can double check server state via management board.

Best regards,
Victor

Hi!

You mean NetXMS server itself or monitored node? For monitored node, server will generate SYS_NODE_DOWN event if node is unreachable. You can create a rule in event processing policy to send email, generate alarm, etc. as a reaction to this event.

Best regards,
Victor

Hi!

Sorry, I forgot to add it to source distribution. Script is attached. It is very simple perl script which uses SSSU to get information from EVA, so you can use it on any machine with Perl and SSSU. Add the following line to your nxagentd.conf:

ExternalParametersProvider = <path>/hp_eva_collect_data.pl

and restart agent. After configuration poll, you should see additional parameters for each controller, disk shelf, and disk in EVA.

Best regards,
Victor

No, I do it today. Version 1.1.7 will include this feature. If it is needed right now, I van make cudtom build of agent.

Best regards,
Victor

Hi!

I have added special option to get number of rows in WMI query result set - if you give %%count%% as property name, agent will return number of rows.

Best regards,
Victor

Hello!

Sorry for delay with that. I do some additional testing, but was unable to reproduce this issue, even by installing event sources without english resources. Agent either give different error or renders text as it should. I have made small changes in log watch subagent, and add logging of message file name after EvtFormatMessage failure, so at least it will be possible to see what application causing this issue. Patched agent version can be downloaded here: https://www.netxms.org/download/dev/nxagent-1.1.6.2-x64.exe.

Best regards,
Victor