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 - deepb

#1
No error in MariaDB...

2024-05-13 16:46:02 0 [Note] C:\Program Files\MariaDB 10.4\bin\mysqld.exe (initiated by: unknown): Normal shutdown
2024-05-13 16:46:02 0 [Note] Event Scheduler: Purging the queue. 0 events
2024-05-13 16:46:02 0 [Note] InnoDB: FTS optimize thread exiting.
2024-05-13 16:46:02 0 [Note] InnoDB: Starting shutdown...
2024-05-13 16:46:02 0 [Note] InnoDB: Dumping buffer pool(s) to C:\Program Files\MariaDB 10.4\data\ib_buffer_pool
2024-05-13 16:46:02 0 [Note] InnoDB: Instance 0, restricted to 16054 pages due to innodb_buf_pool_dump_pct=25
2024-05-13 16:46:02 0 [Note] InnoDB: Buffer pool(s) dump completed at 240513 16:46:02
2024-05-13 16:46:04 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-13 16:46:04 0 [Note] InnoDB: Shutdown completed; log sequence number 12673536826768; transaction id 626221754
2024-05-13 16:46:04 0 [Note] C:\Program Files\MariaDB 10.4\bin\mysqld.exe: Shutdown complete

2024-05-13 16:46:04 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-13 16:46:04 0 [Note] InnoDB: Uses event mutexes
2024-05-13 16:46:04 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-05-13 16:46:04 0 [Note] InnoDB: Number of pools: 1
2024-05-13 16:46:04 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-13 16:46:04 0 [Note] InnoDB: Initializing buffer pool, total size = 2G, instances = 8, chunk size = 128M
2024-05-13 16:46:04 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-13 16:46:07 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-13 16:46:07 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-13 16:46:07 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-13 16:46:07 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
2024-05-13 16:46:07 0 [Note] InnoDB: Waiting for purge to start
2024-05-13 16:46:07 0 [Note] InnoDB: 10.4.25 started; log sequence number 12673536826768; transaction id 626221755
2024-05-13 16:46:07 0 [Note] InnoDB: Loading buffer pool(s) from C:\Program Files\MariaDB 10.4\data\ib_buffer_pool
2024-05-13 16:46:07 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-13 16:46:07 0 [Note] Server socket created on IP: '::'.
2024-05-13 16:46:07 0 [Note] Reading of all Master_info entries succeeded
2024-05-13 16:46:07 0 [Note] Added new Master_info '' to hash table
2024-05-13 16:46:07 0 [Note] C:\Program Files\MariaDB 10.4\bin\mysqld.exe: ready for connections.
Version: '10.4.25-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
2024-05-13 16:46:22 8 [Warning] Aborted connection 8 to db: 'netxms' user: 'netxms' host: 'localhost' (Got an error reading communication packets)
2024-05-13 16:47:00 0 [Note] InnoDB: Buffer pool(s) load completed at 240513 16:47:00
2024-05-13 16:48:20 9 [Warning] Aborted connection 9 to db: 'netxms' user: 'netxms' host: 'localhost' (Got an error reading communication packets)
2024-05-13 16:49:23 10 [Warning] Aborted connection 10 to db: 'netxms' user: 'netxms' host: 'localhost' (Got an error reading communication packets)

I didn't keep a database backup. I don't know what to do now!!

This upgrade has proved to be too costly for me.
#2
Windows event logs have the below MariaDB error:

Aborted connection 40 to db: 'netxms' user: 'netxms' host: 'localhost' (Got an error reading communication packets) 

Do I have to upgrade MariaDB?

Please help in resolving this issue.
#3
I'm facing exactly the same issue. I didn't take database backup so cannot go back to the old schema version either.
#4
Hi,

I upgraded from 4.5.6 to 5.0.2 and NetXMS server refuses to start. I'm using MariaDB 10.4. 

Your database has format version 50.32, but server is compiled for version 50.39

Running  nxdbmgr.exe upgrade has no effect/output either.

C:\NetXMS\bin>nxdbmgr.exe upgrade
NetXMS Database Manager Version 5.0.2 Build 5.0-878-gccaeca5869 (UNICODE)

Upgrading database...
Upgrading from version 50.32 to 50.33

C:\NetXMS\bin>

Please help.
#5
Upgraded to v4.5.6 but the problem with maps persists. 
#6
Hi,

I am reading SNMP  Objects ifHCOutOctets(Counter64) and ifHCInOctets ( Counter64 ) from switch interfaces every 60 secs and then Transformation Average Delta Per Second along with script $1*8 to get interface bandwidth in bits/sec. The problem is that this is giving me exaggerated values in full load condition - consider 11 or 12 Mbps on a 10 Mbps channel. Please help in sorting this issue.

Regards,
Deep
#7
General Support / Changes in Maps not getting Saved
March 28, 2024, 08:35:05 AM
Hi,

Ever since I upgraded to v4.5.4 I've observed that changes made in maps (like creating a link, changing text box color etc.) are not getting saved sometimes. The problem is erratic. Please help to resolve this issue.

Thanks
Deep  
#8
General Support / Re: JVM Monitoring
December 27, 2023, 09:30:47 AM
It didn't make any difference. Same error.
#9
General Support / Re: JVM Monitoring
December 20, 2023, 08:02:05 AM
Hi Victor,

The agent is installed on a Windows machine, so I replaced the jmx.jar at \lib\java and now I'm getting the below given error:

2023.12.20 11:01:42.028 *D* [comm.cs.1          ] Requesting metric "JMX.Memory.Heap.Current(name)"
2023.12.20 11:01:42.439 *D* [                   ] JMX: cannot setup connection to service:jmx:remote+http://localhost:9990
2023.12.20 11:01:42.440 *D* [                   ] JMX:   java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:271)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   org.wildfly.common.context.ContextManager.get(ContextManager.java:242)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   org.jboss.remoting3.EndpointImpl.construct(EndpointImpl.java:231)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   org.jboss.remoting3.EndpointBuilder.lambda$build$0(EndpointBuilder.java:128)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   java.security.AccessController.doPrivileged(Native Method)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   org.jboss.remoting3.EndpointBuilder.build(EndpointBuilder.java:128)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:204)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:156)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:103)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   org.netxms.agent.jmx.Server.connect(Server.java:95)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   org.netxms.agent.jmx.Server.getAttributeValue(Server.java:234)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   org.netxms.agent.jmx.JmxPlugin$JmxObjectParameterAdapter.getValue(JmxPlugin.java:278)
2023.12.20 11:01:42.440 *D* [                   ] JMX:   org.netxms.agent.SubAgent.parameterHandler(SubAgent.java:395)
2023.12.20 11:01:42.441 *D* [                   ] JAVA: Exception in parameter handler: java.lang.NullPointerException: null
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:271)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   org.wildfly.common.context.ContextManager.get(ContextManager.java:242)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   org.jboss.remoting3.EndpointImpl.construct(EndpointImpl.java:231)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   org.jboss.remoting3.EndpointBuilder.lambda$build$0(EndpointBuilder.java:128)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   java.security.AccessController.doPrivileged(Native Method)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   org.jboss.remoting3.EndpointBuilder.build(EndpointBuilder.java:128)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:204)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:156)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:103)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   org.netxms.agent.jmx.Server.connect(Server.java:95)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   org.netxms.agent.jmx.Server.getAttributeValue(Server.java:234)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   org.netxms.agent.jmx.JmxPlugin$JmxObjectParameterAdapter.getValue(JmxPlugin.java:278)
2023.12.20 11:01:42.441 *D* [                   ] JAVA:   org.netxms.agent.SubAgent.parameterHandler(SubAgent.java:395)
2023.12.20 11:01:42.442 *D* [                   ] JAVA: SubAgent::parameterHandler("JMX.Memory.Heap.Current(name)", "JMX/JMX.Memory.Heap.Current(*)"): exception in Java code

Agent config file is as below:
MasterServers = 10.14.50.82
ConfigIncludeDir = C:\NetXMS\etc\nxagentd.conf.d
LogFile = C:\NetXMS\log\nxagentd.log
FileStore = C:\NetXMS\var
SubAgent = winperf.nsm
SubAgent = java.nsm
DebugLevel = 6

[JAVA]
Jvm = C:\Program Files\Java\jdk1.8.0_202\jre\bin\server\jvm.dll
Classpath = C:\NetXMS\lib\java\tools.jar;C:\NetXMS\lib\java\jboss-client.jar;C:\NetXMS\lib\java\jboss-cli-client.jar;
Plugin = jmx.jar

[JMX]
Server = name:service:jmx:remote+http://localhost:9990
#10
General Support / Re: JVM Monitoring
December 14, 2023, 02:25:06 PM
Added jboss-client.jar using Classpath but that didn't solve the problem. Still getting  java.net.MalformedURLException: Unsupported protocol: remote+http
#11
General Support / Re: JVM Monitoring
December 11, 2023, 02:40:43 PM
I'm using Server = name:service:jmx:remote+http://localhost:9990 as applicable for JBoss EAP 7.1/Wildfly 11

This is throwing, Exception in parameter handler: java.net.MalformedURLException: Unsupported protocol: remote+http

I'm supposed to include jboss-client.jar in the application(netxms agent) classpath. Is it possible in NetXMS agent to include an external jar?
#12
General Support / Re: JVM Monitoring
December 05, 2023, 09:31:35 AM
    Hi,

    So, in agent configuration file, under [JMX] if I define Server=servername:login/password@url, then Parameter becomes  JMX.Memory.Heap.Current(servername), right? And if I'm connecting to local Wildfly JMX then I should write Server=servername:wildfly/wildfly@localhost:9990. Is this OK? I'm confused about how to mention the port number.
     I have tried all 3 formats, none working.
    1. name:url
    2. name:login@url
    3. name:login/password@url

    Though I'm able to connect to local Wildfly through JConsole/VisualVM.

    Please guide.

    Regards,
    Deep
#13
General Support / JVM Monitoring
December 01, 2023, 10:24:46 AM
Hi,

I'm new to NetXMS and want to monitor JVM as given in JVM monitoring — NetXMS Administrator Guide (4.4.3).
 
I have created new DCI parameter as below:

Parameter : JMX.Memory.Heap.Current({instance})
Instance Discovery Method : Agent List

What should be the List name? Is any filtering script required?  Please help!