pterodactyl/documentation
1
0
Fork 0
mirror of https://github.com/pterodactyl/documentation.git synced 2025-12-11 14:00:27 -06:00
Code Issues Packages Projects Releases Wiki Activity

Add grep for only the errors

Browse Source
This commit is contained in:
Dane Everitt 2018-07-28 14:18:25 -07:00
parent d2aca4aa56
commit 1ebaf37e13
No known key found for this signature in database
GPG Key ID: EEA66103B3D71F53
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
panel/troubleshooting.md
View File

@ -47,6 +47,14 @@ it does help you get faster support if you're able to provide these logs, and at
Sometimes the errors are pretty strightforward and will tell you exactly what went wrong, such as a `ConnectionException` Sometimes the errors are pretty strightforward and will tell you exactly what went wrong, such as a `ConnectionException`
being thrown when the Panel can't connect to the Daemon. being thrown when the Panel can't connect to the Daemon.
### Utilizing GREP
If you're trying to go through a bunch of errors quickly, you can use the command below which will limit the results returned to only
be the actual error lines, without all of the stack traces.
``` bash
tail -n 1000 ~/Sites/development/code/panel/storage/logs/laravel-2018-07-19.log | grep "\[$(date +%Y)"
```
## Transfer Exceptions / XHR Poll Error ## Transfer Exceptions / XHR Poll Error
If you are seeing errors similar to the examples below, chances are there is some networking related issue, or you If you are seeing errors similar to the examples below, chances are there is some networking related issue, or you
just don't have a required service running. just don't have a required service running.