Incorrect User or Password from GUI

L2 Linker

Re: Incorrect User or Password from GUI

I don't think there is a way to do this? But the issue in this thread ended up being a result of a database issue and mysql being down. If you are experiencing the same issue it's best to contact the fwmigrate team for assistance.

L4 Transporter

Re: Incorrect User or Password from GUI

If you find yourself forgeting the password for the Web access, you can reset the "admin" password via CLI.

 

To do so, simply execute the following script from CLI:

 

expedition@Expedition:~$ php /home/userSpace/utils/restore/restoreAdmin.php

✓ Connected successfully to the database
✓ Admin user found
✓ Admin password restored to: 'paloalto'

Tags (1)
L0 Member

Re: Incorrect User or Password from GUI

We are trying to run this command, but we get this error:

 

expedition@ukdc1-pm-exp01:~$ php /home/userSpace/utils/restore/restoreAdmin.php
Could not open input file: /home/userSpace/utils/restore/restoreAdmin.php
expedition@ukdc1-pm-exp01:~$ php /home/userSpace/utils/restoreAdmin.php
PHP Warning: mysqli::__construct(): (HY000/2002): No such file or directory in /home/userSpace/utils/restoreAdmin.php on line 81
Connection failed: No such file or directoryexpedition@ukdc1-pm-exp01:~$

 

Any Ideas? 

L4 Transporter

Re: Incorrect User or Password from GUI

This feature to restore the Web Admin password is available from 1.1.11.

 

Make sure you update Expedition to the most recent version.

L3 Networker

Re: Incorrect User or Password from GUI

I am still getting that error as well. 

 

expedition@pan-expedition:~$  php /home/userSpace/utils/restore/restoreAdmin.php

PHP Warning:  mysqli::__construct(): (HY000/2002): No such file or directory in /home/userSpace/utils/restore/restoreAdmin.php on line 81

Connection failed: No such file or directoryexpedition@pan-expedition:~$ sudo apt-get install expedition-beta

[sudo] password for expedition:

Reading package lists... Done

Building dependency tree       

Reading state information... Done

expedition-beta is already the newest version (1.1.15).

0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.

expedition@pan-expedition:~$ service mysql status

mariadb.service - MariaDB 10.1.38 database server

   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)

  Drop-In: /etc/systemd/system/mariadb.service.d

           └─migrated-from-my.cnf-settings.conf

   Active: failed (Result: exit-code) since Thu 2019-04-18 17:46:00 CDT; 1min 24s ago

     Docs: man:mysqld(8)

           https://mariadb.com/kb/en/library/systemd/

  Process: 1544 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)

  Process: 1191 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl

  Process: 1159 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)

  Process: 1139 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)

Main PID: 1544 (code=exited, status=1/FAILURE)

   Status: "MariaDB server is down"

 

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.42-84

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140142706677504 [Note] InnoDB: Dumping buffer pool(s) not yet started

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [Note] Plugin 'FEEDBACK' is disabled.

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [Note] Recovering after a crash using tc.log

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [ERROR] Can't init tc log

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [ERROR] Aborting

Apr 18 17:46:00 pan-expedition systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE

Apr 18 17:46:00 pan-expedition systemd[1]: Failed to start MariaDB 10.1.38 database server.

Apr 18 17:46:00 pan-expedition systemd[1]: mariadb.service: Unit entered failed state.

Apr 18 17:46:00 pan-expedition systemd[1]: mariadb.service: Failed with result 'exit-code'.

...skipping...

mariadb.service - MariaDB 10.1.38 database server

   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)

  Drop-In: /etc/systemd/system/mariadb.service.d

           └─migrated-from-my.cnf-settings.conf

   Active: failed (Result: exit-code) since Thu 2019-04-18 17:46:00 CDT; 1min 24s ago

     Docs: man:mysqld(8)

           https://mariadb.com/kb/en/library/systemd/

  Process: 1544 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)

  Process: 1191 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl

  Process: 1159 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)

  Process: 1139 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)

Main PID: 1544 (code=exited, status=1/FAILURE)

   Status: "MariaDB server is down"

 

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.42-84

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140142706677504 [Note] InnoDB: Dumping buffer pool(s) not yet started

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [Note] Plugin 'FEEDBACK' is disabled.

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [Note] Recovering after a crash using tc.log

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [ERROR] Can't init tc log

Apr 18 17:45:58 pan-expedition mysqld[1544]: 2019-04-18 17:45:58 140143676705024 [ERROR] Aborting

Apr 18 17:46:00 pan-expedition systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE

Apr 18 17:46:00 pan-expedition systemd[1]: Failed to start MariaDB 10.1.38 database server.

Apr 18 17:46:00 pan-expedition systemd[1]: mariadb.service: Unit entered failed state.

Apr 18 17:46:00 pan-expedition systemd[1]: mariadb.service: Failed with result 'exit-code'.

~

~

~

~

~

~

~

~

~

~

~

~

~

~

~

~

~

~

expedition@pan-expedition:~$ sudo php /home/userSpace/utils/restore/restoreAdmin.php

PHP Warning:  mysqli::__construct(): (HY000/2002): No such file or directory in /home/userSpace/utils/restore/restoreAdmin.php on line 81

Connection failed: No such file or directoryexpedition@pan-expedition:~$

L4 Transporter

Re: Incorrect User or Password from GUI

I can see that your log points out that the database is not available.

 

The users credentials are in the database, and if we do not have it running, it can't validate them.

 

The issue seems to be in the tc.log file. It may have got corrupted at some point (no big deal) and it can access it.

Try deleting the file

sudo rm -f /var/lib/mysql/tc.log

and afterwards, try starting mariadb again.

sudo service mysql start

 

Later, if MariaDB started correctly, just check if you can log into the GUI with your normal credentials. If it still fails, then try restorning the admin password with the CLI script

 

php /home/userSpace/utils/restore/restoreAdmin.php

 

Tags (1)
L2 Linker

Re: Incorrect User or Password from GUI

I've been getting this as well.

 

Your suggestion definitely allowed me to start MariaDB and log in to the GUI, thanks; but seems Expedition is corrupted "Remote Exception" with no additional detail as soon as I log in, and much of the dashboard and all of the Internal Checks is broken.

 

Thanks anyway, looks like I'll have to rebuilt.

L4 Transporter

Re: Incorrect User or Password from GUI

We could check the apache error logs to see if there is something more that we should check.

 

Could you check if you have errors in

/var/log/apache/error.log?

 

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!