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.

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

0_1531597915961_f32d1fe4-f814-4f9c-b1b4-dca87337e8b1-image.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.

Hi Dan,

One of the easiest ways to ensure Mango restarts on crash is to touch /path/to/mango/RESTART which will cause the ma-start.sh or ma-start.bat script to start Mango again when the currently running Mango finishes. Scripts in Mango/bin/ext-enabled are called with the first argument 'restart'

To your question, yes it is possible to schedule a restart from within a Mango script, but there aren't any wrapper hooks, so you have to do it the same way the modules page would,

com.serotonin.m2m2.web.dwr.ModulesDwr.scheduleRestart(); //Schedule restart for ten seconds from now.

or you can get whatever delay you want,

var timeout = com.serotonin.m2m2.Common.getMillis(com.serotonin.m2m2.Common.TimePeriods.MINUTES, 17); var lifecycle = com.serotonin.provider.Providers.get(com.serotonin.m2m2.IMangoLifecycle.class); lifecycle.scheduleShutdown( timeout, true /* restart */, null);

Did you set up the event handler on the data source event, as I instructed? I don't see an image of your event handler there.

You shouldn't need any configuration changes, the lost backdates were likely due to a corrupt shard that was repaired while the system was running and inserting data. This is a rare scenario and has been fixed in the next release.

Certainly!

I meant if the data source started (not Mango) on an second divisible by 30. You can just restart the data source to restart its poll timer.

No that was never written. One can do either, but one would have to use a scripting data source and perhaps supporting points to make it happen.

//Export all data for point cxtPnt into an SQL table... var pvd = com.serotonin.m2m2.Common.databaseProxy.newPointValueDao(); pvd.getPointValuesBetween( cxtPnt.getDataPointWrapper().getId(), 0, java.lang.Long.MAX_VALUE, function(pvt) { sqlContextPoint.set('(' + pvt.getValue().toString() + ',' + pvt.getTime() + ')', pvt.getTime()); //sqlContextPoint is an 'update tables only' point on an SQL data source });

And there would be a similar way to write those out to a file or wherever.

Hmm, then the SMTP settings are the issue. If you had it working in the past, I would recommend using those settings. Also, it would be good to try to send a few test emails in the period of time covered by the log file, otherwise there's no information in there relevant to the SMTP issue.