Re: [rt-users] RT Log file
/var/log/messages are handled by syslog and LogToSyslog. In production environment you don't want to use LogToFile options. You can reconfigure syslog to redirect RT logs into separate file. Look at option LogToSyslogConf in the RT config. As alternative you can use apache logs instead. Everything that is logged to screen end ups in apache error log, users of api sure will see messages on STDERR. On Sat, Dec 27, 2008 at 3:53 AM, kem cho kemcho12...@yahoo.com wrote: Hi, I have a weird issue... Running RT (version 3.8.1 on suse 11) I am trying to move RT logs to /var/log/rt3/rt.log, but it keeps putting entries in /var/log/messages... Here is part of my RT_SiteConfig.pm -- # Mail loops will generate a critical log message. Set($LogToSyslog, 'debug'); Set($LogToScreen, 'error'); Set($LogToFile , undef); Set($LogDir, '/var/log/rt3'); Set($LogToFileNamed , rt3.log);#log to rt.log -- I have tried commenting out Set($LogToFile , undef, but same results. Any ideas? Thanks ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com -- Best regards, Ruslan. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Database transfer from OTRS to RT
Has anyone ever switched from OTRS to RT before? Is there away to import all my tickets from OTRS to RT? -- View this message in context: http://www.nabble.com/Database-transfer-from-OTRS-to-RT-tp21186292p21186292.html Sent from the Request Tracker - User mailing list archive at Nabble.com. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Database transfer from OTRS to RT
Has anyone ever switched from OTRS to RT before? Is there away to import all my tickets from OTRS to RT? We've definitely worked with clients who have moved from OTRS to RT, though they've all decided to ditch their history and make a fresh start with RT. Do you have in-house developers who might be interested in helping to build out a converter? Best, Jesse pgpYkLovj30Uf.pgp Description: PGP signature ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] DBIx::SearchBuilder::Handle::Pg -- again
Ruslan, Here are the results for this query: =# EXPLAIN ANALYZE SELECT main.* FROM Users main WHERE main.id IN ( SELECT main.id FROM Users main CROSS JOIN ACL ACL_2 JOIN Principals Principals_1 ON ( Principals_1.id = main.id ) JOIN CachedGroupMembers CachedGroupMembers_3 ON ( CachedGroupMembers_3.MemberId = Principals_1.id ) WHERE (Principals_1.Disabled = '0') AND (ACL_2.PrincipalId = CachedGroupMembers_3.GroupId) AND (Principals_1.id != '1') AND (ACL_2.PrincipalType = 'Group') AND (Principals_1.PrincipalType = 'User') AND (ACL_2.RightName = 'OwnTicket') AND ((ACL_2.ObjectType = 'RT::Queue') OR (ACL_2.ObjectType = 'RT::System')) ) ORDER BY main.Name ASC; QUERY PLAN --- Sort (cost=1263.60..1263.60 rows=1 width=1179) (actual time=956.963..957.124 rows=277 loops=1) Sort Key: main.name Sort Method: quicksort Memory: 119kB - Nested Loop (cost=1094.48..1263.59 rows=1 width=1179) (actual time=952.019..955.245 rows=277 loops=1) - HashAggregate (cost=1094.48..1094.93 rows=45 width=12) (actual time=952.005..952.276 rows=277 loops=1) - Nested Loop (cost=2.76..1094.37 rows=45 width=12) (actual time=0.403..907.237 rows=41094 loops=1) - Nested Loop (cost=2.76..1080.42 rows=45 width=8) (actual time=0.363..546.328 rows=41094 loops=1) - Nested Loop (cost=2.76..544.73 rows=1638 width=4) (actual time=0.311..109.119 rows=41782 loops=1) - Bitmap Heap Scan on acl acl_2 (cost=2.76..37.09 rows=43 width=4) (actual time=0.234..0.831 rows=145 loops=1) Recheck Cond: (((rightname)::text = 'OwnTicket'::text) AND ((principaltype)::text = 'Group'::text)) Filter: (((objecttype)::text = 'RT::Queue'::text) OR ((objecttype)::text = 'RT::System'::text)) - Bitmap Index Scan on acl1 (cost=0.00..2.75 rows=49 width=0) (actual time=0.198..0.198 rows=145 loops=1) Index Cond: (((rightname)::text = 'OwnTicket'::text) AND ((principaltype)::text = 'Group'::text)) - Index Scan using cachedgroupmembers3 on cachedgroupmembers cachedgroupmembers_3 (cost=0.00..11.31 rows=40 width=8) (actual time=0.023..0.374 rows=288 loops=145) Index Cond: (cachedgroupmembers_3.groupid = acl_2.principalid) - Index Scan using principals_pkey on principals principals_1 (cost=0.00..0.31 rows=1 width=4) (actual time=0.007..0.008 rows=1 loops=41782) Index Cond: (principals_1.id = cachedgroupmembers_3.memberid) Filter: ((principals_1.id 1) AND (principals_1.disabled = 0::smallint) AND ((principals_1.principaltype)::text = 'User'::text)) - Index Scan using users_pkey on users main (cost=0.00..0.30 rows=1 width=4) (actual time=0.005..0.006 rows=1 loops=41094) Index Cond: (main.id = principals_1.id) - Index Scan using users_pkey on users main (cost=0.00..3.74 rows=1 width=1179) (actual time=0.006..0.007 rows=1 loops=277) Index Cond: (main.id = principals_1.id) Total runtime: 957.753 ms (23 rows) Here are the timing results without EXPLAIN ANALYZE: ... (277 rows) Time: 562.191 ms Happy holidays, Ken On Wed, Dec 24, 2008 at 03:17:58AM +0300, Ruslan Zakirov wrote: I see how it can be improved without slowing more simple queries. Can you test the following query for me? Send plan. SELECT main.* FROM Users main WHERE main.id IN ( SELECT main.id FROM Users main CROSS JOIN ACL ACL_2 JOIN Principals Principals_1 ON ( Principals_1.id = main.id ) JOIN CachedGroupMembers CachedGroupMembers_3 ON ( CachedGroupMembers_3.MemberId = Principals_1.id ) WHERE (Principals_1.Disabled = '0') AND (ACL_2.PrincipalId = CachedGroupMembers_3.GroupId) AND (Principals_1.id != '1') AND (ACL_2.PrincipalType = 'Group') AND (Principals_1.PrincipalType = 'User') AND (ACL_2.RightName = 'OwnTicket') AND ((ACL_2.ObjectType = 'RT::Queue') OR (ACL_2.ObjectType = 'RT::System')) ) ORDER BY main.Name ASC; On Wed, Dec 24, 2008 at 2:00 AM, Kenneth Marshall k...@rice.edu wrote: Ruslan, Here is a sample query that benefits from the change: # EXPLAIN ANALYZE SELECT main.* FROM ( SELECT DISTINCT main.id FROM Users main CROSS JOIN ACL ACL_2 JOIN Principals Principals_1 ON (
Re: [rt-users] Database transfer from OTRS to RT
Jesse Vincent wrote: We've definitely worked with clients who have moved from OTRS to RT, though they've all decided to ditch their history and make a fresh start with RT. Do you have in-house developers who might be interested in helping to build out a converter? Best, Jesse I may just need to do a fresh start. It wouldn't be a big deal, but would be nice to be able to move ticket data. We don't have any in-house developers, Just me and another guy for IT. -- View this message in context: http://www.nabble.com/Database-transfer-from-OTRS-to-RT-tp21186292p21188542.html Sent from the Request Tracker - User mailing list archive at Nabble.com. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
