Hello Paride,
for a kinde of integrity i did the same with the ubuntu 20.04 Apache.
:~$ apt-get source apache2
:~$ cp apache2-2.4.41/modules/proxy/mod_proxy_balancer.c .
:~$ vim mod_proxy_balancer.c
[...]
/* Ignore parameters if this looks like XSRF */
ref = apr_table_get(r->headers_in, "
There is an copy & paste bug in my Substitute it must be.
[...]
Substitute "s|http://192.168.56.170:81|http://192.168.56.70|i"
[...]
And i investigate further on i grab some httpd versions i can get from
wget http://archive.apache.org/dist/httpd/httpd-2.4.39.tar.gz
wget http://a
Hello Paride,
i am sorry but i am not familiar with LXD containers and yes i can
reproduce the issue. So i use my config from above
The Proxy Machine is now Debian 11 apache2 2.4.51-1~deb11u1
18.04/bionic apache2 2.4.29-1ubuntu4.20 -> is working as expected
20.04/focal apache2 2.4.41-4ubunt
Hello Paride,
any kind of suggestion on that issue.
thx Horst
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939678
Title:
Apache2 Balancer Manager not working after dist-upgrade to focal
behind
Hello Paride, today i recreate my bigger configuration with Debian 10
and 11
Debian 10 Proxy and Debian 10 LB Manager witch Apache 2.4.38-3+deb10u5
every thing worked as expected no error log entrys. LB Manager over
proxy is fully workable.
- - - - - - - - - - - - - - - - - - -
Hello Paride, thank you for your reply. I'am not sure that your minimal
configuration reproduce the hole issue. I reproduce your config with
18.04/bionic and 20.04/focal. What i can say is yes with focal i saw
also the error
[...]
[Wed Aug 18 08:22:14.241792 2021] [authz_core:debug] [pid 4199:tid
mybe i thought with a newer apache the problem is solved but with no
luck.
LB Manager VM dist-upgrade 21.04 / hirsute
:~# vim /etc/update-manager/release-upgrades
[...]
#Prompt=lts
Prompt=normal
:~# do-release-upgrade
:~# shutdown -r now
:~# lsb_release -a
No LSB modules are available.
Distribu
Public bug reported:
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal
Approximately two years ago i creat the following bug report.
https://bugs.launchpad.net/apache2/+bug/1842701/
At the end talk to that bug report is a hin "that bug is still opend in
apache 2.4.41" and further o
from my perspective looks good with the new version from focal-proposed
p.s. @christian what should i say with that name and that kind of job
:-)
what i did in detail. took the configs and the checks from above and test the
proposed version. on a virtual test box and the more close produktion m
hi christian,
looks good for me.
what i did on a test system more closer to production. to get things
working with the buggy version revert the workaround to require
#SSLProxyVerify none
SSLProxyVerify require
pull your packages
wget
https://launchpad.net/~ci
hi sergio,
my be i have a solution with selfsign.
over all i recreate the apache packages with the new verion
2.4.41-4ubuntu3.3 and use only the patch with the tow rows involved.
then i found a descripion to create a rootCA with ocsp inside
https://raymii.org/s/tutorials/OpenSSL_command_line_Ro
hi sergio,
test with selfsign if i create selfsign there is no problem, because no
chain no ocsp_uri inside ther cert.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
:~$ openssl s_client -showcerts -connect localhorst.org:443
:~$ vim localhorst.org.crt
-BEGIN CERT
dear ubuntu/apache maintainer,
please excuse me my impatience. is there any release plan to get this
fix final done in the focal apache? this bug stops my effort to continue
the dist-upgrade(s) from bionic to focal.
regards horst
--
You received this bug notification because you are a member of
Public bug reported:
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename: focal
After dist-upgrade bionic -> focal and Apache Update
from: 2.4.29-1ubuntu4.14
to: 2.4.41-4ubuntu3.1
Overall I found a hint in
https://downloads.apache.org/httpd/CHANGES_2.4
[...]
*) mod_ssl: O
hi Christian,
thx for the info and please let me know if there is a posibility
solution for the future releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842701
Title:
Apache2 Balancer Manage
with the new packages my problem is solved.
on more question in the next Ubuntu release for example 20.04 with a
newer apache version. it is possible that this kind of problem is
comming back again? because the patches are in the newer version from
apache.org.
thx again, regards horst
--
You re
i'am sorry for that...
on the ubuntu page is a further more discussion and i explain and test
the initilal problem LB manager behind a proxy ist not working after the
update. mybe this helped out to get my problem more clear.
lynx is only comming to the playground for debug the initial problem.
l
unfortunately the ppa solve also not the behind a proxy problem.
usualy in my produktion in front (bastion/proxy host) is debian 9
so i test both with debian 9 and ubuntu 18.04 ppa at on the proxy
host.
i modified a littel the configuration to get closer for the
production env.
VM with LB Manager
sorry i can't use your PPAs in the production. for a quick test i used
my patched compiled module where only one line is changing from the
patch i discribed above
:$ diff mod_proxy_balancer.c_org mod_proxy_balancer.c
1081c1081
< && (!ref || !safe_referer(r, ref))) {
---
> && (ref &
with that patch from here
https://bz.apache.org/bugzilla/show_bug.cgi?id=63688#c3
and with the ubuntu 18.04 apache2 sources
:~$ apt-get source apache2
:~$ find . -name mod_proxy_balancer.c
./apache2-2.4.29/.pc/balance-member-long-hostname-part2.patch/modules/proxy/mod_proxy_balancer.c
./apache2
https://bz.apache.org/bugzilla/show_bug.cgi?id=63688#c5
and there is a Patch available
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842701
Title:
Apache2 Balancer Manager mod_proxy_balancer not w
i found https://bz.apache.org/bugzilla/show_bug.cgi?id=63688 and this
sounds like of a similar problem and i can reporduce that within debian
10 which i described there.
** Bug watch added: bz.apache.org/bugzilla/ #63688
https://bz.apache.org/bugzilla/show_bug.cgi?id=63688
--
You received th
Hi all,
same for me with Ubunut 18.04
:~# dpkg -l | grep snmp
ii snmp 5.7.3+dfsg-1.8ubuntu3.2
ii snmpd 5.7.3+dfsg-1.8ubuntu3.2
ii libsnmp-base 5.7.3+dfsg-1.8ubuntu3.2
ii libsnmp-dev5.7.3+dfsg-1.8ubuntu3.2
ii libsnmp30:amd645.7.3+dfsg-1.8ubuntu3.2
Public bug reported:
OS
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename: bionic
I use this kind of configuration to reache the Balancer Manager.
-
|Bastian Host |
|Apache Proxy | ---> LB Apache Balancer Manger
-
After Apache Update
fr
simliar problem with proxy_balancer / slotmem_shm
in my further on configuration with prox_balancer. i figured out a
another start/reboot problem with proxy_balancer configuration.
remember
:~# systemctl disable apache2
default apache is disabled -> reboot -> /var/run/apache2/ don't exist
:~#
ok and thx should be now
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838932
kind regards horst
** Bug watch added: Debian Bug tracker #838932
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838932
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: "patch for /etc/apache2/envvars"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1627339/+attachment/4748279/+files/envvars.patch
** Tags added: apache2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Description changed:
- multiple instances don't start after reboot without the default apache
- enabled.
+ multiple apache instances don't start after reboot without the default
+ apache enabled.
:~# sh /usr/share/doc/apache2/examples/setup-instance xxx
:~# sh /usr/share/doc/apache2/exam
Public bug reported:
multiple instances don't start after reboot without the default apache
enabled.
:~# sh /usr/share/doc/apache2/examples/setup-instance xxx
:~# sh /usr/share/doc/apache2/examples/setup-instance yyy
:~# systemctl enable apache2-xxx
:~# systemctl enable apache2-yyy
disable defa
mybe it looks like a problem with logrotating
/var/log/proftpd/proftpd.log
[...]
2014-09-07 06:25:07,634 *** proftpd[1664] ***.***.***.***: ProFTPD 1.3.5rc3
standalone mode SHUTDOWN
-> no "STARTUP" entry
cat /etc/crontab
[...]
25 6* * * roottest -x /usr/sbin/anacron || ( cd / &&
today there is a update from ubuntu 10.04.1 LTS kernel up to
2.6.32-28-server.
package -> linux-image-2.6.32-28-server2.6.32-28.55
that kernel solve the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
maybe it help.
in a test environment i made a realease-upgrade to ubuntu 10.10 with kernel
2.6.35-24-server.
you run in a grub2 error but with editing manually
vim /boot/grub/grub.cfg
:%s/(hd0,msdos1)/(hd0,0)/g
the VM boot/reboot the kernel 2.6.35-24-server in a regular way.
--
You received
** Description changed:
System: Ubuntu 10.04.1 LTS
Package: linux-image-2.6.32-27-virtual
The servers are running as guests under XenServer 5.6 (with update 1,2 and 4).
After installation of the new kernel, my ubuntu guests won't reboot or
restart as they did with the older kernels.
i figured out after a while one of the VCPU increase nearly to 100% on the
performance screen from xencenter see performance.jpg
if i change the VCPU from the VM to only one, the reboot behavior changed to
a normal manner.
** Attachment added: "performance.jpg"
https://bugs.launchpad.net/ubun
34 matches
Mail list logo
