Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

Alas 2.8 is not likely to get fixes for this sort of thing. This issue has certainly been fixed, as I mentioned. Did someone from your group call and leave a voicemail about this thread? It was not easy to make out their email address from their message (but it was a gmail address) and they seemed to mention this thread. They said they had compiler output after upgrading, but were getting an error which they provided an incomplete description of. If that was on this issue, could you post the output of the compiler here if you would like help getting through compilation issues?

Hmm, that looks okay. I wonder if maybe there's another cron definition invoking the script? You could try commenting out the line that tries to invoke /usr/sbin/systemInfo/timeAlive in /usr/sbin/systemInfo/getAll to see if that error is what's getting there, but I have the same line in the device I'm looking at and it doesn't produce /var/mail/mail contents. That definitely looks a lot like what was happening when the output of the cron job was not being redirected to /dev/null

@joelhaggar : Thanks! I got it~ Vincent

@phildunlap Thanks for the help. Now the data points have started coming up itself.

I used that function because it will give a java.util.List which we could addAll to the other list acquired the same way. You could also use the lastValue function, as described in the JavaScript help, or simply use the .value and .time from the point (which actually wouldn't work quite right here because we need to go through the text renderer, and a .value is a primitive data type usually instead of a DataValue object.

I would not expect 2000 - 3000 Modbus points polled perhaps every 5 seconds to overwhelm the ES from a data acquisition standpoint. Were you able to get it started and running again?

It looks like @leandro is opening the websocket connection from a browser, in which case only session authentication is an option. You can't set the Authorization header using the browser WebSocket API.

I replied via email to check for /opt/mango/hs_err* files.

Weird! I would try copying your databases folder into the new installation. If that works, I would stop Mango, move the old installation directory, move the new one where the old one was, and start Mango again, which will get the license working.

@phildunlap Hi, I've disconnected the other MangoES from the network, now I have only one that is getting data from the PLC, and I let it to run a while and I don't have any discarded polls. Thank you!

@phildunlap I moved enable-alph extension script to ext-enable folder, and also I made the SSL settings like before but I get the same errors and I couldn't navigate to the web page.

@phildunlap Thank you, that has it fixed. I appreciate your quick response. Bryce

You don't have any modules installed. It looks like you downloaded only the core. You need to download one of the bundles from: https://store.infiniteautomation.com/core [image: nh0poAD.png]

@jackchang I know this was 2 years ago, but if you're still around could you point me to which RS232 to RS485 converter you used?

Hi benaznbe, You need to check the log files. You can also try starting it on the command line using either cd /path/to/Mango/bin; ./ma.sh start or cd C:\Path\To\Mango\bin && ma-start.bat and post the output here.

You read the end of it, looking for a line that begins with ERROR and then you either deduce the next step to take by searching the error, which I encourage, or you post it here with a line containing three ``` marks above and below the copy-pasted text so that the lines format nicely. If you have a bash shell you can tail -f logs/ma.log and then cause the server error to see the relevant information that would enable me to help you, or you to help yourself.

Worked with Rollup Type, the file is ok now. Thank you!

I've copied mah2.h2.db and the other two files and than I've restored my NoSQL backup to mangoTSDB folder and worked perfect. Thanks!

@anmont You are not wrong, it probably should have said that. It does say we recommend JDK 8 on the store's download page, but it doesn't say the others wouldn't have worked. However, we are actively addressing compatibility issues. If you click the like to the known issue you will see that it's ready for testing. Mango 3.4, the beta of which is released, can be launched on Java 9 without encountering that illegal access exception. There may be lingering issues yet undiscovered, but you can definitely use Java 9 now! I haven't tested JDK 10 with it.