Skip to contentSkip to conversation

LTTng 2.1: create session errors

DISCUSSION David Goulet 2 participants 2 messages Dec 20, 2012 – Dec 21, 2012 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Just in time before I push for 2.1 sable.

Bernd Hufmann:

Quoted 13 lines

Hello

I'm currently using lttng-tools 2.1.0-RC9. I see some errors when using "lttng create " with streaming options:

1) lttng create mysession -C net://192:1.1.1: -D net://192:1.1.1.1

The command output shows:
Session mysession created.
Traces will be written in (null)
Control URL net://192.1.1.1.1 set for session mysession Data URL net://192.1.1.1.1 set for session mysession

Quoted 4 lines

The line "Traces will be written in (null)" should show the correct location similar when using the -U option. Also, when typing "lttng list mysession" afterwards the trace path is not displayed correctly. (mysession (net://192.1.1.1:5342/ [data: 5343]) [inactive]).

Fixed.

Quoted 10 lines

2) lttng create mysession -C net://192:1.1.1:5342 -D net://192.1.1.1:5343

This command output shows:
Session mysession created.
Traces will be written in (null)
Error: Control URL uses the net:// protocol and the data URL is
different. Not allowed.
Error: Invalid parameter

Quoted 4 lines

The command fails with an error. However, the session seems to be created, but no consumer is defined. First of all, it should be possible to define the port with the option -C and -D. Secondly, if an error occurs the session shouldn't be created.

Both URL are not equal since the port is different here. So, you CAN'T use net:// with create session unless both URLs are identical. Use tcp:// here. The net:// protocol stands for the default transport layer for both port.

The session stays created here and I can't change that for now. You can simply use "lttng enable-consumer" after to set the correct thing. This could however be changed for next version as a bug fix.

Quoted 6 lines

3) lttng create mysession -C net://192.1.1.1

This command doesn't fail. I expected it to fail since the command help states that -D <data URL> must be used too. BTW, "lttng create mysession -D net://192.1.1.1" fails.

Fixed.

Quoted 4 lines

4) lttng create mysession -C net://192:1.1.1 -D net://192.1.1.2 This command fails, because the IP address is not the same. Is this intended?

It is because URLs are not identical. Use tcp:// here instread.

Quoted 4 lines

5) In "lttng create -h" and "enable-consumer -h" show "tcp[4|6]" as possible protocols, but "tcp4" doesn't work. I have to use "tcp". The help should be updated for that.

Fixed

Quoted 4 lines

6) Why isn't it possible to use "tcp[6]" together with option -U? Instead "net[6]" has to be used, which defaults to TCP as network transport.

-U is used to specify BOTH url for ports so for now we only allow net:// that do this job.

Future work will fine grained more the URI parsing but for now, use net[6]:// only with -U.

It will be upstream in a jiffy.

Thanks!
David

Quoted 8 lines

Could someone please look into this?

Best Regards
Bernd

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw

Hi David

I just restarted working on the LTTng 2.1 integration in Eclipse this week. So, I only noticed these things yesterday.

Thanks a lot for the fixes and the explanations.

BR,
Bernd

Quoted 82 lines · David Goulet

Just in time before I push for 2.1 sable.

Bernd Hufmann:

Quoted 13 lines

Hello

I'm currently using lttng-tools 2.1.0-RC9. I see some errors when using "lttng create " with streaming options:

1) lttng create mysession -C net://192:1.1.1: -D net://192:1.1.1.1

The command output shows:
Session mysession created.
Traces will be written in (null)
Control URL net://192.1.1.1.1 set for session mysession Data URL net://192.1.1.1.1 set for session mysession

Quoted 4 lines

The line "Traces will be written in (null)" should show the correct location similar when using the -U option. Also, when typing "lttng list mysession" afterwards the trace path is not displayed correctly. (mysession (net://192.1.1.1:5342/ [data: 5343]) [inactive]).

Fixed.

Quoted 9 lines

2) lttng create mysession -C net://192:1.1.1:5342 -D net://192.1.1.1:5343

This command output shows:
Session mysession created.
Traces will be written in (null)
Error: Control URL uses the net:// protocol and the data URL is
different. Not allowed.
Error: Invalid parameter

Quoted 4 lines

The command fails with an error. However, the session seems to be created, but no consumer is defined. First of all, it should be possible to define the port with the option -C and -D. Secondly, if an error occurs the session shouldn't be created.

Both URL are not equal since the port is different here. So, you CAN'T use net:// with create session unless both URLs are identical. Use tcp:// here. The net:// protocol stands for the default transport layer for both port.

The session stays created here and I can't change that for now. You can simply use "lttng enable-consumer" after to set the correct thing. This could however be changed for next version as a bug fix.

Quoted 5 lines

3) lttng create mysession -C net://192.1.1.1

This command doesn't fail. I expected it to fail since the command help states that -D<data URL> must be used too. BTW, "lttng create mysession -D net://192.1.1.1" fails.

Fixed.

Quoted 3 lines

4) lttng create mysession -C net://192:1.1.1 -D net://192.1.1.2 This command fails, because the IP address is not the same. Is this intended?

It is because URLs are not identical. Use tcp:// here instread.

Quoted 3 lines

5) In "lttng create -h" and "enable-consumer -h" show "tcp[4|6]" as possible protocols, but "tcp4" doesn't work. I have to use "tcp". The help should be updated for that.

Fixed

Quoted 3 lines

6) Why isn't it possible to use "tcp[6]" together with option -U? Instead "net[6]" has to be used, which defaults to TCP as network transport.

-U is used to specify BOTH url for ports so for now we only allow net:// that do this job.

Future work will fine grained more the URI parsing but for now, use net[6]:// only with -U.

It will be upstream in a jiffy.

Thanks!
David

Quoted 7 lines

Could someone please look into this?

Best Regards
Bernd

Signature · 1 line
This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer