Log Artifacts Collection
Logs can be gathered from each Lightbits server configured in the hosts file.
For each command below, two variations are provided. Choose the "Ansible Method" if you are installing via Ansible, or follow the "Docker Method" if you are using Docker for installation.
Additionally, each Docker example requires the correct Docker URL: docker.lightbitslabs.com/lightos-3-(Minor Ver)-(Rev)-rhl-(8/9)/lb-ansible:v9.1.0. Note that the path bit is incomplete and requires substitution. Refer to the Lightbits Installation Customer Addendum for the correct repo name.
x
# If using Ansible Method, run this:cd ~/light-appansible-playbook -i ansible/inventories/cluster_example/hosts playbooks/logs.yml -vvv# If using Docker Method, run this:cd ~/light-appdocker run -it --rm --net=host \ -e UID=`id -u` \ -e GID=`id -g` \ -e UNAME=$USER \ -v `pwd`:/ansible \ -w /ansible \ -e ANSIBLE_LOG_PATH=/ansible/ansible.log \ docker.lightbitslabs.com/lightos-3-(Minor Ver)-(Rev)-rhl-(8/9)/lb-ansible:v9.1.0 \ sh -c 'ansible-playbook -i ansible/inventories/cluster_example/hosts playbooks/logs.yml -vvv'The output of each Lightbits server is saved into a dated directory inside /tmp/ on the Ansible host.
- This can be run against servers that have Lightbits installed, as well as servers that do not have Lightbits installed.
- To properly gather logs from Lightbits servers, the playbook will depend on the jwt being in the
~/lightos-system-jwtfile. - If a node is inactive, unattached, or services seem unresponsive, collect logs using
lb-support.sh -s 7 -l $(hostname -s). The-s 7parameter specifies a seven-day log capture duration; you can adjust this as needed, based on when the issue began. The-l $(hostname -s)option inserts the server's hostname to the log tarball filename, aiding in file differentiation. Forward the issue and tarball to Lightbits Support for evaluation, and to determine if intervention or a restart of the NM, CM, or server is needed.
Was this page helpful?