Unsolved Fedora Server for production use?
-
@scottalanmiller said in Fedora Server for production use?:
It's only a memory check, not an actual technical issue. I would go ahead with it.
A check in the kernel phase? It happens right after choosing the kernel command line.
-
@thwr said in Fedora Server for production use?:
@scottalanmiller said in Fedora Server for production use?:
It's only a memory check, not an actual technical issue. I would go ahead with it.
A check in the kernel phase? It happens right after choosing the kernel command line.
It has to be in the installer.
-
@scottalanmiller said in Fedora Server for production use?:
@thwr said in Fedora Server for production use?:
@scottalanmiller said in Fedora Server for production use?:
It's only a memory check, not an actual technical issue. I would go ahead with it.
A check in the kernel phase? It happens right after choosing the kernel command line.
It has to be in the installer.
That's what I thought. So the kernel panic is likely caused by something else.
-
Raised the VMs memory to 1GB, did a text mode install, as suggested.
But the "blank" system alone is already using 256MB of RAM. There's some kind of management webserver installed and lots of other processes running in the background.
-
This is going to be one of these days...
Currently installing Ubuntu 16.04.1 using the ~700MB server ISO. It won't find the installation source mount point when I try to run the machine with just 256MB...
Works fine with 512MB.
-
@thwr said in Fedora Server for production use?:
Raised the VMs memory to 1GB, did a text mode install, as suggested.
But the "blank" system alone is already using 256MB of RAM. There's some kind of management webserver installed and lots of other processes running in the background.
Cockpit. You have to "leanify" Fedora.
-
@thwr said in Fedora Server for production use?:
This is going to be one of these days...
Currently installing Ubuntu 16.04.1 using the ~700MB server ISO. It won't find the installation source mount point when I try to run the machine with just 256MB...
Works fine with 512MB.
Why an old version? Current has the best chance of success and for production use, support is critical so that should rule out the older versions that are limited support.
-
@scottalanmiller said in Fedora Server for production use?:
@thwr said in Fedora Server for production use?:
This is going to be one of these days...
Currently installing Ubuntu 16.04.1 using the ~700MB server ISO. It won't find the installation source mount point when I try to run the machine with just 256MB...
Works fine with 512MB.
Why an old version? Current has the best chance of success and for production use, support is critical so that should rule out the older versions that are limited support.
Because it's the current stable LTS release.
-
Ubuntu 16.04.1, not yet updated. Looks way better.
-
@thwr said in Fedora Server for production use?:
@scottalanmiller said in Fedora Server for production use?:
@thwr said in Fedora Server for production use?:
This is going to be one of these days...
Currently installing Ubuntu 16.04.1 using the ~700MB server ISO. It won't find the installation source mount point when I try to run the machine with just 256MB...
Works fine with 512MB.
Why an old version? Current has the best chance of success and for production use, support is critical so that should rule out the older versions that are limited support.
Because it's the current stable LTS release.
That's not a reason. LTS is not the fully supported product from Canonical. There is nothing current about 16.04. 16.10 is the only fully supported Ubuntu product today. If this is for production, you need support. Don't skip support just to get an LTS moniker. LTS is three letters, it is not a support agreement.
-
You're right. Just had the ISO here and didn't thought about the 16.10 release.
-
The trick in the wording is that 16.04 is "partial" support for two years, while "current" gets full support for 6-9 months. So for full support, it's a twice a year release process. If limited or partial support (security stuff gets patched, they will help when stuff is easy) is enough, LTS can suffice. But since current gets total support (including bugs you find, stability issues and such that are not covered with LTS) and you get the latest technology, it's a win/win.
-
@thwr said in Fedora Server for production use?:
Interesting: Fedora 25 starts to panic with RAM < 512MB at the beginning of the kernel init phase, even in text mode. Just had a look at the manual which clearly says that Fedora requires 1GB of RAM.
Looks like I'm out of luck and have to stick to Ubuntu / Debian.
Another thing to note is with RHEL/CentOS 7.3 they recommend a 1GB boot partition instead of 512MB.
Just an aside.
-
@stacksofplates said in Fedora Server for production use?:
@thwr said in Fedora Server for production use?:
Interesting: Fedora 25 starts to panic with RAM < 512MB at the beginning of the kernel init phase, even in text mode. Just had a look at the manual which clearly says that Fedora requires 1GB of RAM.
Looks like I'm out of luck and have to stick to Ubuntu / Debian.
Another thing to note is with RHEL/CentOS 7.3 they recommend a 1GB boot partition instead of 512MB.
Just an aside.
Should work as long as you keep an eye on it. Ubuntu for example likes to keep old kernel and initrd images there until you clean them up (e.g. apt autoclean etc)
-
@thwr said in Fedora Server for production use?:
@stacksofplates said in Fedora Server for production use?:
@thwr said in Fedora Server for production use?:
Interesting: Fedora 25 starts to panic with RAM < 512MB at the beginning of the kernel init phase, even in text mode. Just had a look at the manual which clearly says that Fedora requires 1GB of RAM.
Looks like I'm out of luck and have to stick to Ubuntu / Debian.
Another thing to note is with RHEL/CentOS 7.3 they recommend a 1GB boot partition instead of 512MB.
Just an aside.
Should work as long as you keep an eye on it. Ubuntu for example likes to keep old kernel and initrd images there until you clean them up (e.g. apt autoclean etc)
Ya I usually keep 3 and remove the others but I think the images are getting big enough they needed to adjust the size. If you do anew install it defaults to 1GB.
