Update chapter 12 "Advance Administration" for Debian 10

changed the description

assigned to @stender

marked the checklist item Fix #21 (closed): document performance loss in RAID-0 with a disk larger than others as completed

I've updated everything except section "12.4.2. Setting up Nagios". I cannot access the Nagios4 control panel because I got an error restarting Apache after starting the nagios service. This looks like a bug in the default configuration. I'm going to dig into it later and report a bug if necessary.

# journalctl -xe
[...]
Jun 27 13:17:48 debian apachectl[15384]: AH00526: Syntax error on line 40 of /etc/apache2/conf-enabled/nagios4-cgi.conf:
Jun 27 13:17:48 debian apachectl[15384]: Invalid command 'AuthGroupFile', perhaps misspelled or defined by a mod
Jun 27 13:17:48 debian apachectl[15384]: Action 'start' failed.
[...]

Looks like "a2enmod authz_groupfile" needs to be run. That's the module providing the directive: https://httpd.apache.org/docs/current/mod/mod_authz_groupfile.html

a2enmod authz_groupfile didn't make it work. I reported a bug

a2enmod auth_digest must be executed as well.

added In progress label and removed Chapter to update label

added Chapter to review label and removed In progress label

marked the checklist item Update the chapter as completed

assigned to @dleidert and unassigned @jorgesumle-guest

Some thoughts regarding chapter 12.1:

In general the section makes the assumption that RAID is a safeguard for data. That's not the case. RAID is a safeguard for the availability of the system. A RAID is not going down just because one element fails. Assuming the data on the remaining RAID elements has not been corrupted, the system stays operational.

However a RAID won't prevent data corruption. Instead corrupt data will be mirrored inside the RAID! The only safeguard for data is a backup created from a non-corrupt state, not a RAID system. Of course the backup itself can be stored in a RAID.

Something else: In the LVM section in chapter 12.1.2.2 the VG "vg_normal" has 12GB. Does it really show <10.99g?

# vgdisplay -C
  VG          #PV #LV #SN Attr   VSize   VFree  
  vg_critical   2   0   0 wz--n-   7.99g   7.99g
  vg_normal     3   0   0 wz--n- <10.99g <10.99g

Further after 1GB of "vg_critical" has been assigned to "vg_critical/lv_files", the remaining space would be 0.99g, but the output says:

# vgdisplay -C vg_critical
  VG          #PV #LV #SN Attr   VSize VFree   
  vg_critical   2   2   0 wz--n- 7.99g 92.00m

and later

# vgdisplay -C vg_critical
  VG          #PV #LV #SN Attr   VSize VFree
  vg_critical   3   2   0 wz--n- 9.09g 1.09g

I find this odd. Why is there only 99 MB space left, when there should be almost 0.99 GB?

Done with reading. There is just a minor merge request. Some thoughts:

12.2 maybe add a sidebar, that virtualizaton support needs to be enabled in BIOS on some systems (e.g. on my Lenovo Thinkpad 11e)
12.2.3.3 should the virt-install example install a Debian Buster (10) image instead of Debian 9?
12.4.1.1 the link to the plugin gallery should be a block link or it won't be visible for book readers

mentioned in merge request !27 (merged)

mentioned in commit 5b2efe77

mentioned in commit e1fa4557

assigned to @jorgesumle-guest and unassigned @dleidert

Update chapter 12 "Advance Administration" for Debian 10

Child items ...

Activity