Who Me Too'd this topic

Who Me Too'd this topic


Filr 3.4.3 to 4.0 upgrade

Hi today i was trying to upgrade filr 3.4.3 to 4.x but i had some problems with upgrade.

More or less problem was with migration from mysql to postgresql.

I was following this documentation:

Everything went well until i came to this point:
When the appliance displays the final screen in the console window, open your management browser and log in to the appliance on port 9443 as the vaadmin user.

Here i had some errors/missing icons:

  1. phpPGAdmin icon is missing in UI
  2. Filr - Configuration returned error. PostgreSQL problem.

  3. From what i have noticed is that Postgres is trying to use ROOT user which doesn't exist. I had to modify /filrinstall/installer.xml and change username to POSTGRES

    <Config id="Installed" type="PostgreSql">
    <Resource driverClassName="org.postgresql.Driver" for="icecore" password="SOME_PASSWORD" url="jdbc:postgresql://localhost:5432/filr?charSet=UTF-8" username="postgres"/>

    Second problem was that even that authentication was correct in console, i didn't get it to work from filr script so i have changed postgres authentication method from MD5 to Trust.

    File: /vastorage/postgres/conf/vabase-pg_hba.conf
    local all all trust

    And the third problem was that database filr was missing. I was first looking if some script includes creation of filr database but i couldn't find it so i have created it on my own.
    psql -U postgres -c "create database filr;"

    After this upgrade finished.

    Upgrade could be restarted through https://FILR_IP:9443/filrconfig
    After you get an error you click "Finish" and filr retries upgrade.

    After another check i have noticed that if upgrade is succesfull phpPGAdmin icon is there, but connecting to https://FILR_IP:8443/ssf/a/ returns an error so i need to debug more.


    HTTP Status 500 – Internal Server Error
    Type Exception Report

    Description The server encountered an unexpected condition that prevented it from fulfilling the request.


    Note The full stack trace of the root cause is available in the server logs.

    I hope this helps someone.
Who Me Too'd this topic
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.