Trouble in using the RT command line tools

RT Users
1

Tried to use the rt2/bin/rt to access my tickets.

and the result is:
frank@discovery:/opt/rt2/bin > rt
Can’t do setuid

has anybody a idea why i get this error?

tks
FRANK

2

Tried to use the rt2/bin/rt to access my tickets.

and the result is:
frank@discovery:/opt/rt2/bin > rt
Can’t do setuid

I think you have to run it as root so that you’re allowed to use the
setuid command. Otherwise, your box may be configured not to run
setuid/setgid scripts.

Those are my two leading guesses. =]

–j
Jim Meyer, Geek At Large purp@wildbrain.com

3

This is in the FAQ. your copy of perl isn’t built with setuid/segid support.

-jesseOn Tue, Jan 22, 2002 at 11:50:07AM -0800, Jim Meyer wrote:

On Mon, 2002-01-21 at 08:04, Frank Rutzen wrote:

Tried to use the rt2/bin/rt to access my tickets.

and the result is:
frank@discovery:/opt/rt2/bin > rt
Can’t do setuid

I think you have to run it as root so that you’re allowed to use the
setuid command. Otherwise, your box may be configured not to run
setuid/setgid scripts.

Those are my two leading guesses. =]

–j

Jim Meyer, Geek At Large purp@wildbrain.com

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

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.

4

Tks for helping me.
Sorry for ignoring the FAQ.

I modified the suidperl as in the FAQ.
Now it’s going one step further and i get the Error:
“No RT user found. Please consult your RT administrator.”

For testing i setup a user with the same name in the linux box and on my
RT system and get the mentioned error.

Do i need to allow a database connections for this linux user to the RT
database?

If somebody can give me a hint.

TKS
FRANK

Jesse Vincent wrote:

5

I modified the suidperl as in the FAQ.
Now it’s going one step further and i get the Error:
“No RT user found. Please consult your RT administrator.”

For testing i setup a user with the same name in the linux box and on my
RT system and get the mentioned error.

Make sure that the User’s ‘Unix Login’ is also set in their
User’s Configuration.

Do i need to allow a database connections for this linux user to the RT
database?

That ‘depends’. If a given unix user can a) execute ‘rt’, and b)
config.pm is being read correctly (different error message if it isn’t),
then the MySQL database is seeing a connection from the username and
password defined in config.pm. The rough answer is ‘no, only the rt_user
needs to access SQL, all other users effectively are the rt_user when
connecting to the databases’.

The next obvious thing to do is to verify that you are allowing that user
to connect from any host that has access to your RT installation… which
means the webserver you run RT on, and any hosts where ‘rt’ can be
executed on. ( For myself, thats over a hundred hosts, so I have a
somewhat ‘loose’ SQL access list to my annoyance. )

However, you should get a rather obvious error message from the perl DB
libraries if the above paragraph is the case.

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

Bruce Campbell writes:> On Mon, 28 Jan 2002, Frank Rutzen wrote:

“No RT user found. Please consult your RT administrator.”

Make sure that the User’s ‘Unix Login’ is also set in their
User’s Configuration.

I’ve followed along this far, but RT doesn’t seem to do anything:
(The web interface is working fine)

$ rt --status=new
$

“rt --help” does what one would expect.
What next?

Thanks,
Andy

7

Bruce Campbell writes:

“No RT user found. Please consult your RT administrator.”

Make sure that the User’s ‘Unix Login’ is also set in their
User’s Configuration.

I’ve followed along this far, but RT doesn’t seem to do anything:
(The web interface is working fine)

$ rt --status=new
$

“rt --help” does what one would expect.
What next?

Be careful with that one. I was working with the CLI earlier today, and found
that to be able to show stuff, i needed to add --id=1-

So I did your command, with the added.

rob@judgehart:~$ rt --status=open --id=1-
That is already the current value
Status changed from resolved to open by rob
That is already the current value
That is already the current value
Status changed from resolved to open by rob
Status changed from resolved to open by rob
That is already the current value
That is already the current value
That is already the current value
That is already the current value
Status changed from stalled to open by rob
Status changed from resolved to open by rob
That is already the current value
That is already the current value
Status changed from resolved to open by rob
That is already the current value
That is already the current value
Status changed from resolved to open by rob
That is already the current value
Status changed from resolved to open by rob
That is already the current value
That is already the current value

Doh!

Rob (heading off to the web interface to fix things. :wink:

8

Bruce Campbell writes:

“No RT user found. Please consult your RT administrator.”

Make sure that the User’s ‘Unix Login’ is also set in their
User’s Configuration.

I’ve followed along this far, but RT doesn’t seem to do anything:
(The web interface is working fine)

$ rt --status=new
$

So, what are you trying to accomplish?

rob

9

Rob Walker writes:

$ rt --status=new

So, what are you trying to accomplish?

Apparently, what I wanted to do was this:

$ rt --limit-status=new --summary

Perhaps we should add a few (working!) examples to the docs.

Thanks,
Andy

10

Quoting Andreas Meyer ahm@ixtelecom.com [13 Feb-02 16:52]:

Bruce Campbell writes:

“No RT user found. Please consult your RT administrator.”

Make sure that the User’s ‘Unix Login’ is also set in their
User’s Configuration.

I’ve followed along this far, but RT doesn’t seem to do anything:
(The web interface is working fine)

$ rt --status=new
$

I think you need to specify some more limits. Also, be aware
that by default, rt assumes you are editing, not displaying; I
made that error a few weeks ago, and issued a --queue=$myqueue,
which began changing the queue to all of our tickets, starting
with 1, to $myqueue. Luckily, the low numbered tickets were test
tickets, and had been long closed, so it had no real
consequences, but still…

Is there any way that the default behavior of rt can be changed?
It seems silly to me to have the default be to make (potentially
difficult to fix) changes, considering that many people simply
run an unknown command with no options when they don’t know what
it does.

Change line 99 to be “$edit = 0;” and we’re good to go.

(darren)

Shame is an improper emotion invented by pietists
to oppress the human race.