NetXMS Support Forum

Here is the requested dump

This is the dump I made while I could not connect to the server via the console.
Just after getting you this dump the whole core service has shut down, this is new behaviour.

Download dump file: http://www.mediafire.com/?madxezmwjem
Mirror: http://rapidshare.com/files/112653022/netxms.dump.html

I hope I made the dump correctly, please let me know as soon as possible.
Thanks in advance.

Anything else I can try untill I get you the minidump data? 

Hello,

Thank you for this, unfortunately the most of all my monitoring is on windows nodes  Thanks anyway.

I am sorry, minidump is currently not an option (working over internet, the firewall is configured to not give that server http access).
I will get it for you on monday.

Here is the output from the commands:


NetXMS Server Remote Console V0.2.20 Ready
Enter "help" for command list

netxmsd: show mutex
Mutex status:
  g_hMutexIdIndex: locked for reading
  g_hMutexNodeIndex: locked for reading
  g_hMutexSubnetIndex: unlocked
  g_hMutexInterfaceIndex: unlocked

netxmsd: show pollers
PT  TIME                   STATE
S   01/May/2008 17:36:26   wait
S   01/May/2008 17:37:17   poll: [Censored] - Oki 3530 [372] - child poll
S   01/May/2008 17:36:26   wait
S   01/May/2008 17:36:36   wait
S   01/May/2008 17:37:18   wait
S   01/May/2008 17:36:26   wait
S   01/May/2008 17:36:26   wait
S   01/May/2008 17:36:26   wait
S   01/May/2008 17:37:13   wait
S   01/May/2008 17:36:26   wait
C   01/May/2008 17:35:17   poll: [Censored] - [Censored] [369] - interface check
C   01/May/2008 17:37:18   poll: [Censored]- [Censored] [440] - interface check
C   01/May/2008 17:36:51   poll: [Censored] - [Censored] [444] - capability check
C   01/May/2008 17:36:00   poll: [Censored] - [Censored] [425] - interface check
R   01/May/2008 17:34:19   wait
R   01/May/2008 17:34:27   wait
R   01/May/2008 17:35:16   wait
R   01/May/2008 17:34:36   wait
R   01/May/2008 17:34:36   wait
D   01/May/2008 17:33:06   wait
N   01/May/2008 17:33:06   wait
N   01/May/2008 17:33:06   wait
N   01/May/2008 17:33:06   wait
N   01/May/2008 17:33:06   wait
N   01/May/2008 17:33:06   wait
N   01/May/2008 17:33:06   wait
N   01/May/2008 17:33:06   wait
N   01/May/2008 17:33:06   wait
N   01/May/2008 17:33:06   wait
N   01/May/2008 17:33:06   wait
A   01/May/2008 17:33:06   wait

netxmsd: show queues
Condition poller                 : 0
Configuration poller             : 0
Data collector                   : 330
Database writer                  : 0
Event processor                  : 0
Network discovery poller         : 0
Node poller                      : 0
Routing table poller             : 0
Status poller                    : 0

netxmsd: show status
ERROR: Invalid SHOW subcommand

netxmsd: show stats
Total number of objects:     103
Number of monitored nodes:   36
Number of collectable DCIs:  383

netxmsd: show watchdog
Thread                                           Interval Status
----------------------------------------------------------------------------
Item Poller                                      20       Running
Syncer Thread                                    130      Running
Poll Manager                                     60       Running


Please note that I have changed the object names to: [Censored]

Thanks again 

As of yesterday I started monitoring all the nodes in my own network as a big test,
however I'm trying to log in today and the console is stuck at "synchronizing objects"

The core service and SQL are still running, but I will restart them both now to see if that solves the problem.

This the log file data:


[30-Apr-2008 15:16:05] Thread "Item Poller" does not respond to watchdog thread
[30-Apr-2008 15:17:05] Thread "Poll Manager" does not respond to watchdog thread
[30-Apr-2008 15:18:45] Thread "Syncer Thread" does not respond to watchdog thread


This is a very big problem as I want to keep it running 24/7, any way to determine what caused this and how it can be prevented
in the future?

Thanks in advance.

-UPDATE
I couldn't stop the mysql service, but I stopped and started netXMS core and I can log in now.

-UPDATE2-
Deleting DCI'S is causing timeouts, related problem? I think so.

-UPDATE3-
It was just a matter of time, it happened again


[30-Apr-2008 16:29:36] Log file opened
[30-Apr-2008 16:29:37] Database driver "mysql.ddr" loaded and initialized successfully
[30-Apr-2008 16:29:37] Stalled database lock removed
[30-Apr-2008 16:29:39] Failed to load template object with id 412 from database
[30-Apr-2008 16:29:39] NetXMS Server started
[30-Apr-2008 16:34:39] Thread "Item Poller" does not respond to watchdog thread
[30-Apr-2008 16:35:59] Thread "Poll Manager" does not respond to watchdog thread


Great, thanks

It would be great if the agent (for windows) had the option to read out the available updates for windows, do you think it would be possible to implement this function or is it a bad idea?

Is it possible to exclude polling for certain DCI's at set times?

For example I do not want the DCI's in my server template to check from 19:00-08:00 how
would I do this?

Bump

Sorry, I'll explain a little better.

DCI 1) Monitors a windows XP service through SNMP.

When this service is stopped, this DCI does not switch to status 4, instead it turns red.
Now I want to know how I can make a policy for this DCI if the status never changes?

How about: ChildStatus(408) ?

Because that isn't working, and 408 is the ID of the DCI i want to monitor 

I have a specific service that I want to monitor to see if it's up or not.

However the problem is, when it goes down (service stops) it's status stays at "0" and it just turns red, and I can't monitor it!

How do I get this DCI to switch to status 4 when it's down just like the internal status check?

Thank you, I tested this with prime95 and you are correct, as always 

Thanks, works like a charm 

Some questions about the parameters:

System.cpu.usage & System.CPU.Usage($1)

The system.cpu.usage readout is fine, but what will happen if I run this parameter on a node with multiple cores?  I know the system.cpu.usage($1) is used for multiple CPU'S but running this parameter on one of my dual core machines gives me incorrect information.   I'm just using "0" and "1" parameter for this, is this correct? and where can I find the core ID?

What's the deal? What parameter should I be using for monitoring CPU LOAD on DUAL CORE machines?   And which parameter for monitoring CPU LOAD on Hyperthreading machines?

Just a little confused