MAMAS version 0.6.1 "early1" p1

• status: obsoleted by MAMAS v.0.7.0
• released at: 2022-12-06
• supported modes of operation:
  • production: Yes
  • free usage: Yes (included, 15 seats, 3 webtunnel, expires 2023-01-19)
• supported deployment modes:
  • DT SAAS / DT Cloud / DT Server Managed: Yes / No / Yes
  • Partner SAAS / Partner Cloud / Partner Server Managed: Yes / No / Yes
  • Customer self-managed: Yes
  • Private network: Yes
• support planned: until 0.6.2/0.7.0 release
  • See release table
• upgrade supported from:
  • Feature version 0.6.0 (See release table)
• target audience: early adopters
• showcase video: Showcase for MAMAS 0.6.x

Release notes - known issues, changes since last release

Version 0.6.1 is a patch version bringing various feature and usability fixes and slight improvements over the version 0.6.0, making the early adopter experience smoother. See below on the list of changes since last version.

To get more complete information about the branch 0.6.x as a whole, please see the Release page for version 0.6.0.

Known issues (updates with bugs being reported)

• On deployments where SSL certificate handling is offloaded to a service (e.g. Caddy or Nginx), the apache ssl module may not be enabled during deployment. This causes webtunnel functionality to fail.
  • Workaround: execute following commands as root user:
    • a2enmod ssl
    • systemctl restart apache2
  • Reported: 2022-Dec-09
  • Status: Fixed, available in 0.7.0
• On some deployments, there can be general problem with Webtunnel functionality. This could be caused by either the systemctl binary being located in /bin/systemctl with no link to that binary in /usr/bin/systemctl (A) OR incorrect rights on mamas user directory (/opt/cache_mamas/home).
  • Workaround for problem A: multistep, complex:
    • create link by executing ln -s /bin/systemctl /usr/bin/systemctl as root
    • remove all tunnels in MAMAS
    • edit your sudo rules for mamas. They are located in /etc/sudoers/mamas* where the number of files matches the number of MAMAS deployments on your server and the complete file name contains your domain.
      • you need to locate entries beginning with mamas that allows mamas daemon to reload the apache server after new tunnel definition has been created
      • you need to either edit them or copy these lines (3 of them) to new lines and edit those new lines
      • on the edited lines, the path /bin/systemctl needs to be replaced to /usr/bin/systemctl
      • NOTE that you can ignore lines starting with something else than mamas as only the mamas daemon has the path hardcoded. Other elements of MAMAS deployment are using the actual path, so other sudo rules are called and work as expected.
    • restart the server / container
    • setup the required tunnels
  • Workaround for problem B:
    • execute chmod 755 ~mamas. If not effective, you could need restarting the mamas and ssh service. If unsure how to do that, restart the server/container.
  • Reported: 2022-Dec-09 (A), 2022-Dec-10 (B)
  • Status: Fixed (both A and B cases), available in 0.7.0
• OpenWRT devices are dependent on curl library. During the release testing period, we found out that the curl library dependencies are broken in OpenWRT thus the OpenWRT MAMAS agent may be mulfunctioning depending on which curl library version is installed on the OpenWRT device. Additional facts:
  • Problem can appear on OpenWRT 21.02 and resolves around installing correct version (enforcing upgrade) of curl. See more on the OpenWRT forum post
  • Our humble tip is to run this command sequence (no guarantees given, better study the OpenWRT problem yourself, we are far from experts on OpenWRT):
    • opgk update
    • opkg upgrade libcurl4 (NOTE that without explicit "upgrade" of the libcurl4 package we have experienced no improvement)
    • opkg upgrade curl

Changes since version 0.6.0 "early1"

• Fixed bug causing wrong configuration for webtunnels read from DB after manual MAMAS service restart (e.g. when rebooting the server you deployed MAMAS on). This caused a need to setup tunnels anew after the MAMAS server or service restart.
• UI usability fix on agent - when agent has problems with communication to server, it is now visible in the main Advantech UI agent directly (line showing PID changes color and shows error counters, thus indicating there is problem).
• UI usability fix on server - some device selectors were showing just device IDs (without the accompanying device names if devices had names assigned). The alert definition UI and configuration cloning selector were updated to show also device names.
• Support displaying ICCID of first SIM card in the device details if the device sports a SIM card.
• Better information about version; added buildtag - visible in the About box
• Improvements to the upgrade process in both server and agents.
• Other small improvements, please see the About menu to review the complete list.
• For list of changes in 0.6.x please visit also the feature release 0.6.0 page