This topic has 3 replies, 2 voices, and was last updated 4 years, 1 month ago by NaturalBornCamper.

  • Author
    Posts
  • #22330
     NaturalBornCamper
    Participant

    Hello, I followed these guides:
    https://backstage.forgerock.com/docs/openam/13.5/getting-started/
    https://backstage.forgerock.com/docs/openam/13.5/install-guide/

    But OpenAM fails to configure, I keep getting this message in “install.log” when using custom configuration:

    errorcom.sun.identity.common.configuration.ConfigurationException: OpenDJ cannot be started

    I can’t use default configuration because it results in a bunch of errors since it’s trying to set all the ports to “-1”.
    So with the manual configuration, I leave everything at default with the recommended ports with the simple user store (not using OpenDJ).
    I’m using a Google Cloud VM with Ubuntu 18
    OpemAM 13.5.2
    Oracle Java (javac 1.8.0_171)
    Running tomcat as root using sudo since it’s only a developement environment and I want to avoid permission issues

    #22331
     joe.starling
    Participant

    The ‘-1’ port thing is usually because the hostname isn’t resolvable. Check your /etc/hosts

    #22341
     NaturalBornCamper
    Participant

    Hello :)

    hosts file is ok, the hostname is reachable. I think it’s the Azure and Google Cloud load balancers.

    Anyways, the most important issue is openDJ, I tried on another VM where the default config works and it still hangs when starting OpenDJ, the install.log contains this:


    06/20/2018 09:21:57:928 AM EDT: …Success.
    06/20/2018 09:21:57:928 AM EDT: …Success
    06/20/2018 09:21:57:929 AM EDT: Installing OpenAM configuration store in /root/openam/opends
    06/20/2018 09:21:57:929 AM EDT: Starting OpenDJ in /root/openam/opends

    Dumping all configuration parameters…

    Request Parameters:
    acceptLicense = true
    actionLink = createDefaultConfig
    ADMIN_CONFIRM_PWD = #########
    ADMIN_PWD = #########

    #22342
     NaturalBornCamper
    Participant

    I’m currently trying with the paid Access Management officiall ForgeRock software and the same thing happens, freezes around openDS:

    06/20/2018 12:08:19:824 PM EDT: Checking license acceptance…
    06/20/2018 12:08:19:825 PM EDT: License terms accepted.
    06/20/2018 12:08:19:837 PM EDT: Checking configuration directory /root/am.
    06/20/2018 12:08:19:840 PM EDT: …Success.
    06/20/2018 12:08:20:027 PM EDT: Extracting DS, please wait…
    06/20/2018 12:08:28:317 PM EDT: Complete
    06/20/2018 12:08:28:320 PM EDT: Running DS setup
    06/20/2018 12:08:44:519 PM EDT: …Success
    06/20/2018 12:08:44:530 PM EDT: Starting DS for serverRoot /root/am/opends

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

©2022 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?