[SOLVED] How to rollback from 21.1.7_1 due to a major issue??

[hakuna]

Hi guys,

Since the update, the update section is dead and somehow stuck!





It seems like I am supposed to run: opnsense-revert -kr 20.1
But I am not sure.

I really appreciate any help. I've been unable to get any help on how to solve this.

Thanks

[franco]

Hi there,

First things first: why do you think it's stuck? It's not rebooting? How about rebooting it via that fancy shell menu you got there?


Cheers,
Franco

[hakuna]

Hi franco,

No matter what I do I can no longer access the update section.
I have rebooted the baremetal dozens of times, I have tried to update via the terminal and I always receive the message "A firmware action is currently in progress."

Other users have had the same issues which seem to be a bug with the browser caching and a new feature released into this 21.1.7.
I have tried to clean up everything but it is still the same.

It is frustrated coz it is broken, I have no idea how to fix and nobody seems to be able to help.
I have asked here, Reddit, paste everything and nothing.

Thank you for replying anyway.

[hakuna]

Problem solved!

Everything was screwed anyways so I went radical, backup checked and that is it.

While checking general log, there were dozens of lines "error in configd communication Traceback (most recent call last): File "/usr/local/opnsense/service/configd_ctl.py", line 68, in exec_config_cmd line = sock.recv(65536).decode() socket.timeout: timed out"

After some Google, it was somehow related to Sensei.
I try to access it and indeed it was crashed like all pages were empty so I used the uninstall option within it to remove everything.

Then I try opensense-update via terminal and few packages was gonna be removed, that was a win already.

I try option 12 and got the same "A firmware action is currently in progress."

Then I did a pkg update -f and why not force the upgrade??
So I did "pkg upgrade -f" and received "The following 137 package(s) will be affected (of 0 checked)"

A big F yes, I have nothing to lose anyway, reboot the router after all and everything is back online.

Fun fact, since 2 updates ago, I could not longer ssh with my users, I had to enable root to ssh the router.
After all the mess above, my user is back and the root user automatically got blocked from ssh the router.

At least everything is working as expected now. F finally.

I hope this help someonw.

[almodovaris]

If you use Sensei in bridge mode you need two WAN ports