Skip to main content

On the screenshot to the right you can see that the webpage is trying to reach a link with fmeapiv4 in it. 

If I look in the logs (I added them as attachment) I see some interesting things in the tomcat/core-0/Catalina log. It looks like fmeserver has trouble starting the webapp fmeapiv4. What I can make of it is in part because it can not reach the DB. But everything else seems to be working so the overall connection to the DB seems to be fine. 

 

Anyone any idea what might cause this issue and how to resolve this?

Hi @mathijs​ Actually the first thing is that the System is not connecting to the 'UnknownHostException: fmeserverdb'. Review line 104 in the log file you shared. If the system cannot establish a connection to the fmeserverdb then basically that is a blocker. The database is key for FME Server to startup at all. Even though you are getting a web ui of sorts, it is not populated and the 404 errors are related to the Web Application not able to connect to the database as well - most likely.

 

So we need to figure out why the connection is failing there. This deployment isn't happy. Have you done anything special when deploying that might have affected the database?

Thanks.


Hi @steveatsafe​ ,

 

thanks for your answer. Was able to fix it thanks to Safe support. In the newer version the web container needs a connection to the postgres database. This was not the case in te version I was coming from (2019.2.2) I didn't add all the right environment variables to the web container. Adding them fixed my problem.


Hi @steveatsafe​ ,

 

thanks for your answer. Was able to fix it thanks to Safe support. In the newer version the web container needs a connection to the postgres database. This was not the case in te version I was coming from (2019.2.2) I didn't add all the right environment variables to the web container. Adding them fixed my problem.

Perfect! And hopefully more folks will benefit from this post if they run into a similar issue. Thanks for posting.


Reply