Troubleshooting of IoT agent on freeBSD - TeamViewer Support
<main> <article class="userContent"> <p><br></p><p>The IoT agent is writing its logfile in <strong>/var/log/teamviewer-iot-agent/teamviewer-iot-agent_logfile.log</strong></p><p>Further information about the current package is available at <strong>/etc/defaults/teamviewer-iot-agent.conf</strong></p><p><br></p><h3></h3><h2 data-id="a-the-agent-is-not-starting">A – The agent is not starting</h2><p>After the installation, it is mandatory to approve the EULA of TeamViewer. As long as the EULA is not accepted, the IoT agent will not start.</p><p>Although you might have called</p><pre class="code codeBlock" spellcheck="false" tabindex="0">service teamviewer_iot_agent start </pre><p>and the info file shows that the IoT agent is online, even so the output of the start command shows</p><pre class="code codeBlock" spellcheck="false" tabindex="0">Starting teamviewer_iot_agent </pre><p>The log file will also indicate the missing EULA acceptance with an entry of the format:</p><pre class="code codeBlock" spellcheck="false" tabindex="0">2021/11/29 09:50:05.555 8794 100830 0!! [Beehive] EULA not accepted. Aborting., Errorcode=2 </pre><p>The EULA has to be accepted via:</p><pre class="code codeBlock" spellcheck="false" tabindex="0">/usr/local/libexec/teamviewer-iot-agent/teamviewer-iot-agent eula </pre><p>Or, if it should be done programmatically without user interaction:</p><pre class="code codeBlock" spellcheck="false" tabindex="0">/usr/local/libexec/teamviewer-iot-agent/teamviewer-iot-agent eula -y </pre><p><br></p><h3 data-id="-1"></h3><h2 data-id="b-file-transfer-is-not-available">B – File transfer is not available</h2><p>The file transfer is deactivated by default in our FreeBSD package.</p><p>It can be activated via the FileTransferAccessControl setting in the agent.conf. Further description can be found on <a href="https://www.teamviewer.com/en-us/iot/documentation/teamviewer-iot-documentation/#use-cases-for-files-transfer" rel="nofollow noreferrer ugc">File Transfer on FreeBSD</a>.</p><p><br></p><h3 data-id="-2"></h3><h2 data-id="c-after-an-update-of-the-agent-the-new-behaviorchanges-are-not-visible.">C – After an update of the agent, the new behavior/changes are not visible.</h2><p>On FreeBSD it is expected that the administrator is performing the switch of the loaded binaries. This means, that during the update process, a running IoT agent is not stopped and a the new one is loaded. This has to be done by the administrator.</p><p>To solve this issue, simply restart the IoT agent via:</p><pre class="code codeBlock" spellcheck="false" tabindex="0">service teamviewer_iot_agent restart </pre><p><br></p><h3 data-id="-3"></h3> </article> </main>
