On 18 May 2010 18:54, Mike Hanby <[email protected]> wrote: > Aha, same here. cobbler-web must have added itself during the yum update > that I performed just prior to my upgrade from 0.7 to 0.8 > > > > I know I didn't specifically request it to be installed. > > > > Once you uninstalled cobbler-web, did you have to do anything else (aside > from rhn-satellite {stop|start} to set things right? > > > > My repodata directories are now slowly updating (time stamps are changing to > todays date). > > > > Also, after restarting rhn-satellite, I now see new entries in > httpd/error_log which may be unrelated: > > > > [Tue May 18 12:53:35 2010] [notice] Digest: generating secret for digest > authentication ... > > [Tue May 18 12:53:35 2010] [notice] Digest: done > > [Tue May 18 12:53:35 2010] [notice] mod_python: Creating 4 session mutexes > based on 256 max processes and 0 max threads. > > [Tue May 18 12:53:36 2010] [notice] Apache configured -- resuming normal > operations > > [Tue May 18 12:53:43 2010] [error] (111)Connection refused: proxy: AJP: > attempt to connect to 127.0.0.1:8009 (*) failed > > [Tue May 18 12:53:43 2010] [error] proxy: AJP: failed to make connection to > backend: localhost > > [Tue May 18 12:53:47 2010] [error] (111)Connection refused: proxy: AJP: > attempt to connect to 127.0.0.1:8009 (*) failed > > [Tue May 18 12:53:47 2010] [error] proxy: AJP: failed to make connection to > backend: localhost > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Brian T. O'Neill > Sent: Tuesday, May 18, 2010 12:45 PM > To: [email protected] > Subject: Re: [Spacewalk-list] Problem with taskomatic on new 1.0 install > > > > Looks like I solved my problem…. > > > > I had installed cobbler-web as well as cobbler (just a stupid, it needs > cobbler, I’ll install all the packages sort of thing). The cobbler-web http > configuration broke the http redirects and such needed by spacewalk. > > > > Brian > > > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Brian T. O'Neill > Sent: Tuesday, May 18, 2010 10:32 AM > To: [email protected] > Subject: [Spacewalk-list] Problem with taskomatic on new 1.0 install > > > > I have just installed 1.0, brand new install. There were some issues where > it appears that the install didn’t complete. After the install was done, > neither jabber, taskomatic, or osa-dispatcher worked. I was able to get > jabber and osa-dispatcher working by finishing the proper configs in files > by hand. I’m still stuck on taskomatic. > > > > What is happening is taskomatic is going to http://127.0.0.1/rpc/api which > doesn’t exist (it does exist when using https). So, I have basically > narrowed the issue down to either one of two problems: > > #1 /rpc/api should work on http and my initial setup missed this and I have > no idea how to get it working properly > > Or > > #2 Some config file should be telling taskomatic to use https instead of > http (thinking some file should be pointing at a pem file but isn’t…) > > > > Anyone happen to have an idea if the fix is #1 or #2 and hopefully how to do > it? > > > > Any help would be greatly appreciated. > > > > Thanks, > > Brian > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
If you installed cobbler-web I'm going to take a bit of a guess you ended up with cobbler 2.0.3 installed? As a heads up that version (rather than the 1.6.x that was in EPEL previously) is a bit broken in kickstart snippet behaviour. Check the mailing list archives - but there is something I recall about the variables needing to be escaped now or something like that... James _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
