@dan said in New installation strange errors:

/dijit/form/Form.js.map

What version of mango is this?
Can you have a look in your /opt/mango/web/resources folder if all the permissions are good there and if the directory has any content?

@sean if what you are trying to do does not need a time series history then I believe the JSON store is better suited for this. The JSON store is there to be used for static data. There is a limit on the size of the string that can be stored as a value.

@cmusselm that is not a list of successful polls it is a list of the latest polls that completed either successfully or with a timeout. An aborted poll happens when the duration of the current poll is longer than the poll interval. in other words, mango is still busy with the current poll when the next poll should happen so it aborts it and reschedules it.

@Nurr TCP sockets remain open until they are closed or broken, the keep-alive packet is used to check if the socket is still open, not to keep the socket open.
What the modbus data source does is :
TCP with keep alive:
Open a socket to the device
Poll for data
Wait for interval
Poll for data
(if at any time the TCP connection is closed it will reopen it)

TCP without keep alive:
Open socket to device
Poll for data
close Socket
Wait for interval
Open socket to device
Poll for data
close Socket

@cmusselm Those warnings are coming from the rest controller. It seems like there are dashboards that have opened WebSockets to get updates on those points and the WebSocket messages are falling. As to the number of warnings, this would depend on the number of datapoints x the number of WebSockets opened on each point.

Hi Nurr

This could be a bug but we would need more information on what is happening. If the data source is "not able" to read values there should be an error message or a log entry...

Hi @MattFox

We recently discovered that the high-priority thread pool cannot be set higher than 100. If it is set above 100 Mango will not be able to boot up if it restarts. As for what to set them to for now I don't see why to not set it to 100. Once you are able I would just increase it by like 50% and see if the performance improves.

@NinoK is your ssh access through cloud connect or do you have a direct network connection to the mangoES. I you have ssh access that is not through cloud connect you will not need to drive out as you can fix the failed upgrade through ssh.

Changing the tag will not cause loss of data. Neither will changing the XID from within mango. Something else must have happened.

Hi @cwangv there is a use cron checkbox at the top which brings out the corn pattern input.