Hi, I created a queue and later renamed it before any tickets were
created in it. Now when any tickets are created in it, the old queue
name is displayed in the edit page. Displaying the ticket shows the
correct queue name. Searches display the correct queue name. It seems to
be only the edit page that has this problem.
Is this a known problem?
I’ve attached a screenshot of the search results displaying the correct
queue name, and the edit page displaying the incorrect (old) queue name.
Hi everyone,
I just installed a fresh copy of 3.8 (new server). It is up and
running. I want to use the data in my existing 3.6.3 db on it. I
dumped and copied my db over to the new server, I restored it. Good so
far. I now want to update it to make sure its 3.8 friendly (though I
can log in and view my old tickets on it now).
I was looking through the upgrade docs and archives put I can’t seem to
get the upgrade working properly. When I try this:
In order to create or update your RT database, this script needs to
connect to your mysql instance on localhost as root
Please specify that user’s database password below. If the user has no
database
password, just press return.
Password:
Working with:
Type: mysql
Host: localhost
Name: rt3
User: rt_user
DBA: root
Couldn’t finish ‘upgrade’ step.
ERROR: Couldn’t read dir ‘./etc/upgrade’ with upgrade data
I’m sure its something small I’m overlooking (I hope). Any advice would
be great.
Queues are keyed by ID number, not name. The name field is merely a
reference or related field. When a ticket points to a queue, it points
to the id number and in your instance, that never changed. Searches,
however, may have the selection criteria referring to a name and in that
instance, the search needs to be changed… It is probably your cache
that needs to be refreshed. Hope this helps.
Kenn
LBNLOn 8/14/2008 9:47 AM, scott smith wrote:
Hi, I created a queue and later renamed it before any tickets were
created in it. Now when any tickets are created in it, the old queue
name is displayed in the edit page. Displaying the ticket shows the
correct queue name. Searches display the correct queue name. It seems to
be only the edit page that has this problem.
Is this a known problem?
I’ve attached a screenshot of the search results displaying the correct
queue name, and the edit page displaying the incorrect (old) queue name.
Queues are keyed by ID number, not name. The name field is merely a
reference or related field. When a ticket points to a queue, it points
to the id number and in your instance, that never changed. Searches,
Yeah, I thought as much
however, may have the selection criteria referring to a name and in that
instance, the search needs to be changed… It is probably your cache
that needs to be refreshed. Hope this helps.
Hi everyone,
I just installed a fresh copy of 3.8 (new server). It is up and
running. I want to use the data in my existing 3.6.3 db on it. I
dumped and copied my db over to the new server, I restored it. Good so
far. I now want to update it to make sure its 3.8 friendly (though I
can log in and view my old tickets on it now).
I was looking through the upgrade docs and archives put I can’t seem to
get the upgrade working properly. When I try this:
In order to create or update your RT database, this script needs to
connect to your mysql instance on localhost as root
Please specify that user’s database password below. If the user has no
database
password, just press return.
Password:
Working with:
Type: mysql
Host: localhost
Name: rt3
User: rt_user
DBA: root
Couldn’t finish ‘upgrade’ step.
ERROR: Couldn’t read dir ‘./etc/upgrade’ with upgrade data
I’m sure its something small I’m overlooking (I hope). Any advice would
be great.
Cheers!
You need to run it from your extracted source directory… the
etc/upgrade files are there. So to do that you have to specify the full
path to rt-setup-database which is in your installed ./sbin dir.
ex: /opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password
–action upgrade
I did notice I don’t have an “upgrade” folder in my installed etc
folder. I do in my install source though. Would that have something to
do with it?
You need to run it from your extracted source directory… the
etc/upgrade files are there. So to do that you have to specify the full
path to rt-setup-database which is in your installed ./sbin dir.
ex: /opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password
I did notice I don’t have an “upgrade” folder in my installed etc
folder. I do in my install source though. Would that have something to
do with it?
You need to run it from your extracted source directory… the
etc/upgrade files are there. So to do that you have to specify the full
path to rt-setup-database which is in your installed ./sbin dir.
ex: /opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password
–action upgrade
Curtis
You’ll have to run it from your /usr/src/rt-3.8.1rc4 or equivalent
directory because like you said the etc/upgrade files are in there,
which is why you have to specify the full path to the rt-setup-database
Curtis,
Thank you VERY much! That did it! I am now rocking my 3.8 db
You’ll have to run it from your /usr/src/rt-3.8.1rc4 or equivalent
directory because like you said the etc/upgrade files are in there,
which is why you have to specify the full path to the rt-setup-database
