-
Notifications
You must be signed in to change notification settings - Fork 73
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: add pb runner troubleshooting
- Loading branch information
1 parent
77006d9
commit 16b81a9
Showing
1 changed file
with
27 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Troubleshooting | ||
|
||
## Where are pegboard-manager logs? | ||
|
||
```bash | ||
cat /var/lib/rivet-client/logs | ||
``` | ||
|
||
## Where are rivet-isolate-v8-runner logs? | ||
|
||
```bash | ||
cat /var/lib/rivet-client/runner/logs | ||
``` | ||
|
||
## Why don't my runner logs exist? | ||
|
||
If there are no logs at `/var/lib/rivet-client/runner/logs`, the runner binary likely failed to spawn. | ||
|
||
Common causes: | ||
|
||
- The path to the binary is incorrect | ||
- Error loading libraries | ||
- The binary is not set as executable | ||
- The binary is for the wrong architecture | ||
|
||
Trying to manually find and run the binary usually resolves these issues. | ||
|