[Glass] "Transcript enableLoggingToGemLogFileForSession" not working anymore?

Fri Feb 3 10:36:46 PST 2017

On Fri, Feb 3, 2017 at 2:54 PM, Dale Henrichs <
dale.henrichs at gemtalksystems.com> wrote:

> Mariano,
>
> It works for me... output below ... When I look at tyour output, I see
> that you are doing an rpc login:
> topaz> login
> [Info]: libssl-3.3.3-64.so: loaded
> [02/02/2017 13:31:55.942 EST]
>   gci login: currSession 2  rpc gem processId 13381 socket 6
> successful login
>  fileformat is now utf8
> sourcestringclass is now Unicode16
>
> so you probably left the `-l` off of the command line .. in the rpc case
> the logfile is created and then deleted on successful logout ...
>
>
OK, good spot. It was not that, but related. It seems that in the .topaz
ini of the stone I was trying I had the

topaz> set gemnetid !tcp at xxx#netldi:debrisDemo_333_ldi#task!gemnetobject

On another stone in which I DO NOT set above magic line, the same scripts
receives a linked session (it honors -l).

So the problem is that if I define the above line in .topazini then the -l
argument is completly ignored in `startTopaz`. This looks wrong to me. Of
course, if I remove that line from .topazini it does work correctly.

Thoughts?

> Dale
>
> ----my topaz output ----
>
> topaz> login
> [Info]: LNK client/gem GCI levels = 33002/33002
> --- 02/03/2017 09:49:51.862 PST Login
> [Info]: libssl-3.3.3-64.so: loaded
> [Info]: User ID: DataCurator
> [Info]: Repository: gs_333
> [Info]: Session ID: 4
> [Info]: GCI Client Host: <Linked>
> [Info]: Page server PID: -1
> [Info]: libicudata.54.1.so: loaded
> [Info]: libicuuc.54.1.so: loaded
> [Info]: libicui18n.54.1.so: loaded
> [Info]: Gave this process preference for OOM killer: wrote to
> /proc/24074/oom_score_adj value 250
> [02/03/2017 09:49:51.880 PST]
>   gci login: currSession 1  linked session
> successful login
>  fileformat is now utf8
> sourcestringclass is now Unicode16
> topaz 1> run
> Transcript enableLoggingToGemLogFileForSession.
> Transcript show: 'wtf'.
> %
> --transcript--'wtf'
> TranscriptProxy
> Logging out session 1.
> --- 02/03/2017 09:49:51.894 PST Logging out
> Error on or near line 64 :: startTopaz gs_333 -l :: startTopaz gs_333 -l
> foos:bin>
>
>
> On 2/2/17 10:32 AM, Mariano Martinez Peck wrote:
>
>
>
> On Thu, Feb 2, 2017 at 1:25 PM, Dale Henrichs via Glass <
> glass at lists.gemtalksystems.com> wrote:
>
>> Mariano,
>>
>> When you run topaz the log file is written to stdout. In order to get a
>> "log file" for a topaz session, you either capture stdout/stderr via output
>> redirection or you can use the topaz `output` to route stdout/stderr to
>> another file ... note that you have to supply the full path when using the
>> `output` command.
>>
>> I would recommend using output redirection when you want to create a log
>> for topaz, because output redirection picks up the startup banner which
>> includes a lot of useful information about the session...
>>
>
> OK, I understand that. But then, why below script:
>
>
> #!/bin/bash
>
> $GS_HOME/bin/startTopaz $1 -l <<EOF
>
> login
> run
> Transcript enableLoggingToGemLogFileForSession.
> Transcript show: 'wtf'.
> %
>
> commit
> logout
> exit
>
> EOF
>
>
>
> Does not print 'wtf' in stdout ?  See the output:
>
>
>
> topaz> login
> [Info]: libssl-3.3.3-64.so: loaded
> [02/02/2017 13:31:55.942 EST]
>   gci login: currSession 2  rpc gem processId 13381 socket 6
> successful login
>  fileformat is now utf8
> sourcestringclass is now Unicode16
> topaz 2> run
>
> Transcript enableLoggingToGemLogFileForSession.
> Transcript show: 'wtf'.
>
>
> %
> TranscriptProxy
> topaz 2>
> topaz 2> commit
> Successful commit
> topaz 2> logout
> topaz> exit
> ...finished :: startTopaz debrisDemo_333 -l
> [quuve at quuveserver1 upgrade]$
>
>
>
>
>
>> Dale
>>
>> On 2/2/17 5:49 AM, Mariano Martinez Peck via Glass wrote:
>>
>> Hi Dale,
>>
>> Remember some time ago we added #enableLoggingToGemLogFileForSession and
>> related methods?
>>
>> I am trying this simple script on a 3.3.3 stone:
>>
>> #!/bin/bash
>>
>> $GS_HOME/bin/startTopaz $1 -l <<EOF
>>
>> login
>> run
>> Transcript enableLoggingToGemLogFileForSession.
>> Transcript show: 'wtf'.
>> %
>>
>> commit
>> logout
>> exit
>>
>> EOF
>>
>>
>> And then on my stone logs directory:
>>
>> [xx at xx logs]$ grep "wtf" *.log
>> [xx at xx logs]$
>>
>>
>> The string does gets written in the ObjectLog. But I want to gem file!
>>
>> Thanks in advance,
>>
>>
>>
>> --
>> Mariano
>> http://marianopeck.wordpress.com
>>
>>
>> _______________________________________________
>> Glass mailing listGlass at lists.gemtalksystems.comhttp://lists.gemtalksystems.com/mailman/listinfo/glass
>>
>> _______________________________________________ Glass mailing list
>> Glass at lists.gemtalksystems.com http://lists.gemtalksystems.co
>> m/mailman/listinfo/glass
>
> --
> Mariano http://marianopeck.wordpress.com
>
>

-- 
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20170203/c39d50d3/attachment.html>