NetXMS Support Forum

can you send event processing policy section and threshold section of your dcis please.

You can try this:
Stop netxms server, and do a db check with this command:
nxdbmgr check -f
Then run netxms server again. There are 2 possibilities:
1- object is fully deleted
2- object is recreated (due to dependencies)

If 1.st alternative is occures, then you can create same object again.
if 2nd alternative is occures, then your object is back.

I hope there is not any other alternative

Quote from: curruscanis on September 21, 2015, 07:36:42 PM
I have a node with a DCI issue.

I am getting the error:

'Read DCI data from server' has encountered a problem.  Cannot get data for DCI "Node Name":[1464]: database failure

I noticed this as the data from the node was displaying on a dashboard and now just shows "Cannot get DCI Value..."

I have run a database check and all passed, I have deleted and recreated the DCI collection items with no success.

Please let me know what I can do to troubleshoot this.

Thank you.

Hi. After you delete and recreate dci items, you have to adjust dashboards, too. Because Your new DCISs' id numbers are different then older ones and dashboards save dci information as their ids. So, If you deleted and recreated any DCI that using by dashboard, you must adjust that dashboard (delete old dci info and add new ones).

do you have to restore it ?

You can right click to container and select "create node". Only thing you need is object's IP address.

Hi.

I am trying to use xmpp with netxms. but I could not success yet.

I settled all necessary settings in server configuration. but it is not way to success

I tried to reinstall netxms ( i am using cents 7 X64), I saw that when configure finished, report is :
LDAP NO
XMPP NO
I could not change this. I looked to the forum but could not find any info.

Can anybody help me about using xmpp, please.

thanks.

Hi.
You said
- Unified macros in all types of object tools
in 2.0.RC1.


Can you write an explanation for actual macros (or give a link) ? I found ALARM_ID macro for sending alarm id to object tool (trying to send alarm id to server command), bur could not use it. I think perhaps something changed.

Thanks.

Ok. Here is my solution:

I am using linux and created a bash script. Script gets username as a parameter, and running query to my netxms server for user's full name. And then creating event to netxms server. In Object tool section, I am running this script with necessary information (Object id, User Name, etc) and script creating an event, and passing user full name and other necessary information to this event. I can use user's full name now.

So, It is some different but working

Thanks.

Hi.

I know we can use %USERNAME% in macros with action configuration. Bu I have an action that loads only script (%[script]). I am using this action to create support ticket to my ISP. I have at least 5 persons that is doing this job.  I want to add personal info to this.

Can this be done? How can I use username in script that loaded from action?

Thanks.

instance discovery bug has been corrected.

Thank you.

Hi. I don't know if this is the  easiest way but I can offer you something: (step by step)


1. Create a new event as INFORM_APP_NORMAL. (note this event's id)
2. Create a Script and name it minutecheck
    Script should be as this :



a1=$node->id;
a2=d2x(a1,8);
a2="EO_SERVICE_0x" . a2;

alarm=FindAlarmByKey(a2);

if (alarm->severity>1) // Here, we are checking if alert's severity is bigger then minor.
{
PostEvent($node, INFORM_APP_NORMAL event's id, null, "param1", "param2","param3"); // if you want to send parameters to event, you can use      param1 ..... param99 as parameter..     INFORM_APP_NORMAL event's id must be numeric ID of INFORM_APP_NORMAL event.

}

alarm->terminate(); //we will terminate alarm in all case with this script. So we won't need terminate alarm in event processing policy.




3. save the script.
4. Create a new action and tell this action to Execute NXSL Script. and name it as you want (you can use minute check again). and write script's name (in this example minutecheck).
5. In Event Processing Policy section, edit EO_SERVICE_NORMAL policy.
    You must choose "Do not change Alarms" in alarm section and In server actions section, remove Notify Suppor Analyst and add "minutecheck" action. So there will be only one action in EO_SERVICE_NORMAL event process policy.
6. Create a new Event Processing Policy for the event that you created (in this example INFORM_APP_NORMAL event).
    In this event processing policy, there will be only one thing.  "Notify Suppor Analyst ".

Thats all I think.

Hi. Is there any news about instance discovery error ?

Thanks.

Hi, again.

Perhaps I could not explain my problem.
I added screensohts for template DCI. Instance discovery is working for first OID.
In fact, it is walking for all OIDs, but return %(true,$1,ifName3); command line is not working properly (or, function that calling this script is not working properly)

There must be at least 30 (for each In_ and Out_) DCIs in this node's DCI config section

I set debug level to 6. and here is log:  It seems all discovery is returning first interface's script result.


1-Aug-2015 13:30:06.444] [DEBUG] Node::doInstanceDiscovery(AnaBinaKat2Sw1 [29910]): Updating instances for instance discovery DCI .1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]
[11-Aug-2015 13:30:06.444] [DEBUG] [CLSN-0] Sending message CMD_POLLING_INFO
[11-Aug-2015 13:30:06.563] [DEBUG] Node::doInstanceDiscovery(AnaBinaKat2Sw1 [29910]): read 29 values
[11-Aug-2015 13:30:06.566] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "1" removed by filtering script
[11-Aug-2015 13:30:06.582] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" replaced by "132"
[11-Aug-2015 13:30:06.583] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.592] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "600" replaced by "132"
[11-Aug-2015 13:30:06.593] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.596] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10001" removed by filtering script
[11-Aug-2015 13:30:06.598] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10002" removed by filtering script
[11-Aug-2015 13:30:06.611] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10003" replaced by "132"
[11-Aug-2015 13:30:06.611] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.621] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10004" removed by filtering script
[11-Aug-2015 13:30:06.624] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10005" removed by filtering script
[11-Aug-2015 13:30:06.637] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10006" replaced by "132"
[11-Aug-2015 13:30:06.637] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.639] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10007" removed by filtering script
[11-Aug-2015 13:30:06.644] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10008" removed by filtering script
[11-Aug-2015 13:30:06.653] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10009" replaced by "132"
[11-Aug-2015 13:30:06.653] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.668] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10010" replaced by "132"
[11-Aug-2015 13:30:06.668] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.670] [DEBUG] StatusPoll(GEVAS_VAN.yourdomain.com): bAllDown=false, dynFlags=0x00001001
[11-Aug-2015 13:30:06.677] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10011" replaced by "132"
[11-Aug-2015 13:30:06.677] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.680] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10012" removed by filtering script
[11-Aug-2015 13:30:06.688] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10013" replaced by "132"
[11-Aug-2015 13:30:06.688] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.696] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10014" replaced by "132"
[11-Aug-2015 13:30:06.697] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.697] [DEBUG] StatusPoll(GEVAS_VAN.yourdomain.com [18592]): boot time set to 1439179618 from SNMP
[11-Aug-2015 13:30:06.697] [DEBUG] StatusPoll(GEVAS_VAN.yourdomain.com [18592]): unable to get agent uptime
[11-Aug-2015 13:30:06.697] [DEBUG] Finished status poll for node GEVAS_VAN.yourdomain.com (ID: 18592)
[11-Aug-2015 13:30:06.709] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10015" replaced by "132"
[11-Aug-2015 13:30:06.709] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.716] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10016" replaced by "132"
[11-Aug-2015 13:30:06.716] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.726] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10017" replaced by "132"
[11-Aug-2015 13:30:06.726] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.734] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10018" replaced by "132"
[11-Aug-2015 13:30:06.734] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.749] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10019" replaced by "132"
[11-Aug-2015 13:30:06.749] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.752] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10020" removed by filtering script
[11-Aug-2015 13:30:06.754] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10021" removed by filtering script
[11-Aug-2015 13:30:06.767] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10022" replaced by "132"
[11-Aug-2015 13:30:06.767] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.775] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10023" replaced by "132"
[11-Aug-2015 13:30:06.775] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.789] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10024" replaced by "132"
[11-Aug-2015 13:30:06.789] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"

.

I solved network map section.

Network map must be closed before any change made in network map preferences. If I do so, it is ok.

I was waiting this version for nearly 2 weeks.  First of all, I want to say "thank you" 

Is there any problem with
return %(true, $1, stringvariable_for_instance-name); command line ?
I have an instance discovery script, and it was working good in prior versions. But now, It is not doing instance discovering. I tried to debug with trace commands, and saw that everything is ok except this line.

Script returns true but instance discovery is not adding necessary DCIs

In network maps, there was a problem when network map imported to a dashboard (about show objects as icons). Now, There is a problem with network maps, too. When I open network map, property is settled to show objects as status icons, but objects are shown as their images. I am changing to show objects as icons, it is ok. but when I close and re open, it is same again ( showing as images)

Good solution  .  While we have this option, we don't need to execute a command on server or execute action in NXSL.

Thank you.