• SolvedFixed

  • "An unexpected error has occurred" Grommunio Web Search

WalterH You ma try a repair for this mailbox:

/usr/libexec/gromox/cgkrepair [-n] -e [user]@domain

Unfortunately, it didn't help either. The error remains.


localhost:~ # /usr/libexec/gromox/cgkrepair -e joerg@xxxxx-xxxxx.ch
Hierarchy discovery: 87 folders
2h (ok)
3h (ok)
4h (ok)
5h (ok)
1fah (ok)
215h (ok)
6h (ok)
7h (ok)
8h (ok)
9h (ok)
ah (ok)
bh (ok)
ch (ok)
dh (ok)
eh (ok)
fh (ok)
10h (ok)
11h (ok)
12h (ok)
13h (ok)
14h (ok)
15h (ok)
16h (ok)
17h (ok)
19h (ok)
1ah (ok)
1bh (ok)
1ch (ok)
1dh (ok)
1d0001h (ok)
1d2711h (ok)
1d4e21h (ok)
1d7531h (ok)
1d9c41h (ok)
1dc351h (ok)
1dea61h (ok)
1e1171h (ok)
1e3881h (ok)
1e5f91h (ok)
1e86a1h (ok)
1eadb1h (ok)
1ed4c1h (ok)
1efbd1h (ok)
1f22e1h (ok)
1f49f1h (ok)
1f7101h (ok)
1f9811h (ok)
1fbf21h (ok)
1fe631h (ok)
200d41h (ok)
203451h (ok)
205b61h (ok)
208271h (ok)
20a981h (ok)
20d091h (ok)
20f7a1h (ok)
211eb1h (ok)
2145c1h (ok)
216cd1h (ok)
2193e1h (ok)
21baf1h (ok)
21e201h (ok)
220911h (ok)
223021h (ok)
225731h (ok)
227e41h (ok)
22a551h (ok)
22cc61h (ok)
22f371h (ok)
231a81h (ok)
234191h (ok)
2368a1h (ok)
238fb1h (ok)
23b6c1h (ok)
23ddd1h (ok)
2404e1h (ok)
242bf1h (ok)
245301h (ok)
247a11h (ok)
18h (ok)
101h (ok)
102h (ok)
24a121h (ok)
24c831h (ok)
24ef41h (ok)
251651h (ok)
253d61h (ok)

    WalterH You may try the SQLite Recovery described here: https://docs.grommunio.com/kb/sqlite.html for this database.

    I get a parse error on recover:

    localhost:~ # sqlite3 /var/lib/gromox/user/2/1/exmdb/exchange.sqlite3
SQLite version 3.44.2 2023-11-24 11:41:44
Enter ".help" for usage hints.
sqlite> pragma integrity_check;
ok
sqlite> 

localhost:~ # cd /var/lib/gromox/user/2/1/exmdb/
localhost:/var/lib/gromox/user/2/1/exmdb # sqlite3 exchange.sqlite3 ".recover" | sqlite3 new.db
Parse error near line 8: object name reserved for internal use: sqlite_sequence
localhost:/var/lib/gromox/user/2/1/exmdb # chmod u=rw,g=rw new.db 
localhost:/var/lib/gromox/user/2/1/exmdb # chown grommunio:gromox new.db 
localhost:/var/lib/gromox/user/2/1/exmdb # mv exchange.sqlite3 old.db
localhost:/var/lib/gromox/user/2/1/exmdb # mv new.db exchange.sqlite3
localhost:/var/lib/gromox/user/2/1/exmdb # systemctl restart gromox-http
localhost:/var/lib/gromox/user/2/1/exmdb #

      When I create a new user and do a search in the completely empty account, I also get the error in the web search: "An unexpected error has occurred"

      Solved:
      The complete reinstall brought the solution.
      Deleting all settings and re-parameterizing using "grommunio setup wizzard" was not enough.

      Joerg changed the title to Solved: "An unexpected error has occurred" Grommunio Web Search .

      I have the same problem, but a reinstall is no solution.

      greets
      Michael

        MichaelH I have the same problem, but a reinstall is no solution.

        Yes, unfortunately I've had to find that out again now. After migrating several accounts to the new system with grommunio on Friday, I realized that the search in the web interface doesn't work for the other mail accounts :-(
        The system is currently running productively (only for my family) but I am considering migrating back to Kopano...
        Actually, I hope that a solution can be found in the next few days. Strangely enough, the search on my own account still works after the reinstallation.

          Joerg changed the title to Reopened: "An unexpected error has occurred" Grommunio Web Search .

          Same problem here. And it's "only" the web-search, the search with smartphones works without an error (iPhone with Exchange-mailbox). So it seems, the error is in the website-part and not in database. @Joerg: can you confirm this?

          I hope too that a sloution can be found, although the search on smartphone is a short-term alternative.

            Angua And it's "only" the web-search, the search with smartphones works without an error (iPhone with Exchange-mailbox)

            Yes, I can confirm that. (Anroid 14 "Vanilla" with standard mail client)

              Angua Same problem here.

              this statement is not really helpful. Any errors in the logs or in journalctl -f?

                  I found out something else interesting:
                  Since the new installation, the web search works on my account "joerg@XXXXX-XXXXX.ch") (This did not work during the first installation, although I had imported the data in the same way).
                  The web search does not work on the shared account "familie@XXXXX-XXXXX.ch".
                  However, the web search of the shared account "familie" works when I search in the inbox "Favoriten".

                  Work:

                  Doesn't work:

                    Joerg However, the web search of the shared account "familie" works when I search in the inbox "Favoriten".

                    Oh no! The test mail in "sent items" is found, not the mail in the family inbox
                    <facepalm> :-(

                      WalterH
                      Sorry, i didn'd consider of sharing logs because i thought, Joerg had submitted the relevant logs. My bad.

                      I have checked the nginx-logs, the logs in admin-gui and journalctl -f. There are no errors.

                      I tried to raise log-level by adding http_debug=1 and msrpc_debug=1 in /etc/gromox/http.cfg, like described in documentation, but without any effect, even after reboot. Where am i going wrong?

                        Joerg changed the title to "An unexpected error has occurred" Grommunio Web Search .
                        9 days later

                        This should be the solution:

                        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.

                        Joerg
                        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

                              15 days later

                              Joerg
                              I tried it both. I changed the user and group of the files in the /var/lib/grommunio-web/sqlite-index folder to groweb:groweb and set the permissions of the index.sqlite3 file to 0660.

                              After did so, the websearch was woking but I got this failures when I was reindexing:

                              [ERROR] Failed to insert message 10/1918698: attempt to write a readonly database
                              [ERROR] Failed to insert message 10/1918699: SQLite query failed: 8

                              I think, the way with the wrong permissions is right, but this is in my case not the solution.

                                  Die Rechte müssen so aussehen:

                                  # ls -l /var/lib/ | grep grommunio-web
drwxrwx--- 1 groweb    groweb     44 Feb 15 12:12 grommunio-web/

 # ls -l /var/lib/grommunio-web
total 4
drwxrwx---  1 groweb groweb   74 Feb 19 18:22 session/
drwxrwx--- 27 groweb groweb 4096 Feb 15 12:12 sqlite-index/
drwxrwx---  1 groweb groweb   36 Feb 15 12:12 tmp/

# ls -l /var/lib/grommunio-web/sqlite-index/
drwxrwx--- 2 grommunio groweb 27 Feb 20 07:30 user\@domain.tld/

                                  jstampfer ndex.sqlite3 file to 0660

                                  0660 ist definitiv falsch.

                                  Hoffe das hilft weiter?

                                  • Andy replied to this.

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