Search Engine: Elastic

Article ID: 2057, created on Jul 27, 2007, last review on Aug 12, 2016

  • Applies to:
  • Odin Automation
  • Odin Business Automation Standard 4.5


To change the Odin Business Automation Standard (OBAS) system hostname, use the following instructions.

  • Make sure that the new hostname is resolving properly to the IP address assigned to the OBAS server.
  • Set the new hostname for the OBAS server using the following commands on the Virtuozzo hardware node where your OBAS container resides:

    ~# vzctl stop %CTID%
    ~# vzctl set %CTID% --hostname %NEWHOSTNAME% --save
    ~# vzctl start %CTID%

    The %NEWHOSTNAME% variable in the command above should be replaced with the new hostname to be assigned to the OBAS system and %CTID% should be replaced with the real ID of the container.

  • Execute the following command inside the OBAS server:

    ~# hspc-config --reset-hostname
  • Check the OBAS Store URL on the Top > Commerce Director > Store Manager > Configure Store screen in your Provider Control Panel and update it if required using the Edit button.

  • If SSL is configured for the Provider Control Panel, you will need to update the SSL certificate on the Top > Configuration Director > Miscellaneous settings > SSL Setup screen to avoid a warning message regarding SSL certificate mismatch.

Additional Information

  • For a OBAS server running on SUSE Enterprise Linux, make sure you have hostname set in FQDN form. For example:

    # hostname

    if hostname is "", then all is correct. if hostname is just "myhost", then execute

    # hostname
  • Changing the hostname for a running container with a running MySQL server could cause issues with MySQL server behavior. This is because MySQL server initscripts/tools depend on "hostname" output and, when the container hostname is changed in runtime, MySQL server might be unable to find some runtime files (the pid file, for example) which were created before hostname was changed.

400e18f6ede9f8be5575a475d2d6b0a6 8fc71f07abe5b233fea1ae0377cd5e3d 70a5401e8b9354cd1d64d0346f2c4a3e 624ca542e40215e6f1d39170d8e7ec75 3ef1f5f998c0dc182718a7fe4376f875

Email subscription for changes to this article
Save as PDF