Upgrade to 20.7 fails

[niclasc]

I'm trying to upgrade from 20.1.9 to 20.7. After all packages are extracted (installed?) the system hangs at:

Configuring system logging...done

If I press ctrl-c it continues and then stops at:

Starting NTP service...deferred

If I press ctrl-c there it just boots to 20.1.9

I'm running Opnsense as a VM in ESXi

Any Idea how to fix this?

[niclasc]

No help on this??

Tried to update once more today and I get stuck on the same part

[ssnell]

I'll chime in that I appear to be hitting the same roadblock. I'm using ESX to host testing VMs with OPNSense being one of them. I installed a fresh copy earlier today from the latest provided ISO and after a successful installation I then went to check for updates and install them. During the update installation everything appears to go well until the end when it gets stuck at "Configuring system logging...done." I'm running ESX 6.7 with the VM options set to FreeBSD12. How does your ESX setup compare?

[esh]

The same is happening for me with a physical machine - an Intel i3-7100 with 8 GB RAM.
I noticed that a core dump was produced at /syslog-ng.core around the time of the hang. Possibly related?

[DoomRoman]

Hello,
I'm having the same issue!
I have a fresh installation of opnsense 20.7 (nano-image) and am trying to update to 20.7.3, because I have huge problems with the kernel panic and vpanic..

I've installed it on an Quotom (hardware: i3 and 16gb RAM, 64GB mSSD), an other hardware (i3, 8gb RAM, 30gb mSSD) and on esxi (5.6 and 7). But I have the same problem on every device.

I'd be grateful, if anyone could solve this problem.

Thanks and regards
Roman

[littlepepper]

@DoomRoman you might want to refer to this thread https://forum.opnsense.org/index.php?topic=19175.0 and install the kernel which is in testing phase.

[thijs_a]

Hello,

I was having the same issue when upgrading. I am also using ESXI.

I managed to work around the issue by installing the upgrade as usual and when it hangs at Configuring system logging...done, I clicked the stop icon at the syslog-ng service on the dashboard. Later during the upgrade, you need to do this again when it hangs at the same message. After that, the upgrade completed successfully.

Hope this helps,
Thijs

[DoomRoman]

I have a similar hotfix.
After the update interrupted at "configurated logging", i rebooted opnsense from the ui and restarted dthe update.
Now it made a full update to 20.7.3 and the health-check was fine.

[gex]

thanks @Thijs! that helped

Hello,

I was having the same issue when upgrading. I am also using ESXI.

I managed to work around the issue by installing the upgrade as usual and when it hangs at Configuring system logging...done, I clicked the stop icon at the syslog-ng service on the dashboard. Later during the upgrade, you need to do this again when it hangs at the same message. After that, the upgrade completed successfully.

Hope this helps,
Thijs

[Deku]

I'm also failing to upgrade my ESXi guest from 20.1 to 20.7.  The system just keeps rebooting over and over.  I didn't have any hangs on configurated logging.  It appeared to upgrade fine prior to going into a loop.

[pablo]

Hey everyone,

In my VirtualBox test bed, I had to repeatedly stop syslog-ng for the upgrade from 20.7 to 20.7.3 to complete.

With one browser driving the upgrade, I used a second browser to stop syslog-ng from restarting.

I clog -f'd /var/log/system.log and when syslog would restart, I'd use the second browser to stop it. 

The recipe was the following:

1) Stop syslog-ng in browser #2
2) clog -f /var/log/system.log in a shell
3) Start the upgrade from 20.7 to 20.7.3 in browser #1
4) When I see syslog restarting in the shell, use browser #2 to stop it again
5) Watch the upgrade press on in browser #1
6) Repeat 4) and 5) until done

To confirm all went well, I did an audit after the upgrade completed.

Thx!
-pablo

[Demo_User]

While running upgrade I ran into the same issue on a Protectli device.

I only stopped the service "syslogd Legacy Syslog Daemon" which also sopped the service "syslog-ng Syslog-ng Daemon".

Once both of the services were stopped the upgrade ran the rest of the way without issue.