Re: [Server-devel] XS_0_4 install]
Unfortunately, we started ejabberd after running domain_config. We also made changes to /etc/hosts, ifcfg-eth0, ifcfg-eth1, and network after running domain_config to match our situation before running ejabberd; hence the problem with getting the service to run. Tony Martin Langhoff wrote: > On Tue, Sep 30, 2008 at 5:18 PM, Bryan Berry <[EMAIL PROTECTED]> wrote: >> What's more concerning to me is that ejabberd has never once worked for >> me "out-of-box." I have always had to reinstall it before getting it to >> work. Has anyone out there gotten ejabberd to work consistently on new >> XS installs w/ reinstalling it? > > That sounds like you might be trying to start it before running domain_config. > > It's a tiny change to the installation workflow outlined in the doco, > but can trip people up. We could change the init script to check for > that case and refuse to start. > > cheers, > > > > m ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS_0_4 install]
I can't remember precisely, but I thought I started ejabberd after running domain_config, but I could be mistaken. Tony, did u start ejabberd before or after running domain_config on ur latest install? On Wed, 2008-10-01 at 11:13 +1300, Martin Langhoff wrote: > On Tue, Sep 30, 2008 at 5:18 PM, Bryan Berry <[EMAIL PROTECTED]> wrote: > > What's more concerning to me is that ejabberd has never once worked for > > me "out-of-box." I have always had to reinstall it before getting it to > > work. Has anyone out there gotten ejabberd to work consistently on new > > XS installs w/ reinstalling it? > > That sounds like you might be trying to start it before running domain_config. > > It's a tiny change to the installation workflow outlined in the doco, > but can trip people up. We could change the init script to check for > that case and refuse to start. > > cheers, > > > > m -- Bryan W. Berry Technology Director OLE Nepal, http://www.olenepal.org ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS_0_4 install]
On Tue, Sep 30, 2008 at 5:18 PM, Bryan Berry <[EMAIL PROTECTED]> wrote: > What's more concerning to me is that ejabberd has never once worked for > me "out-of-box." I have always had to reinstall it before getting it to > work. Has anyone out there gotten ejabberd to work consistently on new > XS installs w/ reinstalling it? That sounds like you might be trying to start it before running domain_config. It's a tiny change to the installation workflow outlined in the doco, but can trip people up. We could change the init script to check for that case and refuse to start. cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS_0_4 install]
What's more concerning to me is that ejabberd has never once worked for me "out-of-box." I have always had to reinstall it before getting it to work. Has anyone out there gotten ejabberd to work consistently on new XS installs w/ reinstalling it? On Mon, 2008-09-29 at 17:13 +0545, Tony Anderson wrote: > The problem with ejabberd turned out to be documented earlier by Bryan. > A slightly simpler solution works: > > Ejabberd fails when the hostname has been changed. The symptom is that: > > service ejabberd status > > returns ejabberd not running. > > Try the following to fix ejabberd: > service ejabberd stop > killall epmd > rm -rf /var/lib/ejabberd/* > service ejabberd start > > Tony > > Original Message > Subject: Re: XS_0_4 install > Date: Thu, 25 Sep 2008 17:35:06 +0545 > From: Tony Anderson <[EMAIL PROTECTED]> > To: Martin Langhoff <[EMAIL PROTECTED]>, Bryan Berry > <[EMAIL PROTECTED]>, server-devel@lists.laptop.org > References: <[EMAIL PROTECTED]> > <[EMAIL PROTECTED]> > > Today the behavior has changed a little. > > First, the network problem. > > The 'other host' problem turns out to be a newbie error on my part. The > router was configured as 172.18.0.1 but labeled as 172.18.0.3. We have > reconfigured the router to be 172.18.0.3 and the XO has access to the > internet via the schoolserver! > > The ejabberd problem persists; however, I think it may also be a newbie > problem. I'll try to keep you posted. > > Yours, > > Tony > > Martin Langhoff wrote: > > On Wed, Sep 24, 2008 at 11:04 PM, Tony Anderson <[EMAIL PROTECTED]> wrote: > >> started ejabberd: > >> > >> chkconfig --level 345 ejabberd on > >> service ejabberd start > >> > >> and attempted to register admin: > >> > >> ejabberdctl ejabberd register admin schoolserver.schoolnet.gov.np admin > >> > >> This failed with a message: > >> > >> RPC failed on the node [EMAIL PROTECTED]: nodedown > > > > That's strange. The procedure is right, perhaps something went wrong > > with the domain_config step? Does the /etc/ejabberd/ejabberd.cfg file > > show the correct domain? > > > >> The command service ejabberd status gets the same error (on timeout); > >> however, ps -aux shows an ejabberd daemon. > >> > >> I then tried to set up the networks manually: > >> > >> ifcfg-eth0 was modified to use a static address (192.168.5.44). This seems > >> to work ok. > > > > Good. > > > >> ifcfg-eth1 was modified by adding BOOTPROTO=static. This gives an error: > >> "Error, some other host already uses 172.18.0.1." > > > > Is that interface connected to anything? Any other host that would be > > answering for that ip address? The error you mention is from doing an > > 'arping' to the address - > > > > cheers, > > > > > > > > m > > -- Bryan W. Berry Technology Director OLE Nepal, http://www.olenepal.org ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS_0_4 install]
The problem with ejabberd turned out to be documented earlier by Bryan. A slightly simpler solution works: Ejabberd fails when the hostname has been changed. The symptom is that: service ejabberd status returns ejabberd not running. Try the following to fix ejabberd: service ejabberd stop killall epmd rm -rf /var/lib/ejabberd/* service ejabberd start Tony Original Message Subject: Re: XS_0_4 install Date: Thu, 25 Sep 2008 17:35:06 +0545 From: Tony Anderson <[EMAIL PROTECTED]> To: Martin Langhoff <[EMAIL PROTECTED]>, Bryan Berry <[EMAIL PROTECTED]>, server-devel@lists.laptop.org References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Today the behavior has changed a little. First, the network problem. The 'other host' problem turns out to be a newbie error on my part. The router was configured as 172.18.0.1 but labeled as 172.18.0.3. We have reconfigured the router to be 172.18.0.3 and the XO has access to the internet via the schoolserver! The ejabberd problem persists; however, I think it may also be a newbie problem. I'll try to keep you posted. Yours, Tony Martin Langhoff wrote: > On Wed, Sep 24, 2008 at 11:04 PM, Tony Anderson <[EMAIL PROTECTED]> wrote: >> started ejabberd: >> >> chkconfig --level 345 ejabberd on >> service ejabberd start >> >> and attempted to register admin: >> >> ejabberdctl ejabberd register admin schoolserver.schoolnet.gov.np admin >> >> This failed with a message: >> >> RPC failed on the node [EMAIL PROTECTED]: nodedown > > That's strange. The procedure is right, perhaps something went wrong > with the domain_config step? Does the /etc/ejabberd/ejabberd.cfg file > show the correct domain? > >> The command service ejabberd status gets the same error (on timeout); >> however, ps -aux shows an ejabberd daemon. >> >> I then tried to set up the networks manually: >> >> ifcfg-eth0 was modified to use a static address (192.168.5.44). This seems >> to work ok. > > Good. > >> ifcfg-eth1 was modified by adding BOOTPROTO=static. This gives an error: >> "Error, some other host already uses 172.18.0.1." > > Is that interface connected to anything? Any other host that would be > answering for that ip address? The error you mention is from doing an > 'arping' to the address - > > cheers, > > > > m ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS_0_4 install
On Wed, Sep 24, 2008 at 11:04 PM, Tony Anderson <[EMAIL PROTECTED]> wrote: > started ejabberd: > > chkconfig --level 345 ejabberd on > service ejabberd start > > and attempted to register admin: > > ejabberdctl ejabberd register admin schoolserver.schoolnet.gov.np admin > > This failed with a message: > > RPC failed on the node [EMAIL PROTECTED]: nodedown That's strange. The procedure is right, perhaps something went wrong with the domain_config step? Does the /etc/ejabberd/ejabberd.cfg file show the correct domain? > The command service ejabberd status gets the same error (on timeout); > however, ps -aux shows an ejabberd daemon. > > I then tried to set up the networks manually: > > ifcfg-eth0 was modified to use a static address (192.168.5.44). This seems > to work ok. Good. > ifcfg-eth1 was modified by adding BOOTPROTO=static. This gives an error: > "Error, some other host already uses 172.18.0.1." Is that interface connected to anything? Any other host that would be answering for that ip address? The error you mention is from doing an 'arping' to the address - cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] XS_0_4 install
I am trying to install XS_0_4 here. I am following the install procedure as closely as possible. I added: chown -R xs-sync:xs-sync /library/xs-sync, then set the domain: /etc/sysconfig/olpc-scripts/domain_config schoolnet.gov.np. started ejabberd: chkconfig --level 345 ejabberd on service ejabberd start and attempted to register admin: ejabberdctl ejabberd register admin schoolserver.schoolnet.gov.np admin This failed with a message: RPC failed on the node [EMAIL PROTECTED]: nodedown The command service ejabberd status gets the same error (on timeout); however, ps -aux shows an ejabberd daemon. I then tried to set up the networks manually: ifcfg-eth0 was modified to use a static address (192.168.5.44). This seems to work ok. ifcfg-eth1 was modified by adding BOOTPROTO=static. This gives an error: "Error, some other host already uses 172.18.0.1." So far we have not been able to find a way around either the eth1 problem or the ejabberd problem. Any help will be greatly appreciated. Yours, Tony ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
