Difference between pages "Package:Monit" and "Install/BootLoader"

(Difference between pages)
 
(Emerging GRUB)
 
Line 1: Line 1:
{{Ebuild
+
<noinclude>
|Summary=a utility for monitoring and managing daemons or similar programs running on a Unix system.
+
{{InstallPart|boot loader configuration}}
|CatPkg=app-admin/monit
+
</noinclude>
|Maintainer=
+
=== Installing a Bootloader ===
}}
+
[http://mmonit.com/monit/ Monit] is a utility for managing and monitoring processes, programs, files, directories and filesystems on a UNIX system.
+
  
== Installation ==
+
These install instructions show you how to use GRUB to boot using BIOS (old-school) or UEFI (new-school).
=== Emerge ===
+
To install {{Package|app-admin/monit}}:
+
<console>###i## emerge monit</console>
+
  
== Configuration ==
+
==== Old School (BIOS) ====
Config file of monit resides in <tt>/etc/monitrc</tt>. And there is a item to specify a config directory. Uncomment if needed.
+
  
{{File|name=/etc/monitrc|desc=config dir|body=
+
If you're using the BIOS to boot, setting up GRUB, the bootloader, is pretty easy.
## It is possible to include additional configuration parts from other files or
+
## directories.
+
#
+
#  include /etc/monit.d/*
+
#
+
}}
+
  
=== Users ===
+
To use this recommended boot method, first emerge <code>boot-update</code>. This will also cause <code>grub-2</code> to be merged, since it is a dependency of <code>boot-update</code>.
Users added to the monit or users group will be able to manipulate monit through the web interface.
+
  
<console>###i## gpasswd -a $USER monit</console>
+
<console>
<console>###i## gpasswd -a $USER users</console>
+
(chroot) # ##i##emerge boot-update
 +
</console>
  
{{fancywarning|passwords can be streamed to monits web interface, disable it all together after it is setup}}
+
Then, edit <code>/etc/boot.conf</code> and specify "<code>Funtoo Linux genkernel</code>" as the <code>default</code> setting at the top of the file, replacing <code>"Funtoo Linux"</code>.
  
{{fancyimportant|for security purposes change this entry}}
+
<code>/etc/boot.conf</code> should now look like this:
  
{{file|name=/etc/monitrc|desc=|body=
+
<pre>
allow admin:monit}}
+
boot {
 +
generate grub
 +
default "Funtoo Linux genkernel"
 +
timeout 3
 +
}
  
== Boot Services ==
+
"Funtoo Linux" {
=== inittab ===
+
kernel bzImage[-v]
{{fancynote|this is the preferred method to run monit}}
+
}
{{file|name=/etc/inittab|desc=auto restart monit in case of failure|body=
+
ca:12345:ctrlaltdel:/sbin/shutdown -r now
+
  
# Run monit in standard runlevels
+
"Funtoo Linux genkernel" {
mo:2345:respawn:/usr/bin/monit -Ic /etc/monitrc
+
kernel kernel[-v]
 +
initrd initramfs[-v]
 +
params += real_root=auto
 +
}
  
# Used by /etc/init.d/xdm to control DM startup.
+
"Funtoo Linux better-initramfs" {
}}
+
kernel vmlinuz[-v]
 +
initrd /initramfs.cpio.gz
 +
}
 +
</pre>
  
to start monit immediately after changing inittab
+
Please read <code>man boot.conf</code> for further details.
  
<console>###i## telinit q</console>
+
===== Running grub-install and boot-update =====
  
=== OpenRC ===
+
Finally, we will need to actually install the GRUB boot loader to your disk, and also run <code>boot-update</code> which will generate your boot loader configuration file:
{{fancynote|prefer inittab method over rc services}}
+
To start the service at boot.
+
<console>###i## rc-update add monit default</console>
+
To start the service immediately.
+
<console>###i## /etc/init.d/monit start</console>
+
  
==== Monitoring Monit ====
+
<console>
This hourly cron script will check to make sure monit has not crashed.  As this uses pgrep, make sure to not name it monit.
+
(chroot) # ##i##grub-install --no-floppy /dev/sda
 +
(chroot) # ##i##boot-update
 +
</console>
  
{{file|name=/etc/cron.hourly/moncheck|desc=|body=
+
Now you need to update your boot loader configuration file:
#!/bin/bash
+
<console>
if ! pgrep monit >/dev/null;then
+
(chroot) # ##i##boot-update
rc-service monit restart
+
</console>
fi
+
You only need to run <code>grub-install</code> when you first install Funtoo Linux, but you need to re-run <code>boot-update</code> every time you modify your <code>/etc/boot.conf</code> file, so your changes are applied on next boot.
}}
+
  
== Pidfile Check ==
+
==== New School (UEFI) ====
Monit relies upon pid files. For daemons that do not create a pidfile: a [http://mmonit.com/wiki/Monit/FAQ#pidfile work around] is needed.
+
  
== Examples ==
+
If you're using UEFI to boot, setting up the boot loader is a bit more complicated for now, but this process will be improving soon. Perform the following steps.
=== Auto Restart Mysql ===
+
 
{{file|name=/etc/monitrc|desc=auto restart mysql|body=
+
===== Emerging GRUB =====
check process mysql with pidfile /var/run/mysqld/mysqld.pid
+
 
    start program = "/bin/bash -c 'rc-service mysql start'"
+
You will still use GRUB as a boot loader, but before emerging grub, you will need to enable EFI booting. To do this,
    stop program  = "/bin/bash -c 'rc-service mysql stop'"
+
add the following line to <code>/etc/make.conf</code>:
 +
 
 +
For x86-64bit systems:
 +
 
 +
<pre>
 +
GRUB_PLATFORMS="efi-64"
 +
</pre>
 +
 
 +
For x86-32bit systems:
 +
 
 +
<pre>
 +
GRUB_PLATFORMS="efi-32"
 +
</pre>
 +
 
 +
Then, <code>emerge boot-update</code>. You will notice <code>grub</code> and <code>efibootmgr</code> getting pulled in as dependencies. This is expected and good:
 +
 
 +
<console>
 +
(chroot) # ##i##emerge boot-update
 +
</console>
 +
 
 +
===== Installing GRUB =====
 +
 
 +
Now, for the magic of getting everything in place for booting. You should copy your kernel and initramfs (if you have one -- you will if you are following the default install) to <tt>/boot</tt>. GRUB will boot those. But how do we get UEFI to boot GRUB? Well, we need to run the following command (for 32 bit simply set it as i386-efi):
 +
 
 +
<console>
 +
(chroot) # ##i##grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda
 +
</console>
 +
This command will simply install all the stuff to <tt>/boot/EFI</tt> and <tt>/boot/grub</tt> that your system needs to boot. In particular, the <tt>/boot/EFI/grub/grubx64.efi</tt> file will be created. This is the GRUB boot image that UEFI will load and start.
 +
 
 +
A more detailed explanation of the flags used in the above command:
 +
* <code>--target=x86_64-efi</code>: Tells GRUB that we want to install it in a way that allows it to boot in UEFI
 +
* <code>--efi-directory=/boot</code>: All GRUB UEFI files will be installed in ''/boot''
 +
* <code>--bootloader-id="Funtoo Linux [GRUB]"</code>: This flag is not necessary for GRUB to boot. However, it allows you to change the text of the boot option in the UEFI BIOS. The stuff in the quotes can be set to anything that you would like.
 +
* <code>--recheck</code>: If a device map already exists on the disk or partition that GRUB is being installed on, it will be removed.
 +
* <code>/dev/sda</code>:The device that we are installing GRUB on.
 +
 
 +
===== Configuring GRUB =====
 +
 
 +
OK, now UEFI has the GRUB image it needs to boot. But we still need to configure GRUB itself so it finds and boots your kernel and initramfs. This is done by performing the following steps. Since boot-update doesn't yet support UEFI, we will use boot-update, but then edit our <code>/boot/grub/grub.cfg</code> to support UEFI booting.
 +
 
 +
First, you will need to edit <code>/etc/boot.conf</code>. Format this as you would if you were booting without UEFI. If you are not sure how this should look, below is an example of what it could look like if you are booting from an unencrypted ext4 partition:
 +
 
 +
{{file|name=/etc/boot.conf|desc=|body=
 +
boot {
 +
        generate grub
 +
        default "Funtoo Linux"
 +
        timeout 3
 +
}
 +
 
 +
"Funtoo Linux" {
 +
        kernel vmlinuz[-v]
 +
        params += rootfstype=ext4 root=/dev/sda2
 +
}
 
}}
 
}}
  
== Web Interface ==
+
After you have edited your <code>/etc/boot.conf</code> file, run <code>boot-update</code>. You should now have a <code>/boot/grub/grub.cfg</code> file, which you can edit using the following command:
 +
 
 +
<console>
 +
# ##i##nano /boot/grub/grub.cfg
 +
</console>
 +
 
 +
 
 +
To get your <code>/boot/grub/grub.cfg</code> to support booting with UEFI, make the following changes. Below the existing insmod lines, add the following lines.  Both of these involve adding support for the UEFI framebuffer to GRUB.:
 +
 
 +
<pre>
 +
  insmod efi_gop
 +
  insmod efi_uga
 +
</pre>
 +
 
 +
Then, change the <code>set gfxpayload</code> line to read as follows. UEFI does not support text mode, so we will keep video initialized to the current resolution.:
  
Navigate to http://localhost:2812/ & login using your edited configuration line or admin / monit if you have not changed it yet.
+
<pre>
 +
  set gfxpayload=keep
 +
</pre>
  
[[Category:Monitoring]]
+
You can now save your changes by pressing <code>Control-X</code> and answering <code>y</code> when asked if you want to save the modified buffer. When prompted for a filename, hit Enter to use the existing filename.
{{EbuildFooter}}
+

Revision as of 19:48, January 1, 2015


Note

This is a template that is used as part of the Installation instructions which covers: boot loader configuration. Templates are being used to allow multiple variant install guides that use most of the same re-usable parts.


Installing a Bootloader

These install instructions show you how to use GRUB to boot using BIOS (old-school) or UEFI (new-school).

Old School (BIOS)

If you're using the BIOS to boot, setting up GRUB, the bootloader, is pretty easy.

To use this recommended boot method, first emerge boot-update. This will also cause grub-2 to be merged, since it is a dependency of boot-update.

(chroot) # emerge boot-update

Then, edit /etc/boot.conf and specify "Funtoo Linux genkernel" as the default setting at the top of the file, replacing "Funtoo Linux".

/etc/boot.conf should now look like this:

boot {
	generate grub
	default "Funtoo Linux genkernel" 
	timeout 3 
}

"Funtoo Linux" {
	kernel bzImage[-v]
}

"Funtoo Linux genkernel" {
	kernel kernel[-v]
	initrd initramfs[-v]
	params += real_root=auto 
} 

"Funtoo Linux better-initramfs" {
	kernel vmlinuz[-v]
	initrd /initramfs.cpio.gz
}

Please read man boot.conf for further details.

Running grub-install and boot-update

Finally, we will need to actually install the GRUB boot loader to your disk, and also run boot-update which will generate your boot loader configuration file:

(chroot) # grub-install --no-floppy /dev/sda
(chroot) # boot-update

Now you need to update your boot loader configuration file:

(chroot) # boot-update

You only need to run grub-install when you first install Funtoo Linux, but you need to re-run boot-update every time you modify your /etc/boot.conf file, so your changes are applied on next boot.

New School (UEFI)

If you're using UEFI to boot, setting up the boot loader is a bit more complicated for now, but this process will be improving soon. Perform the following steps.

Emerging GRUB

You will still use GRUB as a boot loader, but before emerging grub, you will need to enable EFI booting. To do this, add the following line to /etc/make.conf:

For x86-64bit systems:

GRUB_PLATFORMS="efi-64"

For x86-32bit systems:

GRUB_PLATFORMS="efi-32"

Then, emerge boot-update. You will notice grub and efibootmgr getting pulled in as dependencies. This is expected and good:

(chroot) # emerge boot-update
Installing GRUB

Now, for the magic of getting everything in place for booting. You should copy your kernel and initramfs (if you have one -- you will if you are following the default install) to /boot. GRUB will boot those. But how do we get UEFI to boot GRUB? Well, we need to run the following command (for 32 bit simply set it as i386-efi):

(chroot) # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda

This command will simply install all the stuff to /boot/EFI and /boot/grub that your system needs to boot. In particular, the /boot/EFI/grub/grubx64.efi file will be created. This is the GRUB boot image that UEFI will load and start.

A more detailed explanation of the flags used in the above command:

  • --target=x86_64-efi: Tells GRUB that we want to install it in a way that allows it to boot in UEFI
  • --efi-directory=/boot: All GRUB UEFI files will be installed in /boot
  • --bootloader-id="Funtoo Linux [GRUB]": This flag is not necessary for GRUB to boot. However, it allows you to change the text of the boot option in the UEFI BIOS. The stuff in the quotes can be set to anything that you would like.
  • --recheck: If a device map already exists on the disk or partition that GRUB is being installed on, it will be removed.
  • /dev/sda:The device that we are installing GRUB on.
Configuring GRUB

OK, now UEFI has the GRUB image it needs to boot. But we still need to configure GRUB itself so it finds and boots your kernel and initramfs. This is done by performing the following steps. Since boot-update doesn't yet support UEFI, we will use boot-update, but then edit our /boot/grub/grub.cfg to support UEFI booting.

First, you will need to edit /etc/boot.conf. Format this as you would if you were booting without UEFI. If you are not sure how this should look, below is an example of what it could look like if you are booting from an unencrypted ext4 partition:

/etc/boot.conf
boot {
        generate grub
        default "Funtoo Linux"
        timeout 3
}

"Funtoo Linux" {
        kernel vmlinuz[-v]
        params += rootfstype=ext4 root=/dev/sda2
}

After you have edited your /etc/boot.conf file, run boot-update. You should now have a /boot/grub/grub.cfg file, which you can edit using the following command:

# nano /boot/grub/grub.cfg


To get your /boot/grub/grub.cfg to support booting with UEFI, make the following changes. Below the existing insmod lines, add the following lines. Both of these involve adding support for the UEFI framebuffer to GRUB.:

  insmod efi_gop
  insmod efi_uga

Then, change the set gfxpayload line to read as follows. UEFI does not support text mode, so we will keep video initialized to the current resolution.:

  set gfxpayload=keep

You can now save your changes by pressing Control-X and answering y when asked if you want to save the modified buffer. When prompted for a filename, hit Enter to use the existing filename.