Announcement

Collapse
No announcement yet.

Problem with "listuser"

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problem with "listuser"

    Hello,

    after upgrading to the latest Version 7.8.4 (from 7.8.0) of Appsuite I get the error "Service OXUser_V2 is not available" when using /opt/open-xchange/sbin/listuser an the command line.

    Has anyone here an idea what the problem is?

    BTW: I found nothing in the logs

    The output of "/opt/open-xchange/sbin/listbundles | grep -v ACTIVE" is
    bundlename: com.openexchange.logback.classic.extensions status: RESOLVED
    bundlename: com.openexchange.logback.configuration status: RESOLVED
    bundlename: com.openexchange.logback.core.extensions status: RESOLVED
    bundlename: com.openexchange.system.extension status: RESOLVED
    Thanks in advance
    Last edited by 881822; 12-29-2017, 02:42 PM.
    Viele Gre
    Rene

    OS: Ubuntu Server amd64 16.4 LTS
    JRE: openjdk-8-jre, MySQL 5.7, Apache 2.4, Dovecot 2.2.22
    OX-Server backend: OXSE latest
    OX-frontend: OXSE latest appsuite + ox6

  • #2
    The listbundle output above does not really help. Those RESOLVED are expected.
    Still the Admin part of App Suite is not running on your system. I think you need to watch the logs during startup. I would expect that some component will report an error there.

    Comment


    • #3
      indeed, there are errors, but I can't interpret them. Can anyone help on this?

      Attached is the /var/log/open-xchange/open-xchange.log.0 (only errors)
      Attached Files
      Last edited by 881822; 12-31-2017, 03:50 PM.
      Viele Gre
      Rene

      OS: Ubuntu Server amd64 16.4 LTS
      JRE: openjdk-8-jre, MySQL 5.7, Apache 2.4, Dovecot 2.2.22
      OX-Server backend: OXSE latest
      OX-frontend: OXSE latest appsuite + ox6

      Comment


      • #4
        Hmm, OX has a hard time to access your configdb it seems:
        2017-12-31T14:25:07,666+0100 ERROR [Start Level: Equinox Container: 607962f5-2dee-0017-1f22-f14eac96dc50] com.openexchange.admin.osgi.AdminDaemonInitializer .addingService(AdminDaemonInitializer.java:98)
        Failed to initialize file store utils
        com.openexchange.admin.rmi.exceptions.StorageExcep tion: Table "filestore2user" does not exist.

        This is preventing the Admin from starting up correctly.

        Documentconverter configuration also needs some love during this update:
        Documentconverter remote connection could not be established => please check remote converter setup (remoteurl=http://localhost:8008/documentconverterws, async_request=true)

        But it seems that
        Error in SQL syntax in the following statement on schema configdb: com.mysql.jdbc.StatementImpl@738e7664
        com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorEx ception: Specified key was too long; max key length is 767 bytes
        is a bigger issue here.

        I haven't seen such an error before on upgrade though.

        What is your exact database software and version?

        Comment


        • #5
          Thanks for your quick reply (on new years eve )

          The DB is mariaDB-10.0 v10.0.31
          Viele Gre
          Rene

          OS: Ubuntu Server amd64 16.4 LTS
          JRE: openjdk-8-jre, MySQL 5.7, Apache 2.4, Dovecot 2.2.22
          OX-Server backend: OXSE latest
          OX-frontend: OXSE latest appsuite + ox6

          Comment


          • #6
            @Wolfgang: Would you mind to change to MySQL-Server or should we try to fix this issue with MariaDB?
            Viele Gre
            Rene

            OS: Ubuntu Server amd64 16.4 LTS
            JRE: openjdk-8-jre, MySQL 5.7, Apache 2.4, Dovecot 2.2.22
            OX-Server backend: OXSE latest
            OX-frontend: OXSE latest appsuite + ox6

            Comment


            • #7
              The problem was the max key length in mariadb-10.0 (and MySQL 5.6 or older). After an update to MariDB 10.2 the OX Server startet without issues.
              Viele Gre
              Rene

              OS: Ubuntu Server amd64 16.4 LTS
              JRE: openjdk-8-jre, MySQL 5.7, Apache 2.4, Dovecot 2.2.22
              OX-Server backend: OXSE latest
              OX-frontend: OXSE latest appsuite + ox6

              Comment


              • #8
                Still an interesting finding. Currently our database software requirements still allow MySQL 5.5 for example. So I'm wondering if there is a certain configuration applied for the used database. Something seems to be special I think but I cannot directly point to the relevant setting.

                Comment

                Working...
                X