Skip to content

#47 Add Troubleshooting section on documentation #50

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.

Sign up for GitHub

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

Merged
njoubert-cleverage merged 1 commit into from
Feb 24, 2025
Merged

#47 Add Troubleshooting section on documentation #50

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,12 +91,12 @@ See more details about ***messenger:consume*** command in consume message sectio
## Consume Messages
Symfony messenger is used in order to run process via UI or schedule process

*To consume process launched via UI make sure the following command is running*
* To consume process launched via UI make sure the following command is running*
```bash
bin/console messenger:consume execute_process
```

*To consume scheduled process make sure the following command is running*
* To consume scheduled process make sure the following command is running*
```bash
bin/console messenger:consume scheduler_cron
```
Expand Down Expand Up @@ -144,6 +144,17 @@ killasgroup=true
stopasgroup=true
```

## Troubleshooting

### PHP Fatal error: Allowed memory size of xxx bytes exhausted

When `store_in_database` option is set, with lower value of `database_level` option, the process may generate many LogRecord.
On debug environment, profiling too much queries cause memory exhaustion. So, you can :
- Set `doctrine.dbal.profiling_collect_backtrace: false`
- Increase `memory_limit` in php.ini
- Set `clever_age_ui_process.logs.store_in_database: false` or improve value of `clever_age_ui_process.logs.database_level`
- Use `--no-debug` flag for `cleverage:process:execute`

## Reference

_TODO_