<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I guess I should add that although I
cannot log into RT through the WEB I can confirm that both root
and rtuser can access mysql locally via the command line. I guess
however that although the users that RT runs as can access MySQL
that does not mean that the users defined in there are working...<br>
<br>
<br>
<div class="moz-signature">
<div style="font-family:Arial;font-size:12px">
<p><strong>Paul O’Rorke</strong><br>
Tracker Software Products<br>
<a href="mailto:paul.ororke@tracker-software.com">paul@tracker-software.com</a></p>
</div>
</div>
On 7/29/2013 2:30 PM, Paul O'Rorke wrote:<br>
</div>
<blockquote cite="mid:51F6DEFB.1090407@tracker-software.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Thanks Kevin,<br>
<br>
I'm going through that right now. I must admit I'm a little
confused by the whole LifeCycle thing. I'm going through <a
moz-do-not-send="true"
href="http://bestpractical.com/docs/rt/4.0/customizing/lifecycles.html">http://bestpractical.com/docs/rt/4.0/customizing/lifecycles.html</a>
now to see if I can swing this. <br>
<br>
In the meanwhile I am finding that after running <b>make
upgrade-database</b> (took me through all the upgrades from
3.8.4 to 4.0.15) and then trying to set up Apache again I'm
running into a loop on the login page. If I run Apache I don't
get a login page at all. If I stop Apache and start
<pre style="display: block; font-family: monospace; font-size: 14px; padding-left: 1em; line-height: 1.2em; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">/opt/rt4/sbin/rt-server</pre>
then I get:<br>
<br>
<tt>Reason: your browser did not supply a Referrer header
(/opt/rt4/sbin/../lib/RT/Interface/Web.pm:397)</tt><tt><br>
</tt><tt>[Mon Jul 29 21:25:46 2013] [notice]: Marking original
destination as having side-effects before redirecting for
login.</tt><tt><br>
</tt><tt>Request:
/rt/NoAuth/Login.html?next=d820f5cbf943dfe116cbee257b840411</tt><tt><br>
</tt><tt>Reason: your browser did not supply a Referrer header
(/opt/rt4/sbin/../lib/RT/Interface/Web.pm:397)</tt><tt><br>
</tt><tt>[Mon Jul 29 21:26:00 2013] [error]: FAILED LOGIN for
root from 192.168.0.254
(/opt/rt4/sbin/../lib/RT/Interface/Web.pm:753)</tt><tt><br>
</tt><tt>[Mon Jul 29 21:26:12 2013] [error]: FAILED LOGIN for
rtuser from 192.168.0.254
(/opt/rt4/sbin/../lib/RT/Interface/Web.pm:753)</tt><tt><br>
</tt><br>
I'm assuming I've not actually managed to get my database
upgraded properly as I'm very confident of the credentials used
(tried others as well that worked in 3.8.4). After running <b>make
upgrade-database</b> do I still need to do the individual
upgrades in each of the README files for the various updates or
does <b>make upgrade-database</b> effectively do the same?<br>
<br>
Thanks<br>
<br>
<br>
<div class="moz-signature">
<div style="font-family:Arial;font-size:12px">
<p><strong>Paul O’Rorke</strong><br>
Tracker Software Products<br>
<a moz-do-not-send="true"
href="mailto:paul.ororke@tracker-software.com">paul@tracker-software.com</a></p>
<br>
</div>
</div>
On 7/26/2013 5:53 AM, Kevin Falcone wrote:<br>
</div>
<blockquote cite="mid:20130726125343.GS22003@jibsheet.com"
type="cite">
<pre wrap="">On Thu, Jul 25, 2013 at 01:47:07PM -0700, Paul O'Rorke wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> I meant the README Docs in the installer archive mostly.
My concern with the migration is that I used custom statuses for queues and I have to now use
the LifeCycle set up. I wasn't sure how the DB restore would go because I imagine I'm going
to have different fields in my database than what 4.0.18 expects. Anyway - installing 4.0.14
on my new server now and will get back I'm sure if I run into any troubles...
</pre>
</blockquote>
<pre wrap="">To start, just port your custom statuses to LifeCycles. That should
be as easy as adding them to the active and inactive lists and
defining some transitions.
Once you're migrated, you can deal with tweaking them to be more
complicated.
-kevin
</pre>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>