NetXMS Support Forum

Hi Victor,

I changed the rule and deleted all the alarms with current severity 255. The problem is so far solved. Thanks your your guidance about this issue.

Regards,

Christian

Hi Victor.

Rule 37 terminates interface down alarms when interface is up even though the rule has been set to terminate the alarm generate by rule 36, the action/alarm/terminate was configured on the tool box but not shown on the event processing policy.

Please find attached the screen shots from the event processing policy for rule 37 and the properties window for the same rule showing the action "terminate all alarms with key".

thanks so much for your help.

Hi Victor,

Please find attached the cvs files from the required queries.

Thanks

Hi Victor,


I'm having the same problem on all the consoles (5 different  users).

Please find attached the required ile

hi,

anyone having the same problem?

thanks,

Thanks Guys, great job!!!!! 

Hi,

Since I cleaned the old alarms on the my database I'm having this problem.

In fact, I'm getting alarms but I cann't see them on the object tree.

Do you have a clue how I cuold fixe it?

BTW, I'm running version 1.2.15 but the problem is coming from version 1.2.14. Thanks

a picture of my Netxms console is attached

Hi  Victor,

I runned the nxupload on line command and the result is:


903: I/O failure


thanks

Hi Alex.

The way you suggested, its the way I normally use to upload files. but the result is the same "Unknown command" in server Jobs window. I'm going to check the nxupload command. Thanks for your help.

Hi Tatiana. Thanks for your reply.

what do you mean by "upload of file to default path(When destination path is empty)"?

the only way I found to deploy these xml files to my nodes was as follows:

I created a npi file for each file, so then I uploaded the xml files as a software using the package manager, then as usual I deployed the files to the nodes (the files have been stores at the directory set up on the agent's configuration file.

I know the new version has a file manager subagent. I added the filemgr.snm by hand on one of my nodes. please find attached the configfile used. the file manager worked, I was able to upload a file using the new manager. But in this new case I've to update every single node I've (we're talking about 80 nodes) by hand, and Im still no able to deploy in one shot one file to all the nodes.

Hi Victor.

This is the message I received after trying to upload a xml file from the server to the nodes (Win 64 and 32 architecure). Basically the files I'm tryining to upload, are  log parse configuration files. Before the upgrade I was able to do it and any problem came up.

Hi,

Am I supposed to update all the agents I've running with previous versions (1.2.8 and 1.2.14) in order to upload a file from the netxms server (1.2.15)? and wait until the new realese (inclundin the missing file manager subagent).


I've having a really hard time trying to install remotly software using the package manager on server 1.2.15, could it be a new bug?. NPI file are ok and sometime the server could achieve the task but mostly it fails.

Thanks,

Hi Victor,

Please find the required log file on the attachments. Thanks,

Hi Victor,

I will run this valgrid on my server for a few hours, as soon as the test is done, I'll send you the log. Thanks for your help.

BTW, this is the command I'm going to use, is there any additional parameters I should  add?

valgrind --leak-check=full --undef-value-errors=no --log-file=netxmsd-valgrind.log netxmsd -D3

Please find below the result for the command " sh sta"


Total number of objects:     771
Number of monitored nodes:   76
Number of collectable DCIs:  1564