Flopsar Documentation
3.0
3.0
  • Introduction
  • Overview
    • Versioning
    • Licensing
    • Supported Platforms and Requirements
    • Distribution Packages
    • Release Notes
    • Flopsar Lite
  • Administrator Guide
    • Architecture Fundamentals
    • Installation
    • Agent
    • Server
    • Data Archiving
    • Authentication and Authorization
    • Logging
    • Docker
  • User Guide
    • Workstation
    • Agents Profiles
    • Agents Status
    • Data Browsing
    • Online Monitoring
    • Data Inspector
    • Custom Key-Value Metrics
    • Method Execution Stack
  • Developer Guide
    • Agent API
    • Agent Plugins
    • Server Plugins
    • Database API
  • MISCELLANEOUS
    • Troubleshooting
    • Third-party Components
    • Bug Reporting
Powered by GitBook
On this page
  • Manager stops periodically
  • I see DROPPED in the Parameters column in Workstation
  1. MISCELLANEOUS

Troubleshooting

Manager stops periodically

I see the following message in the Manager log file:

[FATAL ][PID] Flopsar cannot run any longer. No license control file found. Shutdown initiated.

Manager creates a license lock file in /tmp directory. If this file is deleted, then Manager stops. It occurs on Red Hat-like distributions usually. In order to prevent the operating system from deleting this file, you can create a file /usr/lib/tmpfiles.d/flopsar.conf with the following contents:

x       /tmp/*.flp

Please, refer to tmpfiles.d(5) man page for details.

I see DROPPED in the Parameters column in Workstation

This means that instrumented JVM drops parameters due to memory pressure. Either, increase memory limits for your application or decrease instrumentation.

Last updated 5 years ago