Incorrect User or Password from GUI

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Incorrect User or Password from GUI

L2 Linker

We have changed the admin password to something other than the default but now after a period of time we are getting "Incorrect User or Password" when trying to login via the GUI.  A few times before this we getting logged in then kicked out immediately and I had to reboot the device to fix it. But now nothing seems to work. 

 

I can still login via the CLI with expedition user. Is there a way I can add an Expedition user or edit the admin account from the CLI?

 

 

1 accepted solution

Accepted Solutions

L5 Sessionator

Is still the issue persisting?

 

This may be related to a database access issue, and the reasons could be:

  • PHP database access parameters have been modified and are now incorrect (php files within /home/userSpace)
  • The OS has been upgraded an libraries for database drivers are now in a non-supported version (this would require recreating an Expedition instance)
  • Database is not up and running (the service mysql is down)

 

View solution in original post

25 REPLIES 25

L5 Sessionator

Is still the issue persisting?

 

This may be related to a database access issue, and the reasons could be:

  • PHP database access parameters have been modified and are now incorrect (php files within /home/userSpace)
  • The OS has been upgraded an libraries for database drivers are now in a non-supported version (this would require recreating an Expedition instance)
  • Database is not up and running (the service mysql is down)

 

@dgildelaig Thanks again for your help. As you mention it was an issue with mysql being down. But looks like something might be corrupt since our conversion of the origional beta tool from Fusion to ESX. 

 

To be safe we will probably build a new Expedition and migrate our projects if needed. 

 

 

I am experiencing the same issue. I can login immediately after rebooting Expedition using the "admin" account. I cannot login using any LDAP accounts or using admin credentials after logging out or waiting to login.

 

  • Which file houses the database paramenters? userDefinitions.php?
  • The OS has not been upgraded, still on 16.04.5 LTS. Upgraded to Expedition 1.1.3 yesterday using the update commands.
  • The mysql service is running.

 

Found the issue, how would this be resolved?

 

> service mysql status

 

Jan 17 15:52:20 Expedition mysqld[1693]: 2019-01-17 15:52:20 140514870733568 [Warning] Aborted connection 106 to db: 'RealTimeUpdates' user: 'root' host: 'localhost' (Got timeout reading communication pac
Jan 17 15:52:20 Expedition mysqld[1693]: 2019-01-17 15:52:20 140515157236480 [Warning] Aborted connection 103 to db: 'pandb' user: 'root' host: 'localhost' (Got timeout reading communication packets)
Jan 17 15:52:20 Expedition mysqld[1693]: 2019-01-17 15:52:20 140514871339776 [Warning] Aborted connection 104 to db: 'pandbRBAC' user: 'root' host: 'localhost' (Got timeout reading communication packets)
Jan 17 15:55:20 Expedition mysqld[1693]: 2019-01-17 15:55:20 140515605535488 [Warning] Aborted connection 2 to db: 'pandb' user: 'root' host: 'localhost' (Got timeout reading communication packets)
Jan 17 15:55:20 Expedition mysqld[1693]: 2019-01-17 15:55:20 140515552967424 [Warning] Aborted connection 3 to db: 'pandbRBAC' user: 'root' host: 'localhost' (Got timeout reading communication packets)
Jan 17 15:55:20 Expedition mysqld[1693]: 2019-01-17 15:55:20 140515552664320 [Warning] Aborted connection 4 to db: 'RealTimeUpdates' user: 'root' host: 'localhost' (Got timeout reading communication packe
Jan 17 15:55:20 Expedition mysqld[1693]: 2019-01-17 15:55:20 140515552361216 [Warning] Aborted connection 5 to db: 'RealTimeUpdates' user: 'root' host: 'localhost' (Got timeout reading communication packe
Jan 17 15:56:51 Expedition mysqld[1693]: 2019-01-17 15:56:51 140515456244480 [Warning] Aborted connection 54 to db: 'pandb' user: 'root' host: 'localhost' (Got timeout reading communication packets)
Jan 17 15:56:51 Expedition mysqld[1693]: 2019-01-17 15:56:51 140515160570624 [Warning] Aborted connection 56 to db: 'RealTimeUpdates' user: 'root' host: 'localhost' (Got timeout reading communication pack
Jan 17 15:56:51 Expedition mysqld[1693]: 2019-01-17 15:56:51 140515160267520 [Warning] Aborted connection 57 to db: 'RealTimeUpdates' user: 'root' host: 'localhost' (Got timeout reading communication pack

 

 

Thanks!

Which version of Mariadb are you using?

 

You can see the installed package by executing the following:

 

apt list --installed | grep mariadb

 

It seems that your database is cutting connections, which should affect the whole Expedition experience.

LDAP module is not set up via php parameters, but you define the parameters in the Servers section, providing the server name, port, prefix, suffix, etc.

 

Here is the output:

 


libmariadb2/xenial,now 2.0.0-1 amd64 [installed]
libmariadbclient18/now 10.1.35+maria-1~xenial amd64 [installed,upgradable to: 10.1.37+maria-1~xenial]
mariadb-client/now 10.1.35+maria-1~xenial all [installed,upgradable to: 10.1.37+maria-1~xenial]
mariadb-client-10.1/now 10.1.35+maria-1~xenial amd64 [installed,upgradable to: 10.1.37+maria-1~xenial]
mariadb-client-core-10.1/now 10.1.35+maria-1~xenial amd64 [installed,upgradable to: 10.1.37+maria-1~xenial]
mariadb-common/now 10.1.35+maria-1~xenial all [installed,upgradable to: 10.1.37+maria-1~xenial]
mariadb-server/now 10.1.35+maria-1~xenial all [installed,upgradable to: 10.1.37+maria-1~xenial]
mariadb-server-10.1/now 10.1.35+maria-1~xenial amd64 [installed,upgradable to: 10.1.37+maria-1~xenial]
mariadb-server-core-10.1/now 10.1.35+maria-1~xenial amd64 [installed,upgradable to: 10.1.37+maria-1~xenial]

It does not seem to be an issue related to the Mariadb version, as the one we are using is also 10.1 (subversion 33, tho).

 

Please, send us an email to fwmigrate at paloaltonetworks dot com and we will try to give you support via a Zoom meeting or similar.

 

Did you guys ever talk about a way to reset the GUI admin password via the expedition user in the CLI?  I can't seem to find a way to do that.  My services look good, We did do an update so there is a possibility of the corruption you mentioned.  Is there a way to do a password reset through the CLI?

Thanks,

Alex in MT

Hi, did you find a way to password reset through the CLI?

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.

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'

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? 

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

 

Make sure you update Expedition to the most recent version.

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:~$

  • 1 accepted solution
  • 26070 Views
  • 25 replies
  • 1 Likes
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 LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!