• M

    @phildunlap said in Cannot upgrade:


    That was it, thanks Phil

    posted in MangoES Hardware read more
  • M

    I am getting an error on all of our Mango instances when trying to upgrade modules from the old GUI:

    Your instance cannot be upgraded due to a versioning problem: store.url environment property blank, cannot check for updates

    I searched the forum and found another similar issue was due to their internet connection, but our works perfectly well. Are there any other possible reasons for these failures?

    posted in MangoES Hardware read more
  • M

    After today's reboot (for OS and module updates) everything is working well. It could also have been the previous time the modules were updated, as we only reboot these for updates.

    posted in User help read more
  • M

    Release is
    Distributor ID: Debian
    Description: Debian GNU/Linux 9.7 (stretch)
    Release: 9.7
    Codename: stretch

    Kernel is

    posted in MangoES Hardware read more
  • M

    Hi everyone,

    After a long while, over a year, of having this issue and trying to resolve it on and off, I'm here asking for some help.

    We have a file server that we use as a backup target for our devices, which is shared via smb/cifs. Absolutely all of our devices support SMB versions higher than 1, except for this MangoES. I have run all of the OS updates that are possible and I assume the cifs-utils package is so old that it does not work with SMB version other than 1.0.

    Since I am not very familiar with the OS running on the MangoES (it's some version of ODroid) I have difficulty trying to find a package of cits-utils or whatever is necessary to be able to mount smb shared with SMB higher than version 1.


    posted in MangoES Hardware read more
  • M

    Ah you know what, that error would have been prior to at least one restart I imagine, so you're right.

    posted in User help read more
  • M

    @phildunlap said in Persistent TCP not Automatically Reconnecting after Reboot:

    ALTER TABLE excelReportTemplates ADD COLUMN fileStoreName VARCHAR(100);

    Submit Update Button gives me this:

    StatementCallback; bad SQL grammar [ALTER TABLE excelReportTemplates ADD COLUMN fileStoreName VARCHAR(100);]; nested exception is org.h2.jdbc.JdbcSQLException: Duplicate column name "FILESTORENAME"; SQL statement: ALTER TABLE excelReportTemplates ADD COLUMN fileStoreName VARCHAR(100); [42121-196]

    Okay Phil. I'll keep an eye on it, see if I figure out anything.

    posted in User help read more
  • M

    Hey Phil,

    The first query:

    ALTER TABLE excelReportTemplates ADD COLUMN fileStoreName VARCHAR(100);

    is giving this error:

    org.h2.jdbc.JdbcSQLException: Method is only allowed for a query. Use execute or executeUpdate instead of executeQuery; SQL statement: ALTER TABLE excelReportTemplates ADD COLUMN fileStoreName VARCHAR(100); [90002-196]

    As far as your second point, we are connecting via IP.

    I searched all of the ma.log files (older rotated ones) and could not find anything with "exception" and "PersistentSenderRT " in the same line (with grep).

    Also, our other MangoES v2 has no problems at all with this (same module versions), so it's pretty weird.

    posted in User help read more
  • M

    Module Core 3.5.6 on both
    Module Persistent 3.5.6 on both

    Our MangoES's Mango Persistent TCP connection is not working after Mango restarts,

    It is connecting to our Enterprise install.

    I have to manually go and Stop the publisher and then Start the publisher, which then fixes this problem.

    I see this error at the top:

     Push to Main Historian: No route to host (Host unreachable) Acknowledge
     Push to Main Historian: No route to host (Write failed) Acknowledge

    There are also some errors in ma.log but I'm not sure if it has anything to do with it:

    ERROR 2019-02-04T12:26:41,807 (com.serotonin.m2m2.Lifecycle.runtimeManagerInitialize:806) - RuntimeManager initialization failure
    org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [SELECT ert.id,ert.data,ert.xid,ert.name,ert.userId,ert.editPermission,ert.reportReadPermission,ert.filename,ert.fileStoreName,ert.preventPurge,ert.sche$
    SELECT ert.id,ert.data,ert.xid,ert.name,ert.userId,ert.editPermission,ert.reportReadPermission,ert.filename,ert.fileStoreName,ert.preventPurge,ert.schedule,ert.scheduleCron,ert.email,ert.zipData,ert.emailTemplateFilename,u.username FROM$
            at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.doTranslate(SQLErrorCodeSQLExceptionTranslator.java:234) ~[spring-jdbc-5.0.10.RELEASE.jar:5.0.10.RELEASE]
            at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:72) ~[spring-jdbc-5.0.10.RELEASE.jar:5.0.10.RELEASE]
            at org.springframework.jdbc.core.JdbcTemplate.translateException(JdbcTemplate.java:1402) ~[spring-jdbc-5.0.10.RELEASE.jar:5.0.10.RELEASE]
            at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:388) ~[spring-jdbc-5.0.10.RELEASE.jar:5.0.10.RELEASE]
            at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:446) ~[spring-jdbc-5.0.10.RELEASE.jar:5.0.10.RELEASE]
            at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:456) ~[spring-jdbc-5.0.10.RELEASE.jar:5.0.10.RELEASE]
            at com.serotonin.db.DaoUtils.query(DaoUtils.java:246) ~[mango-3.5.6.jar:?]
            at com.serotonin.m2m2.db.dao.AbstractBasicDao.getAll(AbstractBasicDao.java:667) ~[mango-3.5.6.jar:?]
            at com.infiniteautomation.mango.excelreports.RTMDefinition.initialize(RTMDefinition.java:34) ~[?:?]
            at com.serotonin.m2m2.rt.RuntimeManagerImpl.startRTMDefs(RuntimeManagerImpl.java:253) ~[mango-3.5.6.jar:?]
            at com.serotonin.m2m2.rt.RuntimeManagerImpl.initialize(RuntimeManagerImpl.java:151) ~[mango-3.5.6.jar:?]
            at com.serotonin.m2m2.Lifecycle.runtimeManagerInitialize(Lifecycle.java:803) ~[ma-priv-3.5.6.jar:?]
            at com.serotonin.m2m2.Lifecycle.initialize(Lifecycle.java:353) ~[ma-priv-3.5.6.jar:?]
            at com.serotonin.m2m2.Main.main(Main.java:138) ~[ma-priv-3.5.6.jar:?]
    Caused by: org.h2.jdbc.JdbcSQLException: Column "ERT.FILESTORENAME" not found; SQL statement:
    SELECT ert.id,ert.data,ert.xid,ert.name,ert.userId,ert.editPermission,ert.reportReadPermission,ert.filename,ert.fileStoreName,ert.preventPurge,ert.schedule,ert.scheduleCron,ert.email,ert.zipData,ert.emailTemplateFilename,u.username FROM$
            at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) ~[h2-1.4.196.jar:1.4.196]
            at org.h2.message.DbException.get(DbException.java:179) ~[h2-1.4.196.jar:1.4.196]
            at org.h2.message.DbException.get(DbException.java:155) ~[h2-1.4.196.jar:1.4.196]
            at org.h2.expression.ExpressionColumn.optimize(ExpressionColumn.java:147) ~[h2-1.4.196.jar:1.4.196]
            at org.h2.command.dml.Select.prepare(Select.java:839) ~[h2-1.4.196.jar:1.4.196]
            at org.h2.command.Parser.prepareCommand(Parser.java:263) ~[h2-1.4.196.jar:1.4.196]
            at org.h2.engine.Session.prepareLocal(Session.java:578) ~[h2-1.4.196.jar:1.4.196]
            at org.h2.engine.Session.prepareCommand(Session.java:519) ~[h2-1.4.196.jar:1.4.196]
            at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1204) ~[h2-1.4.196.jar:1.4.196]
            at org.h2.jdbc.JdbcStatement.executeQuery(JdbcStatement.java:73) ~[h2-1.4.196.jar:1.4.196]
            at org.springframework.jdbc.core.JdbcTemplate$1QueryStatementCallback.doInStatement(JdbcTemplate.java:433) ~[spring-jdbc-5.0.10.RELEASE.jar:5.0.10.RELEASE]
            at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:376) ~[spring-jdbc-5.0.10.RELEASE.jar:5.0.10.RELEASE]
            ... 10 more

    posted in User help read more
  • M

    Hey Matt,

    I did go through the aptitude GUI but it wasn't very helpful because it still only uses the sources.list.

    Here you can see screenshots that it's saying I have installed the 4.5 kernels for both of my MangoES:

    MangoES original:


    MangoES v2:


    but these numbers have nothing to do with what I get when I do a uname -a, as seen in my above post, I am getting 3.8 and 3.10, which I have learned have to do with an ODROID kernel version.

    Even if it would work, when I search for a new kernel via aptitude on my MangoES v2, I get nothing:


    Whereas for the MangoES original I do get a list of kernels, but I am afraid to upgrade to any of these, as I still don't understand why they woudn't be automatically marked as upgradeable. My other apprehension is that aptitude on one is not the same as on the other: Why would MangoES v2 not have any kernel updates but the MangoES original does?


    Looking at this post, I understand that normally, these kernels are not set to upgrade via apt-get, but this person made it possible to do so.

    I already added these two lists, but they didn't provide any ODROID kernel updates:

    wget https://oph.mdrjr.net/meveric/sources.lists/meveric-stretch-main.list        # package list for all ODROID devices / Debian Stretch (not for Debian Wheezy, Jessie, or Ubuntu 12.04, 14.04)
    wget https://oph.mdrjr.net/meveric/sources.lists/meveric-stretch-backports.list   # package list for all ODROID devices / Debian Stretch (not for Debian Wheezy, Jessie, or Ubuntu 12.04, 14.04)

    I suspect I may have to add one of these to each MangoES:

    wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-N1.list              # package list for ODROID N1 devices and all Distributions (Kernel and Headers)
    wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-U.list               # package list for ODROID U2/U3 devices and all Distributions (Kernel and Headers)
    wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-X.list               # package list for ODROID X devices and all Distributions (Kernel and Headers)
    wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-X2.list              # package list for ODROID X2 devices and all Distributions (Kernel and Headers)
    wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-XU.list              # package list for ODROID XU devices and all Distributions (Kernel and Headers)
    wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-XU3.list             # package list for ODROID XU3 devices and all Distributions (Kernel and Headers)
    wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-C1.list              # package list for ODROID C1 devices and all Distributions (Kernel and Headers)
    wget https://oph.mdrjr.net/meveric/sources.lists/meveric-all-C2.list              # package list for ODROID C2 devices and all Distributions (Kernel and Headers)

    So now, my next problem is to figure out which is the correct ODROID hardware version that these MangoES run.

    I found this post when searching on how to figure out which ODROID version I am running.

    The MangoES v2 has 3.10.82+, which according to the above post is 1.0, which says that it would have to be re-imaged? I'm not quite sure how to accomplish this or even if I want to pursue this.
    The MangoES original has, which could mean it could be a sub 1.0 version or something?

    And again I don't understand why I am getting different versions with uname and what is showing up on Aptitude.

    I feel like I'm rambling, so I'll just stop for now.

    posted in MangoES Hardware read more