Forum OpenACS Development: nsvhr and inittab problem

Collapse
1: nsvhr and inittab problem
Posted by David Kuczek on 04/14/03 10:52 PM
I have a little problem with nsvhr.

It runs smoothly whenever I start master.tcl and myserver.tcl manually. But whenever I start it via inittab the following error occurs:

[14/Apr/2003:22:48:55][19316.16384][-main-] Error: nsunix: listen: error binding socket on path: modules/nsunix/MYSERVER.nsunix

[14/Apr/2003:22:48:55][19316.16384][-main-] Error: nsunix: failed to start listening: Address already in use (modules/nsunix/MYSERVER.nsunix)

My inittab entry:

nss1:345:respawn:/usr/local/aolserver/bin/nsd -u nsadmin -g web -i -t /usr/local/aolserver/master.tcl
nss2:345:respawn:/usr/local/aolserver/bin/nsd -u nsadmin -g web -i -t /usr/local/aolserver/myserver.tcl

Any hints?

Collapse
2: Re: nsvhr and inittab problem (response to 1)
Posted by David Kuczek on 04/15/03 08:06 AM
Btw, are there any downfalls with nsvhr? I read about some IE ns_returnredirect problems... What else do I have to keep in mind when switching from a regular aolserver setup to nsvhr?
Collapse
3: Re: nsvhr and inittab problem (response to 1)
Posted by David Kuczek on 04/15/03 05:42 PM
Or maybe somebody could comment on how he keeps the different aolserver processes alive... Doesn't the master-process have to be running before a slave-process can start? I have not yet used daemontools.
Collapse
4: Re: nsvhr and inittab problem (response to 1)
Posted by Lamar Owen on 04/15/03 11:42 PM
Someone who uses nsvhr may have better ideas, but this may be one instance where inittab isn't necessarily the best tool.  The two nsd instances will start concurrently; this may not be workable.  There are ways of serializing execution in inittab; however, you may be better off using daemontools or something similar for this purpose.
Collapse
5: Re: nsvhr and inittab problem (response to 1)
Posted by Jerry Asher on 04/17/03 06:44 AM
I think Lamar is right.

When I was using nsvhr, I would start my aolservers one at a time, in serial order, and I am almost positive the master was first.

I am not sure what those error messages indicate w/o looking at the code.  It says address already in use.  Does that really mean the unix domain socket doesn't exist just yet?  Could be, or it might be something different.

I would recommend you try starting them up serially.

Collapse
6: Re: nsvhr and inittab problem (response to 1)
Posted by David Kuczek on 04/22/03 10:54 PM
could anyone tell me how to serially start aolserver via inittab... If this isn't possible I will have to install daemontools: Any examples for daemontools serial starts?

BTW. How many people are still using nsvhr? I've heard some on Apache as reverse proxie on the oacs bboards. Would this be a better solution for virtual hosting?

Collapse
7: Re: nsvhr and inittab problem (response to 1)
Posted by Tom Jackson on 04/23/03 12:08 AM
I don't have much time right now, but I have posted several times init.d scripts which start my servers. You can use this to start them in any order you need. I posted it in the last few months.
Collapse
8: Re: nsvhr and inittab problem (response to 7)
Posted by Gilbert Price on 04/23/03 12:49 AM
Tom,

I think this is the thread you were referring too:

https://openacs.org/forums/message-view?message_id=31394

Collapse
9: Re: nsvhr and inittab problem (response to 1)
Posted by Jade Rubick on 04/23/03 07:06 PM
See also: https://openacs.org/irc/log/2003-04-19

for a discussion on nsvhr