June 15th update broke installation

[gjpc]

I used webmin to update to the latest EGroupware using apt. and now I get Service Unavailable, try again later.

The update produced the following errors while installing:

Recreating egroupware
e[1Ae[2K
Recreating egroupware ... e[32mdonee[0m
e[1BRecreating egroupware-watchtower ... 

egroupware-db is up-to-date
Recreating egroupware-watchtower
egroupware is up-to-date
Creating egroupware-push ... 

Creating egroupware-push
e[1Ae[2K
Creating egroupware-push ... e[31merrore[0m
e[1B
ERROR: for egroupware-push  Cannot create container for service push: failed to mount local volume: mount /var/lib/docker/volumes/egroupware-docker_sources/_data/swoolepush:/var/lib/docker/volumes/egroupwaredocker_sources-push/_data, flags: 0x1000: no such file or directory
e[1Ae[2K
Recreating egroupware-watchtower ... e[32mdonee[0m
e[1B
ERROR: for push  Cannot create container for service push: failed to mount local volume: mount /var/lib/docker/volumes/egroupware-docker_sources/_data/swoolepush:/var/lib/docker/volumes/egroupwaredocker_sources-push/_data, flags: 0x1000: no such file or directory
e[31mERRORe[0m: Encountered errors while bringing up the project.
Module proxy already enabled
Considering dependency proxy for proxy_http:
Module proxy already enabled
Module proxy_http already enabled
Considering dependency proxy for proxy_wstunnel:
Module proxy already enabled
Module proxy_wstunnel already enabled
Module headers already enabled

The Apache error log states:

[Mon Jun 15 13:52:02.293551 2020] [proxy_http:error] [pid 9245] [client 173.13.184.18:62878] AH01114: HTTP: failed to make connection to backend: 127.0.0.1

Docker status:

root@ip-172-31-26-2:/var/log# docker ps
CONTAINER ID        IMAGE                          COMMAND                  CREATED             STATUS                          PORTS               NAMES
0b2817cec3ef        containrrr/watchtower:latest   "/watchtower --sched…"   52 minutes ago      Up 46 minutes                   8080/tcp            egroupware-watchtower
248f4d88d27e        egroupware/egroupware:20.1     "/entrypoint.sh php-…"   52 minutes ago      Up 8 seconds                    9000/tcp            egroupware
4d9ebd5f503f        nginx:stable-alpine            "nginx -g 'daemon of…"   6 weeks ago         Restarting (1) 36 seconds ago                       egroupware-nginx

Rebooting the machine and restarting Apache does not help.
Suggestions?

[StefanU]

Hi gjpc,

I have been a user of Webmin for 20 years myself.
But you must never use Webmin to update systems where questions about updates of configuration files are asked. Webmin always answers yes and will overwrite configuration data with its own entries.
ALWAYS do this on the console and you decide which changes are applied.

And there is more:
EGroupware updates are first delivered with the Docker container. This is usually (not always) independent of the packages. I always note this in the release notes. So it is not always necessary to install the packages.

Now to your problem:
You could restore your system backup.

What have you installed? There the push server comes with it. This is not included in the CURRENT Release 19.1.20200605.

EGroupware/egroupware

Stefan

[RalfBecker]

Ok, your problem is, that you (still) use our beta/release candidate repository “server:eGroupWare:trunk”, in which I’m currently working on the next release (20.1).

Not an easy task to fix, if you have no backups, specially as I’m rapidly building new packages and I therefore don’t know which one exactly you used!

First check if you have a file /etc/egroupware-docker/docker-compose.override.yml.
If that’s the case, run the following commands:

cd /etc/egroupware-docker
docker-compose stop
docker-compose rm -f
cp docker-compose.override.yml docker-compose.yml
sed 's|egroupware/egroupware:20.1|egroupware/egroupware:latest|g' -i docker-compose.yml
docker-compose up -d

And change your repository to the correct stable one:

cd /etc/apt/sources.list.d
sed 's/server:eGroupWare:trunk/server:eGroupWare/g' -i *egroupware*

Ralf

[gjpc]

Thanks for the replies Stefan & Ralf.

Stefan, I generally do not backup apt installed software, I think that is exactly what apt is for. Besides, when I do a find / -name "*egroup* the output is so voluminous I’d have no idea what I would need to backup.

Ralf, I had the override yml file and all your commands executed without error, but the application still would not come up.

So I apt removed EGroupware and used the install commands from the website:

echo 'deb http://download.opensuse.org/repositories/server:/eGroupWare/xUbuntu_18.04/ /' | sudo tee /etc/apt/sources.list.d/server:eGroupWare.list
sudo wget -nv https://download.opensuse.org/repositories/server:eGroupWare/xUbuntu_18.04/Release.key -O "/etc/apt/trusted.gpg.d/server:eGroupWare.asc"
apt update
apt install egroupware-docker

OOPS! forgot to give the --no-install-recommends so time to remove rocket and collabra:

apt remove  egroupware-rocketchat:amd64
apt remove  egroupware-collabora-key

OK! now I have my EGroupware installation up and running on my teeny tiny AWS EC2, no data loss.

I elected to use the distribution’s yml file, however, for some reason I am still running the released beta egroupware-docker (20.1.20200613) hardy; urgency=low. Maybe because I did not delete all the override yml files in /etc/egroupware-docker directory?

I don’t mind running the beta release, I am the only user of the install and, being retired, it gives me something to do. Would you recommend removing the override yml to fall back to the 19.x release? Once the yml overrides are gone will docker revert to release 19? Or would I have to do a apt remove in order to downgrade to 19.x? Will the working trunk software update show up again in apt update? It is not there now.

One other thing, this procedure chewed up 20% of my free disk space, any suggestions where I can find files I may delete?

[StefanU]

Hi gjpc.

I generally do not backup apt installed software, I think that is exactly what apt is for.

This is a mistake and a misunderstanding!

The package manager apt does not protect you from failed updates. Why would it?
Especially not if you let Webmin decide to overwrite configuration files without checking them.

I’d have no idea what I would need to backup.

This is simple and straightforward. I have just written this down in a FAQ:

(What is to) Backup before(!) an update

You can use the file backup function of Webmin for this purpose. Then this is quickly done before an update. Or you do it automatically…

Of course you still had the problem that you installed the developer version. Not good for a production system…

Stefan

[gjpc]

Thanks Stefan,

Does the watchtower docker update do a backup?

Of course you still had the problem that you installed the developer version. Not good for a production system…

As I stated, I am the only user, but ok how do I back out of development to the release? Nevermind I just found the Github installation page. I am genning up a VM to do a practice run.

[RalfBecker]

Would you recommend removing the override yml to fall back to the 19.x release? Once the yml overrides are gone will docker revert to release 19?

If you remove /etc/egroupware-docker/docker-compose.override.yml, which overrides the docker image from :latest to :20.1, and do a: cd /etc/egroupware-docker; docker-compose up -d you are back on a 19.1 container.

As the 19.1 --> 20.1 update does NOT include a schema-update of the database, you can always go forward and backward relativ easily.

I’ll publish tomorrow a bit more about the technical background of the update and the upcomming 20.1 release.

Ralf

[gjpc]

If you remove /etc/egroupware-docker/docker-compose.override.yml, which overrides the docker image from :latest to :20.1, and do a: cd /etc/egroupware-docker; docker-compose up -d you are back on a 19.1 container.

Worked like a charm Ralf, thanks!