@cbyrne yes mostly but things have changed and I recently gave some training of which the results ended up in this repository:

https://github.com/infiniteautomation/ma-modules-contrib

I suspect you will need to clear the Browser cache. We are working on a permanent fix for Mango 4 that will go out will the full release.

Any chance you could tell me:

1. Did you have Mango 3.x running on that same host/port combo?
2. What beta version are you running?

@usi I just took a quick peek at the logs and can see one problem, however it isn't going to be the same thing that is causing those events to be raised in your first post.

The data source trying to convert the value using the multiplier setting on the data point. I would check all of your data points on that data source and confirm the multiplier is set to 1 (or something that you want to multiply by). It seems one (or many) of your points have something that isn't numerical set on that setting.

ERROR 2021-03-10T09:33:47,909 (com.serotonin.m2m2.util.timeout.TimeoutTask.run:61) - Uncaught Task Exception 
java.lang.NumberFormatException: null
	at java.math.BigDecimal.<init>(BigDecimal.java:497) ~[?:1.8.0_231]
	at java.math.BigDecimal.<init>(BigDecimal.java:383) ~[?:1.8.0_231]
	at java.math.BigDecimal.<init>(BigDecimal.java:809) ~[?:1.8.0_231]
	at com.serotonin.m2m2.modbus.rt.ModbusDataSourceRT.updatePointValue(ModbusDataSourceRT.java:404) ~[?:?]
	at com.serotonin.m2m2.modbus.rt.ModbusDataSourceRT.doPoll(ModbusDataSourceRT.java:230) ~[?:?]
	at com.serotonin.m2m2.rt.dataSource.PollingDataSource.doPollNoSync(PollingDataSource.java:228) ~[mango-3.7.7.jar:?]
	at com.serotonin.m2m2.rt.dataSource.PollingDataSource.scheduleTimeoutImpl(PollingDataSource.java:183) ~[mango-3.7.7.jar:?]
	at com.serotonin.m2m2.rt.dataSource.PollingDataSource$1.scheduleTimeout(PollingDataSource.java:85) ~[mango-3.7.7.jar:?]
	at com.serotonin.m2m2.util.timeout.TimeoutTask.run(TimeoutTask.java:59) ~[mango-3.7.7.jar:?]
	at com.serotonin.timer.Task.runTask(Task.java:179) ~[mango-3.7.7.jar:?]
	at com.serotonin.timer.TaskWrapper.run(TaskWrapper.java:23) ~[mango-3.7.7.jar:?]
	at com.serotonin.timer.OrderedThreadPoolExecutor$OrderedTaskCollection.run(OrderedThreadPoolExecutor.java:314) ~[mango-3.7.7.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_231]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_231]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_231]

I would check the work item priority for Excel reports in the System settings area.

Administration --> System settings --> Excel reports

The low priority pool generally has 1 processing thread in it (which can be configured in the thread pools system settings) and this means any task put in that pool will run when the thread is free to do the work. If you have many low priority tasks running around 1AM it will sit in a queue until it is processed.

You could either increase the low pool size or have it run in the medium priority pool.

And what @MattFox said, make your posts readable and you will get better help. A wall of poorly formatted text is very off-putting.

@Nurr

The LDAP module doesn't currently have any special handling for LDAPS that would use the mango HTTPS keystore. However from some light reading it may be possible to tell the LDAP connector where the key is by using these JVM Arguments which would go into the startOptions.sh script.

Try: Google -> Spring Security LDAP SSL

-Djavax.net.ssl.keyStore="C:/Program Files/Java/jdk1.7.0_79/jre/lib/security/cacerts"
-Djavax.net.ssl.keyStorePassword=changeit

There are more elegant ways to do this in code but the requirements for the module were for LDAP not LDAPS so this wasn't considered.

Hope that helps.

Either get more memory or try this env property:

#Set the number of files the database can have open at one time
db.nosql.maxOpenFiles=500

It will close/unmap files at the expense of cpu use. If this problem persists then try another stream type:

#Query Performance Tuning, File Access Type:Available[INPUT_STREAM,FILE_CHANNEL,RANDOM_ACCESS_FILE,MAPPED_BYTE_BUFFER]

db.nosql.shardStreamType=MAPPED_BYTE_BUFFER

@MattFox this page is a good read for what you are trying to do: https://docs-v3.mango-os.com/internal-task-performance?rq=priority

That explains each pool and what it is used for, that should give you an idea of where to start tuning. I usually setup a Watchlist using the Internal Metrics data source to watch the queue sizes of the pools and various other metrics while you change the settings.

@Nurr it is possible that you are seeing a rendered value which makes it look like there was a difference of 0.01 but if you look at the raw data you might find the difference to be slightly larger and being rounded by the TextRenderer on that point. Just a thought, the logging in your scenario works like I said about.

@Nurr never mind about the timestamps. You are using "Interval logging and point value changes". This type of logging will log every 5 minutes AND when the value changes.