Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461) Description of problem: Discovered when installing APLAWS+ Production Server on RHEL 3: Appendix B1 - instead of 'up2date postgresql-server' use 'up2date rh-postgresql- server'* '4.1.2. CCM Runtime' - to avoid conflicts with existing packages which ship with RHEL, before doing anything else, execute the following from the terminal window as root 'rpm -e junit ant ant-libs' '4.1.3. APLAWS Applications' P19 - It's implied that both the CCM_CONFIG... env variables are required, but they don't seem to be. '4.3.2. Loading APLAWS+' - for 'ccm set waf.runtime.db_pool_size=100' we got a 'no such parameter' message Discovered when installing on Fedora: '4.3.2. Loading APLAWS+' - we needed to modify rights to /opt/resin/2.1.12/bin and wrapper.pl within it. * Not actually tested by us, due to problems with the RHN Version-Release number of selected component (if applicable): February 2004 Beta How reproducible: Didn't try Additional info:
The above points have all been incorporated in the documentation updates, with the exception of: > '4.3.2. Loading APLAWS+' > - we needed to modify rights to /opt/resin/2.1.12/bin and wrapper.pl > within it. Please provide more detailed information on this point, since we are unable to reproduce it & the above information is not sufficient to include in documentation
Apologies but I can't give much more information, except to say that 1. in our experience, the 'ccm load-bundle --interactive --name aplaws-standard' command didn't do much without changing rights to wrapper.pl. 2.we saw this problem twice, once on Red Hat 9 & once on Fedora.
This sounds dubious because 'ccm load-bundle' has nothing todo with starting resin (& thus running wrapper.pl). The only thing that will use wrapper.pl is 'ccm start' / 'ccm stop'. Before we can document it, at minimum we need to know what command was failing, what the original permissions were & what you changed them too.
As I said, I don't have further information since I personally didn't actually do the install on Fedora. If you are saying you have done so following the 'Quick Start Install Guide' & you didn't see this problem, I'll take your word for it.
Ok I'm closing this bug as resolved then. If you come across it again, please collect as much information as possible & open a new bugzilla ticket.