На НСР есть утилита C:\Program Files\NCR APTRA\Advance NDC\....\DebugLog\DebugLog.exe (иногда путь другой, но не суть важно). Прога выдает логи DEBUG.log, SECURITY.log, MESSAGEIN.log, MESSAGEOUT.log, OOXFS.log, STATEDATA.log .
Интересует снятие лога по работе с чиповой картой - STATEDATA, но этот лог почему то пустой. Может его где включить нужно дополнительно?
Настройки DebugLog
Модератор: central
-
kentaur
- Друг Банкоматчика
- Сообщения: 424
- Зарегистрирован: 27 окт 2010, 01:57
- Авто: Колымага
- Откуда: грецкий орех
- Благодарил (а): 59 раз
- Поблагодарили: 50 раз
Настройки DebugLog
Вы должны настроить debuglog.ini/silentdebug.ini войти также STATEDATA:
PS: Есть по крайней мере 3 версии debuglog. Например, мы имеем в Personas сервис с именем "NCR DEBUG LOG", и в SelfServ "NCRSilentDebug"
см. также это:
Код: Выделить всё
[LOGINFO]
;Max log file size in kilo bytes
MAXFILESIZE=10000
;Trace streams to be logged
TRACE=DEBUG,MESSAGEOUT,MESSAGEIN,STATEDATA
;Merged Logging Options
MERGEDTRACE=0
;Create a new log file per day, or per month
LOGBYDAY=1PS: Есть по крайней мере 3 версии debuglog. Например, мы имеем в Personas сервис с именем "NCR DEBUG LOG", и в SelfServ "NCRSilentDebug"
см. также это:
Спойлер
Configuring Silent Debug 5
The configuration settings for the Silent Debug can be edited in the
SilentDebug.ini file which is stored in the following location:
C:\Program Files\NCR APTRA\Advance NDC\Config
If the configuration parameters are not within the permitted ranges,
or the SilentDebug.ini file cannot be validated, Silent Debug will not
start logging.
MAXFILESIZE
Defines the maximum permitted size of the log files in kilobytes (KB). The file is
overwritten from the beginning when the file size exceeds the specified value
The minimum setting is 1. If MAXFILESIZE is set to zero, Silent Debug will not start. By
default, MAXFILESIZE is set to 10 MB
A counter keeps track of the number of times the file is overwritten. The counter starts at
zero and increments by one each time the file starts to overwrite the log trace data. In
this way, old trace data will gradually be overwritten with new trace data.
An <END> marker is placed at the end of the last input of new trace data to the file.
If the counter indicates a high incidence of overwriting in a short space of time, increase
the value of MAXFILESIZE.
Sufficient disk space must be available for logging and for other purposes, such as EJ
backup files or PD investigations.
TRACE
Gets the log names for each trace stream that is to be logged. The default log names are
listed in Table 11-1 “Default Trace Stream Types” on page 11-5.
Log names are separated by a comma.
You can also add names representing additional trace streams. For further information
see “Advance NDC Trace Information” on page 11-5.
MERGEDTRACE
Defines whether trace information for each log name defined in the TRACE parameter is
captured in individual files, in a merged file, or both.
Valid values are as follows:
l 0 - an individual file is created for each log name
l 1 - an individual file is created for each log name and an additional file is created that
holds merged trace information for all of the log names.
l 2 - one file is created that holds merged trace information for all of the log names. This
is the default.
The merged trace file name will take the form MergedTrace.log or
MergedTrace_<dd>.log if daily files are specified.
LOGBYDAY
See Table Note 6
Configures when new log files are created.
Valid values are as follows:
l 0 - the same log files are used until they reach the value specified by the MAXFILESIZE
parameter, after which the log files are overwritten
l 1 - a new log file is created for each specified trace as specified by the MERGEDTRACE
parameter on every day of the month that Silent Debug is running. This is the default
If configured to use daily log files, logging to the current files ends at 12 midnight.
Logging is then started to a new daily file, which is created in one of the following
ways:
l If no files exist for the date, new log files are created as defined in the
configuration
l If files exist for the date, the existing log files are overwritten.
Daily log files contain the trace data type and day of the month in their file name.
For example, if a trace log is created for the MESSAGEIN trace on the second day of
the month, the name of the log file is MESSAGEIN_02.log.
The configuration settings for the Silent Debug can be edited in the
SilentDebug.ini file which is stored in the following location:
C:\Program Files\NCR APTRA\Advance NDC\Config
If the configuration parameters are not within the permitted ranges,
or the SilentDebug.ini file cannot be validated, Silent Debug will not
start logging.
MAXFILESIZE
Defines the maximum permitted size of the log files in kilobytes (KB). The file is
overwritten from the beginning when the file size exceeds the specified value
The minimum setting is 1. If MAXFILESIZE is set to zero, Silent Debug will not start. By
default, MAXFILESIZE is set to 10 MB
A counter keeps track of the number of times the file is overwritten. The counter starts at
zero and increments by one each time the file starts to overwrite the log trace data. In
this way, old trace data will gradually be overwritten with new trace data.
An <END> marker is placed at the end of the last input of new trace data to the file.
If the counter indicates a high incidence of overwriting in a short space of time, increase
the value of MAXFILESIZE.
Sufficient disk space must be available for logging and for other purposes, such as EJ
backup files or PD investigations.
TRACE
Gets the log names for each trace stream that is to be logged. The default log names are
listed in Table 11-1 “Default Trace Stream Types” on page 11-5.
Log names are separated by a comma.
You can also add names representing additional trace streams. For further information
see “Advance NDC Trace Information” on page 11-5.
MERGEDTRACE
Defines whether trace information for each log name defined in the TRACE parameter is
captured in individual files, in a merged file, or both.
Valid values are as follows:
l 0 - an individual file is created for each log name
l 1 - an individual file is created for each log name and an additional file is created that
holds merged trace information for all of the log names.
l 2 - one file is created that holds merged trace information for all of the log names. This
is the default.
The merged trace file name will take the form MergedTrace.log or
MergedTrace_<dd>.log if daily files are specified.
LOGBYDAY
See Table Note 6
Configures when new log files are created.
Valid values are as follows:
l 0 - the same log files are used until they reach the value specified by the MAXFILESIZE
parameter, after which the log files are overwritten
l 1 - a new log file is created for each specified trace as specified by the MERGEDTRACE
parameter on every day of the month that Silent Debug is running. This is the default
If configured to use daily log files, logging to the current files ends at 12 midnight.
Logging is then started to a new daily file, which is created in one of the following
ways:
l If no files exist for the date, new log files are created as defined in the
configuration
l If files exist for the date, the existing log files are overwritten.
Daily log files contain the trace data type and day of the month in their file name.
For example, if a trace log is created for the MESSAGEIN trace on the second day of
the month, the name of the log file is MESSAGEIN_02.log.
У вас нет необходимых прав для просмотра вложений в этом сообщении.
Извините за мой "слэнг" - я пишу через переводчик с английский.