0 gid=0 euid=0 suid=0 fsuid=0
> > > egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="apache2"
> > > exe="/usr/sbin/apache2" subj==/usr/sbin/apache2 (enforce) key=(null)
> > > type=AVC msg=audit(1539750555.347:77): apparmor="DENIED&qu
On 2018-10-18 07:15, steve wrote:
Le 18-10-2018, à 07:07:34 +0100, mick crane a écrit :
On 2018-10-18 05:11, steve wrote:
Still reading on this new thing for me.
Thanks
Steve
I never came across this apparmor.
did you try stopping it with systemctl then see if apache works as
expected ?
On 2018-10-18 07:07, mick crane wrote:
On 2018-10-18 05:11, steve wrote:
Still reading on this new thing for me.
Thanks
Steve
I never came across this apparmor.
did you try stopping it with systemctl then see if apache works as
expected ?
Ah, OK I see you tried that.
Would that not indi
Le 18-10-2018, à 07:07:34 +0100, mick crane a écrit :
On 2018-10-18 05:11, steve wrote:
Still reading on this new thing for me.
Thanks
Steve
I never came across this apparmor.
did you try stopping it with systemctl then see if apache works as
expected ?
Yes I did and apache failed to s
On 2018-10-18 05:11, steve wrote:
Still reading on this new thing for me.
Thanks
Steve
I never came across this apparmor.
did you try stopping it with systemctl then see if apache works as
expected ?
mick
--
Key ID4BFEBB31
a3=8 items=0 ppid=17482 pid=17485 auid=4294967295 uid=0 gid=0
euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="apache2"
exe="/usr/sbin/apache2" subj==/usr/sbin/apache2 (enforce) key=(null)
type=AVC msg=audit(1539750555.347:77): apparmor="DENI
Thanks Reco for your input.
I'll have to go trough it, but don't have time right now.
Steve
Le 17-10-2018, à 05:38:11 +, Steve Kemp a écrit :
To recap you reported the original error:
apache2: Could not open configuration file /etc/apache2/apache2.conf:
Permission denied
Now you've provided more details, from your audit-log:
type=AVC msg=audit(1539750555.3
:22:01 box systemd[1]: Starting The Apache HTTP Server...
> > > oct 16 07:22:01 box apachectl[32122]: apache2: Could not open
> > > configuration file /etc/apache2/apache2.conf: Permission denied
> > > oct 16 07:22:02 box apachectl[32122]: Action 'start' failed.
To recap you reported the original error:
> apache2: Could not open configuration file /etc/apache2/apache2.conf:
> Permission denied
Now you've provided more details, from your audit-log:
> type=AVC msg=audit(1539750555.347:77): apparmor="DENIED"
> operatio
Le 16-10-2018, à 06:39:01 +, Steve Kemp a écrit :
ls -l /etc/apache2/apache2.conf
-rw-r--r-- 1 root root 7224 jun 2 10:01 /etc/apache2/apache2.conf
Getting nuts.
Probably the permissions on /etc/apache2, or /etc are broken for the
user www-data.
ls -l /etc
drwxr-xr-x 213 root root
rting The Apache HTTP Server...
oct 16 07:22:01 box apachectl[32122]: apache2: Could not open configuration
file /etc/apache2/apache2.conf: Permission denied
oct 16 07:22:02 box apachectl[32122]: Action 'start' failed.
oct 16 07:22:02 box apachectl[32122]: The Apache error log may have mo
On Tue 16 Oct 2018 at 12:24:49 (-0400), Gene Heskett wrote:
> On Tuesday 16 October 2018 11:37:44 Greg Wooledge wrote:
>
> > On Tue, Oct 16, 2018 at 11:28:44AM -0400, Gene Heskett wrote:
> > > Since leaving a sudo -i laying about is considered a security
> > > breach, I'm amazed that the -i option
On Tuesday 16 October 2018 11:37:44 Greg Wooledge wrote:
> On Tue, Oct 16, 2018 at 11:28:44AM -0400, Gene Heskett wrote:
> > Since leaving a sudo -i laying about is considered a security
> > breach, I'm amazed that the -i option doesn't accept a timeout. Say
> > in seconds, as if you think it will
On Tuesday 16 October 2018 11:37:44 Greg Wooledge wrote:
> On Tue, Oct 16, 2018 at 11:28:44AM -0400, Gene Heskett wrote:
> > Since leaving a sudo -i laying about is considered a security
> > breach, I'm amazed that the -i option doesn't accept a timeout. Say
> > in seconds, as if you think it will
On Tue, Oct 16, 2018 at 11:28:44AM -0400, Gene Heskett wrote:
> Since leaving a sudo -i laying about is considered a security breach, I'm
> amazed that the -i option doesn't accept a timeout. Say in seconds, as
> if you think it will take 5 minutes to do the job as root, sudo -i300,
> at the end
On Tuesday 16 October 2018 05:56:31 Jonathan Dowland wrote:
> On Tue, Oct 16, 2018 at 10:09:39AM +0200, Martin wrote:
> >> sudo su - www-data -s /bin/sh
> >
> >Don't use sudo with su. It is evil.
> >You want to use 'sudo -i' in this case.
>
> Fascism is evil. This is just unnecessary.
>
> (I'm
Am 16.10.18 um 11:56 schrieb Jonathan Dowland:
> On Tue, Oct 16, 2018 at 10:09:39AM +0200, Martin wrote:
>>> sudo su - www-data -s /bin/sh
>>
>> Don't use sudo with su. It is evil.
>> You want to use 'sudo -i' in this case.
>
> Fascism is evil. This is just unnecessary.
Good point.
>
> (I'm
On Tue, Oct 16, 2018 at 10:09:39AM +0200, Martin wrote:
sudo su - www-data -s /bin/sh
Don't use sudo with su. It is evil.
You want to use 'sudo -i' in this case.
Fascism is evil. This is just unnecessary.
(I'm guilty of still typing "sudo su -" via muscle memory even after
your messages
o Process: 32122
> > ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
> >
> > oct 16 07:22:01 box systemd[1]: Starting The Apache HTTP Server...
> > oct 16 07:22:01 box apachectl[32122]: apache2: Could not open
> > configuration file /etc/apache2/apa
Am 16.10.18 um 08:39 schrieb Steve Kemp:
>>
>> ls -l /etc/apache2/apache2.conf
>> -rw-r--r-- 1 root root 7224 jun 2 10:01 /etc/apache2/apache2.conf
[...]
> sudo su - www-data -s /bin/sh
Don't use sudo with su. It is evil.
You want to use 'sudo -i' in this case.
[...]
box systemd[1]: Starting The Apache HTTP Server...
> oct 16 07:22:01 box apachectl[32122]: apache2: Could not open configuration
> file /etc/apache2/apache2.conf: Permission denied
> oct 16 07:22:02 box apachectl[32122]: Action 'start' failed.
> oct 16 07:22:02 box apachect
01 box systemd[1]: Starting The Apache HTTP Server...
> oct 16 07:22:01 box apachectl[32122]: apache2: Could not open configuration
> file /etc/apache2/apache2.conf: Permission denied
> oct 16 07:22:02 box apachectl[32122]: Action 'start' failed.
> oct 16 07:22:02 box apache
>
> ls -l /etc/apache2/apache2.conf
> -rw-r--r-- 1 root root 7224 jun 2 10:01 /etc/apache2/apache2.conf
>
>
> Getting nuts.
Probably the permissions on /etc/apache2, or /etc are broken for the
user www-data.
Assuming you have sudo installed you can become "www-dat
ache2/apache2.conf: Permission denied
oct 16 07:22:02 box apachectl[32122]: Action 'start' failed.
oct 16 07:22:02 box apachectl[32122]: The Apache error log may have more
information.
oct 16 07:22:02 box systemd[1]: apache2.service: Control process exited,
code=exited status=1
oct
On 08/23/2006 04:28 AM, Brent Clark wrote:
Hi all
Today i seem to be fighting with Apache2.
I need to have a cgi-bin for /home/images/cgi-bin
But I keep getting premature script.
[...]
If you mean "premature end of script headers," then your
script is dying or for whatever reason not emitti
Hi all
Today i seem to be fighting with Apache2.
I need to have a cgi-bin for /home/images/cgi-bin
But I keep getting premature script.
This is my current conf
ServerAdmin [EMAIL PROTECTED]
ServerAlias abc.com
ServerName abc
SuexecUserGroup images images
On Wed, Nov 30, 2005 at 07:35:40PM +0200, Maxim Vexler wrote:
> Hi,
>
> In [/etc/apache2/apache2.conf] file there's this line :
> <<<
> # Include generic snippets of statements
> Include /etc/apache2/conf.d/[^.#]*
> >>>
>
> What does the [^
On Wed, Nov 30, 2005 at 07:35:40PM +0200, Maxim Vexler wrote:
> In [/etc/apache2/apache2.conf] file there's this line :
> <<<
> # Include generic snippets of statements
> Include /etc/apache2/conf.d/[^.#]*
> >>>
>
> What does the [^.#]* say ?
> I kn
Hi,
In [/etc/apache2/apache2.conf] file there's this line :
<<<
# Include generic snippets of statements
Include /etc/apache2/conf.d/[^.#]*
>>>
What does the [^.#]* say ?
I know that it's regular expression but I've yet to see this regex syntax...
Is it: "
Hey
I had the same problem, but I get around with completely uninstall
apache2-common. (That means not only apt-get remove, but dpkg --purge
and manually deleting /var/www, log files and config files).
Afterwards, the installation of Apache 2 seemed to be as it has to be.
Oh, I also change
On Mon, Sep 19, 2005 at 08:58:52AM +0200, David Huemer wrote:
> By the way: I would absolutetly recommend to compile the apache2 by
> hand so you can define your own profile in the config.layout file to
> customize where config files and so on are located.
That seems like rather a lot of work, whe
On Mon, Sep 19, 2005 at 09:13:31AM -0700, Jared Hall wrote:
> In a way, I guess that this means httpd.conf is obsolete, since
> apache2.conf only includes httpd.conf... but that's more a matter of
> perspective. httpd.conf needs to be there for apt to properly install
> php5
G_FILE="conf/apache2.conf"
What I meant to say originally was just a minor aside about changing
this (httpd.conf seems to be accepted everywhere else) to apache2.conf,
and then using an include for httpd.conf (hint: Include
/etc/apache2/httpd.conf) is sort of unneccessary. But no bi
might look as if you should
not need to modify apache2.conf, but put configuration that's valid for
all your virtual hosts in there, and leave apache2.conf pretty much as
it is.
Best,
Kjetil
--
Kjetil Kjernsmo
Programmer / Astrophysicist / Ski-orienteer / Orienteer / Mountaineer
On 9/19/05, David Huemer <[EMAIL PROTECTED]> wrote:
> I prefer httpd.conf too, but deleting the apache2.conf is no good idea.
> The only good thing about the apache2.conf is, that it includes the
> httpd.conf so all user defined configuration can be done in the
> httpd.conf an
I prefer httpd.conf too, but deleting the apache2.conf is no good idea.
The only good thing about the apache2.conf is, that it includes the
httpd.conf so all user defined configuration can be done in the
httpd.conf and they can be seen very easily. But that is also possible
if you include a
rtain
times)? code consolidation = efficiency.
I agree. Right now apache is compiled to use apache2.conf as the config
file, and then apache2.conf has a line to include httpd.conf. Why
couldn't httpd.conf have just had a line at the top to include apache2.conf?
--
To UNSUBSCRIBE, email
Debian Users
>>The README file that came with Debian doesn't cover the difference
>>between the httpd.conf file and the apache2.conf file. Is the
>>httpd.conf file basically obsolete?
> >
> >I haven't had time to look into it at depth, but I think the
Kjetil Kjernsmo wrote:
On mandag 19 september 2005, 06:53, Steve Dondley wrote:
The README file that came with Debian doesn't cover the difference
between the httpd.conf file and the apache2.conf file. Is the
httpd.conf file basically obsolete?
I haven't had time to lo
David Huemer wrote:
I tried the provided .deb package and also compiled my own apache2
server and discovered the following: If you use the Debian package all
configuration is done in the apache2.conf and the httpd.conf is only for
compatibility reasons. If you compile your own server, all
ng to scroll through all those lines to make one
little change on a virtual host or something like that. I fully
embrace mods-enabled, sites-enabled, and the like. I guess Apache made
the change from httpd.conf to Apache2.conf to make it clear that
things are being consolidated. Let's hope for m
On Mon, Sep 19, 2005 at 08:58:52AM +0200, David Huemer wrote:
> I tried the provided .deb package and also compiled my own apache2
> server and discovered the following: If you use the Debian package all
> configuration is done in the apache2.conf and the httpd.conf is only for
> c
05, 06:53, Steve Dondley wrote:
> > > The README file that came with Debian doesn't cover the difference
> > > between the httpd.conf file and the apache2.conf file. Is the
> > > httpd.conf file basically obsolete?
>
> See /etc/apache2/README. It's pretty
I tried the provided .deb package and also compiled my own apache2
server and discovered the following: If you use the Debian package all
configuration is done in the apache2.conf and the httpd.conf is only for
compatibility reasons. If you compile your own server, all configuration
files are in
On Mon, Sep 19, 2005 at 08:26:37AM +0200, Kjetil Kjernsmo wrote:
> On mandag 19 september 2005, 06:53, Steve Dondley wrote:
> > The README file that came with Debian doesn't cover the difference
> > between the httpd.conf file and the apache2.conf file. Is the
> >
On mandag 19 september 2005, 06:53, Steve Dondley wrote:
> The README file that came with Debian doesn't cover the difference
> between the httpd.conf file and the apache2.conf file. Is the
> httpd.conf file basically obsolete?
I haven't had time to look into it at dep
The README file that came with Debian doesn't cover the difference
between the httpd.conf file and the apache2.conf file. Is the
httpd.conf file basically obsolete? Should I just put all directives
and containers in apache2.conf file? Does it matter?
--
Dondley Communications
Hi,
I have installed the Apache2 webserver and the documentation (apache2-doc).
Unfortunately, the Debian default configuration for the apache2 seems to be
broken regarding the content negotiation:
E.g.: `http://localhost/doc/apache2-doc/manual/'
shows just the content of the type-map file.
Don'
his problem? It seems to be related to "Include"
statements in apache2.conf. As far as I know apache2 did not update in
the last week or so I doubt whether the error is related to apache2 at
all. Anybody any ideas?
Ronald
<<>>
I have to change a few "Includes" statemen
hat I can't get apache2 to install. It *seems* like
apache.conf isn't being created by apache2-common and when
apache2-mpm-prefork's processing tries to read the file, it blows up. I
am sure that, after apt-get errors out, the /etc/apache2 directory
doesn't contain an apache2.c
51 matches
Mail list logo
