Apache is unable to access /tmp in any way
This problem happened in a recent apache release before version 2.4.55. I encountered this after a system upgrade a month ago. Apache is unable to access /tmp in any way. We may let apache host some external websites by: > Alias "/ext" "/path/to/external" > > Options Indexes > Require all granted > You can access that through http://yourwebsite/ext This works most of the time. Changing "/path/to/external" to any path works fine including /bin, /srv, /etc ... Except for anything under /tmp. I always get 403 Forbidden for that. For other directories, as long as apache has access permission on them, I could always get their content listed. Only for /tmp I get 403 Forbidden. Indexing (/ext) and actual file accessing (/ext/index.html) are both forbidden. Why is /tmp different from others? Changing permission of /tmp to 755 does not work, either. Debug log here: > [authz_core:debug] [pid 4469:tid 140408108734144] mod_authz_core.c(815): [client 127.0.0.1:37804] AH01626: authorization result of Require all denied: denied > [authz_core:debug] [pid 4469:tid 140408108734144] mod_authz_core.c(815): [client 127.0.0.1:37804] AH01626: authorization result of : denied > [authz_core:error] [pid 4469:tid 140408108734144] [client 127.0.0.1:37804] AH01630: client denied by server configuration: /tmp/http Build options: > ./configure --sbindir=/usr/bin \ > --enable-layout=Arch \ > --enable-mpms-shared=all \ > --enable-modules=all \ > --enable-mods-shared=all \ > --enable-so \ > --enable-suexec \ > --with-suexec-caller=http \ > --with-suexec-docroot=/srv/http \ > --with-suexec-logfile=/var/log/httpd/suexec.log \ > --with-suexec-bin=/usr/bin/suexec \ > --with-suexec-uidmin=99 --with-suexec-gidmin=99 \ > --enable-ldap --enable-authnz-ldap --enable-authnz-fcgi \ > --enable-cache --enable-disk-cache --enable-mem-cache --enable-file-cache \ > --enable-ssl --with-ssl \ > --enable-deflate --enable-cgi --enable-cgid \ > --enable-proxy --enable-proxy-connect \ > --enable-proxy-http --enable-proxy-ftp \ > --enable-dbd --enable-imagemap --enable-ident --enable-cern-meta \ > --enable-lua --enable-xml2enc --enable-http2 \ > --enable-proxy-http2 --enable-md --enable-brotli \ > --with-apr=/usr/bin/apr-1-config \ > --with-apr-util=/usr/bin/apu-1-config \ > --with-pcre2 Source: https://www.apache.org/dist/httpd/httpd-2.4.55.tar.bz2 - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-227) Only list last X releases and the add/remove release page
[ https://issues.apache.org/jira/browse/COMDEV-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689014#comment-17689014 ] Robert Munteanu commented on COMDEV-227: [~akm] - yes, the slowness is the problem for me and it would be great to have a fix for it. > Only list last X releases and the add/remove release page > - > > Key: COMDEV-227 > URL: https://issues.apache.org/jira/browse/COMDEV-227 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Robert Munteanu >Priority: Major > > In the Apache Sling project we have a large number of releases as we have > many independent modules. When loading the > https://reporter.apache.org/addrelease.html?sling page, it takes upwards of > 10 seconds to load. It would be great if only the last X (50?) releases were > shown, and then a "load all" link would be available at the bottom. > This would greatly speed up our usage of this tool. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Apache is unable to access /tmp in any way
Unfortunately, you have reached the wrong mailing list for this question. We encourage you to email the us...@httpd.apache.org mailing list for this question. More info is available at https://httpd.apache.org/lists.html On Wed, 2023-02-15 at 16:42 +0800, accelerator0099 wrote: > This problem happened in a recent apache release before version > 2.4.55. > I encountered this after a system upgrade a month ago. > > > Apache is unable to access /tmp in any way. > > > We may let apache host some external websites by: > > > Alias "/ext" "/path/to/external" > > > > Options Indexes > > Require all granted > > > > > You can access that through http://yourwebsite/ext > > This works most of the time. Changing "/path/to/external" to any path > works fine including /bin, /srv, /etc ... > > Except for anything under /tmp. > > I always get 403 Forbidden for that. > > For other directories, as long as apache has access permission on > them, > I could always get their content listed. > > Only for /tmp I get 403 Forbidden. > > Indexing (/ext) and actual file accessing (/ext/index.html) are both > forbidden. > > > Why is /tmp different from others? > > Changing permission of /tmp to 755 does not work, either. > > > Debug log here: > > > [authz_core:debug] [pid 4469:tid 140408108734144] > mod_authz_core.c(815): [client 127.0.0.1:37804] AH01626: > authorization > result of Require all denied: denied > > [authz_core:debug] [pid 4469:tid 140408108734144] > mod_authz_core.c(815): [client 127.0.0.1:37804] AH01626: > authorization > result of : denied > > [authz_core:error] [pid 4469:tid 140408108734144] [client > 127.0.0.1:37804] AH01630: client denied by server configuration: > /tmp/http > > > Build options: > > > ./configure --sbindir=/usr/bin \ > > --enable-layout=Arch \ > > --enable-mpms-shared=all \ > > --enable-modules=all \ > > --enable-mods-shared=all \ > > --enable-so \ > > --enable-suexec \ > > --with-suexec-caller=http \ > > --with-suexec-docroot=/srv/http \ > > --with-suexec-logfile=/var/log/httpd/suexec.log \ > > --with-suexec-bin=/usr/bin/suexec \ > > --with-suexec-uidmin=99 --with-suexec-gidmin=99 \ > > --enable-ldap --enable-authnz-ldap --enable-authnz-fcgi \ > > --enable-cache --enable-disk-cache --enable-mem-cache > --enable-file-cache \ > > --enable-ssl --with-ssl \ > > --enable-deflate --enable-cgi --enable-cgid \ > > --enable-proxy --enable-proxy-connect \ > > --enable-proxy-http --enable-proxy-ftp \ > > --enable-dbd --enable-imagemap --enable-ident --enable-cern- > meta \ > > --enable-lua --enable-xml2enc --enable-http2 \ > > --enable-proxy-http2 --enable-md --enable-brotli \ > > --with-apr=/usr/bin/apr-1-config \ > > --with-apr-util=/usr/bin/apu-1-config \ > > --with-pcre2 > > > Source: > > https://www.apache.org/dist/httpd/httpd-2.4.55.tar.bz2 > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Patch for reporter.a.o
On Tue, 2023-02-14 at 14:33 -0800, Andrew Musselman wrote: > Looks good to me. Maybe similar language on this page > too? https://reporter.apache.org/wizard/statistics?lucene That page is generated by the code affected by that patch. > > This ticket could be a good link to point the "Patches welcome" > to: COMDEV-487 > > On Tue, Feb 14, 2023 at 1:22 PM wrote: > > I'd like to propose the attached patch to reporter.a.o so that > > people > > don't keep submitting the same mailing list stats, quarter after > > quarter, a year after that part of the reporter is broken. > > > > Thoughts? > > > > --- > > -- > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Patch for reporter.a.o
On Wed, Feb 15, 2023 at 5:19 AM wrote: > On Tue, 2023-02-14 at 14:33 -0800, Andrew Musselman wrote: > > Looks good to me. Maybe similar language on this page > > too? https://reporter.apache.org/wizard/statistics?lucene > > That page is generated by the code affected by that patch. Got it >
[jira] [Commented] (COMDEV-227) Only list last X releases and the add/remove release page
[ https://issues.apache.org/jira/browse/COMDEV-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689330#comment-17689330 ] Andrew Musselman commented on COMDEV-227: - [~rombert] It would be easy to allow a new query param, e.g., https://reporter.apache.org/addrelease.html?sling&limit=50 How does that sound? > Only list last X releases and the add/remove release page > - > > Key: COMDEV-227 > URL: https://issues.apache.org/jira/browse/COMDEV-227 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Robert Munteanu >Priority: Major > > In the Apache Sling project we have a large number of releases as we have > many independent modules. When loading the > https://reporter.apache.org/addrelease.html?sling page, it takes upwards of > 10 seconds to load. It would be great if only the last X (50?) releases were > shown, and then a "load all" link would be available at the bottom. > This would greatly speed up our usage of this tool. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-227) Only list last X releases and the add/remove release page
[ https://issues.apache.org/jira/browse/COMDEV-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689339#comment-17689339 ] Andrew Musselman commented on COMDEV-227: - Attaching proposed patch > Only list last X releases and the add/remove release page > - > > Key: COMDEV-227 > URL: https://issues.apache.org/jira/browse/COMDEV-227 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Robert Munteanu >Priority: Major > Attachments: COMDEV-227.patch.txt > > > In the Apache Sling project we have a large number of releases as we have > many independent modules. When loading the > https://reporter.apache.org/addrelease.html?sling page, it takes upwards of > 10 seconds to load. It would be great if only the last X (50?) releases were > shown, and then a "load all" link would be available at the bottom. > This would greatly speed up our usage of this tool. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-227) Only list last X releases and the add/remove release page
[ https://issues.apache.org/jira/browse/COMDEV-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Musselman updated COMDEV-227: Attachment: COMDEV-227.patch.txt > Only list last X releases and the add/remove release page > - > > Key: COMDEV-227 > URL: https://issues.apache.org/jira/browse/COMDEV-227 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Robert Munteanu >Priority: Major > Attachments: COMDEV-227.patch.txt > > > In the Apache Sling project we have a large number of releases as we have > many independent modules. When loading the > https://reporter.apache.org/addrelease.html?sling page, it takes upwards of > 10 seconds to load. It would be great if only the last X (50?) releases were > shown, and then a "load all" link would be available at the bottom. > This would greatly speed up our usage of this tool. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [jira] [Commented] (COMDEV-227) Only list last X releases and the add/remove release page
Patch attached here; allows for new query param `limit` so projects that
are getting bogged down can just specify how many releases they want to see
on the page.
E.g.,
reporter.apache.org/addrelease.html?sling shows all releases
reporter.apache.org/addrelease.html?sling&limit=50 shows only the latest 50
releases
reporter.apache.org/addrelease.html?sling;2000 sets baseline year to 2000
reporter.apache.org/addrelease.html?sling;2000&limit=50 sets baseline year
to 2000 and limits to latest 50 releases
Probably would make sense to add a note above "Already registered releases"
to explain this.
Tested query param handling but not cutting off releases at limit since I
don't have a testing env. See if it looks reasonable.
[Y/n]?
On Wed, Feb 15, 2023 at 1:06 PM Andrew Musselman (Jira)
wrote:
>
> [
> https://issues.apache.org/jira/browse/COMDEV-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689339#comment-17689339
> ]
>
> Andrew Musselman commented on COMDEV-227:
> -
>
> Attaching proposed patch
>
> > Only list last X releases and the add/remove release page
> > -
> >
> > Key: COMDEV-227
> > URL: https://issues.apache.org/jira/browse/COMDEV-227
> > Project: Community Development
> > Issue Type: Improvement
> > Components: Reporter Tool
> >Reporter: Robert Munteanu
> >Priority: Major
> > Attachments: COMDEV-227.patch.txt
> >
> >
> > In the Apache Sling project we have a large number of releases as we
> have many independent modules. When loading the
> https://reporter.apache.org/addrelease.html?sling page, it takes upwards
> of 10 seconds to load. It would be great if only the last X (50?) releases
> were shown, and then a "load all" link would be available at the bottom.
> > This would greatly speed up our usage of this tool.
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.20.10#820010)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>
Index: site/js/addrelease.js
===
--- site/js/addrelease.js (revision 1907684)
+++ site/js/addrelease.js (working copy)
@@ -1,6 +1,8 @@
// location may have appended ; for debugging purposes
+// limit param can be passed as query param in URL to limit # of releases
written to the page
+// This URL-handling section could use clean-up
var srch = document.location.search.substr(1).split(';'); // drop ? from the
search and split at semicolon
- var committee = srch[0]; // before the semi (if any)
+ var committee = srch[0].split('&')[0]; // before the semi (if any) and amp
(if any)
var baseyear = 1999;
if (srch.length > 1) {
baseyear = parseInt(srch[1]); // grab trailing start year
@@ -8,6 +10,9 @@
baseyear=1999; // ensure sensible default value
}
}
+ const queryString = document.location.search;
+ const params = new URLSearchParams(queryString);
+ const limit = parseInt(params.get("limit"));
document.getElementById('committee').value = committee;
var xdate = document.getElementById('xdate');
var done = false;
@@ -47,6 +52,9 @@
var basedate = bd.getTime()/1000 // value as stored in the database
var recent = new Array();
for (version in json) {
+if (limit && x == limit) {
+ break;
+}
if (json[version] > basedate) {
recent.push(new Release(version, json[version]));
x++;
@@ -69,4 +77,3 @@
}
document.getElementById('committee').value = committee;
}
-
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] ShaneCurcuru merged pull request #82: Update newcommitter.md
ShaneCurcuru merged PR #82: URL: https://github.com/apache/comdev-site/pull/82 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-488) Apache ShardingSphere: Support mainstream database metadata table query
Chuxin Chen created COMDEV-488:
--
Summary: Apache ShardingSphere: Support mainstream database
metadata table query
Key: COMDEV-488
URL: https://issues.apache.org/jira/browse/COMDEV-488
Project: Community Development
Issue Type: Improvement
Components: GSoC/Mentoring ideas
Reporter: Chuxin Chen
h2. Apache ShardingSphere
Apache ShardingSphere is positioned as a Database Plus, and aims at building a
standard layer and ecosystem above heterogeneous databases. It focuses on how
to reuse existing databases and their respective upper layer, rather than
creating a new database. The goal is to minimize or eliminate the challenges
caused by underlying databases fragmentation.
{*}Page{*}:
[https://shardingsphere.apache.org|https://shardingsphere.apache.org/]
{*}Github{*}: [https://github.com/apache/shardingsphere]
h2. Background
ShardingSphere has designed its own metadata database to simulate metadata
queries that support various databases.
{*}More details{*}:
[https://github.com/apache/shardingsphere/issues/21268]
[https://github.com/apache/shardingsphere/issues/22052]
h2. Task
* Support PostgreSQL AND openGauss `\d tableName` and `l`
* Support query for MySQL metadata `TABLES`, `COLUMNS`
{*}Notice{*}, these issues can be a good example.
[https://github.com/apache/shardingsphere/pull/22053]
[https://github.com/apache/shardingsphere/pull/22057/]
[https://github.com/apache/shardingsphere/pull/22166/]
[https://github.com/apache/shardingsphere/pull/22182]
h2. Relevant Skills
* Master JAVA language
* Have a basic understanding of Zookeeper
* Be familiar with MySQL/Postgres SQLs
h3. Mentor
Chuxin Chen, Committer of Apache ShardingSphere, tuichenchu...@apache.org
Zhengqiang Duan, PMC of Apache ShardingSphere, duanzhengqi...@apache.org
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-488) Apache ShardingSphere: Support mainstream database metadata table query
[
https://issues.apache.org/jira/browse/COMDEV-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuxin Chen updated COMDEV-488:
---
Labels: Mentor ShardingSphere gsoc2023 mentor (was: Mentor ShardingSphere
gsoc2023)
> Apache ShardingSphere: Support mainstream database metadata table query
> ---
>
> Key: COMDEV-488
> URL: https://issues.apache.org/jira/browse/COMDEV-488
> Project: Community Development
> Issue Type: Improvement
> Components: GSoC/Mentoring ideas
>Reporter: Chuxin Chen
>Priority: Major
> Labels: Mentor, ShardingSphere, gsoc2023, mentor
>
> h2. Apache ShardingSphere
> Apache ShardingSphere is positioned as a Database Plus, and aims at building
> a standard layer and ecosystem above heterogeneous databases. It focuses on
> how to reuse existing databases and their respective upper layer, rather than
> creating a new database. The goal is to minimize or eliminate the challenges
> caused by underlying databases fragmentation.
> {*}Page{*}:
> [https://shardingsphere.apache.org|https://shardingsphere.apache.org/]
> {*}Github{*}: [https://github.com/apache/shardingsphere]
> h2. Background
> ShardingSphere has designed its own metadata database to simulate metadata
> queries that support various databases.
> {*}More details{*}:
> [https://github.com/apache/shardingsphere/issues/21268]
> [https://github.com/apache/shardingsphere/issues/22052]
> h2. Task
> * Support PostgreSQL AND openGauss `\d tableName` and `l`
> * Support query for MySQL metadata `TABLES`, `COLUMNS`
> {*}Notice{*}, these issues can be a good example.
> [https://github.com/apache/shardingsphere/pull/22053]
> [https://github.com/apache/shardingsphere/pull/22057/]
> [https://github.com/apache/shardingsphere/pull/22166/]
> [https://github.com/apache/shardingsphere/pull/22182]
> h2. Relevant Skills
> * Master JAVA language
> * Have a basic understanding of Zookeeper
> * Be familiar with MySQL/Postgres SQLs
>
> h3. Mentor
> Chuxin Chen, Committer of Apache ShardingSphere, tuichenchu...@apache.org
> Zhengqiang Duan, PMC of Apache ShardingSphere, duanzhengqi...@apache.org
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
