Still not working the log correctly?

Use this Forum to post your “How to …” questions about your use of aXes. This is not a technical support forum. Both the aXes Support Team at LANSA and other aXes customers may answer your questions. LANSA cannot guarantee the accuracy of any information posted by customers.

Moderator: jeanmichel

Post Reply
jaimosky
Posts: 15
Joined: 30 May 2017, 16:48

Still not working the log correctly?

Post by jaimosky » 23 Nov 2018, 23:58

Hi,

Ist still not working correctly the log? I have in /configs/axesTS and /configs/axesW3 following directives:

Trace=1
TraceLevel=Error

But I get just (notice) messages:

Code: Select all

.aXes5250trc.txt
23/Nov/2018 14:47:19 (notice)   starting aXes5250            
23/Nov/2018 14:47:19 (notice)   getCodec mtSetup_escape      
23/Nov/2018 14:47:19 (notice)   AXESVT: start terminal loop  
23/Nov/2018 14:50:03 (notice)   TS_VTSTATS                   
23/Nov/2018 14:52:28 (notice)   TS_CLEANUP                          

.aXesTStrc.txt  
23/Nov/2018 14:47:19 (notice)   starting aXesTS pid 9229   

.aXesW3trc.txt  
....
23/Nov/2018 14:50:03 (notice)   Get client data 0 of 1                                     
23/Nov/2018 14:50:03 (notice)   Handle request                                             
23/Nov/2018 14:50:03 (notice)   State FR_SEND                                              
23/Nov/2018 14:50:03 (notice)   Handle send: delete fd                                     
23/Nov/2018 14:50:03 (notice)   Handle send: add read fd                                   
23/Nov/2018 14:50:03 (notice)   =======================================                    
23/Nov/2018 14:50:03 (notice)   Select 120000                                              
23/Nov/2018 14:50:03 (notice)   Number ready 1                                             
23/Nov/2018 14:50:03 (notice)   Get client data 0 of 1                                     
23/Nov/2018 14:50:03 (notice)   Handle request                                             
23/Nov/2018 14:50:03 (notice)   State FR_RECV                                              
23/Nov/2018 14:50:03 (notice)   Illegal fd or (exitstatus set or redirect) and no header   
23/Nov/2018 14:50:03 (notice)   Notify W3 and end connection                               
23/Nov/2018 14:50:03 (notice)   Handle close: delete fd                                    
23/Nov/2018 14:50:03 (notice)   =======================================                    
23/Nov/2018 14:50:03 (notice)   Select 3600000                                             
23/Nov/2018 14:52:16 (notice)   tmr_cleanup start 4 allocated, 3 active, 1 free            
23/Nov/2018 14:52:16 (notice)   tmr_cleanup end 3 allocated, 3 active, 0 free




Jaime

User avatar
jeanmichel
Posts: 87
Joined: 23 May 2014, 11:37
Location: Sydney

Re: Still not working the log correctly?

Post by jeanmichel » 24 Nov 2018, 07:15

Hi Jamie,

This is a “how to” forum.

If you believe you have encountered an issue please contact LANSA support.
Regards,

Jean-Michel Rapin

LANSA Pty Ltd
email: JeanMichel.Rapin@lansa.com.au
Address: 122 Arthur Street, North Sydney, NSW 2060, Australia
Tel: +61 289 070 262 http://www.lansa.com | http://blog.lansa.com |

jaimosky
Posts: 15
Joined: 30 May 2017, 16:48

Re: Still not working the log correctly?

Post by jaimosky » 28 Nov 2018, 20:25

OK, I did already and I was wondering if it was already corrected, but I haven´t seen it in the changelog ticket that you have included. Number 159621.

Thanks for the support.

Jaime

User avatar
jeanmichel
Posts: 87
Joined: 23 May 2014, 11:37
Location: Sydney

Re: Still not working the log correctly?

Post by jeanmichel » 30 Nov 2018, 10:58

Hi Jamie,

Yes you are right, I found your bug report 159621.
Unfortunately it is still in the queue.
The issue is not with the trace level, it is related to some trace messages with the wrong trace level.

The current trace levels are the following:
LOG_DEBUG=0,
LOG_INFO=1,
LOG_WARN=2,
LOG_ERR=4, /* below this may be turned off */
LOG_CONFIG=5, /* startup error */
LOG_NOTICE=6, /* completion notice (goes to sysopr) */
LOG_CRIT=7, /* critical error (goes to sysopr) */
LOG_LAST=7

We will fix the messages with the wrong trace level (notice instead of info) in the next version of aXes.
Regards,

Jean-Michel Rapin

LANSA Pty Ltd
email: JeanMichel.Rapin@lansa.com.au
Address: 122 Arthur Street, North Sydney, NSW 2060, Australia
Tel: +61 289 070 262 http://www.lansa.com | http://blog.lansa.com |

Post Reply