NetXMS Support Forum

Hi!

I would suggest calling a script from macro, like this:

1. Create script called "ServiceStateName" in script library:

state = GetEventParameter($event, "currentValue");
switch(state)
{
   case 0:
      return "OK";
   case 1:
      return "error in parameters";
   case 2:
      return "cannot connect to server";
   case 3:
      return "content of does not match";
}
return "UNKNOWN";


2. Use %[ServiceStateName] instead of %<currentValue>

Best regards,
Victor

Hi!

No one complaining so far I agree that this is a flaw in default configuration. I'll change default values of AgentCommandTimeout and portcheck timeout.

Best regards,
Victor

Hi!

Could you please post graphs of memory consumption and results of "show stat" server console command (it will show number of nodes and DCIs)?

Best regards,
Victor

Hi!

Could be either a bug or configuration problem. I suppose that TCP connection timeout (for agent to web server connection) is longer than server timeout for agent communication, and so server just didn't wait long enough to get value for ServiceCheck.HTTP parameter, and because there was no new value, threshold was not triggered. I suggest to 1) specify reasonable but short connection timeout in ServiceCheck.HTTP parameter; 2) ad additional threshold for data collection error.

Best regards,
Victor

Hi!

Graphs looks great! I can imagine a lot of things to enhance (first thing that comes to my mind is to implement scrollable/zoomable graphs, which GraphView supports), but I like the direction. I'm not an Android development guru either, so we are in same position here.

For now, I have committed your changes into subversion, and publish new console on a web site (as an 1.1.9 version). Please send me your desired login name for subversion so you be able to commit changes directly.

Best regards,
Victor

Hi!

Can you please send me a screenshot of how it looks? Are all devices which behaves wrong of same type? I have added new Cisco Catalyst driver in 1.1.8, this may impact Cisco Catalyst switches.

Best regards,
Victor

Our ultimate goal to have web interface with same functionality as console application and having as closer look and feel to console application as possible. We are now using Eclipse RAP which allows to port existing Eclipse-based applications to web applications. It has lot of limitations, but still it allows us to reuse 70-80% of existing code in management console, and resulting web application looks very similar to standalone console.

Best regards,
Victor

Hi!

It was unplanned release, but due to critical bugs in 1.1.8 (mostly because of reported crash on MySQL and Oracle backends and performance data not stored in DB on MS SQL backend) I have to create this bugfix release. My current to-do for 1.1.10 is following (copy-paste from internal Jira):

Bug
[NX-12] - Multiple bugs in image library
[NX-54] - Missing "interconnect networks" property for cluster objects
[NX-65] - Extra new line character in local command output

Improvement
[NX-3] - Ability to set native agent port on node creation
[NX-18] - Improve dashboard configuration tools
[NX-40] - Make log viewers really usable
[NX-45] - Add option to force creation of character string instead of hex string in SNMP trap mapping
[NX-56] - Add possibility to add and edit names on map link
[NX-57] - Add certificate authentication to Java console

New Feature
[NX-17] - Add "monitors" for events, SNMP traps, and syslog records
[NX-33] - Implement configuration export in Java console
[NX-35] - Implement concept of "normal" interface state
[NX-38] - Add additional page for containers where threshold violations for underlying nodes are shown
[NX-43] - Allow per-DCI SNMP version settings
[NX-49] - Implement NXSL actions
[NX-50] - Add possibility to add parameters and/or specify entry point in scripts called via %[] macro
[NX-51] - Ability to copy/paste scripts in script library
[NX-63] - Timed alarm acknowledgement
[NX-70] - Implement syslog parser edit from Java console
[NX-71] - Add new policy type for distributing log parsers

I plan to release 1.1.10 in the beginning of February. Also, I plan to release alpha version of new web interface (RAP based) somewhere in January.

Best regards,
Victor

Hi all!

NetXMS version 1.1.9 is out. It's a bugfix release which solves some important problems found in 1.1.8. Changes from previous release:

- Fixed server crash during startup
- Fixed failed SQL queries if MS SQL used as backend
- Fixed "Resource not available" error when trying to view VLANs on a switch
- Bugfix: data collection configuration not available for cluster objects
- Bugfix: cannot remove package from list if file does not exist
- Bugfix: temporary file not deleted after external parameter execution
- Bugfix: cannot change node's "force encryption" flag from Java console
- Bugfix: cannot execute local commands with spaces in path
- Template can be moved between template groups
- Added "refresh" function to alarm browser in Java console

Best regards,
Victor

Hi!

It's various macros. They are described in NetXMS user manual, section "Macros used in event processing".

Best regards,
Victor

Hi!

Could you run agent under gdb and send me a backtrace?

Best regards,
Victor

Hi!

That's excellent news! There are no restrictions, and I'm very happy that someone will take care about Android client. I have a lot of work with the core and main UI. For now, you can send me your modified version, and if you plan to continue development, I'll ask Alex to assign you commit rights for svn repository.

Best regards,
Victor

Da, eto vpolne vzmozno ta-ze oshibka. Ja segodnja vecherom vilozu bugfix release 1.1.9, tam eta oshibka uze budet ispravlena.

Hi!

I suspect some configuration error. Could you please post screenshots of your network discovery configuration? Also, try to run server with debug level 5 and see what it reports in log regarding discovery.

Best regards,
Victor

Please check this: http://www.linuxquestions.org/questions/slackware-14/weird-error-message-while-attempting-to-run-eclipse-629757/. NetXMS console is built on top of Eclipse, so it's probably the same error. From what I see it looks like problem with X setup, but I'm not an expert in this area, so I may be wrong.

Best regards,
Victor