User Tools

Site Tools


update_does_not_work_clicking_on_the_update_message_does_not_update_the_system

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
update_does_not_work_clicking_on_the_update_message_does_not_update_the_system [2016/10/21 19:30]
lucy
update_does_not_work_clicking_on_the_update_message_does_not_update_the_system [2019/07/25 12:50] (current)
Line 8: Line 8:
 You have various possibilities to fix this: You have various possibilities to fix this:
  
-  * 1) **Re-boot the server** and try updating again+  * 1) **Re-boot the server** and try updating again. Please [[reboot_lucy|do a hard reboot of the server]] if the reboot within the web gui has no effect.
   * 2) **Re-fresh the webpage and push the update button again** (sometimes there is a latency that causes the update to fail). We had reports that it needed up to 3-4 attempts where the user had to click the according update again.   * 2) **Re-fresh the webpage and push the update button again** (sometimes there is a latency that causes the update to fail). We had reports that it needed up to 3-4 attempts where the user had to click the according update again.
   * 3) **Fix possible virtual host configuration via SSH/​console**:​ Sometimes apache virtual host configuration files of old scenarios don't get deleted. So when you delete a company with many SSL-enabled scenarios, it's possible that /​etc/​apache2/​sites-enabled/​scenario-<​SCENARIO ID>-ssl file will remain in there and checking apache configuration may fail (as the scenario doesn'​t exist yet, and its directories on disk are cleaned up as well). This configuration check is performed during the update, so if it fails, the update is rolled back to the previous version. Solution: find such configuration files and remove them, then try to update again. The error might be located in /​opt/​phishing/​runtime/​resque_worker.log file - somewhere between latest UpdateJob start and UpdateJob finish log entries. ​   * 3) **Fix possible virtual host configuration via SSH/​console**:​ Sometimes apache virtual host configuration files of old scenarios don't get deleted. So when you delete a company with many SSL-enabled scenarios, it's possible that /​etc/​apache2/​sites-enabled/​scenario-<​SCENARIO ID>-ssl file will remain in there and checking apache configuration may fail (as the scenario doesn'​t exist yet, and its directories on disk are cleaned up as well). This configuration check is performed during the update, so if it fails, the update is rolled back to the previous version. Solution: find such configuration files and remove them, then try to update again. The error might be located in /​opt/​phishing/​runtime/​resque_worker.log file - somewhere between latest UpdateJob start and UpdateJob finish log entries. ​
update_does_not_work_clicking_on_the_update_message_does_not_update_the_system.txt ยท Last modified: 2019/07/25 12:50 (external edit)