May 23 14:28:34 REG-S1 osaflogd[8850]: NO lgs_imm_init_configStreams:
log_stream_open_file_restore Fail
May 23 14:28:34 REG-S1 osaflogd[8850]: NO lgs_imm_init_configStreams:
log_stream_open_file_restore Fail
May 23 14:28:34 REG-S1 osaflogd[8850]: NO lgs_imm_init_configStreams:
log_stream_open_file_restore Fail
This is not error messages. It only means that log_stream_open_file_restore()
fail to restore log files. This may happen if the file system is not available
(scandir fail) or if more than one found file is empty. If this happen new
files will be created using log_stream_open_fileinit(). If this also fail the
log service will try to create the files when a client request to write a log
record.
The title of this ticket is not correct since these messages does not say that
the log service has failed to recover the streams.
This ticket could be set to "invalid" since it does not indicate any defect in
the log service.
Maybe the messages could be made more informative.
---
** [tickets:#1847] log: lgs_imm_init_configStreams:
log_stream_open_file_restore Fail is observed in syslog.**
**Status:** review
**Milestone:** 5.0.1
**Created:** Tue May 24, 2016 07:32 AM UTC by Madhurika Koppula
**Last Updated:** Fri May 27, 2016 08:46 AM UTC
**Owner:** Vu Minh Nguyen
Setup details: SUSE (32bit-64bit combination) 5 nodes cluster with single PBE
1) Brought up cluster with Active SC, Standby SC, Spare SC and two payloads
PL-4 and PL-5 with headless feature enabled.
2) During startup of Active controller, lgs_imm_init_configStreams:
log_stream_open_file_restore Fail is observed in syslog.
Below is the snippet of active controller syslog:
May 23 14:28:29 REG-S1 osaffmd[8814]: Started
May 23 14:28:29 REG-S1 osafimmd[8824]: Started
May 23 14:28:29 REG-S1 osafimmd[8824]: NO ******* SC_ABSENCE_ALLOWED (Headless
Hydra) is configured: 900 ***********
May 23 14:28:29 REG-S1 osafimmnd[8835]: Started
May 23 14:28:34 REG-S1 osafimmnd[8835]: NO Implementer connected: 1
(safLogService) <2, 2010f>
May 23 14:28:34 REG-S1 osafimmnd[8835]: NO implementer for class
'OpenSafLogConfig' is safLogService => class extent is safe.
May 23 14:28:34 REG-S1 osafimmnd[8835]: NO implementer for class
'SaLogStreamConfig' is safLogService => class extent is safe.
May 23 14:28:34 REG-S1 osaflogd[8850]: NO lgs_imm_init_configStreams:
log_stream_open_file_restore Fail
May 23 14:28:34 REG-S1 osaflogd[8850]: NO lgs_imm_init_configStreams:
log_stream_open_file_restore Fail
May 23 14:28:34 REG-S1 osaflogd[8850]: NO lgs_imm_init_configStreams:
log_stream_open_file_restore Fail
May 23 14:28:34 REG-S1 osafimmnd[8835]: NO Implementer (applier) connected: 2
(@safLogService_appl) <16, 2010f>
May 23 14:28:34 REG-S1 osafntfd[8862]: Started
---
Sent from sourceforge.net because [email protected] 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.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
