OS: Debian / Ubuntu (64bit)
Virtualmin: Latest
VPS 64bit (AMD EPYC) 4core / 4GB RAM / 400GB SSD
Hello, Why i’m getting this Segmentation Fault error only installing on x64 bit OS but not for 32bit OS on my server.
I have tried many time to reinstall with no luck.
It appears from the screenshot that ProFTP is triggering the Segmentation Fault error. If you install Virtualmin with the minimal option, it should skip ProFTP (I think).
Having said that, Virtualmin should install without error on any freshly installed Debian or Ubuntu OS version which is supported. See
Hello @calport and thank you for your input.
Is it a good idea to just ignore this error and complete my installation of the virtualmin and later on i will manually try to install ProFTP?
I don’t really want to minimal installation because i need most features on virtualmin.
any advice?
Thank you
Yes and no.
Yes because I have been successful in ignoring errors during installation, particularly errors after Phase 3, by running a Recheck Configuration after Virtualmin is installed.
And no because one really should install Virtualmin without error on a public facing production system, if one wishes to sleep peacefully at night.
It is trivial to bump up a minimal install of Virtualmin if you have another Virtualmin system to which you could refer.
I don’t have another. let me try to do a minimal installation first and move frwards from there.
I’ve had some success in just re-running the install script. But a segmentation fault on configure seems strange.
@ID10T You mean uninstalling Virtualmin and reinstalling on the same OS or completely reinstall the OS and then reinstalling Virtualmin?
Completely reinstall the OS and then reinstall Virtualmin, because Virtualmin always needs a freshly installed OS as per the documentation but if @ID10T has been able to re-run the install script then this is a revelation.
I just did a fresh OS and re install still the same issue.
i cannot uninstall virtualmin using this command “sh: 0: Can’t open virtualmin-install.sh”
Error: sh: 0: Can’t open virtualmin-install.sh
I use this to install virtualmin: sudo sh -c “$(curl -fsSL https://software.virtualmin.com/gpl/scripts/virtualmin-install.sh)” – --bundle LAMP
Okay, I finally managed to get it installed without any issues. I didn’t run the online command; instead, I had to download the installation file and run it from there.
Well done, @anthonyinit2012
That is an interesting workaround that you have thought of.
--minimal install still has ProFTPd (it was added back, as making changes like that during a major release cycle is something that shouldn’t happen)
@anthonyinit2012 This is not specific to ProFTPd, and installation of the packages, including ProFTPd, completed successfully…your errors are in the configuration stage.
I’ve never seen this problem before, and I’ve done install on Debian 12 on x86_64 quite recently. All of our configuration code is in Perl, so a segfault is something that should be impossible without a bug in Perl or some library Perl is depending on.
I want to suggest this is not a clean freshly installed Debian 12 system. Something else has been installed or done before running the installer. It could also be a container-based system like Virtuozzo or OpenVZ with oversold memory or other resources (but I would have expected it to fail during phase 3, first, because apt grows quite large when installing a bunch of packages).
But, it’s almost certainly not something we caused or can solve (since we have done several recent test installs on Debian 12, and we know it works).
It’s not clear to me what you did different. But, it’s also possible you just got lucky this time.
Were the segfaults always in the exact same steps before or did they change sometimes?
Maybe i got luck. but all i did was install on a clean system. i’m having a VPS on Contabo and they have a system to reinstall OS. this only happens when i try to install (64Bit) OS only.
I’m pretty sure all of those non-labeled systems are also 64-bit. AlmaLinux and Rocky 9 aren’t even available in a 32-bit build, AFAIK, so I suspect the labeled ones are just old enough to have 32 bit versions that did exist. You should not use an old OS (Debian 11 and Ubuntu 20.04 are old, do not install a new system on those systems).
I understand. I already got another warning on the panel.
I will try to reinstall OS with the latest Ubuntu.
Let me see
Oh no! This system is not freshly installed! You already have Webmin installed. Don’t do that. Hosting providers always fuck it up when you let them install stuff. Do not get an image that already has Webmin or Virtualmin (I wish I didn’t have to say this, I wish it was easy to just choose to get Virtualmin preinstalled, but hosting providers are incapable of following our documentation for doing it, so it’s always broken in crazy ways, I don’t know why).
In short: Get a freshly installed supported OS. Nothing preinstalled. Nothing weird. No Apache, no LAMP stack, nothing your host thinks you might want, and no Webmin (the Virtualmin installer installs everything you need…you can start with a quite minimal OS installation, as long as the package manager works and the base OS is there, the installer will pull in all the rest).
Contabo have two customer control panel one is the old panel and the other is the new beta panel. i never wanted to use the new panel because it is still in beta stage however, in that i get to select all the newer OS while the old one is limited and have only the older OS to select.
I used the new New Customer Panel and select the newest Ubuntu version they have and installed it after ran the virtualmin installation and i was able to get it install without any issue.
Finally I’m satisfied
