Re: [Server-devel] My Observations and experiences with XSCE 0.2.1
> If you would be so brave to try the latest rpm, please start with the > testing enabled repo[1]. Done. With a fresh install of 12.1 as just trying to remove the dot files and re-run the config script didn't work very well. >> Reboot and the same >> httpd problem with pathagar exists. > > This is should now be fixed. Yes. httpd started on its own this time. >> Fixing that still does not >> correct the registration problem. >> > There was a strange issue when parsing /domain_config.d/, I wrongly > assumed that dhclient, where the hostname is being set, would run first > based on the filename. This has been resolved. > >> Running tcpdump on the exchange shows that the request to the webcache >> port is responded to with a RST. Nmap the sever and there's nothing >> running on port 8080. > > That most likely was a result of the above hostname failure. Nope. Same problem. I've not seen any problems with the hostname. Its set to schoolserver the .local domain is setup and both clients and server properly resolve schoolserver into the right respective IP. tcpdump shows the client is issuing a request to 8080 and its getting a RST back because nothing is responding at that port. Whats supposed to be servicing port 8080? Whatever it is is not functioning. >> than the next line. The command still works but it makes it difficult >> to review things when you look at history. >> > > This alteration has been removed. yes and there is a # back in my root prompt. :) -- Richard A. Smith One Laptop per Child ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] ds-backup broken in 12.1
I discovered today that ds-backup.sh is broken in 12.1 and beyond. The problem is that the 'ping' command changed to no longer being suid root. ds-backup.sh uses ping to check if the network connection to the schoolserver is functional. Since ping won't run as user olpc it always exits. The fix is to add the use of sudo to the ping command. I'll fix that and get a new rpm built but for people who have 12.1 already deployed and want to use this you will need to fix ds-backup.sh Give that this has been broken for a long time and nobody seems to have noticed I'm guessing there aren't very many users of ds-backup with XO's running 12.1. -- Richard A. Smith One Laptop per Child ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] My Observations and experiences with XSCE 0.2.1
On Wed, 2013-03-20 at 12:54 -0400, Richard Smith wrote: > On Tue, Mar 19, 2013 at 7:16 PM, Richard Smith wrote: > >>> Dunno. Where do I look for the version? > >>> > >> rpm -q xs-config > > > > 0.8.2.100.18.g8895685-1 > Thanks for the great feedback. > I tried a 2nd install on a XO-1.5 I had and received exactly the same > results. (Without the MN tag problem). The install appeared to go > smoothly. ejabberd claimed it could not start up. There is an issue with ejabberd for XO-1.0/1.5s, I patched ejabberd with dsd's pubsub patch but rolled the rpm on ARM only, just need to find time to re-compile the source rpm on i386 and x86-64 and make it available in the yum repo. > Reboot and the same > httpd problem with pathagar exists. This is should now be fixed. > Fixing that still does not > correct the registration problem. > There was a strange issue when parsing /domain_config.d/, I wrongly assumed that dhclient, where the hostname is being set, would run first based on the filename. This has been resolved. > Running tcpdump on the exchange shows that the request to the webcache > port is responded to with a RST. Nmap the sever and there's nothing > running on port 8080. That most likely was a result of the above hostname failure. > So whatever is supposed to be servicing that > didn't happen. Other services look ok. ssh, dns, http are up, squid > is up on 3128, xmpp on 5222 and 5280 and presence is on 5298. > Identical behavior on the 1.75 server install. > > So I'd say either all my machines are broken somehow or there's been a > regression. I'm going to bail and use XS .7 for my dev purposes as > this yak is starting to get hairy. I can still run some diagnostics > on the machines if you find you can't duplicate the failure and want > more info. > If you would be so brave to try the latest rpm, please start with the testing enabled repo[1]. > I've also discovered that the terminal command prompt appears to have > broken line wrapping. If you type really long lines in the terminal > activity it will wrap back to the beginning of the same line rather > than the next line. The command still works but it makes it difficult > to review things when you look at history. > This alteration has been removed. > Hope this helps. > It does, thanks. Jerry 1. http://build.activitycentral.com/xsce.repo ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] My Observations and experiences with XSCE 0.2.1
On Tue, Mar 19, 2013 at 7:16 PM, Richard Smith wrote: >>> Dunno. Where do I look for the version? >>> >> rpm -q xs-config > > 0.8.2.100.18.g8895685-1 I tried a 2nd install on a XO-1.5 I had and received exactly the same results. (Without the MN tag problem). The install appeared to go smoothly. ejabberd claimed it could not start up. Reboot and the same httpd problem with pathagar exists. Fixing that still does not correct the registration problem. Running tcpdump on the exchange shows that the request to the webcache port is responded to with a RST. Nmap the sever and there's nothing running on port 8080. So whatever is supposed to be servicing that didn't happen. Other services look ok. ssh, dns, http are up, squid is up on 3128, xmpp on 5222 and 5280 and presence is on 5298. Identical behavior on the 1.75 server install. So I'd say either all my machines are broken somehow or there's been a regression. I'm going to bail and use XS .7 for my dev purposes as this yak is starting to get hairy. I can still run some diagnostics on the machines if you find you can't duplicate the failure and want more info. I've also discovered that the terminal command prompt appears to have broken line wrapping. If you type really long lines in the terminal activity it will wrap back to the beginning of the same line rather than the next line. The command still works but it makes it difficult to review things when you look at history. Hope this helps. -- Richard A. Smith One Laptop per Child ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
