From: Luigi Tommaseo <luigi@(email surpressed)>
Subject: rresvport_NET: All ports in use
   Date: Fri, 11 May 2007 10:00:36 -0400

Hi Greg,

rush is to the latest a8 version and it is an osx mac-intel 10.4.8

thanks

Luigi Tommaseo
Digital Systems Manager
Senate Visual Effects
Twickenham Film Studios
St.Margarets
Twickenham
Middlesex
TW1 2AW

Tel: (Tel# suppressed)
luigi@(email surpressed)
www.senatevfx.com

Luigi Tommaseo wrote:
> Hi Greg,
> I have a machine here that won't submit with error "rresvport_NET:  
> All ports in use"

Hi Luigi,

	Can you verify the perms on the rush and rushd executables
	are 4755 and owned by root/wheel? eg:

ls -la /usr/local/rush/bin/{rush,rushd}

	If they're wrong, you can fix them with:

		chown 0:0  /usr/local/rush/bin/{rush,rushd}
		chmod 4755 /usr/local/rush/bin/{rush,rushd}

	..then restart rushd, and see if that solves it.

	If that's the problem, I'll add the error message to the FAQ.

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

we had the same problem on a linux box. This is what we did.

stopped the rush service
uninstalled rush

installed it.
gave it the latest host list
started the rush service
it worked after that.


Luigi Tommaseo wrote:

[posted to rush.general]

Hi Greg,

I have a machine here that won't submit with error "rresvport_NET: All ports in use" I tried searching for that error string with no results, can you please let me know what it means and what to do about it?

rush is to the latest a8 version and it is an osx mac-intel 10.4.8

thanks

Luigi Tommaseo
Digital Systems Manager
Senate Visual Effects
Twickenham Film Studios
St.Margarets
Twickenham
Middlesex
TW1 2AW

Tel: (Tel# suppressed)
luigi@(email surpressed)
www.senatevfx.com

Tyler Opatrny wrote:
> [posted to rush.general]
> 
> we had the same problem on a linux box. This is what we did.
> 
> stopped the rush service
> uninstalled rush
> We coppied over the install files, and ran a chmod 777 of the rush 
> folder before installing installed it.
> gave it the latest host list
> started the rush service
> it worked after that.

	Hmm, no, I would not ever recommend chmod 777 of the
	rush directory. That's just an invitation for someone to
	root the machine.

	With perms like that, an ordinary user could rename out the
	/usr/local/rush/etc or /usr/local/rush/bin directories,
	and install their own programs that would run their commands
	as root when the machine reboots to start the daemons.

	No, you want the /usr/local/rush directory, and its subdirs
	to be 755, and the rush and rushd binaries to be 4755 root/root.

	The 'install.sh' script tries to enforce the rush and rushd
	binary perms to prevent such problems. The only way they could
	be changed is by someone manually changing the perms after the
	install.sh script is run, which shouldn't happen.

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

Hi,

thanks


Luigi Tommaseo
Digital Systems Manager
Senate Visual Effects
Twickenham Film Studios
St.Margarets
Twickenham
Middlesex
TW1 2AW

Tel: (Tel# suppressed)
luigi@(email surpressed)
www.senatevfx.com

On 12 May 2007, at 04:20, Greg Ercolano wrote:

[posted to rush.general]

Tyler Opatrny wrote:

[posted to rush.general]

we had the same problem on a linux box. This is what we did.

stopped the rush service
uninstalled rush
We coppied over the install files, and ran a chmod 777 of the rush
folder before installing installed it.
gave it the latest host list
started the rush service
it worked after that.

	Hmm, no, I would not ever recommend chmod 777 of the
	rush directory. That's just an invitation for someone to
	root the machine.

	With perms like that, an ordinary user could rename out the
	/usr/local/rush/etc or /usr/local/rush/bin directories,
	and install their own programs that would run their commands
	as root when the machine reboots to start the daemons.

	No, you want the /usr/local/rush directory, and its subdirs
	to be 755, and the rush and rushd binaries to be 4755 root/root.

	The 'install.sh' script tries to enforce the rush and rushd
	binary perms to prevent such problems. The only way they could
	be changed is by someone manually changing the perms after the
	install.sh script is run, which shouldn't happen.

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

Luigi Tommaseo wrote:
> yes it was a permission and ownership issue, 
> chown 0:0 and chmod 4755 did it.

	Great.

	I've added the 'rresvport_NET: All ports in use' error to the FAQ here:
	http://www.seriss.com/rush-current/rush/rush-admin-faq.html#ADMINFAQ-RRESVPORT

	You might need to hit 'reload' to see the new page.