Monitoring and TroubleshootingPermanent link for this heading

Event LogPermanent link for this heading

At the startup of the Fabasoft Folio COO Service an event log entry is generated, which shows the status of the multicast server.

In the following example the “UDP multicast transport” is enabled, the used multicast address is 224.0.0.11 and the multicast port is 1190.

Example

ReportEvent: FSCRMP-00006: RMP::MulticastServer: startup
  fscrmp.channel: RMP::MulticastServer
  fscrmp.address: 224.0.0.11
  fscrmp.port: 1190
  fscrmp.service: COO Service 1 (COOSVC1)
  fscrmp.sequence: 7053609
  fscrmp.domain: 1.506 (mg-testtux1)
  fscrmp.serviceaccount: fscsrv

In the following example the “event queue transport” is enabled, the used RabbitMQ broker hostname is eventq-development.services.sq.fabasoft.com and the port is 5672.

Example

ReportEvent: FSCRMP-00006: RMP::EventQueueServer: startup
  fscrmp.channel: RMP::EventQueueServer
  fscrmp.address: eventq-development.services.sq.fabasoft.com
  fscrmp.port: 5672
  fscrmp.service: COO Service 1 (COOSVC1)
  fscrmp.sequence: 7053609
  fscrmp.domain: 1.506 (mg-testtux1)
  fscrmp.serviceaccount: fscsrv

If the cache notification is disabled, an entry in the event log is created when starting the Fabasoft Folio COO Service.

Example

ReportEvent: COOSTD-00803: Multicast and event queue based cache invalidation is disabled
  coostd.category: RMP
  coostd.domain: 1.506 (mg-testtux1)
  coostd.service: COO Service 1 (COOSVC1)
  coostd.serviceaccount: fscsrv
  source: Fabasoft Folio Server
  processid: 52390
  processname: COOService_1_506_1
  threadid: 140434003068672
  version: 21.11.0.7

The client (Fabasoft Folio Kernel) writes an entry in the event log after a successful start.

Example

ReportEvent: FSCRMP-00006: RMP::MulticastClient: startup
  fscrmp.channel: RMP::MulticastClient
  fscrmp.address: 224.0.0.11
  fscrmp.port: 1190
  fscrmp.interface: 10.10.67.215

UDP package losses (modification notices and heartbeats) are written as warning in the event log.

Note: A package loss does not lead to a data loss or inconsistency. It is simply impossible to perform optimized cache behavior.

Or

Example

ReportEvent: FSCRMP-00108: RMP::MulticastClient: server lost: heartbeat missing
  fscrmp.channel: RMP::MulticastClient
  fscrmp.address: 224.0.0.11
  fscrmp.port: 1190
  fscrmp.interface: 10.10.67.215

Network Load MonitoringPermanent link for this heading

For analyzing the network traffic, a network sniffing tool like “Wireshark” (http://www.wireshark.org) may be used.

With an appropriate filter all UDP packages of a certain address (e.g. IP address of the server) can be filtered in a certain area.

Example: ip.addr == 192.168.100.83 and udp.port == 1190

This filter restricts to UDP packages with the sender IP address 192.168.100.83 and the destination port 1190.