Can’t update 23.7.7

[guest40773]

Can’t update to 23.7.7 it says OpenSSL is conflicting with OpenSSL “Installing files to same place” and then it stops me from updating any packages and stops the entire process. I just got this a few days ago so I didn’t want to go pushing things and trying things if all I need to do is wait and try again.

[guest40773]

Can anyone please point me in the right direction? I think I see a fix but I don’t want to tinker with anything if all I have to do is wait a little bit until they work the bugs out.


Please and Thank you.

[guest40773]

Nvm. I reinstalled a cpud package or whatever and then it let me update.

[franco]

Posting the log would help. Guess work in support is no fun.

Over the last two days we've put a few hotfixes out to ease into the new "openssl111" world. It wasn't my favourite change but since we follow FreeBSD ports very closely we had to do it.


Cheers,
Franco

[@lex]

Same problem here.

Error due to SSL 1.1.1 then update failed.

I have tried the update again to be able to copy the logs, it passed, seemed to have worked but no more routing since reboot.

I cannot post logs as I am writing this from my phone.

What can I do?

The GUI works OK, but no packet routing and CPU load is super high, used by Python3.9.

[milkywaygoodfellas]

Same problem here.

Error due to SSL 1.1.1 then update failed.

I have tried the update again to be able to copy the logs, it passed, seemed to have worked but no more routing since reboot.

I cannot post logs as I am writing this from my phone.

What can I do?

The GUI works OK, but no packet routing and CPU load is super high, used by Python3.9.

I don't have high CPU load, but I did get the error about OpenSSL conflicting with itself. Tried again and the update installed, but now Python 3.9 keeps crashing and Unbound blocking reporting doesn't seem to be working anymore.

[milkywaygoodfellas]

Logs full of these errors every time I try to reset the logging for unbound. It works for a few minutes, then the graphs just all go to zero until the logger is restarted somehow (I usually do this by just clicking "save" on the DHCPv4 service).

[franco]

SIGABRT? I would recommend resetting the database and hope that the disk itself isn't failing.


Cheers,
Franco

[milkywaygoodfellas]

SIGABRT? I would recommend resetting the database and hope that the disk itself isn't failing.


Cheers,
Franco

Thanks, Franco. I checked the SMART status of the disk and it is passing, so maybe it's the database problem. How would I reset that? I'm unsure to which database you are referring.

[franco]

Reporting: Settings: Unbound DNS reporting: Reset DNS data

At least that is the one it complains about. It fills the graphs for Reporting: Unbound DNS but if you don't need those you could also turn if off as well (from the settings page) to save energy and your disk.


Cheers,
Franco

[milkywaygoodfellas]

Reporting: Settings: Unbound DNS reporting: Reset DNS data

At least that is the one it complains about. It fills the graphs for Reporting: Unbound DNS but if you don't need those you could also turn if off as well (from the settings page) to save energy and your disk.


Cheers,
Franco

Thanks! I reset that and the reporting seems to be working again.

[rwo97215]

I am also having a problem updating from 27.7.6 to 27.7.7_3. Update log file and health audit are attached.