EGW EPL version residual setup config persistance with wrong password

[uengin]

Hello eGW community,
How are you all?

I am trying to setup the epl version of eGW however, during the setup process I gave the wrong admin password for the DB and now this setup command is saved somewhere and it no longer asks me for the parameters, it just uses the old parameters it saved somewhere in the system.

• Which version (from admin/change log and versions)?
  

eGW EPL v 17.1.20190808
Debian 8.0/Jessie

• Installation type (package installation, archive installation or git)?
  

APT installation

• Which module?
  

Setup

• Does the error occur after an update?
  

No, during setup

• Are there any references in the web server error log?
  

Yes:

Sun Feb 16 18:31:45 MSK 2020
/usr/bin/php5 -d memory_limit=-1 /usr/share/egroupware/setup/setup-cli.php --setup-cmd-database sub_command=create_
db ‘domain=default’ ‘db_type=mysql’ ‘db_host=localhost’ ‘db_port=3306’ ‘db_name=egroupware’ ‘db_user=egroupware’ ‘d
b_pass=FUNKYPASSWORD’ ‘db_root=root’ ‘db_root_pw=FUNKYPASSWORD’ 'db_grant_host=localhost’
Can not connect to mysql database mysql on host localhost:3306 using user root! (ADOdb::Connect(localhost:3306, root, $Password, mysql) failed.)

• Which database is used (MySQL/MariaDB or PostgreSQL)?
  

MySQL/MariaDB

• Which web server is used (Apache or nginx)?
  

Nginx

• Which version of PHP is used?
  

PHP5

My question is, how can I clear this cached command, OR how can I edit it so I can put in the right password so the setup could continue?

Thank in advance.

[StefanU]

Hi Emmitt,

the credentials for the DB are stored in
/var/lib/egroupware/header.inc.php

The header.inc.php was written by the EGw-Setup
https://domain.TLD/egroupware/setup

Maybe you can use the setup to change the DB password.

PHP5

Please make sure to update!:

🇬🇧 🇩🇪 End of life (EOL) of PHP 5.6 and 7.0

Stefan

[uengin]

Thank you so much Stefan, for the prompt reply.
TL;DR; The command I’m seeking is not there. Perhaps EPL version versus docker version difference?

The contents of the header.inc.php file is:

<?php // dummy setup file if (strpos($_SERVER['PHP_SELF'],'/setup/') === false) { header('Location: /egroupware/setup/'); exit; }

Not sure if this is the intended contents, I’m concerned about the “Dummy setup file” comment in the file. I did try to search my system for text files containing the command. I could not find it… rather after 18 hours command still did not complete.

The reason why I have to edit the command and run the setup is because setup hasn’t yet placed the php config in for the */egroupware directory, so I cannot access it from the webserver just yet.

Any other ideas, please?

[StefanU]

eGW EPL v 17.1.20190808
Debian 8.0/Jessie

We install or use Docker in the standard version 19.1 and higher. Not with version 17.1.
A package installation of 17.1 puts the file exactly there.
Isn’t this a new installation of a 17.1?

Any other ideas, please?

Because of the old debian installation:
Create a new installation with debian 10, install the EGw backup and upgrade to 19.1:

🇬🇧 My installation of EGroupware 19.1 on Debian 10

Stefan

[uengin]

Again, thank you so much for the response.

We install or use Docker in the standard version 19.1 and higher. Not with version 17.1.

A package installation of 17.1 puts the file exactly there.

Isn’t this a new installation of a 17.1?

I just thought maybe this got overlooked. I realise that only the newer versions are docker based.
Yes, this is clean installation of version 17.1

Though, I did try to install the docker version prior to this, manually trying to install package by package the dependancies, where I gave up and rolled back. docker-composer is not available on jessie in any repository I tried to add. Hence, that fell though, and I rolled back all the packages I installed and settled for the EPL version 17.1.

Then during setup through the terminal mistyped the DB password, and here I am…

Because of the old debian installation:

Create a new installation with debian 10, install the EGw backup and upgrade to 19.1

That would be rather difficult as I have several services running on this server, unless I consider a distribution upgrade, in which case I’d have to analyse if anything will be broken by the distribution upgrade. It’s a battle I’d rather postpoine if I could, having noted your php upgrade in a previous post.

[uengin]

Just poking around under the hood in eGW’s php and web files, in the file
/usr/share/egroupware/header.inc.php.template I came across this:

*/<!-- BEGIN domain -->
$GLOBALS[‘egw_domain’][’{DB_DOMAIN}’] = array(
‘db_host’ => ‘{DB_HOST}’,
‘db_port’ => ‘{DB_PORT}’,
‘db_name’ => ‘{DB_NAME}’,
‘db_user’ => ‘{DB_USER}’,
‘db_pass’ => ‘{DB_PASS}’,
// Look at the README file
’db_type’ => ‘{DB_TYPE}’,
// This will limit who is allowed to make configuration modifications
’config_user’ => ‘{CONFIG_USER}’,
‘config_passwd’ => ‘{CONFIG_PASS}’
);

<!-- END domain -->

It does have a comment "look at the README file, where that readme file is, beats me. However, if only I could find out where these variables are populated from, then I’m sure that’d be the source…

[RalfBecker]

docker-composer is not available on jessie in any repository I tried to add

Docker and docker-compose is available for Jessie from Docker itself:

Get Docker Engine - Community for Debian

I did a successful installation with that on a Jessie system for a customer. I have not documented it, as I would always recommend to use a current and supported distribution.

Ralf

[uengin]

Thank you Ralf.

Docker and docker-compose is available for Jessie from Docker itself:

I am aware of this, however, I don’t see Jessie listed in Prerequisites:

To install Docker Engine - Community, you need the 64-bit version of one of these Debian or Raspbian versions:

*     Buster 10
*     Stretch 9 (stable) / Raspbian Stretch

Am I missing something here?

Plus, after setting up repositories, I get a package not located error, hence why I assumed it is because of version difference.

root@server:~# apt-get install docker-ce docker-ce-cli containerd.io
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package docker-ce-cli

Otherwise I’d rather install version 19.x

[uengin]

I mentioned earlier about manual dependency installations. Here’s what I mean:

root@server:~# apt-get install docker-ce  containerd.io
Reading package lists... Done
Building dependency tree
Reading state information... Done
docker-ce is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 containerd.io : Depends: libseccomp2 (>= 2.3.0) but 2.1.1-1 is to be installed
E: Unable to correct problems, you have held broken packages.

These kinds of library version dependancies are are like a spider web. It’s source is because I am not running Debian 9.0 or 10.0, obviously. So, If i am missing something, please do advise.

Thanks.

[RalfBecker]

Only other idea I have left: is your Jessie up to date?

On the other system I first installed all pending updates, and then docker-ce and last egroupware-docker. I believe the docker-compose came from our own repo, when I installed egroupware-docker.

Anyway Jessie/LTS supports end in June this year. It’s dead, not worse spending time with it!

Ralf

[uengin]

Anyone know where dpkg stores incomplete package setup data? Perhaps I can reach it that way.

[RalfBecker]

https://manpages.ubuntu.com/manpages/xenial/man8/dpkg-reconfigure.8.html

Ralf

[uengin]

Thanks Ralf.

I was going to say, I’ve already tried that, thinking of;

dpkg --configure <package name>

However, dpkg-reconfigure results in:

root@server:~# dpkg-reconfigure egroupware-epl
/usr/sbin/dpkg-reconfigure: egroupware-epl is broken or not fully installed

whereas, as noted, dpkg --configure fetches data inputs saved from the first install/setup/configure attempt.