Disabled nodes problem with today's 1.17 update
Hello,
After today's forced update of Zenarmor to version 1.17 via Zenconsole, a message only appeared on the screen that the version had been updated, after which all 10 pfsense firewall nodes were deactivated.
I tried restarting the engine via Zenconsole, it didn't work.
I accessed via SSH, tried to execute any command zenarmorclt says it is an invalid command.
After i reinstalled zenarmor on one of the pfsense firewalls, but the command "rehash zenarmorctl cloud register" also says invalid command.
We have pfsense firewalls in several versions (2.6, 2.7, 2.7.2) and in all of them they disabled the nodes in Zenconsole.
It has a firewall pfsense with a business license and others with a home license of Zenarmor.
Please I need help.
-
This is bad, really bad... I have this problem as well running pfSense. Logged in tonight to find ZenArmor is not connected to the cloud. Upon further inspection, /tmp/zenarmor_package_update.log shows it just decided to update itself and it failed spectacularly. Our pfSense was running version 1.16.4, but the update script said that was a "conflict" and deleted all the files associated with that version. Then it tried to proceed to upgrade 1.16.6 (which does NOT even exist on the firewall) to 1.17. ZenArmor is effectively gone from what I can tell. The command "zenarmorctl" no longer exists. What do we do now ZenArmor, reinstall and start over?
....... Starting update script .......
Agent version is 1.16.6
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries: . done
SunnyValley repository update completed. 2 packages processed.
Updating pfSense-core repository catalogue...
Fetching meta.conf:
Fetching packagesite.pkg:
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf:
Fetching packagesite.pkg:
pfSense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):Installed packages to be UPGRADED:
zenarmor-agent: 1.16.6 -> 1.17 [SunnyValley]Number of packages to be upgraded: 1
The process will require 80 MiB more space.
74 MiB to be downloaded.
[1/1] Fetching zenarmor-agent-1.17.pkg: .......... done
Checking integrity... done (1 conflicting)
- zenarmor-agent-1.17 [SunnyValley] conflicts with zenarmor-1.16.4 [installed] on /usr/local/zenarmor/db/Cloud/cloud.db.all
Checking integrity... done (0 conflicting)
Conflicts with the existing packages have been found.
One more solver iteration is needed to resolve them.
The following 2 package(s) will be affected (of 0 checked):Installed packages to be REMOVED:
zenarmor: 1.16.4Installed packages to be UPGRADED:
zenarmor-agent: 1.16.6 -> 1.17 [SunnyValley]Number of packages to be removed: 1
Number of packages to be upgraded: 1The operation will free 25 MiB.
[1/2] Deinstalling zenarmor-1.16.4...
[1/2] Deleting files for zenarmor-1.16.4: .......... done
[2/2] Upgrading zenarmor-agent from 1.16.6 to 1.17... -
Does Zenarmor has some sort of big network problem, because all of their services from Finland are slow as hell, I cannot update any packages etc, even the webpages are slow, I cannot access the Dash through web browser etc.
Example of package download problems:
[1/1] Fetching os-sensei-1.17.pkg: 1% 856 KiB 8.2kB/s 01:00:44 ETA -
Pinging dash.zenarmor.com [104.26.9.148] with 32 bytes of data:
Reply from 104.26.9.148: bytes=32 time=76ms TTL=60
Request timed out.
Reply from 104.26.9.148: bytes=32 time=76ms TTL=60
Reply from 104.26.9.148: bytes=32 time=81ms TTL=60
Request timed out.
Reply from 104.26.9.148: bytes=32 time=84ms TTL=60
Reply from 104.26.9.148: bytes=32 time=73ms TTL=60
Reply from 104.26.9.148: bytes=32 time=72ms TTL=60
Request timed out.
Reply from 104.26.9.148: bytes=32 time=80ms TTL=60
Reply from 104.26.9.148: bytes=32 time=80ms TTL=60
Reply from 104.26.9.148: bytes=32 time=81ms TTL=60
Request timed out.
Request timed out.
Reply from 104.26.9.148: bytes=32 time=90ms TTL=60
Request timed out.
Request timed out.Ping statistics for 104.26.9.148:
Packets: Sent = 17, Received = 10, Lost = 7 (41% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 90ms, Average = 79ms
Something is really wrong, I can ping just fine any other IP address currently without any loss. -
You need to access the firewall via SSH, PuTTY program for example.
Log in to the firewall, choose option 8 to open the Shell and type the zenarmor installation command.
curl https://updates.sunnyvalley.io/getzenarmor | sh
This last command to register with the zenarmor account has been changed:
rehash
/usr/local/bin/zenarmorctl cloud registerThen go to Zenconsole, refresh the page, click on the firewall which will ask you to restart the engine.
-
Hi Sandro, thank you very much - successful back in operation.
The Zenarmor Helpdesk requested all information via UI to investigate my installation. This was not possible, as I could not access my Firewall. So your way getting back in operation was the answer, I should have been given by the Zenarmor Helpdesk.
Please sign in to leave a comment.
Comments
8 comments