[SOLVED] OpenVPN will not start on 18.1.r1

[elektroinside]

Sure thing Franco, whenever you feel like it.
Well, so far so good, 5+ reboots, no failures as of yet. I'll stick with this version until r2, unless you want me to try out something else.
I'll build a vm as well later, but that will not help as much with the pppoe issue, as access to my rack is a bit difficult (to change cables and stuff).

Thanks again for everything!

[elektroinside]

Hi Franco,

Unfortunately the pf restart issue happened again. I'm on my way to a client so logs later, also i got a feeling that i accidentally updated to r1. I'll report back once i'm done with the client.

Thanks

[elektroinside]

Can't collect the logs, I forgot to apply the aliases patch, can't connect to my box (remotely).

[franco]

18.1.r2 will be out tonight... that should make the patching unnecessary.


Cheers,
Franco

[elektroinside]

Just upgraded to 18.1.r2  ;D

Didn't need to restart pf, OpenVPN working, but aliases still don't work, unfortunately.. There's no /var/db/aliastables until manually refreshed from the console..

Once manually refreshed, even though i had a cron job to refresh them every minute, they still didn't, i had to manually refresh again.

[franco]

Ok, progress is progress. :)

Can you provide the output for:

# df -h

Aliases are still on my list.


Thanks,
Franco

[elektroinside]

Here you go:

Filesystem         Size    Used   Avail Capacity  Mounted on
/dev/gpt/rootfs     38G    7.2G     28G    21%    /
devfs              1.0K    1.0K      0B   100%    /dev
tmpfs               22G    194M     22G     1%    /var
tmpfs               22G    360K     22G     0%    /tmp
devfs              1.0K    1.0K      0B   100%    /var/dhcpd/dev

[franco]

Aha, /var MFS clears /var/db/aliastables for sure.

Ok, I don't know why Ad changed the behaviour but let's move the alias database to the persistent location...

https://github.com/opnsense/core/commit/6536510

When you apply this patch the next reboot won't work again and you can fix it manually, after that the reboots should not interrupt operation anymore.


Cheers,
Franco

[elektroinside]

Franco, i think it worked! Very well done!!  :)

Thank you!

[franco]

Okay, thank you for confirming. :)

The initial migration could still be tricky coming from 17.7... This will probably be subject to change once we move into 18.1.x or it must be documented in the 18.1 migration notes.


Cheers,
Franco

[elektroinside]

Of course, any time.

Yes, well documentation is important, of course, but testing these particular changes i guess will require just a few vms and some time. I'll build a few vms myself very soon, so i will be able to test the upgrade/update, and i'll report if i find something.