Re: [rt-users] FW: RT 4.0.8 + Fedora 16 - Almost There
Hi Kevin, Thanks for your response. Looking at /etc/httpd/logs/error_log, I see this entry: [...] [error] [client ::1] File does not exist: /opt/rt4/share/html/favicon.ico This leads me to believe that something went wrong with the installation ls -l /opt/rt4/share/html/ drwxr-xr-x. 10 root bin 4096 Nov 27 16:33 Admin drwxr-xr-x. 3 root bin 4096 Nov 27 16:34 Approvals drwxr-xr-x. 4 root bin 4096 Nov 27 16:34 Articles -rw-r--r--. 1 root bin 2263 Nov 27 16:33 autohandler drwxr-xr-x. 3 root bin 4096 Nov 27 16:34 Dashboards -rw-r--r--. 1 root bin 2285 Nov 27 16:34 dhandler drwxr-xr-x. 3 root bin 4096 Nov 27 16:33 Download drwxr-xr-x. 15 root bin 4096 Nov 27 16:33 Elements drwxr-xr-x. 4 root bin 4096 Nov 27 16:33 Helpers -rw-r--r--. 1 root bin 5163 Nov 27 16:33 index.html drwxr-xr-x. 3 root bin 4096 Nov 27 16:34 Install -rw-r--r--. 1 root bin 2231 Nov 27 16:33 l -rw-r--r--. 1 root bin 2188 Nov 27 16:33 l_unsafe drwxr-xr-x. 5 root bin 4096 Nov 27 16:34 m drwxr-xr-x. 9 root bin 4096 Nov 27 16:34 NoAuth drwxr-xr-x. 2 root bin 4096 Nov 27 16:34 Prefs drwxr-xr-x. 3 root bin 4096 Nov 27 16:33 REST drwxr-xr-x. 3 root bin 4096 Nov 27 16:33 Search drwxr-xr-x. 5 root bin 4096 Nov 27 16:33 SelfService drwxr-xr-x. 5 root bin 4096 Nov 27 16:33 Ticket drwxr-xr-x. 2 root bin 4096 Nov 27 16:34 Tools drwxr-xr-x. 2 root bin 4096 Nov 27 16:33 User drwxr-xr-x. 3 root bin 4096 Nov 27 16:33 Widgets Does this look OK? Thanks in anticipation. Regards, Walid -Original Message- From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kevin Falcone Sent: quinta-feira, 29 de Novembro de 2012 16:52 To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] FW: RT 4.0.8 + Fedora 16 - Almost There On Wed, Nov 28, 2012 at 01:56:18PM +, Walid Haider wrote: > I have tried to follow the instructions in order to configure RT to work with > Apache 2 + mod_perl but surely, I am missing some configuration and cannot > figure out what it is. It's worth checking your error logs and possibly dialing Apache's error log up to debug if you think there are weird problems. You don't really need to make these two global changes > Any help would be much appreciated. > > #DocumentRoot "/var/www/html" > DocumentRoot "/opt/rt4/share/html" > # > # This should be changed to whatever you set DocumentRoot to. > # > # > Since you're setting DocumentRoot in your VirtualHost directive -kevin - Não foram detectados vírus nesta mensagem. Verificado por AVG - www.avg.com Versão: 2013.0.2793 / Base de dados de Vírus: 2629/5906 - Data de Lançamento: 11/19/12 A Base de dados de Vírus interna está desactualizada. We're hiring! http://bestpractical.com/jobs
[rt-users] FW: RT 4.0.8 + Fedora 16 - Almost There
Hi All, I have managed to install RT4.0.8 on Fedora 16, but when I launch RT from a browser, I am getting: You're almost there! You appear to have installed RT's web interface correctly but not yet configured your web server to "run" the RT server which powers the web interface. The next step is to edit your web server's configuration file to instruct it to use RT's fastcgi or mod_perl handler. I have tried to follow the instructions in order to configure RT to work with Apache 2 + mod_perl but surely, I am missing some configuration and cannot figure out what it is. Any help would be much appreciated. Attached is the http.conf file. NB: I have also added "LoadModule perl_module modules/mod_perl.so" to http.conf. Is that necessary? Thanks in anticipation, Regards, Walid # # This is the main Apache HTTP server configuration file. It contains the # configuration directives that give the server its instructions. # See http://httpd.apache.org/docs/2.2> for detailed information. # In particular, see # http://httpd.apache.org/docs/2.2/mod/directives.html> # for a discussion of each configuration directive. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # The configuration directives are grouped into three basic sections: # 1. Directives that control the operation of the Apache server process as a # whole (the 'global environment'). # 2. Directives that define the parameters of the 'main' or 'default' server, # which responds to requests that aren't handled by a virtual host. # These directives also provide default values for the settings # of all virtual hosts. # 3. Settings for virtual hosts, which allow Web requests to be sent to # different IP addresses or hostnames and have them handled by the # same Apache server process. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with "/" (or "drive:/" for Win32), the # server will use that explicit path. If the filenames do *not* begin # with "/", the value of ServerRoot is prepended -- so "logs/foo.log" # with ServerRoot set to "/etc/httpd" will be interpreted by the # server as "/etc/httpd/logs/foo.log". # ### Section 1: Global Environment # # The directives in this section affect the overall operation of Apache, # such as the number of concurrent requests it can handle or where it # can find its configuration files. # # # Don't give away too much information about all the subcomponents # we are running. Comment out this line if you don't mind remote sites # finding out what major optional modules you are running ServerTokens OS # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # NOTE! If you intend to place this on an NFS (or otherwise network) # mounted filesystem then please read the LockFile documentation # (available at http://httpd.apache.org/docs/2.2/mod/mpm_common.html#lockfile>); # you will save yourself a lot of trouble. # # Do NOT add a slash at the end of the directory path. # ServerRoot "/etc/httpd" # # PidFile: The file in which the server should record its process # identification number when it starts. Note the PIDFILE variable in # /etc/sysconfig/httpd must be set appropriately if this location is # changed. # PidFile run/httpd.pid # # Timeout: The number of seconds before receives and sends time out. # Timeout 60 # # KeepAlive: Whether or not to allow persistent connections (more than # one request per connection). Set to "Off" to deactivate. # KeepAlive Off # # MaxKeepAliveRequests: The maximum number of requests to allow # during a persistent connection. Set to 0 to allow an unlimited amount. # We recommend you leave this number high, for maximum performance. # MaxKeepAliveRequests 100 # # KeepAliveTimeout: Number of seconds to wait for the next request from the # same client on the same connection. # KeepAliveTimeout 5 ## ## Server-Pool Size Regulation (MPM specific) ## # prefork MPM # StartServers: number of server processes to start # MinSpareServers: minimum number of server processes which are kept spare # MaxSpareServers: maximum number of server processes which are kept spare # ServerLimit: maximum value for MaxClients for the lifetime of the server # MaxClients: maximum number of server processes allowed to start # MaxRequestsPerChild: maximum number of requests a server process serves StartServers 8 MinSpareServers5 MaxSpareServers 20 ServerLimit 256 MaxClients 256 MaxRequestsPerChild 4000 # worker MPM # StartServers: initial number of server processes to start # MaxClients: maximum number of simultaneous client connections # MinSpareThreads: minimum number of worker threads which are kept spare # MaxSpareThreads: maximum number of worker threads which are kept s
Re: [rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason
Hi Kevin, Thanks for the response. Tried cpan Module::Build and got this: Test Summary Report --- t/metadata.t (Wstat: 65280 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 255 Parse errors: Bad plan. You planned 116 tests but ran 1. t/version.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=2, Tests=1, 5 wallclock secs ( 0.01 usr 0.01 sys + 0.07 cusr 2.40 csys = 2.49 CPU) Result: FAIL Failed 2/2 test programs. 1/1 subtests failed. make: *** [test_dynamic] Error 2 DAGOLDEN/Module-Metadata-1.09.tar.gz /usr/bin/make test -- NOT OK //hint// to see the cpan-testers results for installing this module, try: reports DAGOLDEN/Module-Metadata-1.09.tar.gz Running make install make test had returned bad status, won't install without force Running install for module 'version' Running make for J/JP/JPEACOCK/version-0.96.tar.gz Has already been unwrapped into directory /root/.cpan/build/version-0.96-4Zvpfw Has already been made Running make test Has already been tested successfully Running make install Already done Running make for L/LE/LEONT/Module-Build-0.40.tar.gz Has already been unwrapped into directory /root/.cpan/build/Module-Build-0.40-JShO8A CPAN.pm: Building L/LE/LEONT/Module-Build-0.40.tar.gz Warning: Prerequisite 'Module::Metadata => 1.02' for 'LEONT/Module-Build-0.40.tar.gz' failed when processing 'DAGOLDEN/Module-Metadata-1.09.tar.gz' with 'make_test => NO'. Continuing, but chances to succeed are limited. CPAN: Time::HiRes loaded ok (v1.9719) Warning: Prerequisite 'version => 0.87' for 'LEONT/Module-Build-0.40.tar.gz' already built but the result looks suspicious. Skipping another build attempt, to prevent looping endlessly. /usr/bin/perl Build --makefile_env_macros 1 Can't locate Module/Metadata.pm in @INC (@INC contains: t/lib t/bundled lib /usr/local/lib64/perl5/site_perl/5.10.0/x86_64-linux-thread-multi /usr/local/lib/perl5/site_perl/5.10.0 /usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/5.10.0 /usr/lib/perl5/site_perl .) at lib/Module/Build/ModuleInfo.pm line 10. Compilation failed in require at lib/Module/Build/Base.pm line 23. BEGIN failed--compilation aborted at lib/Module/Build/Base.pm line 23. Compilation failed in require at lib/Module/Build.pm line 15. BEGIN failed--compilation aborted at lib/Module/Build.pm line 15. Compilation failed in require at Build line 42. BEGIN failed--compilation aborted at Build line 42. make: *** [all] Error 2 LEONT/Module-Build-0.40.tar.gz /usr/bin/make -- NOT OK Running make test Can't test without successful make Running make install Make had returned bad status, install seems impossible [root@rt-test .cpan]# Thanks, Walid -Original Message- From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kevin Falcone Sent: segunda-feira, 5 de Março de 2012 16:35 To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason On Mon, Mar 05, 2012 at 10:01:44AM +, Walid Haider wrote: > >> That sounds pretty broken. > >> What's in /root/.cpan/build ? > You are absolutely right, I went ahead and removed the build directory before > answering your question. I'm sorry. > > >You can also always manually download HTML::Mason from something like > >http://search.cpan.org/dist/HTML-Mason > >untar it and perl Makefile.PL and see if you get a better error message by > >doing it manually. > Regarding this point, I tried what you suggested and this is the error > message I am getting: > > [root@rt-test HTML-Mason-1.48]# perl Makefile.PL Can't locate > Module/Build/Compat.pm in @INC (@INC contains: inc > /usr/local/lib64/perl5/site_perl/5.10.0/x86_64-linux-thread-multi > /usr/local/lib/perl5/site_perl/5.10.0 > /usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi > /usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl > /usr/lib64/perl5/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/5.10.0 > /usr/lib/perl5/site_perl .) at Makefile.PL line 4. > BEGIN failed--compilation aborted at Makefile.PL line 4. I bet your Module::Build is too old and your CPAN.pm is too old to notice that your Module::Build is too old. Try cpan Module::Build cpan HTML::Mason -kevin
Re: [rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason
Hi Kevin, >> That sounds pretty broken. >> What's in /root/.cpan/build ? You are absolutely right, I went ahead and removed the build directory before answering your question. I'm sorry. >You can also always manually download HTML::Mason from something like >http://search.cpan.org/dist/HTML-Mason >untar it and perl Makefile.PL and see if you get a better error message by >doing it manually. Regarding this point, I tried what you suggested and this is the error message I am getting: [root@rt-test HTML-Mason-1.48]# perl Makefile.PL Can't locate Module/Build/Compat.pm in @INC (@INC contains: inc /usr/local/lib64/perl5/site_perl/5.10.0/x86_64-linux-thread-multi /usr/local/lib/perl5/site_perl/5.10.0 /usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/5.10.0 /usr/lib/perl5/site_perl .) at Makefile.PL line 4. BEGIN failed--compilation aborted at Makefile.PL line 4. -Original Message- From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kevin Falcone Sent: sexta-feira, 2 de Março de 2012 17:07 To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason Please keep list replies on the list. On Wed, Feb 29, 2012 at 05:11:25PM +, Walid Haider wrote: > I tried your suggestion, but still same error. > > Any ideas as to what else I could try? I don't see where you answered this question. >> That sounds pretty broken. >> What's in /root/.cpan/build ? You can also always manually download HTML::Mason from something like http://search.cpan.org/dist/HTML-Mason untar it and perl Makefile.PL and see if you get a better error message by doing it manually. -kevin RT Training Sessions (http://bestpractical.com/services/training.html) * Boston March 5 & 6, 2012
Re: [rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason
Hi Kevin, I tried your suggestion, but still same error. Any ideas as to what else I could try? Thanks, Walid -Original Message- From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kevin Falcone Sent: quinta-feira, 23 de Fevereiro de 2012 16:10 To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason On Thu, Feb 23, 2012 at 08:48:47AM +, Walid Haider wrote: > Hi Kevin, > > Below is the result: > > cpan[1]> look HTML::Mason > Trying to open a subshell in the build directory... > Directory '/root/.cpan/build/HTML-Mason-1.48-ygKQns' has gone. Cannot > continue. That sounds pretty broken. What's in /root/.cpan/build ? You may want to just blow away the build directory and try it fresh, but it sounds like things aren't being unpacked properly on your system. -kevin RT Training Sessions (http://bestpractical.com/services/training.html) * Boston March 5 & 6, 2012
[rt-users] FW: (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason
Hi Ruslan, Thanks for the input. Further to the output that Kevin requested (posted below). Is there anything else I can try, to resolve this issue? Regards, Walid -Original Message- From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Ruslan Zakirov Sent: quarta-feira, 22 de Fevereiro de 2012 19:29 To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason Hi, HTML::Mason uses Module::Build::Compat that may be responsible. -Original Message- From: Walid Haider Sent: quinta-feira, 23 de Fevereiro de 2012 08:49 To: rt-users@lists.bestpractical.com Subject: RE: [rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason Hi Kevin, Below is the result: [root@rt-test rt-4.0.5]# cpan cpan shell -- CPAN exploration and modules installation (v1.9800) Enter 'h' for help. cpan[1]> look HTML::Mason CPAN: Storable loaded ok (v2.21) Reading '/root/.cpan/Metadata' Database was generated on Tue, 21 Feb 2012 13:14:29 GMT CPAN: LWP::UserAgent loaded ok (v5.834) CPAN: Time::HiRes loaded ok (v1.9719) I would like to connect to one of the following sites to get 'authors/01mailrc.txt.gz': http://www.perl.org/CPAN/ ftp://ftp.perl.org/pub/CPAN/ Is it OK to try to connect to the Internet? [yes] yes Fetching with LWP: http://www.perl.org/CPAN/authors/01mailrc.txt.gz CPAN: YAML loaded ok (v0.80) Reading '/root/.cpan/sources/authors/01mailrc.txt.gz' CPAN: Compress::Zlib loaded ok (v2.049) Reading 93 yaml files from /root/.cpan/build/ DONE Restored the state of none (in 1.1443 secs) DONE Fetching with LWP: http://www.perl.org/CPAN/modules/02packages.details.txt.gz Reading '/root/.cpan/sources/modules/02packages.details.txt.gz' Database was generated on Thu, 23 Feb 2012 08:17:27 GMT DONE Fetching with LWP: http://www.perl.org/CPAN/modules/03modlist.data.gz Reading '/root/.cpan/sources/modules/03modlist.data.gz' DONE Writing /root/.cpan/Metadata Running look for module 'HTML::Mason' Trying to open a subshell in the build directory... Directory '/root/.cpan/build/HTML-Mason-1.48-ygKQns' has gone. Cannot continue. -Original Message- From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kevin Falcone Sent: quarta-feira, 22 de Fevereiro de 2012 17:27 To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason On Wed, Feb 22, 2012 at 08:58:02AM +, Walid Haider wrote: > Thanks for your response. > > Below is the full output of make fixdeps (and below that is the output of > cpan HTML::Mason outside make fixdeps): > [root@rt-test rt-4.0.5]# cpan HTML::Mason > '/usr/bin/perl Makefile.PL' returned status 512, won't make Looks like a fascinating failure. If you run cpan look HTML::Mason ls perl Makefile.PL what does it show? -kevin RT Training Sessions (http://bestpractical.com/services/training.html) * Boston March 5 & 6, 2012
Re: [rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason
Hi Kevin, Below is the result: [root@rt-test rt-4.0.5]# cpan cpan shell -- CPAN exploration and modules installation (v1.9800) Enter 'h' for help. cpan[1]> look HTML::Mason CPAN: Storable loaded ok (v2.21) Reading '/root/.cpan/Metadata' Database was generated on Tue, 21 Feb 2012 13:14:29 GMT CPAN: LWP::UserAgent loaded ok (v5.834) CPAN: Time::HiRes loaded ok (v1.9719) I would like to connect to one of the following sites to get 'authors/01mailrc.txt.gz': http://www.perl.org/CPAN/ ftp://ftp.perl.org/pub/CPAN/ Is it OK to try to connect to the Internet? [yes] yes Fetching with LWP: http://www.perl.org/CPAN/authors/01mailrc.txt.gz CPAN: YAML loaded ok (v0.80) Reading '/root/.cpan/sources/authors/01mailrc.txt.gz' CPAN: Compress::Zlib loaded ok (v2.049) Reading 93 yaml files from /root/.cpan/build/ DONE Restored the state of none (in 1.1443 secs) DONE Fetching with LWP: http://www.perl.org/CPAN/modules/02packages.details.txt.gz Reading '/root/.cpan/sources/modules/02packages.details.txt.gz' Database was generated on Thu, 23 Feb 2012 08:17:27 GMT DONE Fetching with LWP: http://www.perl.org/CPAN/modules/03modlist.data.gz Reading '/root/.cpan/sources/modules/03modlist.data.gz' DONE Writing /root/.cpan/Metadata Running look for module 'HTML::Mason' Trying to open a subshell in the build directory... Directory '/root/.cpan/build/HTML-Mason-1.48-ygKQns' has gone. Cannot continue. -Original Message- From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kevin Falcone Sent: quarta-feira, 22 de Fevereiro de 2012 17:27 To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason On Wed, Feb 22, 2012 at 08:58:02AM +, Walid Haider wrote: > Thanks for your response. > > Below is the full output of make fixdeps (and below that is the output of > cpan HTML::Mason outside make fixdeps): > [root@rt-test rt-4.0.5]# cpan HTML::Mason > '/usr/bin/perl Makefile.PL' returned status 512, won't make Looks like a fascinating failure. If you run cpan look HTML::Mason ls perl Makefile.PL what does it show? -kevin RT Training Sessions (http://bestpractical.com/services/training.html) * Boston March 5 & 6, 2012
Re: [rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason
-Mason-1.48/lib/HTML/Mason/Admin.pod HTML-Mason-1.48/lib/HTML/Mason/Lexer.pm HTML-Mason-1.48/lib/HTML/Mason/Tools.pm HTML-Mason-1.48/lib/HTML/Mason/Devel.pod HTML-Mason-1.48/lib/HTML/Mason/CGIHandler.pm HTML-Mason-1.48/lib/HTML/Mason/FakeApache.pm HTML-Mason-1.48/lib/HTML/Mason/Params.pod HTML-Mason-1.48/lib/HTML/Mason/Subclassing.pod HTML-Mason-1.48/lib/HTML/Mason/Tests.pm HTML-Mason-1.48/lib/HTML/Mason/ComponentSource.pm HTML-Mason-1.48/lib/HTML/Mason/Component.pm HTML-Mason-1.48/lib/HTML/Mason/Resolver HTML-Mason-1.48/lib/HTML/Mason/Resolver/Null.pm HTML-Mason-1.48/lib/HTML/Mason/Resolver/File.pm HTML-Mason-1.48/lib/HTML/Mason/Component HTML-Mason-1.48/lib/HTML/Mason/Component/FileBased.pm HTML-Mason-1.48/lib/HTML/Mason/Component/Subcomponent.pm HTML-Mason-1.48/lib/HTML/Mason/Cache HTML-Mason-1.48/lib/HTML/Mason/Cache/BaseCache.pm HTML-Mason-1.48/lib/HTML/Mason/Apache HTML-Mason-1.48/lib/HTML/Mason/Apache/Request.pm HTML-Mason-1.48/lib/HTML/Mason/Plugin HTML-Mason-1.48/lib/HTML/Mason/Plugin/Context.pm HTML-Mason-1.48/lib/HTML/Mason/Compiler HTML-Mason-1.48/lib/HTML/Mason/Compiler/ToObject.pm HTML-Mason-1.48/lib/Bundle HTML-Mason-1.48/lib/Bundle/HTML HTML-Mason-1.48/lib/Bundle/HTML/Mason.pm HTML-Mason-1.48/lib/Apache HTML-Mason-1.48/lib/Apache/Mason.pm HTML-Mason-1.48/htdocs HTML-Mason-1.48/htdocs/FakeApache.html HTML-Mason-1.48/htdocs/Component.html HTML-Mason-1.48/htdocs/index.html HTML-Mason-1.48/htdocs/Compiler.html HTML-Mason-1.48/htdocs/Resolver.html HTML-Mason-1.48/htdocs/Devel.html HTML-Mason-1.48/htdocs/Exceptions.html HTML-Mason-1.48/htdocs/Params.html HTML-Mason-1.48/htdocs/Lexer.html HTML-Mason-1.48/htdocs/Escapes.html HTML-Mason-1.48/htdocs/Plugin.html HTML-Mason-1.48/htdocs/Tools.html HTML-Mason-1.48/htdocs/Utils.html HTML-Mason-1.48/htdocs/Interp.html HTML-Mason-1.48/htdocs/Mason.html HTML-Mason-1.48/htdocs/Admin.html HTML-Mason-1.48/htdocs/ApacheHandler.html HTML-Mason-1.48/htdocs/Parser.html HTML-Mason-1.48/htdocs/CGIHandler.html HTML-Mason-1.48/htdocs/ComponentSource.html HTML-Mason-1.48/htdocs/MethodMaker.html HTML-Mason-1.48/htdocs/Tests.html HTML-Mason-1.48/htdocs/Subclassing.html HTML-Mason-1.48/htdocs/Request.html HTML-Mason-1.48/htdocs/Resolver HTML-Mason-1.48/htdocs/Resolver/File.html HTML-Mason-1.48/htdocs/Resolver/Null.html HTML-Mason-1.48/htdocs/Component HTML-Mason-1.48/htdocs/Component/FileBased.html HTML-Mason-1.48/htdocs/Component/Subcomponent.html HTML-Mason-1.48/htdocs/Cache HTML-Mason-1.48/htdocs/Cache/BaseCache.html HTML-Mason-1.48/htdocs/Plugin HTML-Mason-1.48/htdocs/Plugin/Context.html HTML-Mason-1.48/htdocs/Compiler HTML-Mason-1.48/htdocs/Compiler/ToObject.html HTML-Mason-1.48/inc HTML-Mason-1.48/inc/params.mtxt HTML-Mason-1.48/inc/Mason HTML-Mason-1.48/inc/Mason/Build.pm CPAN: File::Temp loaded ok (v0.22) '/usr/bin/perl Makefile.PL' returned status 512, won't make Running make test Make had some problems, won't test Running make install Make had some problems, won't install CPAN: CPAN::Meta loaded ok (v2.112150) Could not read metadata file. Falling back to other methods to determine prerequisites [root@rt-test rt-4.0.5]# -Original Message- From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kevin Falcone Sent: terça-feira, 21 de Fevereiro de 2012 19:40 To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason On Tue, Feb 21, 2012 at 04:24:05PM +, Walid Haider wrote: >I am trying to install RT 4.0.5 on FC 12, when I "make fixdeps", I am > getting: > >... > >HTML-Mason-1.48/inc/Mason/Build.pm > '/usr/bin/perl Makefile.PL' returned status 512, won't make >Running make test > Make had some problems, won't test >Running make install > Make had some problems, won't install > >... > >Any ideas what could be going wrong, and how to resolve this issue? Is that the full output of make fixdeps around that module? What happens if you run cpan HTML::Mason outside make fixdeps? -kevin RT Training Sessions (http://bestpractical.com/services/training.html) * Boston March 5 & 6, 2012
[rt-users] (Installing RT 4.0.5) Fixdeps unable to make HTML::Mason
Hi, I am trying to install RT 4.0.5 on FC 12, when I "make fixdeps", I am getting: ... HTML-Mason-1.48/inc/Mason/Build.pm '/usr/bin/perl Makefile.PL' returned status 512, won't make Running make test Make had some problems, won't test Running make install Make had some problems, won't install ... Any ideas what could be going wrong, and how to resolve this issue? Thanks in anticipation. Walid RT Training Sessions (http://bestpractical.com/services/training.html) * Boston March 5 & 6, 2012
Re: [rt-users] Time Worked Report
Hi Kenn, Thanks for all the help - I finally managed to implement the Time Worked Report - the problem was when I copied the code for SelectMultiQueue from http://requesttracker.wikia.com/wiki/TimeWorkedReport, I did not realize there was a blank space for each line. Regards, Walid From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kenneth Crocker Sent: quinta-feira, 31 de Março de 2011 18:35 To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] Time Worked Report Walid, In step 4, you don't mention editing the "Tabs" file with the changes specified in the instructions. In steps 5 & 6, those files should have been moved to usr/share/rt3/local/html/Tools/Reports. 1) The "Tabs" and "index.html" files must be modified & kept in-sync in order to see the option in the "Tabs" heading. That certainly explains why they both have the same paths for the same reports. You should compare the code between those two and make sure they look exactly like they should, according to the instructions. 2) The "TimeWorkedReport.html" file has to be where the "Tabs" and "index.html" files are pointing to within the "path" shown. Moving these files around to other directories will just frustrate you more and distract you away from de-bugging the real problem. If this doesn't work, send me a list of the modified code for "Tabs" and "index.html". Kenn LBNL On Thu, Mar 31, 2011 at 1:18 AM, Walid Haider mailto:walid.hai...@movensis.com>> wrote: Hi Kenn, Thanks for the tip regarding RT $home, I will definitely consider it. I must be missing something, as I cannot see the Time Worked Report option on the menu. This is what I did: 1. Created a local directory within /usr/share/rt3, and then created the /usr/share/rt3/local/html and /usr/share/rt3/local/html/Elements directories. 2. Created the new file SelectMultiQueue (with the relevant content) within /usr/share/rt3/local/html/Elements 3. Created .../rt3/local/Tools, .../rt3/local/Tools/Reports, and .../rt3/local/Tools/Reports/Elements directories 4. Copied the Tabs file from /usr/share/rt3/html/Tools/Reports/Elements/Tabs to .../rt3/local/Tools/Reports/Elements 5. Copied the index.html file from /usr/share/rt3/html/Tools/Reports/index.html to .../rt3/local/Tools/ and edited the file accordingly 6. Created the TimeWorkedReport.html (with the relevant content) file in .../rt3/local/Tools/ 7. I restarted httpd and logged into RT, but could not see the Timed Worked Report option on the menu I then tried moving the index.html and TimeWorkedReport.html files from /usr/share/rt3/local/html/Tools/Reports into /usr/share/rt3/local/html/Tools/. But after restarting httpd, I still could not see the Time Worked Report. Finally, I tried creating the local directory in /usr and the rt3 directory within it (/usr/local/rt3). I then moved the entire html directory, created in 1. (above), to /usr/local/rt3. But again, after restarting httpd I could not see the Time Worked Report. Thanks in advance, Walid From: rt-users-boun...@lists.bestpractical.com<mailto:rt-users-boun...@lists.bestpractical.com> [mailto:rt-users-boun...@lists.bestpractical.com<mailto:rt-users-boun...@lists.bestpractical.com>] On Behalf Of Kenneth Crocker Sent: terça-feira, 29 de Março de 2011 16:42 To: rt-users@lists.bestpractical.com<mailto:rt-users@lists.bestpractical.com> Subject: Re: [rt-users] Time Worked Report Opps, that was supposed to be /local/html/Tools/Report. Sorry. Kenn On Tue, Mar 29, 2011 at 8:39 AM, Kenneth Crocker mailto:kfcroc...@lbl.gov>> wrote: Walid, Also, we used to have a different $home than /opt/rt3/ (in Solaris) and it caused endless problems when trying to implement extensions. We decided to just go to opt/rt3 and put it in VM and we've been sailing smoothly ever since. Just a thought for you to consider. Kenn LBNL On Tue, Mar 29, 2011 at 8:37 AM, Kenneth Crocker mailto:kfcroc...@lbl.gov>> wrote: Walid, Well, Wherever you have the .../Tools/Report/... you will need a .../local/Tools/Report/ version to put "TimeWorkedReport". Kenn LBNL On Tue, Mar 29, 2011 at 7:00 AM, Walid Haider mailto:walid.hai...@movensis.com>> wrote: Hi Johan, No, I do not. Should I go ahead and create it and then follow Kenn's instructions? Regards, Walid From: rt-users-boun...@lists.bestpractical.com<mailto:rt-users-boun...@lists.bestpractical.com> [mailto:rt-users-boun...@lists.bestpractical.com<mailto:rt-users-boun...@lists.bestpractical.com>] On Behalf Of Johan Sjöberg Sent: terça-feira, 29 de Março de 2011 14:56 To: rt-users@lists.bestpractical.com<mailto:rt-users@lists.bestpractical.com> Subject: Re: [rt-users] Time Wor
Re: [rt-users] Time Worked Report
Hi Kenn, Thanks for the tip regarding RT $home, I will definitely consider it. I must be missing something, as I cannot see the Time Worked Report option on the menu. This is what I did: 1. Created a local directory within /usr/share/rt3, and then created the /usr/share/rt3/local/html and /usr/share/rt3/local/html/Elements directories. 2. Created the new file SelectMultiQueue (with the relevant content) within /usr/share/rt3/local/html/Elements 3. Created .../rt3/local/Tools, .../rt3/local/Tools/Reports, and .../rt3/local/Tools/Reports/Elements directories 4. Copied the Tabs file from /usr/share/rt3/html/Tools/Reports/Elements/Tabs to .../rt3/local/Tools/Reports/Elements 5. Copied the index.html file from /usr/share/rt3/html/Tools/Reports/index.html to .../rt3/local/Tools/ and edited the file accordingly 6. Created the TimeWorkedReport.html (with the relevant content) file in .../rt3/local/Tools/ 7. I restarted httpd and logged into RT, but could not see the Timed Worked Report option on the menu I then tried moving the index.html and TimeWorkedReport.html files from /usr/share/rt3/local/html/Tools/Reports into /usr/share/rt3/local/html/Tools/. But after restarting httpd, I still could not see the Time Worked Report. Finally, I tried creating the local directory in /usr and the rt3 directory within it (/usr/local/rt3). I then moved the entire html directory, created in 1. (above), to /usr/local/rt3. But again, after restarting httpd I could not see the Time Worked Report. Thanks in advance, Walid From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kenneth Crocker Sent: terça-feira, 29 de Março de 2011 16:42 To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] Time Worked Report Opps, that was supposed to be /local/html/Tools/Report. Sorry. Kenn On Tue, Mar 29, 2011 at 8:39 AM, Kenneth Crocker mailto:kfcroc...@lbl.gov>> wrote: Walid, Also, we used to have a different $home than /opt/rt3/ (in Solaris) and it caused endless problems when trying to implement extensions. We decided to just go to opt/rt3 and put it in VM and we've been sailing smoothly ever since. Just a thought for you to consider. Kenn LBNL On Tue, Mar 29, 2011 at 8:37 AM, Kenneth Crocker mailto:kfcroc...@lbl.gov>> wrote: Walid, Well, Wherever you have the .../Tools/Report/... you will need a .../local/Tools/Report/ version to put "TimeWorkedReport". Kenn LBNL On Tue, Mar 29, 2011 at 7:00 AM, Walid Haider mailto:walid.hai...@movensis.com>> wrote: Hi Johan, No, I do not. Should I go ahead and create it and then follow Kenn's instructions? Regards, Walid From: rt-users-boun...@lists.bestpractical.com<mailto:rt-users-boun...@lists.bestpractical.com> [mailto:rt-users-boun...@lists.bestpractical.com<mailto:rt-users-boun...@lists.bestpractical.com>] On Behalf Of Johan Sjöberg Sent: terça-feira, 29 de Março de 2011 14:56 To: rt-users@lists.bestpractical.com<mailto:rt-users@lists.bestpractical.com> Subject: Re: [rt-users] Time Worked Report Do you have a /usr/local/rt3? /Johan From: rt-users-boun...@lists.bestpractical.com<mailto:rt-users-boun...@lists.bestpractical.com> [mailto:rt-users-boun...@lists.bestpractical.com<mailto:rt-users-boun...@lists.bestpractical.com>] On Behalf Of Walid Haider Sent: den 29 mars 2011 15:20 To: Kenneth Crocker; rt-users@lists.bestpractical.com<mailto:rt-users@lists.bestpractical.com> Subject: Re: [rt-users] Time Worked Report Kenn, Again, thanks for the reply. As I ran a packaged install of RT 3.8.4, my $home is /usr/share/rt3. My folder structure is different compared to what you mention below, as I do not have a share directory within my RT $home. Please advise if I should create the local directory within /usr/share/rt3. Thanks, Walid From: rt-users-boun...@lists.bestpractical.com<mailto:rt-users-boun...@lists.bestpractical.com> [mailto:rt-users-boun...@lists.bestpractical.com<mailto:rt-users-boun...@lists.bestpractical.com>] On Behalf Of Kenneth Crocker Sent: segunda-feira, 28 de Março de 2011 17:33 To: rt-users@lists.bestpractical.com<mailto:rt-users@lists.bestpractical.com> Subject: Re: [rt-users] Time Worked Report Walid, What I mean is this; it is highly recommended that any changes you make to RT code be done in a "local" version. RT will automatically look to $Home/local/.../.../ (where $home is usually opt/rt3/) for any override code that an installation may have developed. In this example (TimeWorkedReport), I copied the various /$home/share/.../... directories & files listed in the "readme' for that report into a /$home/local/.../... version/copy of those directoryies & files. I did NOT make any changes to any /share/ version of RT code. This is recommended for a couple reas
Re: [rt-users] Time Worked Report
Hi Johan, No, I do not. Should I go ahead and create it and then follow Kenn's instructions? Regards, Walid From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Johan Sjöberg Sent: terça-feira, 29 de Março de 2011 14:56 To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] Time Worked Report Do you have a /usr/local/rt3? /Johan From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Walid Haider Sent: den 29 mars 2011 15:20 To: Kenneth Crocker; rt-users@lists.bestpractical.com Subject: Re: [rt-users] Time Worked Report Kenn, Again, thanks for the reply. As I ran a packaged install of RT 3.8.4, my $home is /usr/share/rt3. My folder structure is different compared to what you mention below, as I do not have a share directory within my RT $home. Please advise if I should create the local directory within /usr/share/rt3. Thanks, Walid From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kenneth Crocker Sent: segunda-feira, 28 de Março de 2011 17:33 To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] Time Worked Report Walid, What I mean is this; it is highly recommended that any changes you make to RT code be done in a "local" version. RT will automatically look to $Home/local/.../.../ (where $home is usually opt/rt3/) for any override code that an installation may have developed. In this example (TimeWorkedReport), I copied the various /$home/share/.../... directories & files listed in the "readme' for that report into a /$home/local/.../... version/copy of those directoryies & files. I did NOT make any changes to any /share/ version of RT code. This is recommended for a couple reasons; the least of which it is easier to maintain later versions of RT without wiping out your local code (provided you keep a copy of that code). Also, industry wide for about the last 40 years, it has been considered a best practice to never mess with original code, but to provide a method that allows you to use other code instead. So, my advice is to first; return all /share/ code to it's original state. Then create $home/local/html/Tools/Reports directories in order to copy/create the files mentioned in the "TimeWorkedReport" documentation. That's what I did: 1) If it exists,type "/opt/rt3/local/html/Elements/" otherwise, create it. 2) Copy the "delivered" file (from .../share/...) SelectQueue over to this directory with a the new name. A) Type "cp /opt/rt3/share/html/Elements/SelectQueue SelectMultiQueue" . 3) Replace the code in "SelectMultiQueue" with the code specified for this file from the document the "TimeWorkedReport". 4) If it exists, type "/opt/rt3/local/html/Tools/" , otherwise, create it. 5) Create new directories: A) Create "Reports" directory within "Tools" B) Get into "Reports" directory. C) Create "Elements" directory within "Tools/Reports" 6) Copy the "delivered" files (from .../share/...) (Tabs, index.html) over to the new directories: A) Copy the "Tabs" file over to "Tools/Reports/Elements": 1) Within "Elements", type "cp /opt/rt3/share/html/Tools/Reports/Elements/Tabs ." . 2) Go back 1 directory level to get to "/Tools/Reports". 3) Copy the "index.html" file over to "Tools/Reports" twice: a) Within "Tools/Reports", type "cp /opt/rt3/share/html/Tools/index.html ." . b) Within "Tools/Reports", type "cp /opt/rt3/share/html/Tools/index.html TimeWorkedReport.html" . 7) Modify/Replace the code in "Tabs", "index.html" & "TimeWorkedReport" with the code specified for these files from the document the "Time Worked Report". Anyway, This is the procedure I followed and I had absolutely no problems AND I didn't have to worry about Production being messed up. Also, I'm in 3.8.7 so I made sure to follow the 3.8 instructions. Hope this helps. Kenn LBNL
Re: [rt-users] Time Worked Report
Kenn, Again, thanks for the reply. As I ran a packaged install of RT 3.8.4, my $home is /usr/share/rt3. My folder structure is different compared to what you mention below, as I do not have a share directory within my RT $home. Please advise if I should create the local directory within /usr/share/rt3. Thanks, Walid From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kenneth Crocker Sent: segunda-feira, 28 de Março de 2011 17:33 To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] Time Worked Report Walid, What I mean is this; it is highly recommended that any changes you make to RT code be done in a "local" version. RT will automatically look to $Home/local/.../.../ (where $home is usually opt/rt3/) for any override code that an installation may have developed. In this example (TimeWorkedReport), I copied the various /$home/share/.../... directories & files listed in the "readme' for that report into a /$home/local/.../... version/copy of those directoryies & files. I did NOT make any changes to any /share/ version of RT code. This is recommended for a couple reasons; the least of which it is easier to maintain later versions of RT without wiping out your local code (provided you keep a copy of that code). Also, industry wide for about the last 40 years, it has been considered a best practice to never mess with original code, but to provide a method that allows you to use other code instead. So, my advice is to first; return all /share/ code to it's original state. Then create $home/local/html/Tools/Reports directories in order to copy/create the files mentioned in the "TimeWorkedReport" documentation. That's what I did: 1) If it exists,type "/opt/rt3/local/html/Elements/" otherwise, create it. 2) Copy the "delivered" file (from .../share/...) SelectQueue over to this directory with a the new name. A) Type "cp /opt/rt3/share/html/Elements/SelectQueue SelectMultiQueue" . 3) Replace the code in "SelectMultiQueue" with the code specified for this file from the document the "TimeWorkedReport". 4) If it exists, type "/opt/rt3/local/html/Tools/" , otherwise, create it. 5) Create new directories: A) Create "Reports" directory within "Tools" B) Get into "Reports" directory. C) Create "Elements" directory within "Tools/Reports" 6) Copy the "delivered" files (from .../share/...) (Tabs, index.html) over to the new directories: A) Copy the "Tabs" file over to "Tools/Reports/Elements": 1) Within "Elements", type "cp /opt/rt3/share/html/Tools/Reports/Elements/Tabs ." . 2) Go back 1 directory level to get to "/Tools/Reports". 3) Copy the "index.html" file over to "Tools/Reports" twice: a) Within "Tools/Reports", type "cp /opt/rt3/share/html/Tools/index.html ." . b) Within "Tools/Reports", type "cp /opt/rt3/share/html/Tools/index.html TimeWorkedReport.html" . 7) Modify/Replace the code in "Tabs", "index.html" & "TimeWorkedReport" with the code specified for these files from the document the "Time Worked Report". Anyway, This is the procedure I followed and I had absolutely no problems AND I didn't have to worry about Production being messed up. Also, I'm in 3.8.7 so I made sure to follow the 3.8 instructions. Hope this helps. Kenn LBNL
[rt-users] Time Worked Report
Hi, I am a bit of a newbie with RT, and was wondering if you could help me. After following the installation your instructions at http://requesttracker.wikia.com/wiki/TimeWorkedReport, I get the following errors when clicking on the Time Worked Report link in RT: Error during compilation of /usr/share/rt3/html/Elements/SelectMultiQueue: Global symbol "$d" requires explicit package name at /usr/share/rt3/html/Elements/SelectMultiQueue line 51. Global symbol "$queue" requires explicit package name at /usr/share/rt3/html/Elements/SelectMultiQueue line 69. Global symbol "$queue" requires explicit package name at /usr/share/rt3/html/Elements/SelectMultiQueue line 69. Global symbol "$queue" requires explicit package name at /usr/share/rt3/html/Elements/SelectMultiQueue line 77. Global symbol "$queue" requires explicit package name at /usr/share/rt3/html/Elements/SelectMultiQueue line 80. Although the requirement states RT 3.8.5, I decided to give it a go on 3.8.4. Must I definitely upgrade in order to get this report to work? I am running RT on the following setup: Fedora Core 12, Apache 2.2.14, MYSQL 5.1 Thanks in advance. Regards, Walid
Re: [rt-users] Support Contract Client Check
Hi Roy, Thanks for your response, any chance you can send me an example of the global scrip you are using? Regards, Walid From: Raed El-Hames [mailto:raed.el-ha...@daisygroupplc.com] Sent: quinta-feira, 24 de Março de 2011 12:10 To: Walid Haider; rt-users@lists.bestpractical.com Subject: RE: Support Contract Client Check Walid: I've done something similar but my approach was slightly different. My customers in most cases have more than one contact, so for every customer I created a group, and added their contacts as members of their group, the group name is the customer name, and I added a couple of group custom fields, contract_name and contract_expire_date. When any of the contacts create a ticket, there is a global scrip that identify the requestor and if it belongs to a customer group it populates a ticket custom field customer_name with the name of the group the requestor belongs to, it also populates ticket custom fields relating to contract name and expire grabbed from the group custom fields. To keep my RT in sync with the CRM system (to update the customer and contract information), I run daily script that export this info from CRM and update the group custom fields within my RT. Hope this helps. Regards; Roy From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Walid Haider Sent: 24 March 2011 11:54 To: rt-users@lists.bestpractical.com Subject: [rt-users] Support Contract Client Check Hi, I am running RT 3.8.4 and have created a custom field, with a list of all our clients, so that the client name is selected from the list when creating or updating a ticket. I am now looking to implement a way of checking if the client's support contract has not expired (and perhaps even, displaying a message informing the RT user that the client's contract has expired and also highlighting the custom field in red - under ticket metadata - when viewing existing tickets referring to clients that do not have valid support contract). This support contract information is available in an excel spreadsheet that I could either: · link to RT in some way (of course, the danger here is that in order for this to work, the name of client must be exactly the same as in RT) or; · update the support contract information in RT form time to time (probably safer this way) In future, I would also like to allow our clients to be able to view and update their own tickets, and would also like to deny access (automatically, based on the check above) if the support contract has expired - possibly displaying a message informing the user that why the access was denied. I would really appreciate in if someone could point me in the right direction. Thanks and regards, Walid
[rt-users] Support Contract Client Check
Hi, I am running RT 3.8.4 and have created a custom field, with a list of all our clients, so that the client name is selected from the list when creating or updating a ticket. I am now looking to implement a way of checking if the client's support contract has not expired (and perhaps even, displaying a message informing the RT user that the client's contract has expired and also highlighting the custom field in red - under ticket metadata - when viewing existing tickets referring to clients that do not have valid support contract). This support contract information is available in an excel spreadsheet that I could either: * link to RT in some way (of course, the danger here is that in order for this to work, the name of client must be exactly the same as in RT) or; * update the support contract information in RT form time to time (probably safer this way) In future, I would also like to allow our clients to be able to view and update their own tickets, and would also like to deny access (automatically, based on the check above) if the support contract has expired - possibly displaying a message informing the user that why the access was denied. I would really appreciate in if someone could point me in the right direction. Thanks and regards, Walid
[rt-users] RT 3.8.4 to 3.8.9 Upgrade
Hi, I am a bit of a new-bie on setting up RT and having trouble upgrading RT from 3.8.4 to 3.8.9. (NB: RT 3.8.4 was installed using yum) Problem: Upgrade seemed to complete successfully, but strangely enough when I login to RT, it still shows me version 3.8.4. I am running RT on the following setup: Fedora Core 12, Apache 2.2.14, MYSQL 5.1 PS: I read in a thread (http://www.gossamer-threads.com/lists/rt/users/93541?search_string=3.8.4;#93541) that someone had a similar issue but upgrading to 3.8.8, however, not sure what is meant by "manually installed to 3.8.8". I followed the steps detailed below to perform the upgrade: -- unpacked tar xzvf rt-3.8.9.tar.gz cd rt-3.8.9 ./configure --prefix=/etc/rt3/ -- checked for missing dependencies by running: make testdeps -- script reported some missing dependencies, ran the following command: make fixdeps I was notified to configure the CPAN shell, ran the following command to configure it: /usr/bin/perl -MCPAN -e shell when prompted installed Bundle::CPANxxl After this completed... CPAN -- (typed "exit") -- rechecked for missing dependencies by running: make testdeps -- ran upgrade make upgrade Congratulations. RT has been upgraded. You should now check over /etc/rt3/etc/RT_Config.pm for any necessary site customization. Additionally, you should update RT's system database objects by running /etc/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password --action upgrade + -- updated database objects by running: /etc/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password --action upgrade password: (upgrade to 3.8.9) -- cleared mason cache dir: rm -fr /etc/rt3/var/mason_data/obj -- stopped and started web-server service httpd stop service httpd start I would appreciate it if someone would point me in the right direction. Thanks, Walid
