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

Enabling stack_trace_errors in config_override.php/GUI causes 500 error on site #543

Open
jarred-aos opened this issue Sep 11, 2024 · 0 comments
Labels
Priority:Important Issues & PRs that are important; broken functions; errors; there are workarounds Severity: Major Significant impact/severe disruption Type: Bug Something isn't working

Comments

@jarred-aos
Copy link

Issue

I am trying to enable stack trace to diagnose another error. On enabling of the function either in the GUI or directly from the config_override.php file, the website stops working with a 500 error.

The following error appears in the logs/prod/prod.log file.

php.CRITICAL: Uncaught Error: Too few arguments to function StackTraceErrorHandler(), 4 passed and exactly 5 expected {"exception":"[object] (ArgumentCountError(code: 0): Too few arguments to function StackTraceErrorHandler(), 4 passed and exactly 5 expected at /var/www/suitecrm/public/legacy/include/utils.php:3929)"} []

Possible Fix

No response

Steps to Reproduce the Issue

1. Fresh install of v8.6.2
2. Enable stack_trace_errors either in GUI or directly in config_overrides.php
3. Navigate to CRM URL to see 500 error
4. See the error logged in log/prod/prod.log

Context

This is a fresh install and enabling the stack trace makes the site unusable.

I am currently trying to debug what I believe is related to #537 but I am unable to generate the stack trace for that issue because the stack trace handler is causing its own issues.

Version

8.6.2

What browser are you currently using?

Firefox

Browser Version

Firefox Version 130.0

Environment Information

MariaDB, PHP 8.2.23

Operating System and Version

Ubuntu 20.04.6 LTS

@jarred-aos jarred-aos added the Type: Bug Something isn't working label Sep 11, 2024
@johnM2401 johnM2401 added Priority:Important Issues & PRs that are important; broken functions; errors; there are workarounds Severity: Major Significant impact/severe disruption labels Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:Important Issues & PRs that are important; broken functions; errors; there are workarounds Severity: Major Significant impact/severe disruption Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants