set SyslogLevel=debug for systemd service avoid journald

This setting in combination with `MaxLevelStore=info` in `/etc/systemd/journald.conf`
will prevent Journald from being constantly filled by a considerable flow of
logs from beacon nodes and making debugging of other servics on the host harder.

Due to this `journalctl` will no longer show logs for the service.

Issue: https://github.com/status-im/infra-role-bootstrap-linux/issues/24

Signed-off-by: Jakub Sokołowski <jakub@status.im>
This commit is contained in:
Jakub Sokołowski 2021-09-21 17:25:36 +02:00
parent 84ebd34117
commit 75e8e71993
No known key found for this signature in database
GPG Key ID: 4EF064D0E6D63020
2 changed files with 11 additions and 19 deletions

View File

@ -24,7 +24,6 @@ The service exposes three ports by default:
# Installation # Installation
Add to your `requirements.yml` file: Add to your `requirements.yml` file:
```yaml ```yaml
- name: infra-role-beacon-node-linux - name: infra-role-beacon-node-linux
src: git+git@github.com:status-im/infra-role-beacon-node-linux.git src: git+git@github.com:status-im/infra-role-beacon-node-linux.git
@ -34,52 +33,44 @@ Add to your `requirements.yml` file:
# Configuration # Configuration
The crucial settings are: The crucial settings are:
```yaml ```yaml
# branch which should be built # branch which should be built
beacon_node_repo_branch: 'stable' beacon_node_repo_branch: 'stable'
# ethereum network to connect to # ethereum network to connect to
beacon_node_network: 'mainnet' beacon_node_network: 'mainnet'
# optional setting for debug mode # optional setting for debug mode
beacon_node_log_level: 'DEBUG' beacon_node_log_level: 'DEBUG'
# Infura WebSocket URLs # Infura WebSocket URLs
beacon_node_web3_urls: ['wss://mainnet.infura.io/ws/v3/123qwe123qwe123qwe'] beacon_node_web3_urls: ['wss://mainnet.infura.io/ws/v3/123qwe123qwe123qwe']
``` ```
The order of WebSocket URLs matters. First is the default, the rest are fallbacks. The order of WebSocket URLs matters. First is the default, the rest are fallbacks.
# Usage # Usage
Assuming the `stable` branch was built you can manage the service with: Assuming the `stable` branch was built you can manage the service with:
```sh
```
systemctl start beacon-node-stable systemctl start beacon-node-stable
systemctl status beacon-node-stable systemctl status beacon-node-stable
systemctl stop beacon-node-stable systemctl stop beacon-node-stable
# logs
journalctl -u beacon-node-stable
``` ```
You can view logs under:
```sh
tail -f /data/beacon-node-stable/logs/service.log
```
The service will store all data in the `/data/beacon-node-stable` directory. The service will store all data in the `/data/beacon-node-stable` directory.
# Building # Building
A timer will be installed to build the image: A timer will be installed to build the image:
```sh
```
systemctl list-timers beacon-node-stable-build systemctl list-timers beacon-node-stable-build
``` ```
To rebuild the image: To rebuild the image:
```sh
```
systemctl start beacon-node-stable-build.service systemctl start beacon-node-stable-build.service
```
# check build logs To check build logs use:
```sh
journalctl -u beacon-node-stable-build.service journalctl -u beacon-node-stable-build.service
``` ```

View File

@ -10,6 +10,7 @@ Group={{ beacon_node_group }}
WorkingDirectory={{ beacon_node_path }} WorkingDirectory={{ beacon_node_path }}
SyslogIdentifier={{ beacon_node_service_name }} SyslogIdentifier={{ beacon_node_service_name }}
SyslogFacility=local6 SyslogFacility=local6
SyslogLevel=debug
Restart=on-failure Restart=on-failure
ExecStart={{ beacon_node_repo_path }}/build/nimbus_beacon_node \ ExecStart={{ beacon_node_repo_path }}/build/nimbus_beacon_node \
--network={{ beacon_node_network }} \ --network={{ beacon_node_network }} \