Skip to main content
Solved

Cannot log into FME Server 2018.0 Docker deployment

  • April 20, 2018
  • 3 replies
  • 16 views
2
Forum|alt.badge.img

We have been running FME Server 2017.1 on Docker for a while, its great! I am trying to build a new FME Server 2018.0 on Docker and everything builds and I can bring up the log in page but after entering my credentials the page just clears out my info and nothing happens, I can hit the healthcheck rest endpoint and it says everything is "OK" but if I try and hit an endpoint that requires credentials I get the error:

"message": "Authentication failed: org.postgresql.util.PSQLException: ERROR: column l.last_updated does not exist\\n Position: 16"

I see that I am getting an error from the FME DB container log saying:

ERROR: column "guiline" of relation "fme_parameter" does not exist at character 117

I am using the FME Server 2018.0 as is, the only change is the EXTERNALHOSTNAME variable.

Any help would be appreciated.

Best answer by rylanatsafe

On quick glance, the error "ERROR: column l.last_updated does not exist\\n Position: 16" could appear if you are reusing the same database schema from FME Server 2017.1 for FME Server 2018.

Although if you are going through a "reinstall / upgrade-in-place" process – for example, included the down -v command – and plan to restore using the Web Interface, then I'm not certain why you experience this error!

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

2
Forum|alt.badge.img
  • 2dews
  • Author
  • 18 replies
  • April 20, 2018
@GerhardAtSafe, Safe Chat suggested I tag you on this.

 

rylanatsafe
Safer
Forum|alt.badge.img+14
  • rylanatsafeSafer
  • Safer
  • 671 replies
  • Best Answer
  • April 24, 2018

On quick glance, the error "ERROR: column l.last_updated does not exist\\n Position: 16" could appear if you are reusing the same database schema from FME Server 2017.1 for FME Server 2018.

Although if you are going through a "reinstall / upgrade-in-place" process – for example, included the down -v command – and plan to restore using the Web Interface, then I'm not certain why you experience this error!

2
Forum|alt.badge.img
  • 2dews
  • Author
  • 18 replies
  • April 24, 2018

On quick glance, the error "ERROR: column l.last_updated does not exist\\n Position: 16" could appear if you are reusing the same database schema from FME Server 2017.1 for FME Server 2018.

Although if you are going through a "reinstall / upgrade-in-place" process – for example, included the down -v command – and plan to restore using the Web Interface, then I'm not certain why you experience this error!

Thanks for the hint on the down -v command. I had previously removed all containers and images and ran prune for both but something must have lingered.

 

 

Community Stats

32,100
Posts
121,896
Replies
39,746
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.