Fsck

OK, I sent this to Jesse, but realized I might also be better off (and
Jesse would be better off grin) if I sent this to the list itself.

I had the old “webrt” debian package installed. In its configs, it’d
asked me for “what to call the RT system”, so I called it “ByramRT”,
because that seemed like a nice name. and then later promptly forgot all
about it. When I moved to the 2.0.x tarball, I followed the suggestions
which said “don’t pollute the namespace, use your hostname”. I then
happily imported my data…keyed off ByramRT.

Now I’ve got two names in the system (from the old system, and from the
new system), and it’s torqueing the entire thing as you can well
imagine. Any time someone replies to, say “rt.OURDOMAIN.com #NNN”, they
get a response from “ByramRT #XXX”, thanking them for starting a ticket
up, etc. etc.

Is there any clean way of solving this? Somehow I have the feeling this
is going to be one of those “dump the DB, trash it and start over” but
I’d really prefer NOT to do that.

D

The RT name isn’t stored in the database in RT2. If you change the RT
name in config.pm to rt.OURDOMAIN.com, it should fix the problem.

O- ~ARK

OK, an update. I found the problem… .the problem was that we’d left the
webrt package “installed” (as a fallback) and it was still trying to
route every message we sent to the mailgate into the OLD ‘rt’ database,
because it was finding THAT config.pm FIRST (ugh). :wink:

So, I’ve fixed that, but NOW I get a completely different error. :slight_smile:

----- The following addresses had permanent fatal errors -----

“| /usr/local/rt2/bin/rt-mailgate SysAdmin correspond”
(reason: 2)
(expanded from: sysadmin@rt.byramhealthcare.com)

----- Transcript of session follows -----

Can’t do setuid
554 5.3.0 unknown mailer error 2
Reporting-MTA: dns; web01.byramhealthcare.com
Received-From-MTA: DNS; mail01.byramhealthcare.com
Arrival-Date: Thu, 22 Aug 2002 10:30:22 -0400On Thursday, August 22, 2002, at 10:24 AM, Ayan R. Kayal wrote:

The RT name isn’t stored in the database in RT2. If you change the RT
name in config.pm to rt.OURDOMAIN.com, it should fix the problem.

O- ~ARK

-----Original Message-----
From: rt-users-admin@lists.fsck.com
[mailto:rt-users-admin@lists.fsck.com] On Behalf Of Derek J. Balling
Sent: Thursday, August 22, 2002 10:20 AM
To: Rt-Users (E-mail)
Subject: [rt-users] fsck…

OK, I sent this to Jesse, but realized I might also be better
off (and
Jesse would be better off grin) if I sent this to the list itself.

I had the old “webrt” debian package installed. In its configs, it’d
asked me for “what to call the RT system”, so I called it “ByramRT”,
because that seemed like a nice name. and then later promptly
forgot all
about it. When I moved to the 2.0.x tarball, I followed the
suggestions
which said “don’t pollute the namespace, use your hostname”. I then
happily imported my data…keyed off ByramRT.

Now I’ve got two names in the system (from the old system,
and from the
new system), and it’s torqueing the entire thing as you can well
imagine. Any time someone replies to, say “rt.OURDOMAIN.com
#NNN”, they
get a response from “ByramRT #XXX”, thanking them for
starting a ticket
up, etc. etc.

Is there any clean way of solving this? Somehow I have the
feeling this
is going to be one of those “dump the DB, trash it and start
over” but
I’d really prefer NOT to do that.

D


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-> users

Have you
read the FAQ? The RT FAQ Manager lives at
http://fsck.com/rtfm

OK, an update. I found the problem… .the problem was that we’d left the
webrt package “installed” (as a fallback) and it was still trying to
route every message we sent to the mailgate into the OLD ‘rt’ database,
because it was finding THAT config.pm FIRST (ugh). :wink:

So, I’ve fixed that, but NOW I get a completely different error. :slight_smile:

----- The following addresses had permanent fatal errors -----

“| /usr/local/rt2/bin/rt-mailgate SysAdmin correspond”
(reason: 2)
(expanded from: sysadmin@rt.byramhealthcare.com)

----- Transcript of session follows -----

Can’t do setuid

http://www.fsck.com/rtfm/search.html?LimitContent=setuid&LimitSummary=

/etc/procmailrcs/ is your friend :wink:

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B             Operations/Security
----- Transcript of session follows -----

Can’t do setuid

http://www.fsck.com/rtfm/search.html?LimitContent=setuid&LimitSummary=

Sorry, thats ‘suid’, not ‘setuid’.

http://www.fsck.com/rtfm/factoid.html?id=61 is the actual article.
http://www.fsck.com/rtfm/factoid.html?id=147

/etc/procmailrcs/ is your friend :wink:

http://lists.fsck.com/pipermail/rt-users/2002-February/006506.html

also

http://www.fsck.com/rtfm/article.html?id=213

(about time I put it in there)

Regards,

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B             Operations/Security