Shredder CLI Question

I’m trying to test out the removal of deleted tickets using the
rtx-shredder CLI method. I’ve been entering it nearly verbatim from the
RTx::Shredder page on CPAN (ie, rtx-shredder --force --plugin
’Tickets=queue,CustomerCare;status,deleted’). However, nothing is being
done. I don’t know where the log file for mysql is aside from
/var/log/mysqld.log. But that doesn’t provide any useful information.

I’m wondering if I"m supposed to provide the password for the rt3
database somewhere.

Any help would be appreciated.

Mathew Snyder
Systems Administrator
Network+
ServerVault TechOps

RT/Shredder versions?On 6/23/06, Mathew Snyder msnyder@servervault.com wrote:

I’m trying to test out the removal of deleted tickets using the
rtx-shredder CLI method. I’ve been entering it nearly verbatim from the
RTx::Shredder page on CPAN (ie, rtx-shredder --force --plugin
’Tickets=queue,CustomerCare;status,deleted’). However, nothing is being
done. I don’t know where the log file for mysql is aside from
/var/log/mysqld.log. But that doesn’t provide any useful information.

I’m wondering if I"m supposed to provide the password for the rt3
database somewhere.

Any help would be appreciated.


Mathew Snyder
Systems Administrator
Network+
ServerVault TechOps


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

We’re hiring! Come hack Perl for Best Practical: http://bestpractical.com/about/jobs.html

Best regards, Ruslan.

Hi,

We are trying to migrate rt2 to rt3 using mysql. The size of the
database is 100 Mb with 3500 tickets. It took 45 min to migrate to rt3
(mysql 5). Anybody has similar experience of the time it took.
Ultimately we would like to migrate the main database of size 6 GB. At
this ratio it might take more than 24 hours to migrate.

We have 4GB memory in the import server. Any clues to speed up the
process! Do I have to modify the database parameters before migrate!

My-huge.conf:
key_buffer = 384M
max_allowed_packet = 128M
table_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache = 8
query_cache_size = 32M

Sorry, v04.

Mathew Snyder
Systems Administrator
Network+
ServerVault TechOps

Ruslan Zakirov wrote: