NetXMS Support Forum

Victor,

I stopped the LanSafe service.
Using Putty I get a connection with the serial port.
If I then run the NetXMS ups subagent I get the "no communication" warning, however the com port is the taken by the subagent as I can no more connect using Putty (nor does LaneSafe work).
Since the ups subagent loads I tried to use the DCI, however they all return Unsupported - this is to be expected I guess.
If I then remove ups subagent I once more can connect to the port.
By what I can find, the PowerWare 5125 does not have a pass-through option.
Any idea?

Dan

It's Model 5125.
I'm not sure about how I kan switch to pass-through mode...

Dan

Following the "netxms_solution_guid" (is there a more recent document?) I'm trying to configure our PowerWare UPS with NetXMS.

I've added the SubAgent = ups.nsm
and configuration line
# UPS subagent configuration section
*UPS
Device = 0"COM1:":BCMXCP

however I receive the following error: Unable to add UPS device from configuration file. Original configuration record: 0"COM1:":BCMXCP

Guessing that the documentation has a typo I then tried:
# UPS subagent configuration section
*UPS
Device = 0:"COM1:":BCMXCP

I now get the error: UPS: Cannot establish communication with device #0 "BCMXCP-COM1:"

LanSafe is working fine (i disabled the LanSafe service before trying the above) so I don't think it has to do with the UPS.

Is my syntax correct? Something else wrong?

Dan

I can't find any native way of reading a registry key value.
Doing so with the "reg" shell is awkward as it returns more information than just the value.
This can be done with WMI, but a native way will be so much nicer.

Dan

Hi Victor,

Good news: I forgot (stupid me) to add *LOGWATCH on the line preceding the parser = ... line in nxagentd.conf
Once added, the log shows entries related to the logwatch.
Maybe you would like to consider adding a warning if "SubAgent = logwatch.nsm" is used but no *LOGWATCH and at least one parser=  is set in to nxagentd.conf so folks like me will spend less time searching for stupid omissions 

Bad news: I receive the following error in the log:
[Date] LogWatch: Call to EvtFormatMessage failed: The specified resource language ID cannot be found in the image file.
Software is running on Windows 2008 64 bit English. If I'm not mistaken, someone else had the same error. Is there a solution?

Dan

Hi Victor,

No, there is nothing to be found in the log file related to the Windows Event (while the log get data from other DCI's on the same Agent).
Yes I have event 100, I wrote a utility that can generate events so I can test NetXMS without having to wait for a real event to occur.

Any other plan of action?

Dan

Hi,

I have the following  parser (NetXMS 1.1.4):

<parser trace="7">
  <file>*Application</file>
  <rules>
    <rule>
      <level>31</level>
      <id>100</id>
      <match>(.*)</match>
      <event params="1">100010</event>
    </rule>
  </rules>
</parser>

I've turned tracing on (after I found https://www.netxms.org/forum/configuration/configuration-for-monitor-windows-syslog/
) however I get no triggering at all. Anything wrong with my file? Is there anything else I can do to find out whats going on?

Thanks,

Dan

Hi,

After upgrading to 1.1.4 I've noticed some DCI on the NetXMS server did not get triggered anymore.
A debug session showed rejection of connection.
the Servers parameter in nxagentd.conf was set to 127.0.0.1.
I changed this to the machine IP, and things are now working again.

I'm not sure if this is 1.1.4 related, but maybe this can help someone with the same issue.

Dan

Victor,

I've installed a mail server (hMailServer) on the same server as NetXMS to allow me to capture the smtp conversation.
Funny is that sending mails through this mail server works fine. However since our Exchange settings didn't change and that problems started when upgrading to 1.1.4, taking into account no change was made to the sending mail function, could it be the problems has to do with character sets (compilation)? I'm asking this as the Event Browser shows Chinese chars where the e-mail address should show, this it typical with Unicode related issues.

As for me, I'm going to keep using the local mail server as it presents several advantages over sending mail through the Exchange server.

Dan

Victor,

This is what I can find in the server log:

2011-09-14 08:27:07 IP_NetXMS netxms SMTPSVC1 ANTILOPEML3 IP_Mailserver 0 HELO - +netxms 250 0 41 11 0 SMTP - - - -
2011-09-14 08:27:07 IP_NetXMS netxms SMTPSVC1 ANTILOPEML3 IP_Mailserver - +FROM:+<NetXMS+Server> 501 0 27 26 0 SMTP - - - -
(I replaced the real IP's for obvious reasons)

I should be able to get more details out our Exchange, but it's really a pain... I'll see what I can do to check this further.

Dan

Hi,

Sinds installing 1.1.4 server I do not receive any more e-mails notificaitons.
In NetXMS Event Browser I find errors like:
Unable to send e-mail to <?e>: SMTP conversation failure
(Somtime the <... is followed by the message without and tailing >)
On the mail server I get error 501 (=wrong parameters)

Is this a bug?

Dan

Marco,

My Agents are still running version 1.1.3. (with server now at 1.1.4) but they do work.

Dan

Hello,

I've added two packages to the Package Manager: the 386 and 64 variants.
Can I deploy the packages without explicitly choosing the 32 of 64 servers versions?

Dan

Victor,

Maybe another minor upgrade issue: the NetXMs Management Console shows 1.1.3 in the help/about dialog.

Dan

This makes upgrading such a fun I guess 
Once 1.1.5 is out I'll try using the native sql driver.

Thanks again.

Dan