NetXMS Support Forum

there is an error in your script:

for (i = $1->rowCount -1; i >= 0; i++)

you start with last row (let's say 10 or something like this) and likely want to go down to row 0. But you increment i instead of decrementing it, so it went all way up to 2147483648 (power 31 of 2) where it wraps to -1 due to integer overflow and only then loop stops. So you script done more than two billion iterations - quite a lot for scripting language even on modern hardware.

Best regards,
Victor

Hi,

Windows XP and Server 2003 should still be supported. We didn't change anything in that regard. Can somebody provide me with remote access to test machine so I can try to do upgrade myself and see what happens?

Best regards,
Victor

Currently the only supported options are for auto-login and for automatic dashboard display (described here). Feel free to fill in feature requests for more options.

Best regards,
Victor

Hi,

there are few video tutorials here: http://www.youtube.com/user/alexkirhenshtein and here: http://www.youtube.com/user/TheNetXMS/videos. We plan to gradually add more.

Best regards,
Victor

Hi,

looks like a bug caused by recent changes in topology handling. I'll try to reproduce it in our test environment.

Best regards,
Victor

Can you try to upgrade this agent to 1.2.17 (it will work with server 1.2.16)?

Best regards,
Victor

Hi,

I've fixed it for next release.

Best regards,
Victor

Hi,

currently it's not possible. I'll add a feature request for NXSL data push function - then you'll be able to use action script for pushing DCI data.

Best regards,
Victor

Quite strange. What agent version you are running?

Best regards,
Victor

How's your netxmsd.conf looks like? Can you run nxdbmgr.exe or any other command line tool?

Best regards,
Victor

Can you please show your agent's configuration file?

Best regards,
Victor

Hi,

currently you cannot do that. Feel free to register feature request

Best regards,
Victor

Hi,

you can use nxget command line tool to get any list or table. For example, to get interface list:


C:\Source\NetXMS\release>nxget -e0 -l 10.5.0.162 Net.InterfaceList
1 127.0.0.1/8 24 000000000000 lo0
2 10.5.0.162/24 6 000000000000 bge0


to get file system table:


C:\Source\NetXMS\release>nxget -e0 -T 10.5.0.253 FileSystem.Volumes
MOUNTPOINT       |VOLUME           |LABEL            |FSTYPE           |SIZE.TOTAL       |SIZE.FREE        |SIZE.FREE.PCT    |SIZE.AVAIL    |SIZE.AVAIL.PCT   |SIZE.USED        |SIZE.USED.PCT    |
C:\              |\\?\Volume{39e06104-63ef-11dd-92a4-806d6172696f}\ |                 |NTFS             |40015953920      |33852870656      |84.598435        |33852870656      |84.598435        |6163083264       |15.401565        |
D:\              |\\?\Volume{2ae1c26a-6dc5-11dd-8464-806d6172696f}\ |                 |                 |0                |0
        |0                |0                |0                |0                |0                |
A:\              |\\?\Volume{2ae1c26b-6dc5-11dd-8464-9be8208dfb96}\ |                 |                 |0                |0
        |0                |0                |0                |0                |0                |


There are two useful lists: Agent.SupportedLists and Agent.SupportedTables to get list of all lists and tables supported by agent.

Best regards,
Victor

Yes, this is AD LDAP page size limit. Next release of NetXMS will support LDAP paging so you'll be able to synchronize larger amount of users without increasing page size on AD LDAP server.

Best regards,
Victor

Hi,

sounds really weird. OID you mentioned used only during topology polls to get VLAN information. Unmanaging node or disabling topology polling on it should stop it. Can you check if there is an active topology poll for this switch at time you get those SNMP requests?

Best regards,
Victor