NetXMS Support Forum

Hi!

When login screen is displayed, web server checks URL http://127.0.0.1/netxms_login.dat . If this URL points to valid image file (PNG, JPEG, or GIF), then it will be displayed instead of standard logo. This is not very convenient, so I'll add possibility to configure custom logo in nxmc.properties file in next release.

Best regards,
Victor

Hi!

I see few possible solutions here.

1. Use dummy DCI, and in transformation script call AgentReadParameter to get LdapQuery from agent with required parameters.

2. If values of custom attributes not changing, you can embed them into DCI on template apply time using template macros. It could be something like


LdapQuery(%{script:LdapParameters})


and in script library you can create script named LdapParameters like this:


return GetCustomAttribute($node, "ip") . "," . GetCustomAttribute($node, "user") . "," . GetCustomAttribute($node, "GUID") . "," . GetCustomAttribute($node, "value");


Best regards,
Victor

Quote from: sperlm on January 24, 2014, 03:02:06 PM
p.s. could I get my old topic Dependency script based on infrastructure unlocked to post what I came up with to share with others ?

unlocked.

Best regards,
Victor

Quote from: sperlm on January 24, 2014, 12:29:02 PM
   if I understand it - just by configuring these options and having LogFile = {syslog} in netxmsd.conf (by default) should (after server restart) start up syslog in NetXMS console and start filling it with NetXMS log ?

No, just opposite - LogFile = {syslog} in netxmsd.conf is not related to built-in syslog server in any way. You have to enabled built-in syslog server using EnableSyslogDaemon and company as I described before. Note that these are server configuration variables stored in database (editable in console via Configuration -> Server configuration), not parameters in netxmsd.conf.

Best regards,
Victor

Your problem here is that i->peerNode is an object, not a string, so you should use something like i->peerNode->name.

Best regards,
Victor

Hi!

What version of NetXMS, on what platform and database? Also, can you share portion of server log file (running server with debug level 6)?

Best regards,
Victor

There was a bug in gauge widget. I've fixed it. Fix will be included in 1.2.12 release.

Best regards,
Victor

Not yet. I'll add this as feature request (https://www.radensolutions.com/chiliproject/issues/483).

I'll think about instance discovered DCIs on one graph. Currently it should be possible to fix them using nxshell, but probably it will not be easy.

Best regards,
Victor

Hi!

You have mixed two different functions. When you have LogFile = {syslog} in your netxmsd.conf it only means that server will use syslog for logging instead of writing directly to file, and most likely you'll see related messages in /var/log/messages or /var/log/syslog - depending on your distribution and actual syslog configuration. NetXMS server here is just a client for your local syslog server.

NetXMS server can also work a s a syslog server and collect syslog messages from remote hosts and devices (which is what you need as I understand). It is disabled by default, you should change the following server configuration variables:
EnableSyslogDaemon - set to 1;
SyslogListenPort - port for syslog server to listen on (default is 514, but it may be used already by system syslogd);
SyslogRetentionTime - number of days to keep received messages in database (default is 90).

When you restart server you should see incoming syslog messages stored. You can check that new messages coming using syslog monitor (Monitor->Syslog menu in console).

Once you set up syslog receiving, you can configure message matching policy to capture texts from messages and generate events.

Best regards,
Victor

Hi!

Can you explaint in more detail what you are trying to achieve or maybe post whole script? There are also example of using peerNode and peerInterface attributes: http://wiki.netxms.org/wiki/Script_Example:_Additional_Information_About_Connected_Node.

Best regards,
Victor

Hi!

Check that libstrophe.so.1 was installed into destination libdir. If it is, try to run ldconfig.

Best regards,
Victor

Most likely we will release 1.2.12 as patch release in a next few days to fix crashes reported for 1.2.10 and 1.2.11.

Best regards,
Victor

Hi!

Next release will be built with XMPP support included. It is possible to specify multiple addresses in one action - they must be separated by semicolon.

Best regards,
Victor

Я не знаю какие значения могут принимать эти OIDы, а так с точки зрения конфигурации все выглядит правильно.

Hi!

Yes, it's ok to upgrade directly.

Best regards,
Victor