We recommend using Systemd to manage Bouncebit service and check logs.
Setting up systemd unit file
You can create a Systemd unit file at the following location /etc/systemd/system/bouncebit.service:
sudo tee /etc/systemd/system/bouncebit.service <<EOF
[Unit]
Description=bouncebit node daemon
After=network-online.target
Wants=network-online.target data.mount
Requires=data.mount
[Service]
ExecStart=/usr/local/bin/bbcored start \\
--log_format=json \\
--log_level=info \\
--home=/data/bouncebit
Type=simple
Restart=on-failure
KillMode=process
KillSignal=SIGINT
TimeoutStartSec=infinity
TimeoutStopSec=600
User=bouncebit
Group=bouncebit
CPUSchedulingPolicy=batch
LimitNOFILE=524288
LimitNPROC=16384
MemoryMax=27G
WorkingDirectory=/data/bouncebit
EnvironmentFile=-/etc/bouncebit/bbcored.env
# /run/bouncebit
RuntimeDirectory=bouncebit
RuntimeDirectoryMode=0700
# /etc/bouncebit
ConfigurationDirectory=bouncebit
ConfigurationDirectoryMode=0755
# /var/lib/bouncebit
StateDirectory=bitcoind
StateDirectoryMode=0710
SyslogIdentifier=bbcored
# Provide a private /tmp and /var/tmp.
PrivateTmp=true
# Mount /usr, /boot/ and /etc read-only for the process.
ProtectSystem=full
# Deny access to /home, /root and /run/user
ProtectHome=true
# Disallow the process and all of its children to gain
# new privileges through execve().
NoNewPrivileges=true
# Use a new /dev namespace only populated with API pseudo devices
# such as /dev/null, /dev/zero and /dev/random.
PrivateDevices=true
# Deny the creation of writable and executable memory mappings.
MemoryDenyWriteExecute=true
[Install]
WantedBy=multi-user.target
EOF