Ask the Community
Groups
Update that use FTP may fail. - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Low update, download timeout, or cannot download updates or required Support scripts because the process uses Passive FTP (aka PASV). yum wget</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <p>The Unitrends system is configured to access the Unitrends repository over HTTP by default. The system may be re-configured to update over FTP by following <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Funitrends-support.zendesk.com%2Fhc%2Fen-us%2Farticles%2F360013175817%3Fq%3DSELECT%2BArticleNumber%252CId%252CSummary%252CResolution__c%252CAttachment__Body__s%252CCause__c%252CNotes__c%252CAttachment__ContentType__s%252CAttachment__Length__s%252CAttachment__Name__s%252CTitle%252CKnowledgeArticleId%252CDescription__c%2Bfrom%2BArticle__kav%2Bwhere%2BPublishStatus%253D%2527Online%2527">Upgrade attempt fails because appliance cannot download update packages</a>. When connecting to the Unitrends repository yum fails to retrieve the repo file.</p> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p></p> <p>Using PuTTY or another SSH client connect to the Unitrends system as the root user and run the following:</p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> find / -name ftplib.py -exec sed -i 's/passiveserver = 1/passiveserver = 0/g' {} \;</pre> <p>Updates should now succeed.<br><br><br>When using wget, you can use the option of --no-passive-ftp to force the download to occur over Active FTP mode</p> <h2 data-id="cause"><strong>CAUSE</strong></h2> <p></p> <p>Yum uses http in our configuration. If you have to force yum to use ftp, you might have issues. Those issues might be caused by yum using ftp in passive mode. Active mode should be the answer. You will need to configure yum to use ftp in active mode.<br><br>yum is configured to operate in passive mode over FTP. This configuration may return the following error message when updating via CLI.</p> </article> </main>