Troubleshooting the Reemo Agent¶
This page guides you through common methods of debugging with Reemo.
Enable logs in the Reemo Agent¶
To enable logs in the Reemo Agent on your remote computer, edit the reemo.ini file located at:
Windows:
C:\Program Files\Reemo\service\reemo.iniLinux:
/opt/reemo/reemo.inimacOS:
/Library/Application Support/Reemo/reemo.ini
Then add the following lines:
[logger]
severity = 5
reemo.service.log: logs from the network service.
reemo.capture.log: logs from the capture service.
Enable logs in the Reemo WebClient¶
From your browser, you can view the WebClient logs by opening the Developer Tools > Console tab.
Note
Debug the capture process¶
To specifically debug the capture process, run the following command in a terminal:
./reemod -debug_capture
Collect the logs¶
On macOS and Linux, you can gather all the information needed to diagnose a problem into a single archive to send to the support team.
Note
The service and capture logs are detailed only if you enabled the logs before reproducing the problem.
macOS¶
Run the following command in the Terminal application:
sudo sh -c 'mkdir -p /tmp/reemo-diag && cp /Library/Logs/DiagnosticReports/reemod* /Library/Logs/DiagnosticReports/Retired/reemod* "/Library/Application Support/Reemo/"reemo*.log /tmp/reemo-diag/ 2>/dev/null; sw_vers > /tmp/reemo-diag/macos-version.txt; cd /tmp && zip -qr reemo-diag.zip reemo-diag' && cp /tmp/reemo-diag.zip ~/Desktop/"reemo-diag-$(hostname -s).zip"
The command asks for your administrator password, then creates the reemo-diag-<computer name>.zip archive on the desktop. It contains:
the Reemo logs: reemo.service.log, reemo.capture.log and the update logs (
reemo*.log);the crash reports of reemod, if any;
the macOS version (macos-version.txt).
Linux¶
Run the following command in a terminal:
sudo sh -c 'D=/tmp/reemo-diag; rm -rf "$D"; mkdir -p "$D"; find /opt /usr/local /usr/share /var/log /etc /home /root -maxdepth 5 -type f -name "reemo*.log*" -exec cp {} "$D"/ \; 2>/dev/null; journalctl _COMM=reemod --since "-3d" --no-pager > "$D/journal-reemod.txt" 2>&1; journalctl -u "reemo*" --since "-3d" --no-pager > "$D/journal-units.txt" 2>&1; { coredumpctl list reemod; coredumpctl info reemod; } > "$D/coredumps.txt" 2>&1; dmesg -T 2>/dev/null | tail -n 500 > "$D/dmesg.txt"; { cat /etc/os-release; uname -a; lspci 2>/dev/null | grep -iE "vga|3d|display"; loginctl list-sessions --no-legend | while read -r s _; do loginctl show-session "$s" -p Name -p Type -p Desktop -p State; done; } > "$D/linux-version.txt" 2>&1; tar czf /tmp/reemo-diag.tar.gz -C /tmp reemo-diag && chmod a+r /tmp/reemo-diag.tar.gz' && { DEST=$(xdg-user-dir DESKTOP 2>/dev/null); [ -d "$DEST" ] || DEST=$HOME; cp /tmp/reemo-diag.tar.gz "$DEST/reemo-diag-$(hostname -s).tar.gz"; }
The command asks for your administrator password, then creates the reemo-diag-<computer name>.tar.gz archive on the desktop, or in your home folder if there is no desktop folder. It contains:
the Reemo logs (
reemo*.log*);the system logs of reemod and of the Reemo services for the last three days (journal-reemod.txt, journal-units.txt);
the crash reports of reemod, if any (coredumps.txt);
the last 500 lines of the kernel messages (dmesg.txt);
the system information: distribution, kernel, graphics card and type of graphical session (linux-version.txt).