502 proxy error after latest update

[tecnicatv]

Hi!

I’ve updated our system to the latest egroupware version I can’t make it work again. We’re running egroupware-docker in a ubuntu 18.04.3 server.

I keep getting 502 proxy error. I checked docker to see what containers were running I get that egroupware container was not up. When I try to restart it I get the following error message:

Error response from daemon: Cannot restart container egroupware: OCI runtime create failed: container_linux.go:345: starting container process caused “process_linux.go:430: container init caused “rootfs_linux.go:58: mounting \”/var/run/mysqld/mysqld.sock\” to rootfs \"/var/lib/docker/overlay2/f2f46d2173c861ff27b383021877421a8a3f915b08778d88c02564fe677d1eb4/merged\" at \"/var/lib/docker/overlay2/f2f46d2173c861ff27b383021877421a8a3f915b08778d88c02564fe677d1eb4/merged/run/mysqld/mysqld.sock\" caused \“not a directory\”"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

What can I do to solve it? I’ve tried to reinstall egroupware-docker and mysql-server packages but it didn’t help.

Thanks

[StefanU]

Hi EFE.

I’ve updated our system to the latest egroupware version

How did you make the update?
Have you also made Ubuntu system updates?
Did you restart the system after the update?

Stefan

[tecnicatv]

I made it throught system update, we’ve been doing it that way for ages.

We restarted the system after the update. Sometimes we have to restart docker nginx and docker egroupware after a system restart in order to make it work again but this time it didn’t worked

[StefanU]

I made it throught system update, we’ve been doing it that way for ages.

Hmmm. The latest EGroupware Maintanace Update was a Container Update:

New Maintenance Release 19.1.20191119

Have you been through any system updates?
Don’t you have a backup of the system?

egroupware after a system restart in order to make it work again but this time it didn’t worked

Not starting Docker in 18.04.x: Service not enabled:

503 Service not available

EGroupware/egroupware

I’m afraid I have no idea about your actual problem.
Please make sure to start the Docker Autostart and reboot the system again. Leave the system time afterwards and check again.

Stefan

[tecnicatv]

I think we found what the problem was, There was not enough space for the system to make the mysql.lock pipe.

So we made a fresh new installation of 19.1 and it seems to be working but we’re trying to restore our lastest backups but we can’t log in.

At the ‘update recommendations & troubleshouting’ it says that ‘log into the new EGroupware using the generated sysop user’. I can’t find any more info about that user.

how can I log in? Should I run the setup process first as in the previous versions of egroupsware?

thanks

[StefanU]

From:

EGroupware/egroupware

Stefan

[tecnicatv]

I had read that a hundred times without noticing where the users were.

Thanks for pointing it out.

[StefanU]

Now a little more present…
Was really easy to overlook.

Stefan