Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System encountered a critical error while attempting to access log files through the GetLogsListAction handler. #855

Open
jorikfon opened this issue Jan 21, 2025 · 0 comments

Comments

@jorikfon
Copy link
Collaborator

{
body: `## Description
System encountered a critical error while attempting to access log files through the GetLogsListAction handler.

Error Details

Jan 21 06:59:15 daemon.debug php.backend[782]:  shutdownHandler after 3372.23 seconds with error: 2
Jan 21 06:59:15 daemon.debug php.backend[782]:  filemtime(): stat failed for /storage/usbdisk1/mikopbx/log/ModuleCTIClient/monitord/current
Jan 21 06:59:15 daemon.debug php.backend[782]:  /offload/rootfs/usr/www/src/PBXCoreREST/Lib/SysLogs/GetLogsListAction.php
Jan 21 06:59:15 daemon.debug php.backend[782]:  53 on MikoPBX\\PBXCoreREST\\Workers\\WorkerApiCommands-getLogsList

Technical Analysis

  1. The error occurs in GetLogsListAction.php at line 53
  2. Main issue: filemtime() function fails to stat the file
  3. Location: /storage/usbdisk1/mikopbx/log/ModuleCTIClient/monitord/current
  4. Error type: Level 2 (E_WARNING)
  5. Process duration: 3372.23 seconds before shutdown

Possible Causes

  1. File permissions issue on the log directory
  2. Missing or unmounted USB storage
  3. Corrupted file system on USB device
  4. Symbolic link issues in the log path

Steps to Reproduce

  1. Access log analysis through UI
  2. Attempt to retrieve logs from ModuleCTIClient
  3. System attempts to access monitord/current file
  4. Error occurs during file timestamp check

Suggested Investigation Steps

  1. Verify USB disk mount status
  2. Check file permissions on the entire path
  3. Validate symbolic links if any
  4. Review log rotation configuration

Impact

  • Log analysis functionality is impaired
  • System experiences extended processing time (>3000 seconds)
  • Potential memory leaks due to long execution time

Environment

  • Component: PBXCoreREST
  • Module: ModuleCTIClient
  • File: GetLogsListAction.php
  • Worker: WorkerApiCommands-getLogsList
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant