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

Update path of log #52

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
5 changes: 5 additions & 0 deletions docs/getting-started/faqs.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,11 @@ title: Frequently Asked Questions
sidebar_label: Frequently Asked Questions
---

## SOMETHING is BrOkEnN!!! THis doesn't work and I don't know what to dooooo

Please make sure to read our [general troubleshooting guide](guides/troubleshooting.md) before attacking our Discord support team or hammering the GitHub Issues.


## I just installed swizzin and the dashboard shows that it's using all my RAM. WTF?!

The panel reports three statistics related to memory consumption: `real`, `cache` and `physical`.
Expand Down
12 changes: 6 additions & 6 deletions docs/guides/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,13 +28,13 @@ If you do find your problem, you can subscribe to those issues to get updates wh

### Accessing swizzin/`box` logs

Swizzin stores its logs into the `/root/logs` directories. The installer installs into `install.log`, and any other command you run with `box` will end up in `swizzin.log`. You can access the logs by running the following commands.
Swizzin stores its logs into the `/var/log/swizzin` directories. The installer installs into `setup.log`, and any other command you run with `box` will end up in `box.log` (or some of the older rotations of it). You can access the logs by running the following commands.

```bash
# To check the logs of the Swizzin installer
sudo less -r +G /root/logs/install.log
sudo less -r +G /var/log/swizzin/setup.log
# To check the logs of any application manipulation through box
sudo less -r +G /root/logs/swizzin.log
sudo less -r +G /var/log/swizzin/box.log #or box.log.1 etc.
```

Please consult these logs for any errors or other bad-sounding messages before continuing.
Expand All @@ -43,7 +43,7 @@ Please consult these logs for any errors or other bad-sounding messages before c
If you would like to see "verbose" output of the box command, you can run the following command before any `box` function. This will print all the information stored into the log into your current terminal session as well.
```bash
# to start the verbose output
tail -f /root/logs/swizzin.log &
tail -f /var/log/swizzin/box.log &

box install ligma # do whatever you need to do here

Expand Down Expand Up @@ -78,7 +78,7 @@ Currently, we suggest using `termbin.com` for your `fiche` instance
Want to show us your swizzin logs?

```bash
sudo cat /root/logs/swizzin.log | nc <fiche instance> 9999
sudo cat /var/log/swizzin/box.log | nc <fiche instance> 9999
```

Below is an example for sharing the content of your syslog.
Expand Down Expand Up @@ -257,7 +257,7 @@ You can also attempt to remove swizzin by removing every app you have installed
- `/etc/swizzin`
- `/usr/local/bin/swizzin`
- `/install/`
- `/root/logs/`
- `/var/log/swizzin/`
- `/root/swizzin/`
- `/etc/htpasswd`
- `/etc/htpasswd.d`
Expand Down