Thanks for your reply and adding the noSQL licence, @CraigWeb!

Regarding the other error: I wanted to migrate existing H2 data into noSQL and was mislead by the documentation:

The NoSQL migration can take several hours to complete but it will happen in the background.

My bad -- I thought it was a one-click solution given, that Mango knows which DB it is using and what the credentials are. Will report back when I had access to the client's server again. Thanks again for your help!

Hi everyone,

a customer of ours upgraded their evaluation to a commercial lite license and registering the GUID went smoothly. Unfortunately, the noSQL module was not installed during this process and hence is still shown as "not registered". There is also an error message when trying to migrate the existing data to the noSQL DB. I was told that "the NoSQL module only needs the core to be licenced to work." and that I shall ask in the forum about the latter issue. Has anyone an idea how to mitigate the communications link failure for a DB that is running on the same machine?

Thank you very much in advance for your help!

Best wishes,
Frank

Hi guys,

I ran into some troubles with the documentation / installation and wanted to let you know about it. The one I am referring to is hosted at: https://helpv4.mangoautomation.net/linux-installation and I am running a relatively clean and updated Opensuse 15.2

1. The install script fails when trying to install Mango 4.0 (or any other version than the default 3.6.6 for that matter):

Archive: /tmp/tmp.5ikghN5F2T
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of /tmp/tmp.5ikghN5F2T or
/tmp/tmp.5ikghN5F2T.zip, and cannot find /tmp/tmp.5ikghN5F2T.ZIP, period.

2. There is an error when trying to run "chown -R mango:mango /opt/mango" because there is no mango group yet.

3. The copy command fails because the unzipped mango archive does not have the overrides folder yet.

cp /opt/mango/classes/env.properties /opt/mango/overrides/properties/

4. manually starting Mango complains that the file does not exist...

linux-wh13:/home/fl/SW # sudo -u mango /opt/mango/bin/start-mango.sh > /dev/null &
[1] 13594
linux-wh13:/home/fl/SW # sudo: /opt/mango/bin/start-mango.sh: command not found

[1]+ Exit 1 sudo -u mango /opt/mango/bin/start-mango.sh > /dev/null

... and hence does start.

ls /opt/mango/bin/
certbot-deploy.sh genkey.sh getenv.sh install-mango.sh mango.service start-mango.sh start-options.sh stop-mango.sh

5. While installing the service file works, it does -- unsurprisingly -- not start Mango neither.

mango.service - Mango Automation
Loaded: loaded (/etc/systemd/system/mango.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2020-10-09 10:32:53 CEST; 2s ago
Process: 13198 ExecStart=/opt/mango/bin/start-mango.sh (code=exited, status=203/EXEC)

Oct 09 10:32:53 linux-wh13 systemd[1]: Failed to start Mango Automation.
Oct 09 10:32:53 linux-wh13 systemd[1]: mango.service: Unit entered failed state.
Oct 09 10:32:53 linux-wh13 systemd[1]: mango.service: Failed with result 'exit-code'.

FWIW, v3.7.7 runs beautifully on this machine.

Thanks in advance for any comments and help,
Frank

Congratulations and best wishes on this endeavour! The new layout for the documentation is easy on the eyes and very systematic.

@MattFox kindly developed a user module which extends the code of <ma-point-value> with two fields for "value-anchor" and "anchor-target". With this the popup and the link work properly. While there is a chance that this is feature creep, the modification is much better than the current behaviour which IMHO is a bug.

Anyway: All good now. Many thanks for your comments and help!

Hi Craig,

sorry for the late reply. I tried the options you cited and learned something new. Nice. But as you already guessed, the original problem persists.

True dat. We sleep when we're dead.

But when we are dad, we sleep as soon as the offspring lets us. At least I do.

That is all more than alright; please enjoy your weekend as much as you can in these strange times! The main use is that the user can click on the data point and be led to a different page. Popup with data point details is already bonus functionality. Thinking about it this way, it would even be an option to disable the bubbles for "statistics", "chart", "value table", and "point events". My users would likely not miss them ... no overlays, no problem.

Have a nice weekend!

Frank

Having tried your suggestion -- thanks! -- I would like to be more specific: The datapoint popups which create an overlay are the troubling ones. "Data point details" opens the proper link (the data point details), but the other ones show the overlay and additionally open a new tab with the link.

Even after restructuring thrice the problem description sounds odd. Apologies for that. Maybe the code helps...

<a href="http://localhost:8080/ui/watch-list/" target="pointdata">

<ma-point-value style="position: absolute; left: 0px; top: 350px; width: 90px; height: 40px;" enable-popup="right" quick-info="false" point-xid="internal_mango_num_data_points"></ma-point-value>

</a>

The solution you suggested still works great, @MattFox! There is just one flaw: We added the "enable popup" option but if one clicks on said popup it opens the link as well as the data point page. The link seems to gets surround the the popop as well. We tried all directions for the popups but only got mixed results. In, the majority of cases the link opens as well and not only the data point page. Would you mind sharing your thoughts on this?

Nope, this data point does not recover by activating / deactivating it. And there is also nothing in the events log. After deactivation the screen looks as shown below, but reloading the page makes it look like the screenshot posted previously.

Here is a screenshot of the trouble maker.

`What field did you change? What type of data source is it? What version of the data source module are you running? How did you ascertain that it stopped updating?

I changed Point Properties --> Unit --> from "V" to "kV". The data source is a MODBUS TCP device and the module version is 3.7.0. The point is marked as unreliable and does not receive new values. I poll multiple values from the same devices and the other data points keep updating, just not this one. I tried this for some other devices and data points as well and always got the same issue -- with one difference: after logging out and in again most of my changes were "healed". The data points kept updating again. But some are stuck as "unreliable".

I don't know where daHz comes from. If I enter Hz100 I get hHz which is correct. If I enter Hz1000 I get kHz which is also correct. I can enter kHz just fine too.

As embarrassing it is, I cannot reproduce this one. After saving the data point unit it is not automatically updated in the data sources screen but reloading the website triggers the change and then the correct unit is displayed.

Thanks for your enlightening comments! The surprising element for me was that the unit was automatically changed and I did not know why.

But while playing around with units some more I encountered other bug-like behaviour: Tried to use a custom unit (kV) by entering "kV" in the respective field stopped updating my data point. So I changed everything back but the data point was not resurrected. In fact, all tags were gone. Retried with another unit ("Hz") and it showed the same behaviour. Is that intended (Mango 3.7.2)?

In the link @terrypacker and @CraigWeb posted (https://github.com/infiniteautomation/ma-core-public/issues/309) one user multiplies the unit with a number. I tried that, too ("Hz * 100"), but after saving the data point it would not update neither. Re-entering the datapoint dialogue the Unit was shown as "daHz". How do I get my frequency to be shown and calculated as kHz?

Hi Craig,

in your first sentence you're saying that using the suffix can have undesirable side effects and in your last sentence you say that it is an acceptable workaround. Which one is it? Very likely, the side effects are not that important to me... but still.

Anyway. Today I learned, that the folks who use the dashboards are OK with showing VA instead of VAR, so I will leave it just as it is.

Hi @Turbo, you seem to have lots of experience with this issue! I find it odd that the IA team is not tackling these issues... but then again, with the suffixes it is easy enough to fix. Thanks a lot for your answer! Under these circumstances I will not pursue this further and go with the suffixes.

Hi guys,

I might have found a bug. When I create a data point with the unit VAR, said unit is always shown as VA.

How to reproduce? Edit a data point, change the unit to VAR, hit save and and check the unit again.

Version of mango: 3.7.2

Thanks for your attention & Have a nice weekend,
Frank

Ah, that makes sense. I had tried several syntax variations but none of them opened a new tab.

Awesome! Had tried that at first but it hadn't worked. Must have been an error on my side because it now works like a charm. Thanks!

Purely out of interest: could the ng-click parameter get the job done, too? That's where I got stuck:

ng-click=$window.open(url, '_blank')