If there are errors related to the communications with the database due to the PDOCOnnector, those will show there One easy way to check if the error is there is to keep the file open with aĪnd while having this file open for reading in a terminal, open a Web Browser and try to login. You could check if this is your case looking at the apache error logs, that you could find in /var/log/apache2/error.log. If you have executed an "apt upgrade", most probably MariaDB will have updated to the latest version, and some dependencies would stop working, invoving a PDOConnect. One that has given some problems is the latest versions of MariaDB, the Database manager that we use in Expedition. I mention this because it is important that the correct versions of the package dependencies are installed. You mention that the installation was successful, so I understand that you did not see any errors during the installation script execution. Those are the correct credentials to access via GUI (web https). To get started with your Expedition installation, download the Expedition installer script:ĭownload and follow the use case examples in the available Expedition Admin Guide and Technotes:Īsk questions in the Expedition Community The attached document describes the OS requirements (Ubuntu 16.0.4) and recommend compute resources.ĭownload and read the attached Expedition installer guide. The changes in the Expedition installation provides greater flexibility allowing users to deploy Expedition on-prem onto their local hyper-visor or onto a cloud compute resource in AWS, Azure, and Google Cloud. The process to install and deploy Expedition has been changed by offering an installable script that can be used to deploy onto your own instance of Ubuntu 16.04 LTS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |