Hi folks,
We have a serious issue with the current Apache httpd package, which is an indispensable service for a server these days.
The issue is basically the default configuration as provided by the package:
- if you create just one server in den .conf directory, it results in a non-functional https configuration
- the configuration uses items, that are deprecated since version 2.4
- the default layout of the default configuration is currently not suitable
I wrote a bug report about it:
https://bugzilla.redhat.com/show_bug.cgi?id=2258121
Unfortunately we are experiencing a common Fedora problem, nobody responds to it and the bug reports are left unprocessed and pile up. And because none of the maintainers respond at all, we have now also missed all the deadlines for improving something for f40.
Technically an improvement is more than simple. It’s just a change in the configuration files, as far as I see.
Any idea how to proceed with this?
- Would someone take the bug report and check my analyses?
- Is there any way to bring this forward?
- Should we create a new https-server package which takes the binaries and provides an alternative configuration? Probably similar to default-editor-vim / default-editor-nano?
As it currently stands, we are in no way competitive with, for example, Debian or ArchLinux.
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
The following proposal comes out of the discussion at this weeks Server SIG
meeting[1]
Fedora Server will have:
* / (root) will be a minimum of 2 GiB and a maximum of 15 GiB
* SWAP will continue to be calculated automatically based on available RAM on
the system
* All unused space will be assigned to a volume group and available to be
assigned to new partitions or extend existing partitions.
* Anaconda will continue to handle the appropriate EFI and /boot settings
We also discussed during the meeting whether we should have a separate /var
partition by default, but the general sense was that we might be better served
by developing a mechanism to allow partitions to be split from existing mount
points, which would be more flexible going forward.
As we did not have quorum in the meeting by the point we got to this proposal,
I'm taking it to the list for discussion and votes.
For the record, the current behavior of the partitioning scheme is for / to be
given up to 50 GiB of space and then any remaining space after that is assigned
to a separate /home partition.
[1]
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-03-15/serversig.201…
Folks,
I’ve summarized the discussion at our meeting in an issue and put together a corresponding plan. We should discuss our results here on the mailing list and interim results in the ticket.
See
https://pagure.io/fedora-server/issue/125
Somehow we are also supposed to enter and collect test results on page https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.10_Server (or newer)
While testing our DVD installation medium I found some (minor) issues
- The first boot screen with 'Grub Version 2.6' is not centered, but shifted to the right.
- error message:
[Firmware Bug]: TSC_DEADLINE disabled due to Errata: please update microcode to
Ter)
- error message:
overlays: failed to resolve: '/run/overlays': -Z
This may be partly due to my rather old test hardware. Can anyone reproduce the messages?
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
Since yesterday in the evening the Fedora Docs stg branch generation is fixed and it is back to work.
So we have in installation updated Versions of:
Interactive local installation
Interactive remote installation
Post installation tasks
And a new article in administration:
LVM management cheat sheet
Please, feel free to review and especially to add
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
Please, could someone take over the testing of F40 (Beta and res) update and dnf upgrade? We missed to organize that so far.
I did an update of my Beta installation and got at the end some error messages
>
> Running scriptlet: nfs-utils-1:2.6.4-0.rc5.fc40.x86_64 300/300
> Running scriptlet: appstream-1.0.2-2.fc40.x86_64 300/300
> Running scriptlet: libgcc-14.0.1-0.7.fc40.x86_64 300/300
> Failed to connect to bus: Connection refused
>
> Failed to connect to bus: Connection refused
>
> Failed to connect to bus: Connection refused
> Failed to connect to bus: Connection refused
So far I have not noticed any problems at first glance. But such messages do not necessarily serve to reassure and instill confidence in a system administrator.
Who takes over?
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
Essentials at a glance
=== Follow-up actions & announcements
We will first discuss a possible change to the time of our meetings on the mailing list and decide at the next meeting.
=== LVM2 configuration
!LINK https://bugzilla.redhat.com/show_bug.cgi?id=2247872
The /etc/lvm/devices directory in Fedora-Server-KVM-40_Beta-1.9.x86_64.qcow2 is empty now. So far no check whether First Boot generates a suitable entry.
INFO update: Beta 1.10 contains a devices file in both server images (KVM and aarch64 SBC). So the issue is not resolved yet.
ACTION: cooltshirtguy will monitor and check the aarch64 SBC image, specifically Raspberry Pi.
=== F40 release tests
We have selected items to be tested and allocated work. Details at
LINK https://pagure.io/fedora-server/issue/125/
=== Open Floor
INFO: Unfortunately, no movement on the Apache / httpd configuration layout yet
Details at
https://docs.fedoraproject.org/en-US/server-working-group/wg-minutes-2024/
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
# F40 Blocker Review meeting
# Date: 2024-03-25
# Time: 16:00 UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.…
Hi folks! It's time for another blocker review meeting. We have 3
proposed blockers for Final.
Here is a handy link which should show you the meeting time
in your local time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker…
The meeting will be on Matrix. Click the link above to join in a web
client - you can authenticate with your FAS account - or use a
dedicated client of your choosing.
If you have time today, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F40 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good day and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
Folks,
As discusses at the last meeting I published a new doc „LVM management Cheat Sheet“ at
https://docs.stg.fedoraproject.org/en-US/fedora-server/administration/lvm-m…
There is a section about mounting a virtual disk image partition containing an LVM VG. This may help to check and test our various Fedora Server images.
It’s currently in the stg branch and for some reason the link in the navigation bar is generated incorrectly. But the direct link works.
Feel free to fix any mistake and/or to add some sections.
Best
Peter
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast