svn: E175002: MERGE request on svn/xxx failed: 504 Gateway Time-out. Can't write response to output: Broken pipe - post-commit

Client ERROR:
svn: E175002: Commit failed (details follow):
svn: E175002: MERGE request on '/svn/my_repos/trunk/app' failed: 504 Gateway Time-out
Server ERROR LOG:
[Thu Aug 25 09:24:49.466833 2016] [dav:error] [pid 20669] [client 192.168.2.99:31447] Could not MERGE resource "/svn/my_repos/!svn/txn/68582-1h18" into "/svn/my_repos/trunk/app". [500, #0]
[Thu Aug 25 09:24:49.466882 2016] [dav:error] [pid 20669] [client 192.168.2.99:31447] Error constructing resource list. [500, #32]
[Thu Aug 25 09:24:49.466884 2016] [dav:error] [pid 20669] [client 192.168.2.99:31447] Can't write response to output: Broken pipe [500, #32]

in my case ,there error was caused by post-commit svnsync.
I changed this command:
/usr/bin/svnsync sync --non-interactive --username svnsync --password ****** ${svn_mirror_url}
to run background and redirect stdout and stderr to /dev/null
/usr/bin/svnsync sync --non-interactive --username svnsync --password ****** ${svn_mirror_url} >/dev/null 2>/dev/null &
reference links:
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&viewType=browseAll&dsMessageId=685574#messagefocus
http://stackoverflow.com/questions/4584904/what-causes-the-broken-pipe-error
http://unix.stackexchange.com/questions/60222/why-does-subversion-give-a-broken-pipe-error-when-piped-into-head

Related

[Docker x ColdFusion][Apache2] - (95)Operation not supported: mod_jk

The Apache2 on my Docker container keeps failing on starting; I already check the config using apachectl configtest, and it's returning OK. The error below is what I found under /var/log/apache2/error.log
[Wed Aug 10 15:17:30.643137 2022] [mpm_event:notice] [pid 465:tid 139744629492672] AH00489: Apache/2.4.52 (Ubuntu) mod_jk/1.2.46 configured -- resuming normal operations
[Wed Aug 10 15:17:30.643188 2022] [core:notice] [pid 465:tid 139744629492672] AH00094: Command line: '/usr/sbin/apache2'
[Mon Oct 31 22:14:51.535467 2022] [jk:crit] [pid 63:tid 274907793600] (95)Operation not supported: mod_jk: could not create jk_log_lock
But when I tried to uninstall and reinstall apache2, I could access the localhost:80, but the ColdFusion under it was not working. It just shows me the directory of the working directory..
Docker Desktop: v4.13.1
Docker: version 20.10.20, build 9fdeb9c
ColdFusion: 2018
This happens only on my Macbook 13 M2. I tried running it on a windows laptop, and it's working well.

Unable to use Docker, even though the demon is active

OS: Ubuntu LTS 22.4 | LTS 20.04
I had the same problem on ubuntu LTS 22.4 soo I downgraded to 20.04. I tried following all StackOverflow threads none of the solutions seems to work for me. I am not behind any proxy.
docker run hello-world
Unable to find image 'hello-world:latest' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": proxyconnect tcp: dial tcp: lookup http: Temporary failure in name resolution.
Docker servic seems to be working just okay:
Similar error on trying to login:
If any additional detail is required let me know in the comments, ill edit!
Status logs:
Aug 15 11:15:19 asus systemd[1]: Started Docker Application Container Engine.
Aug 15 11:15:19 asus dockerd[9448]: time="2022-08-15T11:15:19.531101032+05:30" level=info msg="API listen on /run/docker.sock"
Aug 15 11:15:57 asus dockerd[9448]: time="2022-08-15T11:15:57.920565157+05:30" level=warning msg="Error getting v2 registry: Get \"https://registry-1.docker.io/v2/\": proxyconnect tcp: dial tcp: lookup http: no such host"
Aug 15 11:15:57 asus dockerd[9448]: time="2022-08-15T11:15:57.920602673+05:30" level=info msg="Attempting next endpoint for pull after error: Get \"https://registry-1.docker.io/v2/\": proxyconnect tcp: dial tcp: lookup http: no such host"
Aug 15 11:15:57 asus dockerd[9448]: time="2022-08-15T11:15:57.922360289+05:30" level=error msg="Handler for POST /v1.41/images/create returned error: Get \"https://registry-1.docker.io/v2/\": proxyconnect tcp: dial tcp: lookup http: no such host"
Aug 15 11:18:45 asus dockerd[9448]: time="2022-08-15T11:18:45.641224726+05:30" level=warning msg="Error getting v2 registry: Get \"https://registry-1.docker.io/v2/\": proxyconnect tcp: dial tcp: lookup http: no such host"
Aug 15 11:18:45 asus dockerd[9448]: time="2022-08-15T11:18:45.641275059+05:30" level=info msg="Attempting next endpoint for pull after error: Get \"https://registry-1.docker.io/v2/\": proxyconnect tcp: dial tcp: lookup http: no such host"
Aug 15 11:18:45 asus dockerd[9448]: time="2022-08-15T11:18:45.643035998+05:30" level=error msg="Handler for POST /v1.41/images/create returned error: Get \"https://registry-1.docker.io/v2/\": proxyconnect tcp: dial tcp: lookup http: no such host"
Aug 15 11:24:07 asus dockerd[9448]: time="2022-08-15T11:24:07.919119361+05:30" level=info msg="Error logging in to endpoint, trying next endpoint" error="Get \"https://registry-1.docker.io/v2/\": proxyconnect tcp: dial tcp: lookup http: no such host"
Aug 15 11:24:07 asus dockerd[9448]: time="2022-08-15T11:24:07.919328823+05:30" level=error msg="Handler for POST /v1.41/auth returned error: Get \"https://registry-1.docker.io/v2/\": proxyconnect tcp: dial tcp: lookup http: no such host"
lines 1-23
journalctl logs:
sudo journalctl -fu docker.service
[sudo] password for rhythm:
-- Logs begin at Mon 2022-08-15 02:04:27 IST. --
Aug 15 13:18:20 asus dockerd[12520]: time="2022-08-15T13:18:20.454180157+05:30" level=info msg="Loading containers: done."
Aug 15 13:18:20 asus dockerd[12520]: time="2022-08-15T13:18:20.463895293+05:30" level=info msg="Docker daemon" commit=a89b842 graphdriver(s)=overlay2 version=20.10.17
Aug 15 13:18:20 asus dockerd[12520]: time="2022-08-15T13:18:20.463955619+05:30" level=info msg="Daemon has completed initialization"
Aug 15 13:18:20 asus systemd[1]: Started Docker Application Container Engine.
Aug 15 13:18:20 asus dockerd[12520]: time="2022-08-15T13:18:20.481004111+05:30" level=info msg="API listen on /run/docker.sock"
Aug 15 13:19:19 asus dockerd[12520]: time="2022-08-15T13:19:19.377705065+05:30" level=warning msg="Error getting v2 registry: Get \"https://registry-1.docker.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
Aug 15 13:19:19 asus dockerd[12520]: time="2022-08-15T13:19:19.377835945+05:30" level=info msg="Attempting next endpoint for pull after error: Get \"https://registry-1.docker.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
Aug 15 13:19:19 asus dockerd[12520]: time="2022-08-15T13:19:19.385691924+05:30" level=error msg="Handler for POST /v1.41/images/create returned error: Get \"https://registry-1.docker.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
Aug 15 13:30:26 asus dockerd[12520]: time="2022-08-15T13:30:26.166694545+05:30" level=info msg="Error logging in to endpoint, trying next endpoint" error="Get \"https://registry-1.docker.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
Aug 15 13:30:26 asus dockerd[12520]: time="2022-08-15T13:30:26.166963331+05:30" level=error msg="Handler for POST /v1.41/auth returned error: Get \"https://registry-1.docker.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"

set up php-fpm for a centos 8 container

FROM centos:8
RUN yum -y update && \
yum -y install php-fpm httpd
COPY . /var/www/html
CMD ["httpd", "-D", "FOREGROUND"]
I successfully created a simple container image based on centos:7 and it just works fine serving php files from document root. But, when I change the base to centos:8, php files are not served. The 503 Apache page is shown saying "The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."
When I look into /etc/httpd/logs/error_log inside the running container, I see:
[Wed Jun 10 10:57:33.236099 2020] [proxy:error] [pid 7:tid 139731249620736] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php-fpm/www.sock (*) failed
[Wed Jun 10 10:57:33.237322 2020] [proxy_fcgi:error] [pid 7:tid 139731249620736] [client 172.17.0.1:46224] AH01079: failed to make connection to backend: httpd-UDS
[Wed Jun 10 10:57:34.183056 2020] [proxy:error] [pid 7:tid 139731224442624] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php-fpm/www.sock (*) failed
[Wed Jun 10 10:57:34.183132 2020] [proxy_fcgi:error] [pid 7:tid 139731224442624] [client 172.17.0.1:46228] AH01079: failed to make connection to backend: httpd-UDS
Tried to make a difference by creating /run/php-fpm directory inside the container for testing purposes, but the error still persists.
I really wish this would be solvable without seding something into php-fpm or httpd configuration files of the container.

Why docker push registry errors on certificate file?

As described here How to setup docker private registry on ubuntu 16.04,
I changed /etc/hosts like this:
192.168.1.154 registry-server
192.168.1.90 registry-client
Then I pulled the registry image:
docker pull registry
Then I made certificate files
mkdir /etc/certs
cd /etc/certs
openssl req -newkey rsa:4096 -nodes -sha256 -keyout ca.key -x509 -days 365 -out ca.crt
I copied the ca.crt to these pathes in client host:
/etc/certs/
/etc/docker/certs.d/registry-server:5000/
Then I ran the container on the server host:
docker run -d -p 5000:5000 --restart=always --name registry -v /etc/certs:/etc/certs -e REGISTRY_HTTP_TLS_CERTIFICATE=/etc/certs/ca.crt -e REGISTRY_HTTP_TLS_KEY=/etc/certs/ca.key registry
I tagged the image
docker tag phpmyadmin/phpmyadmin:latest registry-server:5000/pma-test
But when I want to push the image registry-server:5000/pma-test to the server:
docker push registry-server:5000/pma-test:latest
The following error occurs:
Error response from daemon: open /etc/docker/certs.d/registry-server:5000: permission denied
======================================
Update:
I ran journalctl -xe, and found these errors:
Sep 30 13:58:37 docker.dockerd[926]: time="2019-09-30T13:58:37.229097561Z" level=debug msg="Calling GET /_ping"
Sep 30 13:58:37 docker.dockerd[926]: time="2019-09-30T13:58:37.238248010Z" level=debug msg="Calling POST /v1.38/images/registry-server:5000/pma-test/push?tag="
Sep 30 13:58:37 docker.dockerd[926]: time="2019-09-30T13:58:37.238670117Z" level=debug msg="hostDir: /etc/docker/certs.d/registry-server:5000"
Sep 30 13:58:37 docker.dockerd[926]: time="2019-09-30T13:58:37.238797277Z" level=debug msg="FIXME: Got an API for which error does not match any expected type!!!: open /etc/docker/certs.d/registry-server:5000: permission denied" error_type="*os.PathError" module=api
Sep 30 13:58:37 docker.dockerd[926]: time="2019-09-30T13:58:37.238831133Z" level=error msg="Handler for POST /v1.38/images/registry-server:5000/pma-test/push returned error: open /etc/docker/certs.d/registry-server:5000: permission denied"
Sep 30 13:58:37 docker.dockerd[926]: time="2019-09-30T13:58:37.238861895Z" level=debug msg="FIXME: Got an API for which error does not match any expected type!!!: open /etc/docker/certs.d/registry-server:5000: permission denied" error_type="*os.PathError" module=api
Sep 30 13:58:37 audit[926]: AVC apparmor="DENIED" operation="open" profile="snap.docker.dockerd" name="/etc/docker/certs.d/registry-server:5000/" pid=926 comm="dockerd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Sep 30 13:58:37 kernel: audit: type=1400 audit(1569851917.234:53): apparmor="DENIED" operation="open" profile="snap.docker.dockerd" name="/etc/docker/certs.d/registry-server:5000/" pid=926 comm="dockerd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Why did this error happen?
Docker version 19.03.2, build 6a30dfc
docker-compose version 1.24.0, build 0aa59064
Server and client host: Ubuntu 18.04
Finally, I found it:
I added the following line to /var/lib/snapd/apparmor/profiles/snap.docker.docker
/etc/docker/certs.d/** r,
Then I ran:
apparmor_parser -r /var/lib/snapd/apparmor/profiles/snap.docker.dockerd
And the problem solved.

Credential validation was not successful: Unable to connect to localhost:8080 from hawkular connection

My connection to hawkular-services-dist-0.30.0.Final of managiq ui is failed. But my manageiq configuration seems to be successful. I can examine the manageiq UI with below url, https://localhost:8443/ (The configuration ref site is http://www.manageiq.org/docs/get-started/docker). However in middleware tab of manageiq UI, adding new middleware provider always throws this message,
Credential validation was not successful: Unable to connect to localhost:8080
Please check the following captured pic.
Even more I have no idea which log files of manageiq container have this error statements.
Update
The ssl error message is shown below,
[Tue Feb 07 11:15:25.015949 2017] [ssl:warn] [pid 23] AH01909: RSA certificate configured for localhost:443 does NOT include an ID which matches the server name
[Tue Feb 07 11:15:25.041695 2017] [ssl:warn] [pid 23] AH01909: RSA certificate configured for localhost:443 does NOT include an ID which matches the server name
[Tue Feb 07 11:15:30.667617 2017] [proxy:error] [pid 134] (111)Connection refused: AH00957: HTTP: attempt to connect to 0.0.0.0:3000 (0.0.0.0) failed
[Tue Feb 07 11:15:30.667658 2017] [proxy:error] [pid 134] AH00959: ap_proxy_connect_backend disabling worker for (0.0.0.0) for 60s
[Tue Feb 07 11:15:30.667693 2017] [proxy_http:error] [pid 134] [client 172.17.0.1:42666] AH01114: HTTP: failed to make connection to backend: 0.0.0.0
[Tue Feb 07 11:15:30.727713 2017] [proxy:error] [pid 137] (111)Connection refused: AH00957: HTTP: attempt to connect to 0.0.0.0:3000 (0.0.0.0) failed
[Tue Feb 07 11:15:30.727756 2017] [proxy:error] [pid 137] AH00959: ap_proxy_connect_backend disabling worker for (0.0.0.0) for 60s
[Tue Feb 07 11:15:30.727766 2017] [proxy_http:error] [pid 137] [client 172.17.0.1:42672] AH01114: HTTP: failed to make connection to backend: 0.0.0.0
[Tue Feb 07 11:15:30.740819 2017] [proxy:error] [pid 135] (111)Connection refused: AH00957: HTTP: attempt to connect to 0.0.0.0:3000 (0.0.0.0) failed
[Tue Feb 07 11:15:30.740878 2017] [proxy:error] [pid 135] AH00959: ap_proxy_connect_backend disabling worker for (0.0.0.0) for 60s
[Tue Feb 07 11:15:30.740893 2017] [proxy_http:error] [pid 135] [client 172.17.0.1:42678] AH01114: HTTP: failed to make connection to backend: 0.0.0.0
[Tue Feb 07 11:15:36.283437 2017] [proxy:error] [pid 139] (111)Connection refused: AH00957: HTTP: attempt to connect to 0.0.0.0:3000 (0.0.0.0) failed
[Tue Feb 07 11:15:36.283474 2017] [proxy:error] [pid 139] AH00959: ap_proxy_connect_backend disabling worker for (0.0.0.0) for 60s
[Tue Feb 07 11:15:36.283483 2017] [proxy_http:error] [pid 139] [client 172.17.0.1:42684] AH01114: HTTP: failed to make connection to backend: 0.0.0.0
[Tue Feb 07 11:15:44.561119 2017] [proxy:error] [pid 140] (111)Connection refused: AH00957: HTTP: attempt to connect to 0.0.0.0:3000 (0.0.0.0) failed
[Tue Feb 07 11:15:44.561154 2017] [proxy:error] [pid 140] AH00959: ap_proxy_connect_backend disabling worker for (0.0.0.0) for 60s
[Tue Feb 07 11:15:44.561162 2017] [proxy_http:error] [pid 140] [client 172.17.0.1:42692] AH01114: HTTP: failed to make connection to backend: 0.0.0.0
[Tue Feb 07 11:16:07.212882 2017] [ssl:warn] [pid 557] AH01909: RSA certificate configured for localhost:443 does NOT include an ID which matches the server name
[Tue Feb 07 11:16:07.254083 2017] [ssl:warn] [pid 557] AH01909: RSA certificate configured for localhost:443 does NOT include an ID which matches the server name
Any idea?
Can you show the logs of hawkular-services ?
Did you create the "jhwang" user without errors ?

Resources