NetXMS Support Forum

Hi,

I've set the EventLogRetentionTime setting to 90 days, but when I view the eventlog I only see the last two days, with no filter applied.
When I filter for a specific source or event I see about 30 days. How can I get the whole history?

Thanks in advance

Stefan

Thank You, noe I understood the way it works. That was a good tip.

Best regards

Stefan

Thanks for Your reply, but it doesn't answer my question. I know that those are DCIs coming from template definitions, but where do the templates named like the server come from (the DCIs marked in the red box)? I don't find them in the templates. Looks like they are created automatically somehow.

Hello,

when I check the Data Collection Configuration on each of my monitored server I see DCIs from a template that's named like the servername.
These DCIs are alwas related to drive size. (see attached screenshot)
As the Operating System template also includes this information I find the useless, but I have no idea how to get rid of them.

It's running on Windows. Configuration Polling was a good tip.
With debug level 6 I now see

Requesting list "PDH.ObjectCounters("{7ed66c3b-fa9a-4610-98c5-2f85f23d17d8}")"
2020.12.14 16:52:10.140 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 16:52:10.140 *D* [comm.cs.4          ]


When I run the configuartion poll manually I see an error in the NetXMS Console output saying:


[14.12.2020 16:52:11]    Checking EtherNet/IP...
[14.12.2020 16:52:12]    Cannot get device identity via EtherNet/IP (CONNECT FAILED)


When I check "Disable usage of EtherNet/IP for all polls" in the Polling properties, the error is gone

Not sure if this is required for some other things.

Hello,

I have a recurring error message in all of my agents log files, which I have no idea where they come from.
They appear about every hour and fill the log. The agent itself seems to have no problem with it.
Sometimes an agent crashes, but I don't know if it related to this.
Core agent version: 3.5-125-g35c04417dd
I checked if there is a DCI that is polled only once per hour, but there is none.

Here is an example of a log file:

2020.12.14 03:52:18.609 *D* [comm.cs.1378       ] Server ID set to 2C03B84F800043D7
2020.12.14 04:32:11.128 *D* [comm.cs.1379       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 04:52:22.593 *D* [comm.cs.1380       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 04:52:23.681 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 04:52:23.687 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 04:52:23.901 *D* [comm.cs.1380       ] Server ID set to 2C03B84F800043D7
2020.12.14 05:45:13.180 *D* [comm.cs.1381       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 05:52:27.989 *D* [comm.cs.1382       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 05:52:28.871 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 05:52:28.875 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 05:52:29.051 *D* [comm.cs.1382       ] Server ID set to 2C03B84F800043D7
2020.12.14 06:52:33.360 *D* [comm.cs.1383       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 06:52:34.309 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 06:52:34.312 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 06:52:34.478 *D* [comm.cs.1383       ] Server ID set to 2C03B84F800043D7
2020.12.14 06:55:10.729 *D* [comm.cs.1384       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 07:30:54.759 *D* [notifications      ] Notification housekeeper thread started
2020.12.14 07:30:54.768 *D* [notifications      ] Notification housekeeper thread stopped
2020.12.14 07:42:11.388 *D* [comm.cs.1385       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 07:52:38.808 *D* [comm.cs.1386       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 07:52:39.569 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 07:52:39.576 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 07:52:39.768 *D* [comm.cs.1386       ] Server ID set to 2C03B84F800043D7
2020.12.14 08:25:11.134 *D* [comm.cs.1387       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 08:52:44.273 *D* [comm.cs.1388       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 08:52:45.217 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 08:52:45.225 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 08:52:45.493 *D* [comm.cs.1388       ] Server ID set to 2C03B84F800043D7
2020.12.14 09:25:10.951 *D* [comm.cs.1389       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 09:52:49.715 *D* [comm.cs.1390       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 09:52:50.195 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 09:52:50.199 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 09:52:50.400 *D* [comm.cs.1390       ] Server ID set to 2C03B84F800043D7
2020.12.14 09:55:10.474 *D* [comm.cs.1391       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 10:35:10.262 *D* [comm.cs.1392       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 10:52:55.012 *D* [comm.cs.1393       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes
2020.12.14 10:52:55.706 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 10:52:55.711 *W* [                   ] H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems (The specified object was not found on the computer.)
2020.12.14 10:52:55.987 *D* [comm.cs.1393       ] Server ID set to 2C03B84F800043D7
2020.12.14 10:55:25.283 *D* [comm.cs.1394       ] Server capabilities: IPv6: yes; bulk reconciliation: yes; compression: yes


I have this problem since a while now. I think it started with 3.1. It's the same problem as described here:
https://www.netxms.org/forum/general-support/some-internal-dcis-change-to-unsupported-after-upgrade-to-3-1-343/msg27721/#msg27721

Every day i get these alarms (see screenchot) and just terminate them. Disabling in template doesn't help, as they get recerated.

How can I avoid to get these alarms?

I use the latest NetXMS Version with SQL Server 2016.

Best regards

Stefan

Thank You, I'll try this.

Regards

Stefan

Hi,

I know this sounds strange, but let me explain why I need this.
We have some test servers we only need 2 to 3 times in  the year and we pay for them only when the are running on a hourly base.
It happens that we miss to shut down these servers which leads to unnecessary costs.
So what i need is:

- A daily alarm if the server is running
- No alarm if the node is down, like NetXMS is doing by default I think and I found no way to change this. I can't find what is fireing the "SYS_IF_DOWN" event.

Can someone give me a hint on ho to achieve this?

Best regards

Stefan

I finally found the problem. Man, I'm so stupid. I forgot to add the instance name after the servername in the agent config

Hello,
is there a manual on how to setup and use the reporting functions in NetXMS 3.5 under Windows?
All I found is this https://wiki.netxms.org/wiki/Reporting_server_setup, but it looks outdated to me and it's not for Windows.

Thanks

Stefan

Hello,

I'm monitoring a webservice using NetXMS and want to restart the windows service that's responsible for this webservice, in case of a returnvalue other then HTTP 200.
The monitoring already works fine and I get notified when the returnvalue is different to 200.
The service itself is running when I check it, but it delivers no results anymore.
So I restart in manually at the moment to fix this.

How can I make NetXMS do the net stop/net start commands?

Best regards

Stefan

I still have this problem. Is there a way to get more information to find out where the problem is?

Hi, I'm back from vacation now and checked the configuration again.
TCP/IP is enabled for Native Client 32bit and 64bit. (see screenshots)
Is there anything I could test?

Best regards

Stefan

Hi Victor,

I will check this, when I'm back from vacation in two weeks.

Regards

Stefan