Full hostname appears throughout Content Center UI

TeamSite 6.1 Linux
TeamSite 6.1 SP1 Solaris

I have done something to the network settings or configuration files that has caused the hostname shown throughout the UI from servername to servername.company.com. My local IWTemp directory even has both versions.

If I put in //servername inside the CCPro browser it converts it to servername.company.com automatically.

I looked at the /etc/hosts file and compared iw.cfg across a working solaris server and nothing jumped out at me, except that I originally had the full hostname in the launchpad_hostname section. I changed that to just be the server name but that hasn't helped.

Any ideas?

Find more posts tagged with

Comments

nipper

So it is not fully qualified in iw.cfg ?

Has the GUI been rebuilt since you changed it ? I wonder if that is something set at install (and GUI build) time.

Bill Klish

GUI has been rebuilt countless times with ui customizations.

full hostname is specified in iw.cfg in some places, similar to how it is on our solaris servers. This was working until around march and I went back and looked to see if there were any changes to iw.cfg. There were not, so this can't be the issue.

executing hostname at the command line returns me just the server name. Running TeamSite::Config::hostname() gives me the fully qualified name. If I do a nslookup it returns correctly.

This is what my /etc/hosts file has:
127.0.0.1 localhost.localdomain localhost
XX.****.XX.**** servername.company.com servername

I have restarted the iw.server process, did iwreset -a, started and stopped networking. I don't want to just reboot the box, but I may try that too unless anyone else has some better thoughts.

Bill Klish

Oddly, I am getting the following in tsisvalid.log

License is good for node-locked licensing.
(valid string = XXXXXXXXXXXXXXXXXXXXXXXXXX)

However, the host names do not match.
The current hostname is "servername.company.com"
The license key expects the hostname to be "servername"

Not sure if this is related or not. Otherwise I am at a loss for what has changed here.

Bill Klish

I found the answer to this issue. It was fairly easy. The iw-home/cssdk.cfg file had the fully qualified hostname in it, rather then just the hostname. Making that change and restarting the teamsite services fixed this issue.