Bugs item #680168, was opened at 2003-02-04 08:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=680168&group_id=9368
Category: Installation Group: 2.2 Status: Open Resolution: Fixed Priority: 8 Submitted By: Jeff Squyres (jsquyres) Assigned to: Brian Elliott Finley (brianfinley) Summary: rsyncd does not start Initial Comment: As has been discussed on the devel mailing list, /etc/rc.d/init.d/systemimager may fail to launch the rsyncd due to a PATH problem in some environments (e.g., RH 7.3). This causes the clients to be unable to download their images, unless the user manually starts the rsyncd. We should either have a new SI RPM, or, if that's not possible in time, apply a patch to /etc/rc.d/init.d/systemimager at OSCAR's install time to make it do the Right Thing. ---------------------------------------------------------------------- >Comment By: Jeff Squyres (jsquyres) Date: 2003-02-13 11:36 Message: Logged In: YES user_id=11722 <still_frustrated> OSCAR has been waiting for this fix for weeks, even if SI's CVS was fixed. Are you testing what you're committing? As has been shown several times in the past, if something works outside of OSCAR, that doesn't mean that it works *inside* of OSCAR. Also, as Mike mentioned yesterday, you are using the value of the PATCH variable befoe you set it. This directly causes the patch to fail when running inside OSCAR. Here's the last few lines of my oscarinstall.log from a tanked install due to the patch failing: --> Successfully installed server core RPMs --> Running post_server_install scripts for server core packages patch: **** read error : Is a directory Patch of /etc/init.d/systemimager failed! Couldn't run patch script /root/oscar-2.2b4/packages/sis/scripts/systemimager-in it-script.patch.sh at /root/oscar-2.2b4/packages/sis/scripts/post_server_install line 25 Failed running post_server_install for sis at ./wizard_prep line 178 Oscar Wizard preparation script failed to complete at ./install_cluster line 58. </still_frustrated> ---------------------------------------------------------------------- Comment By: Brian Elliott Finley (brianfinley) Date: 2003-02-13 11:13 Message: Logged In: YES user_id=140 Hey guys. I fixed this 3 weeks ago when it first came up and committed it to the upstream code. When I learned on the call this week that a post-install patch was required for the immediate OSCAR release, I created one while we were still on the call, and committed it to OSCAR CVS. I created the patch in what I understood to be appropriate according to OSCAR guidelines. The patch does not create a systemimager.orig file in /etc/init.d/, unless you apply it, then reverse apply it. I did find one problem with it just now -- that is that it was including the $Id $ string in the patch, and each time something was changed in the patch, that string would change, and therefore not match the original file on an end system. Also, "patch" ignores non-patch verbiage in patches. As in, it ignores the shell script stuff at the top. The shell script, however, will try to execute the patch data at the end of the file unless you do an "exit" after the script part (which is there). Please let me know if there are any other problems. ---------------------------------------------------------------------- Comment By: Jeff Squyres (jsquyres) Date: 2003-02-13 10:19 Message: Logged In: YES user_id=11722 <frustrated> Can we *please* get a fix for this from the package maintainers? We've been holding up the 2.2 release for *weeks* because of a simple, one-word fix that is required for SI. This is really silly, and is getting very frustrating. No other progress has been able to get into CVS because it's frozen, waiting this fix. </frustrated> ---------------------------------------------------------------------- Comment By: Jeff Squyres (jsquyres) Date: 2003-02-12 15:39 Message: Logged In: YES user_id=11722 We asked for that 3 weeks ago (!) and didn't get it. So it seemed to be a quicker solution to put in a patch. ---------------------------------------------------------------------- Comment By: Jason Brechin (brechin) Date: 2003-02-12 15:36 Message: Logged In: YES user_id=274641 Why don't we just make the simple change in the packaged file? It seems like a much more robust solution than patching after it's installed. ---------------------------------------------------------------------- Comment By: Michael Chase-Salerno (mchasal) Date: 2003-02-12 14:43 Message: Logged In: YES user_id=99742 This is broken in multiple ways. The problem Tom is seeing is caused because the $PATCH variable is used without being first set, so the patch command is handed the directory instead of the patch. In addition, the actual patch will complain and return badly because the patch is contained in the script and patch tries to deal with the script instructions and can't. Finally, patch creates a systemimager.orig file in the /etc/init.d directory, so after this script runs, you can do a "service systemimager.orig start" which we really don't want to leave around. Brian, I would suggest just using sed to make this change to that file. ---------------------------------------------------------------------- Comment By: Thomas Naughton (naughtont) Date: 2003-02-11 19:59 Message: Logged In: YES user_id=288102 quick test before cutting beta4, patch fails copy/pasted last part of output to logfile attached below (test on rh73vm) ---------------------------------------------------------------------- Comment By: Jeff Squyres (jsquyres) Date: 2003-02-11 15:00 Message: Logged In: YES user_id=11722 This is *not* fixed. You committed a patch, but there's nothing to *apply* this patch at run time. ---------------------------------------------------------------------- Comment By: Brian Elliott Finley (brianfinley) Date: 2003-02-11 14:58 Message: Logged In: YES user_id=140 Created patch for the immediate release. Patched in SystemImager CVS for future releases. Patch committed to packages/sis dir. ---------------------------------------------------------------------- Comment By: Michael Chase-Salerno (mchasal) Date: 2003-02-04 10:27 Message: Logged In: YES user_id=99742 I believe this is the known export problem. Brian, can you please fix this and check a new rpm into OSCAR or provide a patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=680168&group_id=9368 ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
