Update form openSUSE Leap 15.6 to 16.0

WalterH · 2026-04-13T16:12:44+00:00

openSUSE 15.6 is nearly at the end of its life cycle. The Grommunio developers have resolved the dependency issues for the openSUSE 16.0 packages, so it is t...

Andy

dneuhaeuser I had the same problem. After the upgrade the SSH root login was not permitted anymore.

Same here and I try with VNC Terminal but without success. I dont know at which step I can modify the mentioned file, I think before of using of command init 6 at step 19.

Same also with Grommunio Files, at this point I also choose step 2.

At the moment I use old Leap 15.6 and try again later.

dneuhaeuser

Andy
I did the ssh configuration after reboot directly on the console (probably VNC terminal in your case).
You can also try to do this before step 19 reboot, while still connected via ssh.

Duese6

WalterH
No issue.

I got it runnig again.
I reinstalled grommunio-fiules with option 2)
Only thing I had to do is getting back my old config:
/var/lib/grommunio-files/config/config.php

I think (may bee) option 3 ( @dneuhaeuser ) from aboves post dose se same.

Andy

I try again later if I´m back in my home office with all my tools. Therefore also step 17, which I exclude in that first round, I want to consider. But it seems I can also work in step 17 after all is running.

Andy

dneuhaeuser You can also try to do this before step 19 reboot

It´s during step 13 and zypper dup. I work also with WinSCP and Grommunio load 1190 files for the upgrade and in the range of no. 200-250 of file installation any package installation removes sshd_config I make a duplication before and duplicate back now.

We will see.

dneuhaeuser

Duese6
instead of "rd.plymouth=0" I use "plymouth.enable=0" because I like to see all boot messages.

Duese6

@DVCon
I see the same.
Archiving itself works (new mails are stored), but new mails do not appear in the archive web UI anymore.
Only pre‑migration data is shown.
searchd/Sphinx is running and rotating as usual, so this doesn’t look like a classic indexing problem, but rather something in the archive web side after the migration

comparing logs... I miss the dailydelta1 in searchd... but I'm not that deep in the sphinx stuff.

Duese6

dneuhaeuser

I can confirm that. I didn't notice it right away because I switched to key-based authentication a while ago. So I wasn't actually "locked out." Thanks for the tip.

DVCon

@Duese6

The postfix log also looks a bit unusual regarding archive functionality.
I used pilerexport to look at some of the archived mails.
And I found a lot of mails that look like this:

`Received: by mail.domain.tld (Postfix, from userid 462)
id D83516C4508; Wed, 15 Apr 2026 18:45:00 +0200 (CEST)
From: "(Cron Daemon)" groarchive@mail.domain.tld
To: groarchive@mail.domain.tld
Subject: Cron <groarchive@localhost> /usr/bin/indexer --config /etc/sphinx/sphinx.conf --quiet tag1 --rotate
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Auto-Submitted: auto-generated
Precedence: bulk
X-Cron-Env: <XDG_DATA_HOME=/var/lib/grommunio-archive//.local/share>
X-Cron-Env: <XDG_CACHE_HOME=/var/lib/grommunio-archive//.cache>
X-Cron-Env: <XDG_CONFIG_HOME=/var/lib/grommunio-archive//.config>
X-Cron-Env: <XDG_STATE_HOME=/var/lib/grommunio-archive//.local/state>
X-Cron-Env: <LANG=de_DE.UTF-8>
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/var/lib/grommunio-archive/>
X-Cron-Env: <PATH=/usr/bin:/bin:/usr/sbin:/sbin>
X-Cron-Env: <LOGNAME=groarchive>
X-Cron-Env: <USER=groarchive>
Message-Id: 20260415164500.D83516C4508@mail.domain.tld
Date: Wed, 15 Apr 2026 18:45:00 +0200 (CEST)

WARNING: failed to open pid_file '/run/grommunio-archive/grommunio-archive-searchd.pid'.
WARNING: indices NOT rotated.`

/run/grommunio-archive/grommunio-archive-searchd.pid currently exists.

Duese6

Yes. This file contais the PID of the serachd process which is correct.
And grommunio-archive.pid contains the piller PID
Both contain correct PID if running

WalterH

dneuhaeuser When you edit your post, you should be able to save the paths without spaces; at least it works for me.

WalterH

Andy I updated a system a few minutes ago and the sshd_config file survived.

Duese6

@DVCon
I think I've found it.
Scripts are missing (for whatever reason) under /usr/lib/grommunio-archive

I restored them from a backup from this morning.
Don't forget to set the permissions (755).

In the database (groarchive sph_index), I saw an error message saying it was trying to call indexer.delta.sh, which didn't exist.

DVCon

Duese6
I came to the same conclusion. 😉
First, I ran indexer --all --rotate and was able to see all missing mails in grommunio-archive. Then I also saw the error mail that hinted to /usr/lib/grommunio-archive and recovered the directory from another server.

Andy

It will not work in my case. Until step 19 and after modification of the sshd_config the system work, but after step 20 (reboot) it is not possible to connect the system. The only way is VNC terminal, but is no solution.

I´m not sure, if I must be in the same network and need to work with IP adresses, etc.

Duese6

Andy
Or just switch to SSH keys beforehand.
It makes life easier in many cases anyway, depending on what tools you use. I think XPipe is pretty good. It saves a lot of time in everyday use.

Duese6

DVCon
Yes I did the same. 😃
But this "killed" the complete index and all old archived mails were not visible anymore. In my case this is still a testsystem.

But the question remains... what went wrong, the the hole directory was gone... and was it the only one...

DVCon

Duese6 But this "killed" the complete index and all old archived mails were not visible anymore. In my case this is still a testsystem.

Yes, that wasn't a nice surprise this morning.
I got the mails back with reindex -a -p, though the total message count in the search window is wrong now. It's my own server. So I can live with this. But the whole thing should better not happen on the servers of my clients.

Andy

Duese6 It makes life easier in many cases anyway, depending on what tools you use. I think XPipe is pretty good

I use MobaXterm and WinSCP, both are very good. I take a view on XPipe, will see.

I had a mistake with sshd_config and ssh_config, was my fault. I saw it after creating a /root/.ssh/authorized_keys and use a generated key for login I use also for all my NAS.

Now is okay and Grommunio runs with Leap 16.0

I only need to follow step 17 and 23 to 26 in detail, at the moment I nothing, partly because of my knowledge, will see.

crpb

fwiw, you don't need a sshd_config in /etc in opensuse. it will default to the file from /usr.
For any config-overides just use the folder sshd_config.d and place a something.conf with any overrides.

e.g. ... BOAH DRECKS FORUM...
SICHERHEIT UND SO...

https://bin.moep.com/6xZtMRMC

Andy

The question is, in which way is finally Grommunio conform, because such way are more a Linux way.

« Previous Page Next Page »