- **status**: accepted --> invalid
- **assigned_to**: Canh Truong -->  nobody 
- **Blocker**:  --> False
- **Milestone**: 5.17.08 --> future
- **Comment**:

Discuss with Lennart and get the point: "
The logMaxLogrecsize can be found in the log service configuration object but 
the saLogStreamMaxLogFileSize is configured per stream. This means that the 
values has to be verified against each other for each (and every) stream. This 
is not possible during start of the log service so logMaxLogrecsize is only 
checked for max and min allowed value at his time. This means also that there 
may exist pre-configured streams that has a value in saLogStreamMaxLogFileSize 
that is smaller than logMaxLogrecsize. When changing saLogStreamMaxLogFileSize 
in runtime a verification towards
logMaxLogrecsize is done but this is the only place where such a check is done 
and also the only place where it is in practice possible to do so. To always 
allow the log service to write a last log record to the open log file also if 
the file size will pass the saLogStreamMaxLogFileSize has always been the way 
of solving the problem with possibly dropped log records."




---

** [tickets:#1438] log: log file size is bigger than one defined by 
saLogStreamMaxLogFileSize**

**Status:** invalid
**Milestone:** future
**Created:** Mon Aug 10, 2015 06:59 AM UTC by Vu Minh Nguyen
**Last Updated:** Mon Apr 10, 2017 01:40 PM UTC
**Owner:** nobody


The log file size is bigger than MAX_FILE_SIZE defined by 
saLogStreamMaxLogFileSize attribute value.

> me@:~/opensaf/opensaf-staging/tools/cluster_sim_uml/repl-opensaf/saflog$ ll
> -rw-r--r-- 1 osboxes osboxes   144 Jul 23 09:36 saLogSystem.cfg
> -rw-r----- 1 osboxes osboxes  **2048** Jul 23 09:25 
> saLogSystem_20150723_092436.log
> 
> me@:~/opensaf/opensaf-staging/tools/cluster_sim_uml/repl-opensaf/saflog$ cat 
> saLogSystem.cfg
> LOG_SVC_VERSION: A.2.1
> FORMAT:@Cr @Ch:@Cn:@Cs @Cm/@Cd/@CY @Sv @Sl @Cb255
> MAX_FILE_SIZE: **1025**
> FIXED_LOG_REC_SIZE: 1024
> LOG_FULL_ACTION: ROTATE 4

The expectation is that log server should close the current log file and create 
new one 
if the log file size is going to be greater than the maximum value after 
writing the log record to the file.

This defect is reproducible.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to