How to change the http sending value parameter

jmatos

Hi Phil,

It does not work... :(

So I have cross my fingers and do a version upgrade to MANGO 3...

Now MANGO's not responding! (snif!). "ERR_CONNECTION_REFUSED" is all I get as browser response. The Webmin is working fine. Is there something else I can try before I restore the Mango directory ?

Thank you

phildunlap

Hi Jose,

I wouldn't expect the issue you're describing to be resolved by upgrading. But, you probably have an error in startup that we could see if you attempted to start Mango manually on the command line.

So navigate to Mango/bin and run either ./ma.sh start or ma-start.bat

Actually figuring out what's going on in your situation may be too difficult through the forum. I understand the issue to be something like...

Mango 1 polls a data source
Many points links set a point on Mango 1 many times.
The values of that point are published through an HTTP publisher
The receiving end is not ending up with the same set of data as the sending end, but no errors are being recorded on either Mango

There's a lot to explore there.

jmatos

here is the result

mango@mangoES3249:/opt/mango/bin$sudo ./ma.sh start
sudo: unable to resolve host mangoES3249
[sudo] password for mango:
sudo: ./ma.sh: command not found
mango@mangoES3249:/opt/mango/bin$ma.sh start
-bash: ma.sh: command not found
mango@mangoES3249:/opt/mango/bin$dir
ext-available  ext-enabled  h2-web-console.bat  h2-web-console.sh  ma-init.sh  ma.pid  ma-restart.sh  ma.sh  ma-start.bat  ma-start.sh  ma-stop.sh  upgrade.bat  upgrade.sh

phildunlap

Try...

sudo /opt/mango/bin/ma.sh start

sudo su; ./ma.sh start

phildunlap

It's possible ma.sh isn't executable, do sudo chmod +x /opt/mango/bin/ma.sh

jmatos

to all I get the same result:

sudo: unable to resolve host mangoES3249

unless for

sudo su; ./ma.sh start

where I get the PuTTY screen again - with the calendar, cpu info, etc. - as when I entered

phildunlap

You would do the ./ma.sh start after the sudo su scrolls by the login screen again. When you're root@mangoES3249:~

Hmm. That message suggests something is amiss in your /etc/hosts or /etc/hostname file. I bet you've got a line like 127.0.1.1 mangoes in your /etc/hosts file, where you'd want to change it to 127.0.1.1 mangoES3249 then log out and in again. The unable to resolve host message should be gone.

jmatos

@phildunlap

you have right with the issue 127.0.1.1 mangoes. I fix it but then I get

root@mangoES3249:/opt/mango/bin$./ma.sh start
MA_HOME is /opt/mango
./ma.sh: line 31: /opt/mango/bin/ma-start.sh: Permission denied

phildunlap

sudo chmod +x /opt/mango/bin/*.sh

jmatos

It works!!!
What could be wrong?

Thank you very much. I can sleep better this night :)

phildunlap

Well, the upgrade could have failed during the unzip, then it probably wouldn't have chmod'ed the bin directory properly. I would wonder if anything else did occur properly in the upgrade process.

jmatos

After the upgrade I get

???systemSettings.noSqlDatabaseSize(i18n_pt_PT)???

in the System settings > System Information section when refreshing the database size.

Should I worry about or is only a none translated item?

phildunlap

It is just a missing translations key. it was missing from the base translation file even, which is why you saw that instead of English.

Thanks for bringing this to our attention!

jmatos

please answer to the issue about the license that I sent you to support.
Thank you

phildunlap

I have answered your email.

jmatos

Now within MANGO v3 UI, once in awhile I see the following messages in the bottom screen:

connectivity lost... ok
(after 2 sec)
connectivity to MANGO API as been restored

My mangoApi module is 3.1.1

Once mangoNoSqlDatabase is depending on it, could this be in any way related to the problem that we have? (please see bellow reminder text). Is there any log where I can see more info? I search in the ma-log and found nothing.

(reminder)
let me remind you: when more than two simultaneous BACnet devices have it value switched only aleatory two reach's the http publisher. This is the only issue that holding us down to close the project... :-(

Thank you,
Jose

phildunlap

Hi Jose,

I probably can't solve the simultaneous alarms issue through the forum, since I don't really have a clear idea of what's going on and would have to investigate. You could contact us about direct support on that issue.

You can probably get more information about why it's displaying that connectivity message if you watch the browser developer tools' network tab. My guess is some requests are timing out or erroring. You could also consider enabling debug logging by switching the log4j2.xml files in Mango/classes/ and reloading your logging settings, either in the Log4J Reset section of /system_settings.shtm or by restarting Mango.

I would not expect it to be related to the dependency of the NoSQL database on the API. It just provided a new set of endpoints for saving point-time-jsonObject information, shouldn't affect existing things as I'm not aware of any built in features using that database yet.

jmatos

I will come back to the simultaneous alarm issue after I collect some more info.

meanwhile, after upgrade to MANGO v 3...

A) In Home I can not see the number of datasources, datapoints, etc. in the up right corner of the square. Also, Active Sessions, Event Detectors and Mailing Lists are not clickable.

B) !!systemSettings.lastUpgrade!! in Administration > System settings > System information, with 1500555481 as date.

and this one, last two from ma.log?

WARN  2017-07-24T14:50:10,495 (com.serotonin.m2m2.util.timeout.TaskRejectionHandler.rejectedTask:77) - Rejected task: User event cache cleaner because Task Queue Full 
ERROR 2017-07-24T14:50:10,497 (com.infiniteautomation.nosql.MangoNoSqlBatchWriteBehindManager$StatusProvider.scheduleTimeout:726) - 7 BWB Task Failures, first is: Task Queue Full

thank you very much,
Jose

phildunlap

A) The numbers will only appear if you have a configured internal data source. You can reinstall the internal data source and it should create it for you.

B) This has been fixed.

I wouldn't expect either of those log messages to cause you problems, but you can probably make them go away by changing...

runtime.realTimeTimer.defaultTaskQueueSize=0 to runtime.realTimeTimer.defaultTaskQueueSize=2

in your env.properties file and restarting Mango.

jmatos

Hi Phil,

I send you a message to support.

Thank you,
Jose