Part-DB-server/docs/troubleshooting.md
Copilot 02b1f7aa16
Improve documentation clarity and fix outdated information (#1129)
* Initial plan

* Improve documentation clarity, fix typos, and update outdated information

Co-authored-by: jbtronics <5410681+jbtronics@users.noreply.github.com>

* Replace LCSC with Mouser in cloud providers list per d-buchmann's review

Co-authored-by: jbtronics <5410681+jbtronics@users.noreply.github.com>

* Remove outdated Mouser API issue notice

Removed outdated information about the Mouser API's current issues with datasheets and part specifications.

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: jbtronics <5410681+jbtronics@users.noreply.github.com>
Co-authored-by: Jan Böhmer <mail@jan-boehmer.de>
2025-12-06 22:40:45 +01:00

1.7 KiB

layout title
default Troubleshooting

Troubleshooting

Sometimes things go wrong and Part-DB shows an error message. This page should help you to solve the problem.

Error messages

When a common, easily fixable error occurs (like a non-up-to-date database), Part-DB will show you some short instructions on how to fix the problem. If you have a problem that is not listed here, please open an issue on GitHub.

General procedure

If you encounter an error, try the following steps:

  • Clear the cache of Part-DB with the console command:
php bin/console cache:clear
  • Check if the database needs an update (and perform it when needed) with the console command:
php bin/console doctrine:migrations:migrate

If this does not help, please open an issue on GitHub.

Search for a user and reset the password

You can list all users with the following command: php bin/console partdb:users:list To reset the password of a user you can use the following command: php bin/console partdb:users:set-password [username]

Error logs

Detailed error logs can be found in the var/log directory. When Part-DB is installed directly, the errors are written to the var/log/prod.log file.

When Part-DB is installed with Docker, the errors are written directly to the console output. You can see the logs with the following command, when you are in the folder with the docker-compose.yml file

docker-compose logs -f

Please include the error logs in your issue on GitHub, if you open an issue.

Report Issue

If an error occurs, or you found a bug, please open an issue on GitHub.