Mirroristas/bigchaindb
2
0
Fork 0
mirror of https://github.com/bigchaindb/bigchaindb.git synced 2024-10-13 13:34:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix and add some hyperlinks re/ logging.

Browse Source
This commit is contained in:
Troy McConaghy 2018-09-15 14:17:26 +02:00
parent c847e0d0ac
commit c5fe73a2bc
4 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/server/source/appendices/log-rotation.md
View File

@ -38,6 +38,8 @@ then the logs will be written to `$HOME/.bigchaindb-monit/logs/`.
Log rotation is baked into BigchainDB Server using Python's `logging` module. Log rotation is baked into BigchainDB Server using Python's `logging` module.
The logs for BigchainDB Server are rotated when any of the above mentioned files exceeds 209715200 bytes (i.e. approximately 209 MB). The logs for BigchainDB Server are rotated when any of the above mentioned files exceeds 209715200 bytes (i.e. approximately 209 MB).
See also: [the BigchainDB Server configuration settings related to logging](../server-reference/configuration.html#log).
## Tendermint Logging and Log Rotation ## Tendermint Logging and Log Rotation
Tendermint writes its logs to the files: Tendermint writes its logs to the files:

6
docs/server/source/server-reference/configuration.md
View File

@ -269,11 +269,11 @@ The full path to the file where logs should be written.
The user running `bigchaindb` must have write access to the The user running `bigchaindb` must have write access to the
specified path. specified path.
**Log rotation:** Log files have a size limit of 200 MB **Log rotation:** Log files have a size limit of about 200 MB
and will be rotated up to five times. and will be rotated up to five times.
For example, if we `log.file` is set to `"~/bigchain.log"`, then For example, if `log.file` is set to `"~/bigchain.log"`, then
logs would always be written to `bigchain.log`. Each time the file logs would always be written to `bigchain.log`. Each time the file
`bigchain.log` reaches 200 MB it would be closed and renamed `bigchain.log` reaches 200 MB it will be closed and renamed
`bigchain.log.1`. If `bigchain.log.1` and `bigchain.log.2` already exist they `bigchain.log.1`. If `bigchain.log.1` and `bigchain.log.2` already exist they
would be renamed `bigchain.log.2` and `bigchain.log.3`. This pattern would be would be renamed `bigchain.log.2` and `bigchain.log.3`. This pattern would be
applied up to `bigchain.log.5` after which `bigchain.log.5` would be applied up to `bigchain.log.5` after which `bigchain.log.5` would be

4
docs/server/source/simple-deployment-template/network-setup.md
View File

@ -356,10 +356,6 @@ If you started BigchainDB in the foreground, a `Ctrl + C` or `Ctrl + Z` would sh
TBD. TBD.
## Log rotation
Please go over the [document describing log rotation of a BigchainDB node](../appendices/log-rotation.md).
[bdb:software]: https://github.com/bigchaindb/bigchaindb/ [bdb:software]: https://github.com/bigchaindb/bigchaindb/
[bdb:pypi]: https://pypi.org/project/BigchainDB/#history [bdb:pypi]: https://pypi.org/project/BigchainDB/#history

1
docs/server/source/simple-deployment-template/troubleshooting.md
View File

@ -3,6 +3,7 @@
## General Tips ## General Tips
- Check the BigchainDB, Tendermint and MongoDB logs. - Check the BigchainDB, Tendermint and MongoDB logs.
For help with that, see the page about [Logging and Log Rotation](../appendices/log-rotation.html).
- Try Googling the error message. - Try Googling the error message.
## Resolving Tendermint Connectivity Problems ## Resolving Tendermint Connectivity Problems