[Workaround] Segmentation fault while installing 18.1 on a new hardware

[elektroinside]

If you're installing OPNsense 18.1 on a new hardware and the installer crashes with "Segmentation fault (core dumped)" no matter what you try (mbr or uefi, disabling safety features from the BIOS etc.):

1. This is because of FreeBSD 11.1
2. To get around this error, install OPNsense 17.7 first, then upgrade to 18.1
3. If the scope was a clean install, well...: after upgrading to 18.1, install your plugins first, then import your 18.1 settings

[Werner Fischer]

Another workaround:

I have now also come across this error. It happens immediately after choosing the "GPT/UEFI mode" as seen on https://www.thomas-krenn.com/de/wikiDE/images/6/60/OPNsense-Installation-06-Select-install-mode.png

Attached is a screen-shot of the error (you need to log in into the forum to view attachments).

As you can see, the login prompt is shown after the error message. When you then log in again using the "installer" user and the password "opnsense", I find myself again on the screen to choose the install mode. When I then choose again "GPT/UEFI mode", the installation continues and the system runs fine then.

Does anybody know what exactly causes this error and if this could be fixed somehow (so that no workaround is necessary)?

[franco]

Assuming this is more or less console-related fault killing the process because the whole session is killed.... but what you can see here from the login prompt the installer runs in a client-server mode, where the client is the "frontend" graphical menu installer that gets disconnected from the "backend" actual worker.

It should be possible to trace this installer frontend invoke to see why it is crashing for anyone who can reproduce this?

https://github.com/opnsense/core/blob/master/src/etc/rc.installer#L44

Does this error also happen for when the installer is used by SSH? Because it would be unlikely. :)


Cheers,
Franco

[Werner Fischer]

Thank you for your answer Franco (sorry for being late with my reply)

I happens when I run the installer locally (not via SSH).

I did not understand how I could trace it / what steps I should do to trace it.

I could run tests on Friday when you write me the commands which I should run.

Best regards,
Wwerner

[franco]

Hi Werner,

The output of "dmesg" and "/tmp/installer.log" would suffice right after this crash happens.


Thanks!
Franco

[Thomas Niedermeier]

Hi Franco,

I did the tests for Werner and you'll find the output of dmesg and installer.log attached to my post.
I hope these two files help to fix the problem.

Cheers,
Thomas