From: Daniel Browne <dbrowne@(email surpressed)>
Subject: Server hostname change
   Date: Sat, 07 Aug 2010 03:02:56 -0400

Hi Greg,

Sorry to bother you on a weekend, but I'm shifting my servers around, splitting our database and intranet off onto a different server from licenses and Rush. As a result I've had to rename the license/Rush server so that everyone's web browser points instead to the new one. This seems to now be breaking Rush. The server and/or client daemons cannot resolve the host name internally, even though it's set correctly everywhere including in the old server's /etc/hostconfig. The original rush server was named "vegas", now it's renamed "oldvegas". Here's what appears in the server log:

08/06,23:37:31 INIT.D     Startup script '/usr/local/rush/etc/S99rush start'
08/06,23:37:31 INIT.D     Executing: ( /usr/local/rush/etc/S99rush waitlocal && cd /usr/local/rush/var && /usr/libexec/StartupItemContext /usr/local/rush/bin/rushd ) &
08/06,23:37:32 INIT.D     Local hostname oldvegas won't resolve (ping: cannot resolve oldvegas: Unknown host): 10 sec retries
08/06,23:37:42 INIT.D     Local hostname oldvegas won't resolve (ping: cannot resolve oldvegas: Unknown host): 10 sec retries
08/06,23:37:52 INIT.D     Local hostname oldvegas won't resolve (ping: cannot resolve oldvegas: Unknown host): 10 sec retries
08/06,23:38:04 ALERT      Tcp::GetRemoteHostname(0.0.0.0): host 0.0.0.0 not in oldvegas:/usr/local/rush/etc/hosts
08/06,23:38:04 LICENSE    Connect to ???[0.0.0.0] failed: 'vegas.eep.com'[vegas]: valid host is NOT in rush hostlist (/usr/local/rush/etc/hosts)
08/06,23:38:04 LICENSE    no servers could validate license (30 sec retries)
08/06,23:38:34 ALERT      Tcp::GetRemoteHostname(0.0.0.0): host 0.0.0.0 not in oldvegas:/usr/local/rush/etc/hosts
08/06,23:38:34 LICENSE    Connect to ???[0.0.0.0] failed: 'vegas.eep.com'[vegas]: valid host is NOT in rush hostlist (/usr/local/rush/etc/hosts)
08/06,23:38:34 LICENSE    no servers could validate license (30 sec retries)
08/06,23:39:04 ALERT      Tcp::GetRemoteHostname(0.0.0.0): host 0.0.0.0 not in oldvegas:/usr/local/rush/etc/hosts
08/06,23:39:04 LICENSE    Connect to ???[0.0.0.0] failed: 'vegas.eep.com'[vegas]: valid host is NOT in rush hostlist (/usr/local/rush/etc/hosts)
08/06,23:39:04 LICENSE    no servers could validate license (30 sec retries)
08/06,23:39:34 ALERT      Tcp::GetRemoteHostname(0.0.0.0): host 0.0.0.0 not in oldvegas:/usr/local/rush/etc/hosts
08/06,23:39:34 LICENSE    Connect to ???[0.0.0.0] failed: 'vegas.eep.com'[vegas]: valid host is NOT in rush hostlist (/usr/local/rush/etc/hosts)
08/06,23:39:34 LICENSE    no servers could validate license (30 sec retries)
08/06,23:40:04 ALERT      Tcp::GetRemoteHostname(0.0.0.0): host 0.0.0.0 not in oldvegas:/usr/local/rush/etc/hosts
08/06,23:40:04 LICENSE    Connect to ???[0.0.0.0] failed: 'vegas.eep.com'[vegas]: valid host is NOT in rush hostlist (/usr/local/rush/etc/hosts)
08/06,23:40:04 LICENSE    no servers could validate license (30 sec retries)
08/06,23:40:34 ALERT      Tcp::GetRemoteHostname(0.0.0.0): host 0.0.0.0 not in oldvegas:/usr/local/rush/etc/hosts
08/06,23:40:34 LICENSE    Connect to ???[0.0.0.0] failed: 'vegas.eep.com'[vegas]: valid host is NOT in rush hostlist (/usr/local/rush/etc/hosts)
08/06,23:40:34 LICENSE    no servers could validate license (30 sec retries)
08/06,23:41:04 ALERT      Tcp::GetRemoteHostname(0.0.0.0): host 0.0.0.0 not in oldvegas:/usr/local/rush/etc/hosts
08/06,23:41:04 LICENSE    Connect to ???[0.0.0.0] failed: 'vegas.eep.com'[vegas]: valid host is NOT in rush hostlist (/usr/local/rush/etc/hosts)
08/06,23:41:04 LICENSE    no servers could validate license (30 sec retries)
08/06,23:41:34 ALERT      Tcp::GetRemoteHostname(0.0.0.0): host 0.0.0.0 not in oldvegas:/usr/local/rush/etc/hosts
08/06,23:41:34 LICENSE    Connect to ???[0.0.0.0] failed: 'vegas.eep.com'[vegas]: valid host is NOT in rush hostlist (/usr/local/rush/etc/hosts)
08/06,23:41:34 LICENSE    no servers could validate license (30 sec retries)
08/06,23:42:04 ALERT      Tcp::GetRemoteHostname(0.0.0.0): host 0.0.0.0 not in oldvegas:/usr/local/rush/etc/hosts
08/06,23:42:04 LICENSE    Connect to ???[0.0.0.0] failed: 'vegas.eep.com'[vegas]: valid host is NOT in rush hostlist (/usr/local/rush/etc/hosts)
08/06,23:42:04 LICENSE    no servers could validate license (30 sec retries)
08/06,23:42:24 INIT.D     Shutdown script '/usr/local/rush/etc/S99rush stop'
08/06,23:42:24 EXIT       Shutdown script '/usr/local/rush/etc/S99rush stop'

Hi Daniel,

	Rush's permanent floating licenses are locked to the
	hostname/hostid pair, so changing either will disable
	the license.

	I can set you up with a temp license for the new hostname/hostid
	combo, but an actual license migration would be needed to make
	the change stick which may incur an administration fee, depending
	on how many migrations you've had so far.

	I'd suggest keeping the official hostname for the license server
	the same (it is a license server after all ;) and making hostname
	aliases or CNAMEs for the new names so that both resolve.

	If you need the new name for samba to resolve, you can
	likely hardcode 'vegas' into the smb.conf file for the
	new machine.

Daniel Browne wrote:
> Sorry to bother you on a weekend, but I'm shifting my servers around, split=
> ting our database and intranet off onto a different server from licenses an=
> d Rush. As a result I've had to rename the license/Rush server so that ever=
> yone's web browser points instead to the new one. This seems to now be brea=
> king Rush. The server and/or client daemons cannot resolve the host name in=
> ternally, even though it's set correctly everywhere including in the old se=
> rver's /etc/hostconfig. The original rush server was named "vegas", now it'=
> s renamed "oldvegas". Here's what appears in the server log:

	I'm surprised you're getting these errors with the hostname hard coded
	in /etc/hostconfig:

> 08/06,23:37:32 INIT.D     Local hostname oldvegas won't resolve (ping: cannot resolve oldvegas: Unknown host): 10 sec retries
> 08/06,23:37:42 INIT.D     Local hostname oldvegas won't resolve (ping: cannot resolve oldvegas: Unknown host): 10 sec retries

	..but they're benign, since the hostname eventually resolves
	after about 20 seconds.

	But I find it interesting that the OSX boot procedure has the
	OS up for that long without it having set its own hostname.
	Likely the machine's official hostname is 'localhost' during this time,
	from what I've seen from boot consoles on OSX.

	This is the real problem, though:

> 08/06,23:38:04 ALERT      Tcp::GetRemoteHostname(0.0.0.0): host 0.0.0.0 not in oldvegas:/usr/local/rush/etc/hosts
> 08/06,23:38:04 LICENSE    Connect to ???[0.0.0.0] failed: 'vegas.eep.com'[vegas]: valid host is NOT in rush hostlist (/usr/local/rush/etc/hosts)
> 08/06,23:38:04 LICENSE    no servers could validate license (30 sec retries )

	..those errors are the license trying to resolve 'vegas'.

	Contact me off list with the output of:

		rushd -hostid

	..from the new machine, and I can set you up with a temp license
	and migration instructions.

-- 
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)ext.23
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)

Ok, I'll see if switching back the hostname will work. Thanks greg.

On Aug 7, 2010, at 12:54 AM, Greg Ercolano wrote:

> [posted to rush.general]
> 
> Hi Daniel,
> 
> 	Rush's permanent floating licenses are locked to the
> 	hostname/hostid pair, so changing either will disable
> 	the license.
> 
> 	I can set you up with a temp license for the new hostname/hostid
> 	combo, but an actual license migration would be needed to make
> 	the change stick which may incur an administration fee, depending
> 	on how many migrations you've had so far.
> 
> 	I'd suggest keeping the official hostname for the license server
> 	the same (it is a license server after all ;) and making hostname
> 	aliases or CNAMEs for the new names so that both resolve.
> 
> 	If you need the new name for samba to resolve, you can
> 	likely hardcode 'vegas' into the smb.conf file for the
> 	new machine.
> 
> Daniel Browne wrote:
>> Sorry to bother you on a weekend, but I'm shifting my servers around, split=
>> ting our database and intranet off onto a different server from licenses an=
>> d Rush. As a result I've had to rename the license/Rush server so that ever=
>> yone's web browser points instead to the new one. This seems to now be brea=
>> king Rush. The server and/or client daemons cannot resolve the host name in=
>> ternally, even though it's set correctly everywhere including in the old se=
>> rver's /etc/hostconfig. The original rush server was named "vegas", now it'=
>> s renamed "oldvegas". Here's what appears in the server log:
> 
> 	I'm surprised you're getting these errors with the hostname hard coded
> 	in /etc/hostconfig:
> 
>> 08/06,23:37:32 INIT.D     Local hostname oldvegas won't resolve (ping: cannot resolve oldvegas: Unknown host): 10 sec retries
>> 08/06,23:37:42 INIT.D     Local hostname oldvegas won't resolve (ping: cannot resolve oldvegas: Unknown host): 10 sec retries
> 
> 	..but they're benign, since the hostname eventually resolves
> 	after about 20 seconds.
> 
> 	But I find it interesting that the OSX boot procedure has the
> 	OS up for that long without it having set its own hostname.
> 	Likely the machine's official hostname is 'localhost' during this time,
> 	from what I've seen from boot consoles on OSX.
> 
> 	This is the real problem, though:
> 
>> 08/06,23:38:04 ALERT      Tcp::GetRemoteHostname(0.0.0.0): host 0.0.0.0 not in oldvegas:/usr/local/rush/etc/hosts
>> 08/06,23:38:04 LICENSE    Connect to ???[0.0.0.0] failed: 'vegas.eep.com'[vegas]: valid host is NOT in rush hostlist (/usr/local/rush/etc/hosts)
>> 08/06,23:38:04 LICENSE    no servers could validate license (30 sec retries )
> 
> 	..those errors are the license trying to resolve 'vegas'.
> 
> 	Contact me off list with the output of:
> 
> 		rushd -hostid
> 
> 	..from the new machine, and I can set you up with a temp license
> 	and migration instructions.
> 
> -- 
> Greg Ercolano, erco@(email surpressed)
> Seriss Corporation
> Rush Render Queue, http://seriss.com/rush/
> Tel: +1 626-576-0010 ext.23
> Fax: +1 626-576-0020
> Cel: +1 310-266-8906

Hi Greg,

Sounds then like we'll have to wait until we make the transition to a new license server to change the names around.

-Dan


On Aug 7, 2010, at 12:54 AM, Greg Ercolano wrote:

> [posted to rush.general]
> 
> Hi Daniel,
> 
> 	Rush's permanent floating licenses are locked to the
> 	hostname/hostid pair, so changing either will disable
> 	the license.
> 
> 	I can set you up with a temp license for the new hostname/hostid
> 	combo, but an actual license migration would be needed to make
> 	the change stick which may incur an administration fee, depending
> 	on how many migrations you've had so far.
> 
> 	I'd suggest keeping the official hostname for the license server
> 	the same (it is a license server after all ;) and making hostname
> 	aliases or CNAMEs for the new names so that both resolve.
> 
> 	If you need the new name for samba to resolve, you can
> 	likely hardcode 'vegas' into the smb.conf file for the
> 	new machine.
> 
> Daniel Browne wrote:
>> Sorry to bother you on a weekend, but I'm shifting my servers around, split=
>> ting our database and intranet off onto a different server from licenses an=
>> d Rush. As a result I've had to rename the license/Rush server so that ever=
>> yone's web browser points instead to the new one. This seems to now be brea=
>> king Rush. The server and/or client daemons cannot resolve the host name in=
>> ternally, even though it's set correctly everywhere including in the old se=
>> rver's /etc/hostconfig. The original rush server was named "vegas", now it'=
>> s renamed "oldvegas". Here's what appears in the server log:
> 
> 	I'm surprised you're getting these errors with the hostname hard coded
> 	in /etc/hostconfig:
> 
>> 08/06,23:37:32 INIT.D     Local hostname oldvegas won't resolve (ping: cannot resolve oldvegas: Unknown host): 10 sec retries
>> 08/06,23:37:42 INIT.D     Local hostname oldvegas won't resolve (ping: cannot resolve oldvegas: Unknown host): 10 sec retries
> 
> 	..but they're benign, since the hostname eventually resolves
> 	after about 20 seconds.
> 
> 	But I find it interesting that the OSX boot procedure has the
> 	OS up for that long without it having set its own hostname.
> 	Likely the machine's official hostname is 'localhost' during this time,
> 	from what I've seen from boot consoles on OSX.
> 
> 	This is the real problem, though:
> 
>> 08/06,23:38:04 ALERT      Tcp::GetRemoteHostname(0.0.0.0): host 0.0.0.0 not in oldvegas:/usr/local/rush/etc/hosts
>> 08/06,23:38:04 LICENSE    Connect to ???[0.0.0.0] failed: 'vegas.eep.com'[vegas]: valid host is NOT in rush hostlist (/usr/local/rush/etc/hosts)
>> 08/06,23:38:04 LICENSE    no servers could validate license (30 sec retries )
> 
> 	..those errors are the license trying to resolve 'vegas'.
> 
> 	Contact me off list with the output of:
> 
> 		rushd -hostid
> 
> 	..from the new machine, and I can set you up with a temp license
> 	and migration instructions.
> 
> -- 
> Greg Ercolano, erco@(email surpressed)
> Seriss Corporation
> Rush Render Queue, http://seriss.com/rush/
> Tel: +1 626-576-0010 ext.23
> Fax: +1 626-576-0020
> Cel: +1 310-266-8906