tf91 I don't use LDAP for my accounts, however, in point 1 of my process I mentioned that you should NOT creathttps://community.grommunio.com/d/1444-suchfunktion-in-webapp-deskapp-mit-fehlermeldunge the Organisation, Domain or Users, as the database imports to your new server (items 11-13 - only use 12 if you are using Grommunio Files) will do all this as per your existing (old) server.

Looking back at my post and just to make sure this is not misinterpreted, I should have mentioned that the bold text in the various points, should be considered as a single line, not as 1 or more as it displays. ie in Item 6 you should highlight all the text from 'mysql' right through to (and including) 'done' as this is just one command sequence, it is a long command, hence my suggestion to copy and paste it. Also the 'root@192.168.xxx.xxx' bits in item 7 & 8 should be replaced with the account and IP address of your 'root' user on the new server.

Hope your second/third test go a little better. The whole above process should be performed while logged in as the default 'root' user (on both servers) otherwise you might come across permissions errors during the export process.

In item 9 I originally had chown -Rf grommunio:gromox /var/lib/gromox/user, but found that following the 11/23 new appliance ISO's that Grommunnio couldn't find my user directories after I had migrated the data. It seems there had been a slight change to the permissions in the appliance ISO and I had to set the permissions one directory higher. I built a fresh VM to check this, from the same appliance ISO, and using WinSCP found the permissions were different to my previous versions, so modified item 9 to its current form. Once I had made this change I have not had any other issues in the roughly 10 migrations I have done since with the above process.

Hope the above helps.

Andy Thank you.
I did the change like in step 9. On my current grommunio its owned by gromox:gromox. Maybe because its an old appliance. The permissions are same. But it dont work with both owners.

@Mister2 Yes of course, I did all like you described again 🙂
I also didnt configured anything before.
Second test cause the same problem. I will try a bit more.

    tf91 So, as I did when I had a similar problem.

    1. Create a new VM with the same appliance ISO you used to build your new VM (This should be considered as a TEST Machine only)
    2. Run the Setup Wizard as normal, unto the point you can log into the GUI
    3. Create and Test Organisation, and Domain (any thing will do - as its only a test)
    4. Create one new user manually. Grommunio will create the user directory in /var/lib/gromox/user.
    5. Use something like WINSCP on a Windows box (oe a suitable Linux equivalent tool that lets you look at the permissions Grommunio has set on your new users folder (probably /var/lib/gromox/user/0). With the permissions documented rerun the line in item 9 on your not working new server (not the test one) using the permissions you have just recorded, then reboot it.

    I do recall that I did have some issues initially getting the permissions to take on item 9, but as said in my previous post this was caused by me now having sufficient permission to the /var/lib/gromox/user folder, hence I applied the permission one folder higher (/var/lib/gromox) and this deployed the permissions correctly. Obviously once you have set the permission, check they have actually taken as intended, that is how I found that they had not taken at first.

    Mark

    tf91 When you were exporting the data from old to new (step 7) you mentioned you received some warnings. What were these as this is just a straight data copy using rsync. If you are using root on both servers warning s suggest you may have some permissions issues on your 'old' server preventing the files being copied.

    Mark

    @MisterG Thank you again for all youre advices. I Was able to make an Import and to login, after detach a Mail account and "change" password. There have to be a Problem about ldap. I will try a bit more again the next days.

    Though I expereinced still the problem in webapp search. Any news about this at someone here?

    I have found the problem of webapp search ("An unexpected error has occurred"), at least in my installation. The files created by grommunio-index.service in the folder /var/lib/grommunio-web/sqlite-index have the wrong permissions. After creating they are owned by user grommunio and group gromox. If I change the permissions to owner groweb and group groweb the websearch is working again.

      odo125 I have found the problem of webapp search ("An unexpected error has occurred"), at least in my installation. The files created by grommunio-index.service in the folder /var/lib/grommunio-web/sqlite-index have the wrong permissions. After creating they are owned by user grommunio and group gromox. If I change the permissions to owner groweb and group groweb the websearch is working again.

      I can confirm that. However, I had to adjust the rights of the index.sqlite3 file to: -rw-rw---- (0660). In order to show search-results, a re-indexing was necessary: grommunio-index -v -c -A

        Suchfunktion läuft wieder. ...

        Ohne vernünftigen Index gibt es auch keine Suche bei Web. Verbesserte Index-Berechtigungen sind teil eines kommenden Updates (Freitag release)

        Joerg

        I can confirm that you have also to change the rights of the index.sqlite2 file. A re-indexing was not necessary in my case.

        15 days later

        @Mister2
        Thank you again for all youre tips. Finally I got it to work, and it was a problem with LDAP .. and own dumbness.
        Though I still have problems since I can sync with ActiveSync. The log of grommunio_http says (for example)
        E-5320: link /var/lib/gromox/user/2/1/wOF374ChwQLrlsZQ -> /var/lib/gromox/user/2/1/cid/Y-0c/870769629a1bf375e95baac5723cdf: Permission denied
        I set all permissions in /var/lib/gromox/user as you described and also tried like it was set in a new created mailbox in the appliance. I dont know the issue.

          tf91 Your welcome. The error you report suggests some permission is still not quite right. I would try running the chown -Rf grommunio:gromox /var/lib/gromox again, but make sure you have closed down all mail clients (possibly turn off wifi/lan connection from clients) when you run the command to make sure all file permissions are properly set. See if that helps.

          If not work, maybe check the permissions as follows:

          chown -Rf gromox:gromox /var/lib/gromox
          chown -Rf grommunio:gromox /var/lib/gromox/user/*
          chmod -Rf 0770 /var/lib/gromox
          chmod -Rf 0775 /var/lib/gromox/domain/*

          • tf91 replied to this.

            Andy
            Yes, thats exactly the permissions I set.

            When I run the command grommunio-index -v -c -A the following error occurs:

            mkdir /var/lib/grommunio-web/sqlite-index/xxx@xxx.de: Permission denied
            mkdir /var/lib/grommunio-web/sqlite-index/xxx@xxx.de: Permission denied
            mkdir /var/lib/grommunio-web/sqlite-index/xxx@xxx.de: Permission denied
            mkdir /var/lib/grommunio-web/sqlite-index/xxx@xxx.de: Permission denied
            mkdir /var/lib/grommunio-web/sqlite-index/xxx@xxx.de: Permission denied
            ks-srv03-gm:~ # ls -l /var/lib/grommunio-web/sqlite-index/
            total 0
            drw-rw---- 2 groweb groweb 27 Feb 22 14:03 xxx@xxx.de
            drw-rw---- 2 groweb groweb 27 Feb 22 14:03 xxx@xxx.de
            drw-rw---- 2 groweb groweb 27 Feb 22 14:03 xxx@xxx.de
            drw-rw---- 2 groweb groweb 27 Feb 22 14:03 xxx@xxx.de
            drw-rw---- 2 groweb groweb 27 Feb 22 14:03 xxx@xxx.de

            Fix:
            chmod -R 770 /var/lib/grommunio-web/sqlite-index/

            The rights are incorrect:

            # l /var/lib/grommunio-web/sqlite-index/
            total 0
            drwxrwx--- 2 grommunio groweb 27 Feb 23 09:31 xx\@kk.com/
            drwxrwx--- 2 grommunio groweb 27 Feb 20 15:04 yy\@kk.com/

            Das Thema ist in der neuen Appliance v2023.11.3 vom 16.2. leider nicht behoben. Ich bekomme den Fehler erst einmal wieder.

            9 days later

            Weiterhin die gleiche Situation mit dem aktuellen Softwarestand.

            © 2020-2024 grommunio GmbH. All rights reserved. | https://grommunio.com | Data Protection | Legal notice