NetXMS Forum

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

millerpaint

@millerpaint

Topics

M

Out of space - CentOS and MySQL
Watching Ignoring Scheduled Pinned Locked Moved Support
4

0 Votes

4 Posts

25k Views

M

OK, good news: This command worked, with more parameters: du -h --max-depth=1 | sort -n I see now the problem is in /var/lib/mysql/ 110516876 netxxx.millerxxx.com.err This seems to be an error file, that is now massive? -Kevin C.
M

NetXMS won't start - 1.2.17 on CentOS
Watching Ignoring Scheduled Pinned Locked Moved Support
5

0 Votes

5 Posts

43k Views

V

Hi, nxdbmgr supposed to be able yto handle upgrades from any version to current. You can try to run upgrade again, just make sure you check and fix all issues with DB before starting upgrade. If you are interested in paid support from Raden Solutions, just send me private message. Best regards, Victor
M

Out of disk space ... again
Watching Ignoring Scheduled Pinned Locked Moved Support
3

0 Votes

3 Posts

11k Views

M

Thanks for the quick reply. I checked MySQL first, and although binary logging was not enabled, the mysqld.log was huge! I removed it, and all is good now. I'll setup a log rotation script, and this problem should not re-occur. -Kevin C.
M

Invalid network mask - v 1.2.17
Watching Ignoring Scheduled Pinned Locked Moved Support
4

0 Votes

4 Posts

17k Views

V

Yes, nodes will be rediscovered - the only problem if you have configured some data collection on them - all collected data will be lost. If this is not the case then you can just delete them with subnets. Best regards, Victor
M

Not discovering all nodes
Watching Ignoring Scheduled Pinned Locked Moved Support
3

0 Votes

3 Posts

16k Views

M

The nodes responded to pings from the server. So I took another look at my discovery settings, and then recalled I had filtered out the upper end of the IP address ranges of those networks when I initially installed NetXMS ! I modified those filters, saved it, and within 5 minutes, NetXMS discovered the missing nodes... chalk this up to pilot error -Kevin C.
M

Change node down threshold for some (not all) nodes
Watching Ignoring Scheduled Pinned Locked Moved Support
7

0 Votes

7 Posts

24k Views

V

Looks like result of database corruption. If I remember correctly lost_interface_#### objects was created in some older versions after errors. Current version should not create them. As they likely had unreachable IP addresses, status poll just take longer due to timeouts. Best regards, Victor
M

Java console - exit code=13
Watching Ignoring Scheduled Pinned Locked Moved Support
2

0 Votes

2 Posts

16k Views

M

Got this working; as it turns out, the Java update uninstalled all of the "old" versions on my laptop, including the 64-bit version I was using for the NetXMS console. I downloaded the 32-bit version of the console, and it launches fine, no error. -Kevin C.
M

Node down - but for how long? And high latency notification
Watching Ignoring Scheduled Pinned Locked Moved Support
7

0 Votes

7 Posts

33k Views

N

Hi Victor, Yes, that attribute is set and the script works as well. But since that day I haven't received this alarm anymore. And it seems that it is working fine now. I guess i will need to set up event for this alarm, and monitor this for a while. Thank you! Best regards, Nikk
M

Out of memory NetXMS v1.2.5
Watching Ignoring Scheduled Pinned Locked Moved Support
32

0 Votes

32 Posts

181k Views

M

OK thanks - all log files you have requested from valgrind have been sent to that email address. -Kevin C.
M

Host name changes - not updating
Watching Ignoring Scheduled Pinned Locked Moved Support
3

0 Votes

3 Posts

28k Views

M

Excellent, thanks ! I will give this a try. -Kevin C.
M

Discovery issue - over 40 subnets
Watching Ignoring Scheduled Pinned Locked Moved Support
11

0 Votes

11 Posts

68k Views

M

Working !! I just had to change the Network Discovery Configuration, and un-check the following: Accept node if it has NetXMS agent. Accept node if it has SNMP agent. The ONLY option I have checked is: Accept node if it is within given range or subnet. So it seems that maybe it is working as designed after all
M

Change server IP address - now DB locked
Watching Ignoring Scheduled Pinned Locked Moved Support
2

0 Votes

2 Posts

30k Views

M

Ooops. I searched on Google, and found my answer on this forum: https://www.netxms.org/forum/general-support/netxms-database-locked-to-ip-adress/ Working flawlessly now! -Kevin
M

No Network Map
Watching Ignoring Scheduled Pinned Locked Moved Support
4

0 Votes

4 Posts

40k Views

V

Hi! Due to various reasons there was a big pause in development. I hope to make a 1.2.4 release this week. Automatic maps already working Best regards, Victor
M

Too many alerts
Watching Ignoring Scheduled Pinned Locked Moved Support
8

0 Votes

8 Posts

35k Views

M

OK great, thanks Victor! I am now monitoring 50 remote networks, and so far I am happy with NetXMS (and I have yet to upgrade to the latest 1.2.4 version)! -Kevin
M

Host polling - exclusion window
Watching Ignoring Scheduled Pinned Locked Moved Support
5

0 Votes

5 Posts

46k Views

M

Ah, of course. I did not take into account the 59 minutes, and 59 seconds! I will also look at the Saturday and Sunday code example you provided. Thank you! -Kevin
M

Host name display
Watching Ignoring Scheduled Pinned Locked Moved Support
2

0 Votes

2 Posts

12k Views

V

Hi! Currently it's not possible. I'll add this as feature request. Best regards, Victor
M

Manually adding nodes
Watching Ignoring Scheduled Pinned Locked Moved Support
5

0 Votes

5 Posts

22k Views

M

OK Victor, I ran the db check, and it did find several inconsistencies in the database (it seems all were related to the 192.168.1.0 subnet that I had removed). Rather than go thru each of them, I ended up dropping the database, then re-creating it. Everything is good now, and I am using autodiscover again but this time with a filter, so that it only looks at 50 of our subnets.