{"id":339,"date":"2017-11-27T18:59:32","date_gmt":"2017-11-27T20:59:32","guid":{"rendered":"http:\/\/docs.unitplatform.io\/?p=339"},"modified":"2019-04-10T13:29:46","modified_gmt":"2019-04-10T16:29:46","slug":"unit-platform-cloud-agent-advanced-options-linux","status":"publish","type":"post","link":"https:\/\/docs.unitplatform.io\/en\/unit-platform-cloud-agent-advanced-options-linux\/","title":{"rendered":"Unit Platform Cloud Agent advanced options (Linux)","raw":"Unit Platform Cloud Agent advanced options (Linux)"},"content":{"rendered":"<h2>How the agent works<\/h2>\n<p>The Cloud Agent is installed as a service, and can be started\/stopped\/restarted using the init script.<\/p>\n<p>For Cloud Agent version 6.1 and newer:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\"># stopping the agent\r\n\/etc\/init.d\/unit-platform-cloud-agent stop\r\n\r\n# starting the agent\r\n\/etc\/init.d\/unit-platform-cloud-agent start \r\n\r\n# restarting the agent \r\n\/etc\/init.d\/unit-platform-cloud-agent restart<\/pre>\n<p>For previous versions:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\"># stopping the agent\r\n\/etc\/init.d\/unit_cloud_agent stop\r\n\r\n# starting the agent\r\n\/etc\/init.d\/unit_cloud_agent start\r\n\r\n# restarting the agent\r\n\/etc\/init.d\/unit_cloud_agent restart<\/pre>\n<p>To check if the agent is running, execute:<\/p>\n<p>For Cloud Agent version 6.1 and newer:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\">\/etc\/init.d\/unit-platform-cloud-agent status<\/pre>\n<p>For previous versions:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\">\/etc\/init.d\/unit_cloud_agent status<\/pre>\n<p>The installation directory is at: <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">\/opt\/Netwall\/CloudAgent\/<\/code>. The <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">config\/<\/code> directory stores all configuration files.<\/p>\n<p>The log files for version\u00a0 6.1+ are located at\u00a0 <code class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\">\/var\/log\/unit-platform-cloud-agent\/<\/code>. On older versions, the logs are stored at <code class=\"EnlighterJSRAW\">\/var\/log\/unit_cloud_agent.log<\/code>.<\/p>\n<h2>Auto update<\/h2>\n<p>From the version 6.1 onwards, Unit Platform Cloud Agent comes with and additional service, responsible for updating the agent&#8217;s files. The updates are downloaded directly form the Unit Platform.<\/p>\n<p>The update service can be managed using the following commands:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\"># stopping the update service \r\n\/etc\/init.d\/unit-platform-cloud-agent-update stop \r\n\r\n# starting the update service\r\n\/etc\/init.d\/unit-platform-cloud-agent-update start \r\n\r\n# restarting the update service\r\n\/etc\/init.d\/unit-platform-cloud-agent-update restart\r\n\r\n# checking status \r\n\/etc\/init.d\/unit-platform-cloud-agent-update status<\/pre>\n<p>The updates are enabled by default. If you don&#8217;t want the agent to update, simply stop the service and configure the update service to not start at boot using either <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">chkconfig\u00a0unit-platform-cloud-agent-update off<\/code> or <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">update-rc.d\u00a0unit-platform-cloud-agent-update disable<\/code> depending on your distro.<\/p>\n<h2>Customizing the configuration<\/h2>\n<p>The main configuration file is specified at <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">config\/agent.conf<\/code>. In this file you can change the following items:<\/p>\n<ul>\n<li>Enable\/disable sending monitoring information.<\/li>\n<li>Enable\/disable sending inventory information.<\/li>\n<li>Change the interval on which the agent will send monitoring or inventory information to Unit Platform.<\/li>\n<li>Change the company key.<\/li>\n<li>Change the address the agent will send information to. Default: app.unitplatform.io. <em>Change this only if you are using Unit Platform on-premises.<\/em><\/li>\n<li>Configure the data collection timeout value.<\/li>\n<li>Enable\/disable showing more detailed debug messages in the log file.<\/li>\n<\/ul>\n<blockquote><p><strong>IMPORTANT:<\/strong> after making any changes in the <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">agent.conf<\/code> file, <strong>restart the agent service<\/strong> for the changes to take effect<\/p><\/blockquote>\n<h3>Monitoramento de processos<\/h3>\n<p>To monitor processes, inform in the file <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">process.conf<\/code> the names of the processes that should be monitored. The names must be listed one per line. See the example below:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-linenumbers=\"false\">httpd\r\nsshd\r\nmysqld\r\n<\/pre>\n<p>The processes are monitored using the command <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">ps -C \"[proc]\"<\/code>, verify if your process can be monitored using this command.<\/p>\n<blockquote><p><strong>IMPORTANT:<\/strong> after making any changes in the <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">process.conf<\/code> file, <strong>restart the agent service<\/strong> for the changes to take effect<\/p><\/blockquote>\n<h2>Troubleshooting<\/h2>\n<p>These are the most common problems that may prevent the agent from sending information to the Unit Platform:<\/p>\n<h3>The device does not have internet access<\/h3>\n<p>The device being monitored must have access to the Unit Platform using HTTPS. By default the address the agent will send information to is https:\/\/app.unitplatform.io\/. Please check if there are any firewall rules denying access to the internet or the Unit Platform.<\/p>\n<h3>The agent&#8217;s service is not running<\/h3>\n<p>The agent&#8217;s service is configured to stop in case one of the following situations happen:<\/p>\n<ul>\n<li>The company key was not informed or is invalid.<\/li>\n<\/ul>\n<p>To correct this error, edit the <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">agent.conf<\/code>, inform the your company key and restart the agent.<\/p>\n<ul>\n<li>The monitoring\/inventory interval is invalid.<\/li>\n<\/ul>\n<p>To correct this error, edit the <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">agent.conf<\/code>, review the interval values and restart the agent.<\/p>\n<ul>\n<li>The agent was installed on a distribution not supported.<\/li>\n<\/ul>\n<p>Check if your distribution is listed as supported. If your distribution is on the supported list, contact us using the support link in the menu above.<\/p>\n<ul>\n<li>Some prerequisite was not installed correctly.<\/li>\n<\/ul>\n<p>Check if all the prerequisites were installed. If the error persists, execute the ldd command to check if there are any non mapped dependencies:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-linenumbers=\"false\">ldd \/opt\/Netwall\/CloudAgent\/bin\/UnitPlatformCloudAgent_x64<\/pre>\n<p>If any lib has the &#8220;not found&#8221; status, contact us using the support link in the menu above.<\/p>\n<h3>The device limit for your plan has been exceeded<\/h3>\n<p>In this case, revise your Unit Platform subscription and restart the agent.<\/p>\n","protected":false,"raw":"<h2>How the agent works<\/h2>\r\nThe Cloud Agent is installed as a service, and can be started\/stopped\/restarted using the init script.\r\n\r\nFor Cloud Agent version 6.1 and newer:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\"># stopping the agent\r\n\/etc\/init.d\/unit-platform-cloud-agent stop\r\n\r\n# starting the agent\r\n\/etc\/init.d\/unit-platform-cloud-agent start \r\n\r\n# restarting the agent \r\n\/etc\/init.d\/unit-platform-cloud-agent restart<\/pre>\r\nFor previous versions:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\"># stopping the agent\r\n\/etc\/init.d\/unit_cloud_agent stop\r\n\r\n# starting the agent\r\n\/etc\/init.d\/unit_cloud_agent start\r\n\r\n# restarting the agent\r\n\/etc\/init.d\/unit_cloud_agent restart<\/pre>\r\nTo check if the agent is running, execute:\r\n\r\nFor Cloud Agent version 6.1 and newer:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\">\/etc\/init.d\/unit-platform-cloud-agent status<\/pre>\r\nFor previous versions:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\">\/etc\/init.d\/unit_cloud_agent status<\/pre>\r\nThe installation directory is at: <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">\/opt\/Netwall\/CloudAgent\/<\/code>. The <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">config\/<\/code> directory stores all configuration files.\r\n\r\nThe log files for version\u00a0 6.1+ are located at\u00a0 <code class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\">\/var\/log\/unit-platform-cloud-agent\/<\/code>. On older versions, the logs are stored at <code class=\"EnlighterJSRAW\">\/var\/log\/unit_cloud_agent.log<\/code>.\r\n<h2>Auto update<\/h2>\r\nFrom the version 6.1 onwards, Unit Platform Cloud Agent comes with and additional service, responsible for updating the agent's files. The updates are downloaded directly form the Unit Platform.\r\n\r\nThe update service can be managed using the following commands:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\"># stopping the update service \r\n\/etc\/init.d\/unit-platform-cloud-agent-update stop \r\n\r\n# starting the update service\r\n\/etc\/init.d\/unit-platform-cloud-agent-update start \r\n\r\n# restarting the update service\r\n\/etc\/init.d\/unit-platform-cloud-agent-update restart\r\n\r\n# checking status \r\n\/etc\/init.d\/unit-platform-cloud-agent-update status<\/pre>\r\nThe updates are enabled by default. If you don't want the agent to update, simply stop the service and configure the update service to not start at boot using either <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">chkconfig\u00a0unit-platform-cloud-agent-update off<\/code> or <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">update-rc.d\u00a0unit-platform-cloud-agent-update disable<\/code> depending on your distro.\r\n<h2>Customizing the configuration<\/h2>\r\nThe main configuration file is specified at <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">config\/agent.conf<\/code>. In this file you can change the following items:\r\n<ul>\r\n \t<li>Enable\/disable sending monitoring information.<\/li>\r\n \t<li>Enable\/disable sending inventory information.<\/li>\r\n \t<li>Change the interval on which the agent will send monitoring or inventory information to Unit Platform.<\/li>\r\n \t<li>Change the company key.<\/li>\r\n \t<li>Change the address the agent will send information to. Default: app.unitplatform.io. <em>Change this only if you are using Unit Platform on-premises.<\/em><\/li>\r\n \t<li>Configure the data collection timeout value.<\/li>\r\n \t<li>Enable\/disable showing more detailed debug messages in the log file.<\/li>\r\n<\/ul>\r\n<blockquote><strong>IMPORTANT:<\/strong> after making any changes in the <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">agent.conf<\/code> file, <strong>restart the agent service<\/strong> for the changes to take effect<\/blockquote>\r\n<h3>Monitoramento de processos<\/h3>\r\nTo monitor processes, inform in the file <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">process.conf<\/code> the names of the processes that should be monitored. The names must be listed one per line. See the example below:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-linenumbers=\"false\">httpd\r\nsshd\r\nmysqld\r\n<\/pre>\r\nThe processes are monitored using the command <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">ps -C \"[proc]\"<\/code>, verify if your process can be monitored using this command.\r\n<blockquote><strong>IMPORTANT:<\/strong> after making any changes in the <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">process.conf<\/code> file, <strong>restart the agent service<\/strong> for the changes to take effect<\/blockquote>\r\n<h2>Troubleshooting<\/h2>\r\nThese are the most common problems that may prevent the agent from sending information to the Unit Platform:\r\n<h3>The device does not have internet access<\/h3>\r\nThe device being monitored must have access to the Unit Platform using HTTPS. By default the address the agent will send information to is https:\/\/app.unitplatform.io\/. Please check if there are any firewall rules denying access to the internet or the Unit Platform.\r\n<h3>The agent's service is not running<\/h3>\r\nThe agent's service is configured to stop in case one of the following situations happen:\r\n<ul>\r\n \t<li>The company key was not informed or is invalid.<\/li>\r\n<\/ul>\r\nTo correct this error, edit the <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">agent.conf<\/code>, inform the your company key and restart the agent.\r\n<ul>\r\n \t<li>The monitoring\/inventory interval is invalid.<\/li>\r\n<\/ul>\r\nTo correct this error, edit the <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">agent.conf<\/code>, review the interval values and restart the agent.\r\n<ul>\r\n \t<li>The agent was installed on a distribution not supported.<\/li>\r\n<\/ul>\r\nCheck if your distribution is listed as supported. If your distribution is on the supported list, contact us using the support link in the menu above.\r\n<ul>\r\n \t<li>Some prerequisite was not installed correctly.<\/li>\r\n<\/ul>\r\nCheck if all the prerequisites were installed. If the error persists, execute the ldd command to check if there are any non mapped dependencies:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-linenumbers=\"false\">ldd \/opt\/Netwall\/CloudAgent\/bin\/UnitPlatformCloudAgent_x64<\/pre>\r\nIf any lib has the \"not found\" status, contact us using the support link in the menu above.\r\n<h3>The device limit for your plan has been exceeded<\/h3>\r\nIn this case, revise your Unit Platform subscription and restart the agent."},"excerpt":{"rendered":"<p>Advanced configurations and troubleshooting.<\/p>\n","protected":false,"raw":"Advanced configurations and troubleshooting."},"author":3,"featured_media":989,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_pt_post_content":"<h2>Funcionamento do agente<\/h2>\r\nO Cloud Agent \u00e9 instalado como um servi\u00e7o, e pode ser iniciado\/parado\/reiniciado atrav\u00e9s do init script.\r\n\r\nA partir da vers\u00e3o 6.1 do Cloud Agent:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\"># parando o agente\r\n\/etc\/init.d\/unit-platform-cloud-agent stop\r\n\r\n# iniciando o agente \r\n\/etc\/init.d\/unit-platform-cloud-agent start \r\n\r\n# reiniciando o agente \r\n\/etc\/init.d\/unit-platform-cloud-agent restart<\/pre>\r\nPara vers\u00f5es anteriores:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\"># parando o agente\r\n\/etc\/init.d\/unit_cloud_agent stop\r\n\r\n# iniciando o agente\r\n\/etc\/init.d\/unit_cloud_agent start\r\n\r\n# reiniciando o agente\r\n\/etc\/init.d\/unit_cloud_agent restart<\/pre>\r\nPara verificar se o agente est\u00e1 rodando, execute:\r\n\r\nPara o Cloud Agent vers\u00e3o 6.1+:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\">\/etc\/init.d\/unit-platform-cloud-agent status<\/pre>\r\nPara vers\u00f5es anteriores:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\">\/etc\/init.d\/unit_cloud_agent status<\/pre>\r\nO local de instala\u00e7\u00e3o fica em: <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">\/opt\/Netwall\/CloudAgent\/<\/code>. O diret\u00f3rio <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">config\/<\/code> armazena os arquivos de configura\u00e7\u00e3o.\r\n\r\nPara a vers\u00e3o\u00a0 6.1+ os arquivos de log ficam armazenados no diret\u00f3rio\u00a0 <code class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\">\/var\/log\/unit-platform-cloud-agent\/<\/code>. Nas vers\u00f5es anteriores os logs ficam em <code class=\"EnlighterJSRAW\">\/var\/log\/unit_cloud_agent.log<\/code>.\r\n<h2>Atualiza\u00e7\u00e3o autom\u00e1tica<\/h2>\r\nA partir da vers\u00e3o 6.1, o Unit Platform Cloud Agent possui um servi\u00e7o adicional que \u00e9 respons\u00e1vel por atualizar os arquivos do agente. Os updates s\u00e3o baixados direto da Unit Platform.\r\n\r\nO servi\u00e7o de atualiza\u00e7\u00e3o pode ser gerenciado usando os seguintes comandos:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\"># parando o servi\u00e7o de atualiza\u00e7\u00e3o\r\n\/etc\/init.d\/unit-platform-cloud-agent-update stop \r\n\r\n# iniciando o\u00a0servi\u00e7o\u00a0de\u00a0atualiza\u00e7\u00e3o\r\n\/etc\/init.d\/unit-platform-cloud-agent-update start \r\n\r\n# reiniciando o\u00a0servi\u00e7o\u00a0de\u00a0atualiza\u00e7\u00e3o \r\n\/etc\/init.d\/unit-platform-cloud-agent-update restart\r\n\r\n# verificando o status do servi\u00e7o de atualiza\u00e7\u00e3o \r\n\/etc\/init.d\/unit-platform-cloud-agent-update status<\/pre>\r\nAs atualiza\u00e7\u00f5es s\u00e3o habilitadas por padr\u00e3o. Se voc\u00ea n\u00e3o deseja que o agente atualize automaticamente, simplesmente pare o servi\u00e7o de atualiza\u00e7\u00e3o, e configure o servi\u00e7o para n\u00e3o iniciar durante o boot usando o comando <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">chkconfig\u00a0unit-platform-cloud-agent-update off<\/code> ou <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">update-rc.d\u00a0unit-platform-cloud-agent-update disable<\/code> dependendo da sua distro.\r\n<h2>Personaliza\u00e7\u00e3o da configura\u00e7\u00e3o<\/h2>\r\nA configura\u00e7\u00e3o geral do agente \u00e9 especificada no arquivo <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">config\/agent.conf<\/code>. Nesse arquivo \u00e9 permitido alterar os seguintes itens:\r\n<ul>\r\n \t<li>Habilitar\/desabilitar o envio de informa\u00e7\u00f5es de monitoramento.<\/li>\r\n \t<li>Habilitar\/desabilitar o envio de informa\u00e7\u00f5es de invent\u00e1rio.<\/li>\r\n \t<li>Alterar o intervalo de envio de informa\u00e7\u00f5es de monitoramento e invent\u00e1rio para a Unit Platform.<\/li>\r\n \t<li>Alterar a chave da empresa.<\/li>\r\n \t<li>Alterar o endere\u00e7o para o qual as informa\u00e7\u00f5es de monitoramento devem ser enviadas. Por padr\u00e3o: app.unitplatform.io. <em>Apenas altere este campo se voc\u00ea estiver usando a Unit Platform on-premises.<\/em><\/li>\r\n \t<li>Configurar o tempo de timeout para a execu\u00e7\u00e3o dos comandos de coleta de dados.<\/li>\r\n \t<li>Habilitar\/desabilitar a exibi\u00e7\u00e3o de mensagens de debug no arquivo de log do agente.<\/li>\r\n<\/ul>\r\n<blockquote><strong>IMPORTANTE:<\/strong> ap\u00f3s fazer altera\u00e7\u00f5es nos arquivo <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">agent.conf<\/code>, <strong>reinicie o servi\u00e7o do agente<\/strong> para que as altera\u00e7\u00f5es entrem em efeito.<\/blockquote>\r\n<h3>Monitoramento de processos<\/h3>\r\nPara monitoramento de processos, informe no arquivo\u00a0<code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">process.conf<\/code> os nomes dos processos que devem ser monitorados. Os nomes devem ser preenchidos um por linha. Veja o exemplo abaixo:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-linenumbers=\"false\">httpd\r\nsshd\r\nmysqld\r\n<\/pre>\r\nOs processos s\u00e3o monitorados atrav\u00e9s do comando\u00a0<code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">ps -C \"[proc]\"<\/code> certifique-se que o nome do seu processo aparece corretamente na sa\u00edda desse comando.\r\n<blockquote><strong>IMPORTANTE:<\/strong> ap\u00f3s fazer as altera\u00e7\u00f5es no arquivo <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">process.conf<\/code>, <strong>reinicie o servi\u00e7o do agente<\/strong> para que as altera\u00e7\u00f5es entrem em efeito.<\/blockquote>\r\n<h2>Resolu\u00e7\u00e3o de problemas<\/h2>\r\nAbaixo est\u00e3o listados os problemas mais comuns que podem impedir o envio de informa\u00e7\u00f5es do dispositivo para a Unit Platform:\r\n<h3>O dispositivo n\u00e3o possui acesso \u00e0 internet<\/h3>\r\n\u00c9 necess\u00e1rio que o dispositivo tenha permiss\u00f5es para trafegar dados via HTTPS para o endere\u00e7o https:\/\/app.unitplatform.io\/.\u00a0 Revise as regras de firewall que possivelmente estejam impedindo o dispositivo de acessar a internet.\r\n<h3>O servi\u00e7o do agente n\u00e3o est\u00e1 rodando<\/h3>\r\nO servi\u00e7o do agente est\u00e1 configurado para parar automaticamente caso os seguintes erros de configura\u00e7\u00e3o ocorram:\r\n<ul>\r\n \t<li>A chave da empresa n\u00e3o foi informada ou \u00e9 inv\u00e1lida.<\/li>\r\n<\/ul>\r\nPara corrigir este erro, edite o arquivo <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">agent.conf<\/code> e informe a chave correta na vari\u00e1vel \"key\".\r\n<ul>\r\n \t<li>Foi informado um intervalo de monitoramento\/invent\u00e1rio inv\u00e1lido.<\/li>\r\n<\/ul>\r\nPara corrigir esse erro, edite o arquivo <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">agent.conf<\/code> e revise os valores informados nos intervalos.\r\n<ul>\r\n \t<li>O agente foi instalado em uma distribui\u00e7\u00e3o n\u00e3o homologada.<\/li>\r\n<\/ul>\r\nVerifique se a sua distribui\u00e7\u00e3o est\u00e1 na lista de sistemas operacionais homologados, se estiver contate-nos atrav\u00e9s do link \"Suporte\" no menu acima.\r\n<ul>\r\n \t<li>Algum pr\u00e9-requisito n\u00e3o foi instalado corretamente.<\/li>\r\n<\/ul>\r\nRevise se todos os pr\u00e9-requisitos foram instalados corretamente. Caso o erro persista ap\u00f3s a verifica\u00e7\u00e3o dos requisitos, execute o comando ldd para verificar se h\u00e1 alguma depend\u00eancia n\u00e3o mapeada:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-linenumbers=\"false\">ldd \/opt\/Netwall\/CloudAgent\/bin\/UnitPlatformCloudAgent_x64<\/pre>\r\nCaso alguma lib esteja com o status \"not found\", contate-nos atrav\u00e9s do link \"Suporte\" no menu acima.\r\n<h3>O limite de dispositivos contratados no plano foi excedido<\/h3>\r\nNeste caso, revise a sua configura\u00e7\u00e3o de assinatura da Unit Platform e reinicie o agente.","_pt_post_name":"configuracao-avancada-do-unit-platform-cloud-agent-linux","_pt_post_excerpt":"Personaliza\u00e7\u00e3o da instala\u00e7\u00e3o e resolu\u00e7\u00e3o de problemas.","_pt_post_title":"Configura\u00e7\u00e3o avan\u00e7ada do Unit Platform Cloud Agent (Linux)","_en_post_content":"<h2>How the agent works<\/h2>\r\nThe Cloud Agent is installed as a service, and can be started\/stopped\/restarted using the init script.\r\n\r\nFor Cloud Agent version 6.1 and newer:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\"># stopping the agent\r\n\/etc\/init.d\/unit-platform-cloud-agent stop\r\n\r\n# starting the agent\r\n\/etc\/init.d\/unit-platform-cloud-agent start \r\n\r\n# restarting the agent \r\n\/etc\/init.d\/unit-platform-cloud-agent restart<\/pre>\r\nFor previous versions:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\"># stopping the agent\r\n\/etc\/init.d\/unit_cloud_agent stop\r\n\r\n# starting the agent\r\n\/etc\/init.d\/unit_cloud_agent start\r\n\r\n# restarting the agent\r\n\/etc\/init.d\/unit_cloud_agent restart<\/pre>\r\nTo check if the agent is running, execute:\r\n\r\nFor Cloud Agent version 6.1 and newer:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\">\/etc\/init.d\/unit-platform-cloud-agent status<\/pre>\r\nFor previous versions:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\">\/etc\/init.d\/unit_cloud_agent status<\/pre>\r\nThe installation directory is at: <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">\/opt\/Netwall\/CloudAgent\/<\/code>. The <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">config\/<\/code> directory stores all configuration files.\r\n\r\nThe log files for version\u00a0 6.1+ are located at\u00a0 <code class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\">\/var\/log\/unit-platform-cloud-agent\/<\/code>. On older versions, the logs are stored at <code class=\"EnlighterJSRAW\">\/var\/log\/unit_cloud_agent.log<\/code>.\r\n<h2>Auto update<\/h2>\r\nFrom the version 6.1 onwards, Unit Platform Cloud Agent comes with and additional service, responsible for updating the agent's files. The updates are downloaded directly form the Unit Platform.\r\n\r\nThe update service can be managed using the following commands:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\" data-enlighter-linenumbers=\"false\"># stopping the update service \r\n\/etc\/init.d\/unit-platform-cloud-agent-update stop \r\n\r\n# starting the update service\r\n\/etc\/init.d\/unit-platform-cloud-agent-update start \r\n\r\n# restarting the update service\r\n\/etc\/init.d\/unit-platform-cloud-agent-update restart\r\n\r\n# checking status \r\n\/etc\/init.d\/unit-platform-cloud-agent-update status<\/pre>\r\nThe updates are enabled by default. If you don't want the agent to update, simply stop the service and configure the update service to not start at boot using either <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">chkconfig\u00a0unit-platform-cloud-agent-update off<\/code> or <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">update-rc.d\u00a0unit-platform-cloud-agent-update disable<\/code> depending on your distro.\r\n<h2>Customizing the configuration<\/h2>\r\nThe main configuration file is specified at <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">config\/agent.conf<\/code>. In this file you can change the following items:\r\n<ul>\r\n \t<li>Enable\/disable sending monitoring information.<\/li>\r\n \t<li>Enable\/disable sending inventory information.<\/li>\r\n \t<li>Change the interval on which the agent will send monitoring or inventory information to Unit Platform.<\/li>\r\n \t<li>Change the company key.<\/li>\r\n \t<li>Change the address the agent will send information to. Default: app.unitplatform.io. <em>Change this only if you are using Unit Platform on-premises.<\/em><\/li>\r\n \t<li>Configure the data collection timeout value.<\/li>\r\n \t<li>Enable\/disable showing more detailed debug messages in the log file.<\/li>\r\n<\/ul>\r\n<blockquote><strong>IMPORTANT:<\/strong> after making any changes in the <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">agent.conf<\/code> file, <strong>restart the agent service<\/strong> for the changes to take effect<\/blockquote>\r\n<h3>Monitoramento de processos<\/h3>\r\nTo monitor processes, inform in the file <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">process.conf<\/code> the names of the processes that should be monitored. The names must be listed one per line. See the example below:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-linenumbers=\"false\">httpd\r\nsshd\r\nmysqld\r\n<\/pre>\r\nThe processes are monitored using the command <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">ps -C \"[proc]\"<\/code>, verify if your process can be monitored using this command.\r\n<blockquote><strong>IMPORTANT:<\/strong> after making any changes in the <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">process.conf<\/code> file, <strong>restart the agent service<\/strong> for the changes to take effect<\/blockquote>\r\n<h2>Troubleshooting<\/h2>\r\nThese are the most common problems that may prevent the agent from sending information to the Unit Platform:\r\n<h3>The device does not have internet access<\/h3>\r\nThe device being monitored must have access to the Unit Platform using HTTPS. By default the address the agent will send information to is https:\/\/app.unitplatform.io\/. Please check if there are any firewall rules denying access to the internet or the Unit Platform.\r\n<h3>The agent's service is not running<\/h3>\r\nThe agent's service is configured to stop in case one of the following situations happen:\r\n<ul>\r\n \t<li>The company key was not informed or is invalid.<\/li>\r\n<\/ul>\r\nTo correct this error, edit the <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">agent.conf<\/code>, inform the your company key and restart the agent.\r\n<ul>\r\n \t<li>The monitoring\/inventory interval is invalid.<\/li>\r\n<\/ul>\r\nTo correct this error, edit the <code class=\"EnlighterJSRAW\" data-enlighter-language=\"null\">agent.conf<\/code>, review the interval values and restart the agent.\r\n<ul>\r\n \t<li>The agent was installed on a distribution not supported.<\/li>\r\n<\/ul>\r\nCheck if your distribution is listed as supported. If your distribution is on the supported list, contact us using the support link in the menu above.\r\n<ul>\r\n \t<li>Some prerequisite was not installed correctly.<\/li>\r\n<\/ul>\r\nCheck if all the prerequisites were installed. If the error persists, execute the ldd command to check if there are any non mapped dependencies:\r\n<pre class=\"EnlighterJSRAW\" data-enlighter-linenumbers=\"false\">ldd \/opt\/Netwall\/CloudAgent\/bin\/UnitPlatformCloudAgent_x64<\/pre>\r\nIf any lib has the \"not found\" status, contact us using the support link in the menu above.\r\n<h3>The device limit for your plan has been exceeded<\/h3>\r\nIn this case, revise your Unit Platform subscription and restart the agent.","_en_post_name":"unit-platform-cloud-agent-advanced-options-linux","_en_post_excerpt":"Advanced configurations and troubleshooting.","_en_post_title":"Unit Platform Cloud Agent advanced options (Linux)","edit_language":"en","footnotes":""},"categories":[11,10,4,9],"tags":[],"class_list":["post-339","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-asset-management","category-multisite-monitoring","category-tutorials","category-unit-platform-cloud"],"_links":{"self":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts\/339","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/comments?post=339"}],"version-history":[{"count":8,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts\/339\/revisions"}],"predecessor-version":[{"id":1236,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts\/339\/revisions\/1236"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/media\/989"}],"wp:attachment":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/media?parent=339"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/categories?post=339"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/tags?post=339"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}