I've been using Fedora 10 and while trying F12 beta I noticed a
problem in the httpd run directory permission. Then I tried F11 and
the same problem happens:
[Wed Oct 28 12:05:02 2009] [notice] Apache/2.2.13 (Unix) DAV/2
PHP/5.2.9 mod_python/3.3.1 Python/2.6 mod_ssl/2.2.13
OpenSSL/0.9.8k-fips mod_wsgi/2.6 mod_perl/2.0.4 Perl/v5.10.0
configured -- resuming normal operations
[Wed Oct 28 12:05:09 2009] [error] [client 10.0.2.15] (13)Permission
denied: mod_wsgi (pid=2722): Unable to connect to WSGI daemon process
'mygroup' on '/etc/httpd/run/wsgi.2692.0.1.sock' after multiple
The problem is that until F10 the httpd socket directory was /var/run/
and in F11 and F12 it is /var/run/httpd:
# ll /etc/httpd/run
lrwxrwxrwx. 1 root root 19 2009-10-28 11:04 /etc/httpd/run ->
# ll -d /var/run/httpd
drwx------. 2 root root 4096 2009-10-28 11:51 /var/run/httpd
# ll -d /var/run
drwxr-xr-x. 31 root root 4096 2009-10-28 11:35 /var/run
# ll /var/run/httpd/
-rw-r--r--. 1 root root 5 2009-10-28 12:05 httpd.pid
srwx------. 1 apache root 0 2009-10-28 12:05 wsgi.2692.0.1.sock
That can break some apache modules like mod_wsgi which rely on sockets.
Any of these solve the problem:
# chmod o+x /var/run/httpd
# chown apache.root /var/run/httpd
Is there a reason for the /var/run/httpd permissions to be as in
F11/12 ? Is it necessary to have the user intervention to fix it? I
have posted at the mod_wsgi list:
Regards, Clodoaldo Neto
I've got a wireless CDMA modem that works perfectly using the option usb
serial driver, but is not currently listed as one of the supported devices.
I've been manually adding its ID to option.c and recompiling the driver
since F8. This however means that each time I perform a kernel upgrade I
lose internet connectivity until I've done this. It also means that
yum-presto won't do a delta upgrade of the kernel since it's contents have
changed, I have to download the full package (CDMA cell network, can get
Do I get this added to the Fedora kernel first or should I send it
upstream? Any pointers as to the procedures to follow (links to
documentation detailing who to contact etc would be most appreciated).
When: Friday, 2009-10-30 @ 16:00-20:00 UTC (1200-1600 hours EDT)
Where: #fedora-qa on irc.freenode.net
F-12 Blocker Meeting may still be in session (more than likely) in
#fedora-bugzappers, so we will be gathering in #fedora-qa.
The Bug Zappers will be holding a bug triage event this Friday (tomorrow) and
would like to invite any and all that are interested in lending a hand to join
Our goal for this event is to review and triage Fedora 10 bug reports still in
the status of 'NEW' with the aim of confirming and re-versioning or closing
where approriate. This is an effort to put 'eyes' on these reports before EOL
(End Of Life) changes close them.
whether your just curoius about the triage process or have questions and would
like to learn more. This is an oppertunity to do so.
Maybe you like help filing a bug report? We're happy to help.
Everyone is welcome!
I hope to see you there
Jim Parsons left Red Hat a little while back and the only contact
details I have is his Red Hat email address, which is of course no
longer valid. I've opened a bugzilla #530027 as per the unresponsive
maintainer procedure, but I was hoping to be able to skip the section
regarding sending of messages since there seems little point sending to
an email address which I know (and which other Red Hat employees can
easily verify) will not be answered.
Instead I've emailed the one other person who had access to that package
and that has also gone unanswered (see the bugzilla).
There are a number of outstanding bugs filed against
system-config-cluster (including the fact that it seems that it has not
passed an initial review) which I've listed out in the bugzilla.
I would like to either fix (or preferably just remove) this package as
it creates configs for GFS2 which are incorrect and is thus causing
confusion to all who attempt to use it.
Therefore this is my formal request to become maintainer of this
Fedora Release Engineering decided to deal with the 250+ backlog of
Bodhi update requests by tagging them all into f12-final. Bodhi is now
disabled for Fedora 12 updates.
1) Why tag all Update requests into f12-final?
At this point of the schedule we realized that there were updates
sitting in the queue from since October. They were sitting there. Not
getting pushed to any repository. Rawhide gives these packages several
more weeks of testing exposure. This was decided to be better than a
flood of day zero updates that are poorly tested.
2) When will we be able to submit Updates again?
Rel-eng will decide when to begin accepting Updates for Fedora 12 again
during Monday's rel-eng meeting. Meanwhile please use the rel-eng
ticketing system to request tagging into f12-final.
3) How do I file a tag request to include my package into Fedora 12?
Please file tag request tickets here if you want your package build to
be included in Fedora 12. Please include details like:
* Full Name-Version-Release of your package(s)
* What changed?
* How risky is this change?
* How important is this change?
* How well tested is this package build?
* Is this package in the critical-path list?
4) Which packages are critical-path?
Unfortunately we do not yet have a permanent URL with the critical-path
list. This page contains an auto-generated list of critical-path
packages as of today.
If your package is not critical-path and not a risk to others to update,
then it is highly likely proper to tag at this point of the schedule.
5) How many untagged packages are there?
koji list-tagged --latest dist-f12-updates-candidate
This command lists all packages that are not tagged for f12-final. In
some cases these are false positives because a newer package is instead
tagged into f12-final. After you have tested your package and verified
it doesn't make things worse, please file rel-eng tickets to have it
Please direct questions to fedora-devel-list.
Fedora-devel-announce mailing list
Outage Notification - 2009-10-29 21:00 UTC
There will be an outage starting at 2009-10-29 21:00 UTC, which will last
approximately 2 hours.
To convert UTC to your local time, take a look at
date -d '2009-10-29 21:00 UTC'
CVS / Source Control
* None *
Reason for Outage:
Major update for OS.
Please join #fedora-admin in irc.freenode.net or respond to this email to track
the status of this outage.
Stephen J Smoogen.
Ah, but a man's reach should exceed his grasp. Or what's a heaven for?
-- Robert Browning