Filr not available after upgrade to 24.1

Hi Community,

just upgrade our large Filr env to 24.1, didn't receive any error message but now :

- we are unable to login to web interface (nor local admin)

- branding does not appear on the web page (opentext Filr, is displayed)

seems every service are running fine : search appliance, postgresql, filr ... etc

disk space is not critical and inode count seems correct, too

any idea ?

Thanks,

Regards

Everyone is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid. [A. Einstein]

Parents
  • 0

    In general I'm seconding Diethmar :).

    However: since all service are running and you get a login page but cannot log in I have to ask the one basic question I stumblen on a few times with Filr: Have you cleared your browser cache?
    I have seen time and time again that the JS code fo the authentication in Filr was changed and I had to either clear the cache or "Shift-Reload" in my browser. The case that the admin could not log in was there for me after the jump to 23.x.
    As for the branding: if that persists after cache-clearing, look in the network console of your browser and check if the branding is asked for and if so, what error code it get's. 404? 403? 500?

    HTH!

Reply
  • 0

    In general I'm seconding Diethmar :).

    However: since all service are running and you get a login page but cannot log in I have to ask the one basic question I stumblen on a few times with Filr: Have you cleared your browser cache?
    I have seen time and time again that the JS code fo the authentication in Filr was changed and I had to either clear the cache or "Shift-Reload" in my browser. The case that the admin could not log in was there for me after the jump to 23.x.
    As for the branding: if that persists after cache-clearing, look in the network console of your browser and check if the branding is asked for and if so, what error code it get's. 404? 403? 500?

    HTH!

Children
  • 0   in reply to 

    Good point, Christian!

    In one of my update scenarios I had exactly this situation. I assumed that another update failed but then I used a "private" browser window. Unexpectedly Filr was okay.

    With this experience I returned to some of my failed updates hoping for a solution. Unfortunately these filr updates still stuck ...

    Nevertheless my list of waiting updates was shorter Wink


    Use "Verified Answers" if your problem/issue has been solved!

  • 0 in reply to 

    Thank you Christian,

    I did a test with a private browser session.

    I retest just now and received a failing page, then I notice both services : filr.service and  novell-famtd.service, are "suddenly"  : Active: inactive (dead)

    So I have now join the "other" "failure group"

    let's X-fingers on a quick resolution

    Everyone is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid. [A. Einstein]