Hi, A few people are having problems with the new console daemon and I''ve tracked the problem down to the order in which daemons are started. Here''s what currently happens: 1) xend (the script in tools/misc) start will launch xcs and consoled 2) xend (the python server) will launch xenstored whenever it needs it This creates a bit of a chicken and the egg problem since consoled needs xenstored to function. There''s a few options: 1) Have consoled (and all future daemons) implement the logic to wait for xenstored to start 2) Move xenstored launching to xend (the script in tools/misc) 3) Give all the daemons proper init.d scripts with dependencies I''m partial to #3 although #2 would be a fine quick hack. For now, if anyone gets messages about not being able to read the tty with xm console, simply run consoled. Regards, Anthony Liguori _______________________________________________ Xen-tools mailing list Xen-tools@lists.xensource.com http://lists.xensource.com/xen-tools
> This creates a bit of a chicken and the egg problem since > consoled needs xenstored to function. There''s a few options: > > 1) Have consoled (and all future daemons) implement the logic > to wait for xenstored to start > 2) Move xenstored launching to xend (the script in tools/misc) > 3) Give all the daemons proper init.d scripts with dependencies > > I''m partial to #3 although #2 would be a fine quick hack. > > For now, if anyone gets messages about not being able to read > the tty with xm console, simply run consoled.I think I prefer #2 -- you need all of them running to do anything useful, so might as well start them all from one place. The only question is over things like xensv (web interface) that are more complex and optional. They could be started from rc scripts, or from xend after parsing xend-config.sxp Best, Ian _______________________________________________ Xen-tools mailing list Xen-tools@lists.xensource.com http://lists.xensource.com/xen-tools
I wouldn''t worry about the web interface - it now runs via apache, so is going to need user intervention to set up / install. Cheers Tom On 4 Aug 2005, at 20:58, Ian Pratt wrote:> > >> This creates a bit of a chicken and the egg problem since >> consoled needs xenstored to function. There''s a few options: >> >> 1) Have consoled (and all future daemons) implement the logic >> to wait for xenstored to start >> 2) Move xenstored launching to xend (the script in tools/misc) >> 3) Give all the daemons proper init.d scripts with dependencies >> >> I''m partial to #3 although #2 would be a fine quick hack. >> >> For now, if anyone gets messages about not being able to read >> the tty with xm console, simply run consoled. >> > > I think I prefer #2 -- you need all of them running to do anything > useful, so might as well start them all from one place. > > The only question is over things like xensv (web interface) that are > more complex and optional. They could be started from rc scripts, or > from xend after parsing xend-config.sxp > > Best, > Ian > > _______________________________________________ > Xen-tools mailing list > Xen-tools@lists.xensource.com > http://lists.xensource.com/xen-tools >_______________________________________________ Xen-tools mailing list Xen-tools@lists.xensource.com http://lists.xensource.com/xen-tools