KHUB Interface Cannot Be Accessed - Fluid Topics - 3.8

Fluid Topics Troubleshooting Guide

Product
Fluid Topics
FT_Version
3.8
Platform
RHEL
Category
Reference Guide
language
English

Issue

Trying to access the KHUB Interface displays the following error message(s):

  • 500 — Internal Server Error
  • Unable to load Publish Page
  • Cannot list sources in admin page 'Publish'
  • The fluidtopics.log file contains the following line:

    2019-01-14 08:19:35,189 WARN 153.65.221.8 MAC_OS_X-FIREFOX_64.0 36de5579-4aa4-4aaa-a387-6ed134aef98e ft-70107-rc - net.antidot.fluidtopics.server.model.afs.AfsResponseParser - Failed to sanitize AFS input, rollbacking to first error

    It means that Fluid Topics is unable to read the message sent by AFS.

  • The fluidtopics.log file contains the following line:

    Caused by: com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')

    It means that a configuration issue prevents Fluid Topics from contacting AFS web services. When the server tries to do so, it receives an Apache error page with HTML content instead of a proper JSON response from Search and Back-Office web services.

Impact(s) on users

  • This issue prevents KHUB Admin users from uploading content to the portal or managing sources.
  • This issue prevents end-users from having up-to-date documentation.

Possible root cause(s)

This issue might occur when:

  • The ws.conf.json file has not been created or is not properly configured.

Solution(s)

Solution 1

  • Make sure that the Back Office is properly configured:

    Check that the values set for "bo" or "default" in the ws.conf.json file are correct by making the following request on the Front server:

    curl "$URL/bo-ws/authentication/current?afs:output=json"

    You should get a JSON response.

Solution 2

  • Make sure that the Search is properly configured:

    Check that the values set for "search" or "default" in the ws.conf.json file are correct by making the following request on the Front server:

    curl "$URL/search?afs:output=json"

    You should get a JSON response.