News:

We really need your input in this questionnaire

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - lbdecloedt

#1
Ok, I will try this. Thanks for the quick response.
#2
I am getting these errors in the event log for selected nodes. Below are two of the messages I have seen.

Source: NetXMSCore      Event ID:43
Event Type:   Error
Event Source:   NetXMSCore
Event Category:   None
Event ID:   43
Date:      1/14/2009
Time:      10:16:03 AM
User:      N/A
Description:
SQL query failed (Query = "INSERT INTO idata_1734 (item_id,idata_timestamp,idata_value) VALUES (1324,1231946163,'HP NC373i Multifunction Gigabit Server Adapter #232')"): General SQL Server error: Check messages from the SQL Server.

Event Type:   Error
Event Source:   NetXMSCore
Event Category:   None
Event ID:   43
Date:      1/14/2009
Time:      10:16:03 AM
User:      N/A
Description:
SQL query failed (Query = "INSERT INTO idata_1734 (item_id,idata_timestamp,idata_value) VALUES (1532,1231946163,'0')"): General SQL Server error: Check messages from the SQL Server.

It appears to be an issue inserting the date into the MSSQL database, but I am not sure why. Yesterday the system log had no errors.

I am running version 2.22 for both server and agents; on Windows Server 2003 SP2 with SQL Server 2005. With 107 nodes being monitored most which are not connected to the network at this time.

Has anyone run into this issue or can provide any insight into this issue?

Thanks in advance!! ???
#3
General Support / Adding multiple nodes at one time
November 04, 2008, 03:25:54 PM
Hello All,

I need to setup additional nodes manually and it appears that it will take some time to get them all in NetXMS. Is there a script or another way I can add multiple nodes at one time? ???

Thanks in advance!

#4
General Support / Received fatal Debug message
October 18, 2008, 01:27:12 AM
I am attaching the follow that I received, if someone can decipher this that would be great!
Also attaching accompanying file:

NETXMS CONSOLE CRASH DUMP
Fri Oct 17 16:01:06 2008

EXCEPTION: C0000005 (Access violation) at 1000879D

NetXMS Console Version: 0.2.22
OS Version: Windows Server 2003 Build 3790 Service Pack 2
Processor architecture: Intel x86

Register information:
  eax=00000A5F  ebx=00000001  ecx=00000000  edx=0000FE3C
  esi=00000000  edi=02657890  ebp=0012CD5C  esp=0012CD20
  cs=001B  ds=0023  es=0023  ss=0023  fs=003B  gs=0000  flags=00010202

Call stack:
  [libnxclw:1000879D]: public: struct NXC_OBJECT * __thiscall NXCL_Session::FindObjectById(unsigned long,int)
  [libnxclw:10008860]: _NXCFindObjectById
  [nxcon:0043BB6C]: protected: void __thiscall CObjectBrowser::OnTreeViewGetDispInfo(struct tagTVDISPINFOW *,long *)
  [MFC42u:72832665]: Ordinal4418
  [MFC42u:728325F7]: Ordinal4418
  [MFC42u:72832AEE]: Ordinal4421
  [nxcon:0043D129]: public: virtual int __thiscall CObjectBrowser::OnCmdMsg(unsigned int,int,void *,struct AFX_CMDHANDLERINFO *)
  [MFC42u:72833E27]: Ordinal4831
  [MFC42u:72831D10]: Ordinal5157
  [MFC42u:72831C8A]: Ordinal6370
  [MFC42u:72831BF4]: Ordinal1108
  [MFC42u:72831B47]: Ordinal1571
  [MFC42u:728C724E]: Ordinal1572
  [USER32:7739B6E3]: LoadCursorW
  [USER32:7739B874]: LoadCursorW
  [USER32:7739C2D3]: IsWindow
  [USER32:7739C337]: SendMessageW
  [MFC42u:72896951]: Ordinal4830
  [MFC42u:72831D10]: Ordinal5157
  [MFC42u:72831C8A]: Ordinal6370
  [MFC42u:72831BF4]: Ordinal1108
  [MFC42u:72831B47]: Ordinal1571
  [MFC42u:728C724E]: Ordinal1572
  [USER32:7739B6E3]: LoadCursorW
  [USER32:7739B874]: LoadCursorW
  [USER32:7739C2D3]: IsWindow
  [USER32:7739C337]: SendMessageW
  [nxcon:00443E4F]: protected: virtual int __thiscall CObjectTree::OnNotify(unsigned int,long,long *)
  [MFC42u:72831D10]: Ordinal5157
  [MFC42u:72831C8A]: Ordinal6370
  [MFC42u:72831BF4]: Ordinal1108
  [MFC42u:72831B47]: Ordinal1571
  [MFC42u:728C724E]: Ordinal1572
  [USER32:7739B6E3]: LoadCursorW
  [USER32:7739B874]: LoadCursorW
  [USER32:7739C2D3]: IsWindow
  [USER32:7739C337]: SendMessageW
  [COMCTL32:7743B07F]: Ordinal414
  [COMCTL32:77489BF3]: FlatSB_SetScrollProp
  [COMCTL32:77489DE4]: FlatSB_SetScrollProp
  [COMCTL32:7748A8BB]: FlatSB_SetScrollProp
  [COMCTL32:7748A9AC]: FlatSB_SetScrollProp
  [COMCTL32:7745BDD0]: Ordinal384
  [USER32:7739B6E3]: LoadCursorW
  [USER32:7739B874]: LoadCursorW
  [USER32:7739BFCE]: CallWindowProcW
  [USER32:7739BF74]: CallWindowProcW
  [MFC42u:7283225A]: Ordinal2377
  [MFC42u:72831CA1]: Ordinal6370
  [MFC42u:72831BF4]: Ordinal1108
  [MFC42u:72831B47]: Ordinal1571
  [MFC42u:728C724E]: Ordinal1572
  [USER32:7739B6E3]: LoadCursorW
  [USER32:7739B874]: LoadCursorW
  [USER32:7739C8B8]: GetMessageW
  [USER32:7739C9C6]: GetClientRect
  [ntdll:7C828536]: KiUserCallbackDispatcher
  [COMCTL32:7745B881]: Ordinal384
  [USER32:7739B6E3]: LoadCursorW
  [USER32:7739B874]: LoadCursorW
  [USER32:7739BFCE]: CallWindowProcW
  [USER32:7739BF74]: CallWindowProcW
  [MFC42u:7283225A]: Ordinal2377
  [MFC42u:72831CA1]: Ordinal6370
  [MFC42u:72831BF4]: Ordinal1108
  [MFC42u:72831B47]: Ordinal1571
  [MFC42u:728C724E]: Ordinal1572
  [USER32:7739B6E3]: LoadCursorW
  [USER32:7739B874]: LoadCursorW
  [USER32:7739C8B8]: GetMessageW
  [USER32:7739C9C6]: GetClientRect
  [ntdll:7C828536]: KiUserCallbackDispatcher
  [USER32:7739B6E3]: LoadCursorW
  [USER32:77395F82]: IsDialogMessageW
  [USER32:77395E22]: IsDialogMessageW
  [USER32:77395FFA]: DefDlgProcW
  [USER32:7739B6E3]: LoadCursorW
  [USER32:7739B874]: LoadCursorW
  [USER32:7739BFCE]: CallWindowProcW
  [USER32:7739BF74]: CallWindowProcW
  [MFC42u:7283F881]: Ordinal1215
  [USER32:7739B6E3]: LoadCursorW
  [USER32:7739B874]: LoadCursorW
  [USER32:7739C2D3]: IsWindow
  [USER32:77388C01]: ScrollWindowEx
  [USER32:7738964B]: ScrollWindowEx
  [USER32:7739F762]: SoftModalMessageBox
  [USER32:7739F047]: MessageBoxTimeoutW
  [USER32:7739EEC9]: MessageBoxTimeoutW
  [USER32:7739EE65]: MessageBoxExW
  [USER32:7739EE41]: MessageBoxW
  [MFC42u:7288A874]: Ordinal4219
  [(module-name not available):104D8BEC]: (function-name not available)

#5
General Support / Re: Working with Ping Subagent
October 16, 2008, 12:46:32 AM
Thank you for the quick response!!! :D
#6
General Support / Working with Ping Subagent
October 15, 2008, 07:13:50 PM
I have been unable to get a DCI to work for the icmp parameters. I have already read though the Ping Subagent documentation but this does not give an example of what the finished configuration should look like and even where to configure it. I only discovery where is goes through another topic for WinPerf.

Could someone please provide an example of an nxagentd.conf with the Ping subagent configured ???

Thanks in advance!
#7
I checked the settings and corrected them; it is working now.

Thanks for the responses!!! :D
#8
I have several servers where I would like to monitor the NetXMS agent parameters and SNMP traps. However, I cannot seem to get both agents to be active at the same time.  ???

Thanks in advance!
#9
Thank you, I will verify this configuration.
Also, I will set the agent to use the server name instead of the IP. :D
#10
General Support / Communication to agent stops working
August 27, 2008, 05:08:45 PM
I have a problem with NetXMS communicating with the agent but before I jump right into the issue I will provide background information.

I originally had the NetXMS server in install on a report server with SQL 2005 installed using NetXMS version 2.19, everything was working fine (only one NIC connected). I was then asked to move it to another workstation again everything was working fine. I have now been asked to move it back to the original report server. Everything is not fine anymore.

I made sure that I preformed a fresh install (previously uninstalled NetXMS) uninstalled the agent and deleted NetXMS folder. Detached database in SQL 2005; deleted user account and removed the DB and log files from the SQL data folder.

Installed version 2.21 install went without a hitch. Upgraded agents to version 2.21, open NetXMS console and started receiving node objects however they all showed agent inactive. In the setup I used localhost for the server and pointed the agents to IP of server (172.28.7.29) at this point I had two LAN connection on this server, I disable to 2nd LAN (172.28.7.196) and restarted server which failed to restart. When I checked the event logs there was a log that stated the "database was locked by 172.28.7.196" after searching this forum I found the command to unlock the DB. This allowed the service to restart in which case when I polled the status of the node I got the message that the Agent was running.

After several uninstalls and reinstalls and I have since upgraded to version 2.22 Console and agents I have determined my issue but not sure how to fix it.

When installing NetXMS with one NIC connected (172.28.7.29) everything works fine but as soon as I reconnect the 2nd NIC NetXMS can no longer communicate with the agents.

I need both NICs connected is there anyway to fix this? ???

Also when I created a management pack and then tried to import it, it could not because it did not save the pack with the .nxmp extension, so I had to recreate my events and templates each time I reinstalled the program. Can this be fixed? ???

Thanks in advance!!
#11
 :) Thanks for the input on this, This helps alot! I have since upgraded to 2.21 version.
#12
Hello!

???

I am new to NetXMS (1 month) as well as SNMP; so far it looks like a very useful application, but I am having a problem configuring the DCI's. I read the user guide but this does give any in-depth information.

For example I am setting up a DCI for percentage of free disk space available I have NetXMS agent running on my target object. I selected Disk.FreePerc(*) in the parameter dialog box I get "Disk.FreePerc(<insert arguments here>)" what should I but in the () for the argument?

Is there any additional documentation that illustrates sample of these configurations other them the email example? Such as configuring a DCI using SNMP?

I am using version 0.2.19!

Thanks in advance for your help