Another common problem with MS SQL is when recovery model (http://msdn.microsoft.com/en-us/library/ms189275.aspx) set to Full and you don't do backups often - then database recovery log grows very fast because NetXMS do lot of inserts. You can check if this is the case by checking size of data files and log files for your database. Best regards, Victor

All the PhysicalDisk parameters deprecated and not working on most systems. Currently the only option is to integrate with smartmontools using external parameters. Best regards, Victor

Thanks for a quick reply. I found out that procedure few weeks ago and at first it didn’t work. Tried today and it works now. The problem was in a small tipping error made by me which I didn’t found out.

See on wiki: http://wiki.netxms.org/wiki/Server_Installation_Guide#Installing_NetXMS_Server_on_UNIX

Hi All, one of my networks is built upon IBM BladeCenter and i am having problems. major problem that i have is duplicate nodes, problem that i do not have in my other networks. Thank you for your help, Lindeamon

Hi Victor, no fake nodes right now so i will do the check should it occurs again. Best Regards, Lindeamon

Hi, So, is this bug or it isn't implemented yet? Maybe there is another way how to send events to local server? The thing is, that our main devices are located in remote areas, but monitoring should be local. And Proxy-agent connections just occupy the network. Respectfully, Nikk

Hi, I'm trying to us nxapush to push data for another node. So my command is (from the netxms server): ./nxapush -o 1371 nearixvol0=12345 1371 is the id for the node I want the data. nearixvol0 is the parameter I filled in when creating the DCI on node 1371. the dci type is set to push. in the agent log I see: [04-Apr-2014 08:49:15.024] [DEBUG] ProcessPushRequest: connection established [04-Apr-2014 08:49:15.024] [DEBUG] ProcessPushRequest: received message CMD_PUSH_DCI_DATA [04-Apr-2014 08:49:15.024] [DEBUG] PushData: "nearixvol0" = "12345" [04-Apr-2014 08:49:15.024] [DEBUG] ProcessPushRequest: connection closed On the node I see no data comming into the DCI. Am I missing something? Regards, Edward

I'm looking to have a parsed syslog message passed into an Event. Any suggestions to accomplish this?

I believe I already tried what you suggested, but I'll give it another go. Thanks for the feedback.

sounds good. Thanks!

that was my guess too, thanks.

I hope it will be available in a week or two. Best regards, Victor

Hi! Yes, there is a bug which prevents web UI from running on port 80 (any other port will work). I'll fix it in next release. Best regards, Victor

I wanted to use symbols in the subjects of Alert Mail in order to have a faster view of things like up/down status.  Using characters like these (▼▲) works well in Management Console notifications, but I have not been able to configure the server to send them so they appear in the subject line in e-mail clients.  Note that I am able to paste these symbols into e-mail subjects and send them with the characters intact. I have tried changing the value of the "MailEncoding" server parameter to utf-8, but I suspect (from looking at the email.cpp source code) that I need to make use of the "MailBase64Subjects" parameter.  This parameter does not appear in the Server Configuration page in the Management Console, however, and setting it in netxmsd.conf did not seem to make a difference. Can anyone tell me how to make this work?

Hi! Check where critical status comes from - it could be either interface object below host or outstanding alarm. Terminate alarm(s) if they are not relevant. For interface object, set expected state to IGNORE. Also you may want to disable configuration polls for that node. Best regards, Victor

Hi! You probably need to show your event processing policy. I suppose there is a flaw in event processing logic. Best regards, Victor

@scuq said in Automatic Bind Rules - AddrInSubnet: if (AddrInSubnet($node->ipAddr, "10.16.0.0", "255.255.0.0")) { return; } is this valid syntax? Syntax is valid, but depending on context (for example if you are writing a filter script) you may need to return TRUE or FALSE instead of null value. Best regards, Victor

I just performed this same test on a NetXMS v1.2.12 server and agent that were built with Unicode support. I used the same bash script: locale echo 'asdf æøå ÆØÅ qwerty' Here is the result of executing this script manually in a shell: LANG=en_US.UTF-8 LANGUAGE=en_US:en LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= asdf æøå ÆØÅ qwerty This is what I would hope to see. The Norwegian characters appear correctly. Here is the result of the NetXMS agent executing these same commands on the same machine via the "ExternalList" mechanism (I generated this output with nxget -l ...) LANG=en_US.UTF-8 LANGUAGE=en_US:en LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= asdf This is bad.  The echo output is still truncated at the first non-ASCII character. So just compiling NetXMS with Unicode support does not seem to fix this problem, at least according to my test here. Is there anything else I can try?

Hi I know this has been discussed before without any progress, so I'm raising the issue again. Today's Object Tools has tons of potential, but in a diverse environment it generates noise as every entry is shown on _all_ monitored hosts. Would it be possible to have some sort of filter or selecting the hosts that qualify for a new entry?