Starting a Thin cluster w/ Swiftiply should not start on different ports
Reported by Carl | April 17th, 2008 @ 07:46 PM | in 0.8.1
For example:
$ thin start -b Thin::Backends::SwiftiplyClient -e production -p 30000 -a 127.0.0.1 -s 15
Starting server on 127.0.0.1:30000 ...
Starting server on 127.0.0.1:30001 ...
Starting server on 127.0.0.1:30002 ...
All servers should be on port 30000
Comments and changes to this ticket
-
macournoyer April 18th, 2008 @ 10:48 AM
- State changed from “new” to “open”
- Milestone set to “0.8.1”
running w/ -y the option should fix that. the -b option is just in the meantime I fix the other issue.
Can you confirm it works when you add the -y option?
-
-
macournoyer April 18th, 2008 @ 10:19 PM
- State changed from “open” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Carl
macournoyer