Hey Mango community,
We're excited to share that Radix IoT has launched a brand new website! We've put a lot of work into making it cleaner, easier to navigate, and a better reflection of everything we've been building.
Whether you're a long-time Mango user or just getting started, head over and take a look. You'll find:
Check it out at Radix IoT and let us know what you think!
Hey everyone,
I wanted to see if anyone here has started using Portfolio Manager (Pi‑Portfolio) and would be willing to share their experience so far.
Specifically, I’m curious:
For reference, this is the documentation site Pi‑Portfolio is based on:
👉 https://docs-v5.radixiot.com/pi-portfolio-help
If you’ve had hands‑on time with it—even in a limited or test capacity—I’d love to hear your thoughts.
Thanks in advance.
@mihairosu FYI - Image issue with the forum has been fixed.
Hello @mihairosu,
It sounds like your diagnosis is on the right track. Here are the most likely causes based on what you’ve described:
Users roleIf the guest account was created manually rather than through the usual user-creation workflow, it’s possible it never received that role.
You can verify under Administration → Users → guest.
Anonymous, and any point that does not allow Anonymous access will simply disappear with no warning.Also, your example URL uses:
autoLoginPassword=guest1234
But you mentioned the password is guest. If those don’t match, the login will fail and the session becomes anonymous.
Hello @mihairosu, Single data point not publishing from MangoES to MangoEnterprise, steps to try:
If other points on the same publisher are working but one specific point is not arriving on the Enterprise side, the most common cause is an XID mismatch introduced when the point was removed and re-added to the publisher. Work through these steps in order:
On MangoES:
On MangoEnterprise:
To fix:
If the XIDs already match, also check:
The remove/re-add step almost always generates a new Published Point XID on MangoES while the Enterprise side still holds the old one, updating the Point Locator on Enterprise is usually all that is needed
@Jdiaz-co said in Timeout to lock table systemsettings:
hello good,
I'm having a problem. I'm using Mango 3.7.7 and the application crashes every so often.
The error I'm getting is this:
ERROR 2025-10-27T08:26:50,187 (com.serotonin.m2m2.util.timeout.TimeoutTask.run:61) - Uncaught Task Exception
org.springframework.dao.CannotAcquireLockException: PreparedStatementCallback; SQL [select settingValue from systemSettings where settingName=?]; Tiempo vencido intentando trabar (lock) la tabla "SYSTEMSETTINGS"
Timeout trying to lock table "SYSTEMSETTINGS"; SQL statement:
select settingValue from systemSettings where settingName=? [50200-199]; nested exception is org.h2.jdbc.JdbcSQLTimeoutException: Tiempo vencido intentando trabar (lock) la tabla "SYSTEMSETTINGS"I would appreciate any help.
thank you
Hello,
This error comes from the embedded H2 database: something is holding a lock on the SYSTEMSETTINGS table too long, so reads (like select settingValue from systemSettings…) time out and throw CannotAcquireLockException.
Common causes:
Another process/tool (H2 console, external SQL client) connected to the same H2 DB while Mango is running.
Long-running DB operations (backups, purges, heavy writes) that keep the table locked.
Short default H2 LOCK_TIMEOUT (1s) causing normal contention to show up as errors.
Things to try:
Make sure only Mango is connected to the H2 DB (no external tools while it’s running).
Increase H2 lock timeout in env.properties/mango.properties, e.g.
db.url=jdbc:h2:${ma.home}/databases/mah2;LOCK_TIMEOUT=10000
Check logs around the crash time for other FATAL/DB errors that might be the real shutdown cause.
If this is a production system (not just a test setup), I strongly recommend:
Migrating from H2 to MySQL (more robust under load and concurrency).
Upgrading Mango to a more recent supported version if possible, to benefit from DB and stability fixes.
Mango 5.5.4 Release Notes (09/25/25)
access-control
bacnet-ds
radix-tsl
@mihairosu - **Update ** Mango 5.5.3 has been released to the Mango Store yesterday on September 9, 2025.
@mihairosu said in Update core 5.4.1 core 5.5.2 failed:
mihairosu
2 days agoI tried to update Core and all modules from 5.4.1 to 5.5.2 and now Mango won't start up. I don't have permissions
See link to ma.log file.
Hi @mihairosu,
Thanks for sharing the details and sorry to hear about the trouble after upgrading to 5.5.2.
This issue is related to a known bug that was introduced in Mango version 5.5.0 and will be resolved in the upcoming 5.5.3 release.
In the meantime, a workaround is available:
You can manually change the system setting for the alarm level of the system event MAX_ALARM_LEVEL_CHANGED directly in the database while Mango is offline. Here's the SQL command:
UPDATE PUBLIC.SYSTEMSETTINGS t
SET t.SETTINGVALUE = '0'
WHERE t.SETTINGNAME = 'systemEventAlarmLevel.MAX_ALARM_LEVEL_CHANGED';
This should help bypass the startup issue you're encountering. Once Mango is back online, you can verify the change and proceed with your upgrade path or if your not comfortable making this change wait for the Mango v5.5.3 release.
Let us know if you any further questions or if anything else comes up!
@Bård-Lind you are binding to a specific IP, you won't receive broadcasts if you are running this on Linux. You need to bind to the local address of 0.0.0.0 to get the messages from the initial WhoIs during initialization. Hopefully this helps you out, it could be many things but this is a common one when getting started with BACnet over IP.
