The two servers are ready to go. I had edited idmgr.conf. I didn't know if there were other files that needed to be updated.
I tried Fedora 8 & 9. With Fedora 9, installing the jabber does not work because libexpat is a different version. I probably could have compiled, but I'd prefer to stay with RPMs so the server will be easier to upgrade. I did not try idmgr. With Fedora 8, I had SCSI drivers issues. So we're back to Fedora 7. I did not install xs-config. I just copied config files from a working server and modified them for this one. The wiki mentions some .diffs to install for the ejabberd. Can I safely assume those directions are outdated? -----Original Message----- From: John Watlington [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 21, 2008 10:36 PM To: Berkowitz Andrew (Project Connect); Dennis Gilmore Cc: John Watlington; Martin Langhoff; server-devel Subject: Re: [Server-devel] XS software compatibility question On May 21, 2008, at 1:43 PM, Berkowitz Andrew (Project Connect) wrote: > OK, the jabber is working fine. The problem was that hostname was > working correctly but hostname -s & -f were not. > > I installed the idmgr with yum install idmgr. Are there any > configuration files I need to edit? Take a look at /etc/idmgr.conf It should have the FQDN for the server listed for both variables. > I did manage to crash the server after updating all packages. I could > see which one it was. > > This server is running Fedora 7. If I try Fedora 8 or 9 to avoid that > incompatible package, should your packages still work? There lie uncharted waters. Dennis might be able to help with that answer. I suspect that the answer is probably yes, given the limited number of packages you are trying. > Thank you > > -----Original Message----- > From: John Watlington [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 20, 2008 3:21 PM > To: Berkowitz Andrew (Project Connect) > Cc: John Watlington; Martin Langhoff; server-devel > Subject: Re: [Server-devel] XS software compatibility question > > > I don't have enough information to suggest anything, just offer > condolences and vague comments :-) > > From your command line info I assume that you are having problems > keeping ejabberd running, not connecting or collaborating after > starting it up. > > There is a brief time during startup when ejabberd is running > but the status is returned as stopped. Other than during time, > I usually don't see ejabberd processes running while service (or > ejabberdctl) say it isn't running. This only lasts for a minute or > so. > > Can you take a look at /var/log/ejabberd/sasl.log ? Usually when > ejabberd has problems starting, the error is logged cryptically > there... > > wad > > On May 20, 2008, at 2:59 PM, Berkowitz Andrew (Project Connect) wrote: > >> I am having a problem with the ejabberd. >> >> I took the ejabberd.cfg & ejabberdctl.cfg files from a working server >> and then changed the domain before starting ejabbered. >> >> What do you suggest? >> >> [EMAIL PROTECTED] ~]# ejabberdctl ejabberd status Node >> [EMAIL PROTECTED] is started. Status: started ejabberd is not >> running [EMAIL PROTECTED] ~]# ps auxxwww | grep jabber >> ejabberd 2672 0.0 0.0 1932 340 ? S 10:32 0:00 >> /usr/lib/erlang/erts-5.6.1/bin/epmd -daemon >> ejabberd 3320 0.1 0.8 65200 18116 ? Sl 10:39 0:00 >> /usr/lib/erlang/erts-5.6.1/bin/beam.smp -K true -- -root /usr/lib/ >> erlang -progname erl -- -home /var/lib/ejabberd -pa >> /usr/lib/ejabberd-2.0.0/ebin -sname ejabberd -s ejabberd -ejabberd >> config "/etc/ejabberd/ejabberd.cfg" log_path >> "/var/log/ejabberd/ejabberd.log" -sasl sasl_error_logger >> {file,"/var/log/ejabberd/sasl.log"} -mnesia dir >> "/var/lib/ejabberd/spool" -kernel inetrc "/etc/ejabberd/ >> ejabberd.inetrc" >> -noshell -noinput >> >> >> >> -----Original Message----- >> From: John Watlington [mailto:[EMAIL PROTECTED] >> Sent: Monday, May 19, 2008 11:39 PM >> To: Berkowitz Andrew (Project Connect) >> Cc: John Watlington; Martin Langhoff; server-devel >> Subject: Re: [Server-devel] XS software compatibility question >> >> >> On May 19, 2008, at 6:18 PM, Martin Langhoff wrote: >> >>> On Tue, May 20, 2008 at 9:49 AM, Berkowitz Andrew (Project >>> Connect) > > >>> The installation was perfect with the full Fedora 7 installation. >>>> >>>> Is it possible to install all of OLPC's customizations on top of a >>>> stock Fedora installation? >>> >>> Yes. Add the XS repositories to your yum sources, and install xs- >>> pkgs > >>> from there (which should pull all the right dependencies). I suspect >>> it will muck up a few things, such as user accts created for >>> processes. The kernel might also be missing those specific drivers >>> you >> >>> need. >> >> The config file for ejabberd is in xs-config, so you will probably >> want to replace the Fedora repos with the OLPC ones, and install >> xs-pkgs and xs-config. >> >> (I'm thinking evil thoughts about just installing the idmgr and >> ejabberd >> packages and grabbing the ejabberd config file from git... Since in >> the NYC installation you provide all networking services externally!) >> >>> So I can't guarantee it will work. >> Definitely not, but I bet it will be close. >> Don't forget to reboot after installing xs-config, to trigger any >> post-first-boot network configurations... >> >>>> How else would you suggest we proceed? >>> >>> Hmmm. As you aren't using AAs, you probably don't need ourcustom >>> kernel. So perhaps install xs-config and then review what xs-pkgs >>> will >> >>> pull in - you'll want to install all of that except for the custom >>> kernel. >> >> We have no custom kernel, our repositories simply contain a freeze of >> the Fedora 7 release/update repos at a recent date. You are safe >> there... >> >> Thanks for working on this! >> wad >> >> >> >> > > _______________________________________________ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel