I created a symlink from /usr/sbin/apache2ctl to /usr/sbin/apachectl and
that fixed the problem temporarily. I am not familiar enough with
apache2ctl to know if it is backwards-compatible with apachectl so I
wonder if certain scripts will break because of what I did on my system
but it works for me
I have this feeling that you have apache2 installed, and you also have
apache removed (which is not the same as purged). If this is the case,
what happens is that the twiki postinst notices that /etc/init.d/apache
exists, and so runs it, which fails dismally, leading to this problem.
--
Twiki pac
Yes, exactly. Shouldn't twiki check to see which apache is the running one
(because nowadays there are at least three no? httpd, apache, apache-perl from
Ubuntu, etc.)
Perhaps twiki should look at the access log to see the last access time and
deduce the version of apache that way?
In any case,
Both of which are fairly prohibitive to program in shell. :-)
At this point, I don't think it's a bug that I can really do anything about
this close to the Feisty release.
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://bugs.launchpad.net/bugs/96464
You received this
Yeah, good point. Well it is not a show-stopper, not _that_ serious a
bug that it can't wait. Maybe something like this might help?
httpd_vers = $( ls -Rlc /var/log/ | grep "access.log$" | awk '{print
$8}' | head -n 1 )
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https:
Actually, a thought did occur me just before I got today -
We already if the init script exists before we run invoke-rc.d in the
postinst, so my thought was we also check if
/var/lib/dpkg/info/.list exists. It's a little messy and also a
little gross, and I'd personally prefer to not do it. It als
twiki (1:4.0.5-9.1ubuntu1) feisty; urgency=low
* Add a horrible hack to try and detect if htpasswd supports -b.
Now I feel dirty. (LP: #93669)
* Prefer apache2 to apache in the webserver list, and add mini-httpd.
* Only attempt to restart any of the apache's if /usr/sbin/apachectl
ex
** Changed in: twiki (Ubuntu)
Sourcepackagename: update-manager => twiki
Importance: Undecided => High
Status: Unconfirmed => Confirmed
Target: None => ubuntu-7.04
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://launchpad.net/bugs/96464
--
ubuntu-bu
twiki 1:4.0.5-9.1ubuntu1 has built successfully.
** Changed in: twiki (Ubuntu)
Status: Fix Committed => Fix Released
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://bugs.launchpad.net/bugs/96464
You received this bug notification because you are a member of Ub
I created a symlink from /usr/sbin/apache2ctl to /usr/sbin/apachectl and
that fixed the problem temporarily. I am not familiar enough with
apache2ctl to know if it is backwards-compatible with apachectl so I
wonder if certain scripts will break because of what I did on my system
but it works for me
I have this feeling that you have apache2 installed, and you also have
apache removed (which is not the same as purged). If this is the case,
what happens is that the twiki postinst notices that /etc/init.d/apache
exists, and so runs it, which fails dismally, leading to this problem.
--
Twiki pac
Yes, exactly. Shouldn't twiki check to see which apache is the running one
(because nowadays there are at least three no? httpd, apache, apache-perl from
Ubuntu, etc.)
Perhaps twiki should look at the access log to see the last access time and
deduce the version of apache that way?
In any case,
Both of which are fairly prohibitive to program in shell. :-)
At this point, I don't think it's a bug that I can really do anything about
this close to the Feisty release.
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://bugs.launchpad.net/bugs/96464
You received this
Yeah, good point. Well it is not a show-stopper, not _that_ serious a
bug that it can't wait. Maybe something like this might help?
httpd_vers = $( ls -Rlc /var/log/ | grep "access.log$" | awk '{print
$8}' | head -n 1 )
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https:
Actually, a thought did occur me just before I got today -
We already if the init script exists before we run invoke-rc.d in the
postinst, so my thought was we also check if
/var/lib/dpkg/info/.list exists. It's a little messy and also a
little gross, and I'd personally prefer to not do it. It als
twiki (1:4.0.5-9.1ubuntu1) feisty; urgency=low
* Add a horrible hack to try and detect if htpasswd supports -b.
Now I feel dirty. (LP: #93669)
* Prefer apache2 to apache in the webserver list, and add mini-httpd.
* Only attempt to restart any of the apache's if /usr/sbin/apachectl
ex
** Changed in: twiki (Ubuntu)
Sourcepackagename: update-manager => twiki
Importance: Undecided => High
Status: Unconfirmed => Confirmed
Target: None => ubuntu-7.04
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://launchpad.net/bugs/96464
--
ubuntu-bu
twiki 1:4.0.5-9.1ubuntu1 has built successfully.
** Changed in: twiki (Ubuntu)
Status: Fix Committed => Fix Released
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://bugs.launchpad.net/bugs/96464
You received this bug notification because you are a member of Ub
twiki 1:4.0.5-9.1ubuntu1 has built successfully.
** Changed in: twiki (Ubuntu)
Status: Fix Committed => Fix Released
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://bugs.launchpad.net/bugs/96464
You received this bug notification because you are a member of Ub
I created a symlink from /usr/sbin/apache2ctl to /usr/sbin/apachectl and
that fixed the problem temporarily. I am not familiar enough with
apache2ctl to know if it is backwards-compatible with apachectl so I
wonder if certain scripts will break because of what I did on my system
but it works for me
I have this feeling that you have apache2 installed, and you also have
apache removed (which is not the same as purged). If this is the case,
what happens is that the twiki postinst notices that /etc/init.d/apache
exists, and so runs it, which fails dismally, leading to this problem.
--
Twiki pac
Yes, exactly. Shouldn't twiki check to see which apache is the running one
(because nowadays there are at least three no? httpd, apache, apache-perl from
Ubuntu, etc.)
Perhaps twiki should look at the access log to see the last access time and
deduce the version of apache that way?
In any case,
Both of which are fairly prohibitive to program in shell. :-)
At this point, I don't think it's a bug that I can really do anything about
this close to the Feisty release.
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://bugs.launchpad.net/bugs/96464
You received this
Yeah, good point. Well it is not a show-stopper, not _that_ serious a
bug that it can't wait. Maybe something like this might help?
httpd_vers = $( ls -Rlc /var/log/ | grep "access.log$" | awk '{print
$8}' | head -n 1 )
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https:
Actually, a thought did occur me just before I got today -
We already if the init script exists before we run invoke-rc.d in the
postinst, so my thought was we also check if
/var/lib/dpkg/info/.list exists. It's a little messy and also a
little gross, and I'd personally prefer to not do it. It als
twiki (1:4.0.5-9.1ubuntu1) feisty; urgency=low
* Add a horrible hack to try and detect if htpasswd supports -b.
Now I feel dirty. (LP: #93669)
* Prefer apache2 to apache in the webserver list, and add mini-httpd.
* Only attempt to restart any of the apache's if /usr/sbin/apachectl
ex
** Changed in: twiki (Ubuntu)
Sourcepackagename: update-manager => twiki
Importance: Undecided => High
Status: Unconfirmed => Confirmed
Target: None => ubuntu-7.04
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://launchpad.net/bugs/96464
--
ubuntu-bu
I created a symlink from /usr/sbin/apache2ctl to /usr/sbin/apachectl and
that fixed the problem temporarily. I am not familiar enough with
apache2ctl to know if it is backwards-compatible with apachectl so I
wonder if certain scripts will break because of what I did on my system
but it works for me
I created a symlink from /usr/sbin/apache2ctl to /usr/sbin/apachectl and
that fixed the problem temporarily. I am not familiar enough with
apache2ctl to know if it is backwards-compatible with apachectl so I
wonder if certain scripts will break because of what I did on my system
but it works for me
I have this feeling that you have apache2 installed, and you also have
apache removed (which is not the same as purged). If this is the case,
what happens is that the twiki postinst notices that /etc/init.d/apache
exists, and so runs it, which fails dismally, leading to this problem.
--
Twiki pac
Yes, exactly. Shouldn't twiki check to see which apache is the running one
(because nowadays there are at least three no? httpd, apache, apache-perl from
Ubuntu, etc.)
Perhaps twiki should look at the access log to see the last access time and
deduce the version of apache that way?
In any case,
Both of which are fairly prohibitive to program in shell. :-)
At this point, I don't think it's a bug that I can really do anything about
this close to the Feisty release.
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://bugs.launchpad.net/bugs/96464
You received this
Yeah, good point. Well it is not a show-stopper, not _that_ serious a
bug that it can't wait. Maybe something like this might help?
httpd_vers = $( ls -Rlc /var/log/ | grep "access.log$" | awk '{print
$8}' | head -n 1 )
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https:
Actually, a thought did occur me just before I got today -
We already if the init script exists before we run invoke-rc.d in the
postinst, so my thought was we also check if
/var/lib/dpkg/info/.list exists. It's a little messy and also a
little gross, and I'd personally prefer to not do it. It als
twiki (1:4.0.5-9.1ubuntu1) feisty; urgency=low
* Add a horrible hack to try and detect if htpasswd supports -b.
Now I feel dirty. (LP: #93669)
* Prefer apache2 to apache in the webserver list, and add mini-httpd.
* Only attempt to restart any of the apache's if /usr/sbin/apachectl
ex
** Changed in: twiki (Ubuntu)
Sourcepackagename: update-manager => twiki
Importance: Undecided => High
Status: Unconfirmed => Confirmed
Target: None => ubuntu-7.04
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://launchpad.net/bugs/96464
--
ubuntu-bu
twiki 1:4.0.5-9.1ubuntu1 has built successfully.
** Changed in: twiki (Ubuntu)
Status: Fix Committed => Fix Released
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://bugs.launchpad.net/bugs/96464
You received this bug notification because you are a member of Ub
I have this feeling that you have apache2 installed, and you also have
apache removed (which is not the same as purged). If this is the case,
what happens is that the twiki postinst notices that /etc/init.d/apache
exists, and so runs it, which fails dismally, leading to this problem.
--
Twiki pac
Yes, exactly. Shouldn't twiki check to see which apache is the running one
(because nowadays there are at least three no? httpd, apache, apache-perl from
Ubuntu, etc.)
Perhaps twiki should look at the access log to see the last access time and
deduce the version of apache that way?
In any case,
Both of which are fairly prohibitive to program in shell. :-)
At this point, I don't think it's a bug that I can really do anything about
this close to the Feisty release.
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://bugs.launchpad.net/bugs/96464
You received this
Yeah, good point. Well it is not a show-stopper, not _that_ serious a
bug that it can't wait. Maybe something like this might help?
httpd_vers = $( ls -Rlc /var/log/ | grep "access.log$" | awk '{print
$8}' | head -n 1 )
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https:
Actually, a thought did occur me just before I got today -
We already if the init script exists before we run invoke-rc.d in the
postinst, so my thought was we also check if
/var/lib/dpkg/info/.list exists. It's a little messy and also a
little gross, and I'd personally prefer to not do it. It als
twiki (1:4.0.5-9.1ubuntu1) feisty; urgency=low
* Add a horrible hack to try and detect if htpasswd supports -b.
Now I feel dirty. (LP: #93669)
* Prefer apache2 to apache in the webserver list, and add mini-httpd.
* Only attempt to restart any of the apache's if /usr/sbin/apachectl
ex
** Changed in: twiki (Ubuntu)
Sourcepackagename: update-manager => twiki
Importance: Undecided => High
Status: Unconfirmed => Confirmed
Target: None => ubuntu-7.04
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://launchpad.net/bugs/96464
--
ubuntu-bu
twiki 1:4.0.5-9.1ubuntu1 has built successfully.
** Changed in: twiki (Ubuntu)
Status: Fix Committed => Fix Released
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://bugs.launchpad.net/bugs/96464
You received this bug notification because you are a member of Ub
I created a symlink from /usr/sbin/apache2ctl to /usr/sbin/apachectl and
that fixed the problem temporarily. I am not familiar enough with
apache2ctl to know if it is backwards-compatible with apachectl so I
wonder if certain scripts will break because of what I did on my system
but it works for me
I have this feeling that you have apache2 installed, and you also have
apache removed (which is not the same as purged). If this is the case,
what happens is that the twiki postinst notices that /etc/init.d/apache
exists, and so runs it, which fails dismally, leading to this problem.
--
Twiki pac
Yes, exactly. Shouldn't twiki check to see which apache is the running one
(because nowadays there are at least three no? httpd, apache, apache-perl from
Ubuntu, etc.)
Perhaps twiki should look at the access log to see the last access time and
deduce the version of apache that way?
In any case,
Both of which are fairly prohibitive to program in shell. :-)
At this point, I don't think it's a bug that I can really do anything about
this close to the Feisty release.
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://bugs.launchpad.net/bugs/96464
You received this
Yeah, good point. Well it is not a show-stopper, not _that_ serious a
bug that it can't wait. Maybe something like this might help?
httpd_vers = $( ls -Rlc /var/log/ | grep "access.log$" | awk '{print
$8}' | head -n 1 )
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https:
Actually, a thought did occur me just before I got today -
We already if the init script exists before we run invoke-rc.d in the
postinst, so my thought was we also check if
/var/lib/dpkg/info/.list exists. It's a little messy and also a
little gross, and I'd personally prefer to not do it. It als
twiki (1:4.0.5-9.1ubuntu1) feisty; urgency=low
* Add a horrible hack to try and detect if htpasswd supports -b.
Now I feel dirty. (LP: #93669)
* Prefer apache2 to apache in the webserver list, and add mini-httpd.
* Only attempt to restart any of the apache's if /usr/sbin/apachectl
ex
** Changed in: twiki (Ubuntu)
Sourcepackagename: update-manager => twiki
Importance: Undecided => High
Status: Unconfirmed => Confirmed
Target: None => ubuntu-7.04
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://launchpad.net/bugs/96464
--
ubuntu-bu
twiki 1:4.0.5-9.1ubuntu1 has built successfully.
** Changed in: twiki (Ubuntu)
Status: Fix Committed => Fix Released
--
Twiki package: /usr/sbin/apachectl is not executable, exiting...
https://bugs.launchpad.net/bugs/96464
You received this bug notification because you are a member of Ub
54 matches
Mail list logo
