Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

[AEM Gems Webinar | Wednesday, Feb 22nd, 8:00 AM (PST) OR 5:00 PM (CET) OR 9:30 PM (IST)] Accelerating Experience Manager as a Cloud Service development with Rapid Development Environments
SOLVED

Local Dispatcher quits when terminal resizes due to SIGWINCH

Avatar

Level 1

SIGWINCH is a known signal that Apache2 interprets as a signal to do a graceful shutdown:

 

This means that when following the set up of a local Dispatcher, after running the "docker_run.sh ..." command, any resize / update / movement of the terminal will generate:

 

[Tue Sep 06 17:10:46.525423 2022] [core:notice] [pid 1:tid 281473502321736] AH00094: Command line: 'httpd -d /etc/httpd -f /etc/httpd/conf/httpd.conf -D FOREGROUND -D ENVIRONMENT_DEV'
[Tue Sep 06 17:15:31.209544 2022] [mpm_worker:notice] [pid 1:tid 281473502321736] AH00296: caught SIGWINCH, shutting down gracefully
[Tue Sep 06 17:15:34.601264 2022] [core:warn] [pid 1:tid 281473502321736] AH00045: child process 188 still did not exit, sending a SIGTERM
[Tue Sep 06 17:15:34.601441 2022] [core:warn] [pid 1:tid 281473502321736] AH00045: child process 189 still did not exit, sending a SIGTERM
[Tue Sep 06 17:15:34.601489 2022] [core:warn] [pid 1:tid 281473502321736] AH00045: child process 190 still did not exit, sending a SIGTERM

which is totally bizarre! I can reproduce this on demand. Even if I minimize the terminal window, the signal is always sent.

 

Has anyone else experienced this? Has anyone got a workaround? This has made local Dispatcher browsing/testing basically impossible, as the service and the docker instance shut down.

 

Thanks in advance!

1 Accepted Solution

Avatar

Correct answer by
Level 1

Solved by Adobe Support – thank you! For posterity, the fix is to run the command in Docker detached mode either by:

dispatcher/bin/docker_run.sh path/to/dispatcher/src localhost:4503 80 &

or with docker directly:

docker -td dockerimage

View solution in original post

1 Reply

Avatar

Correct answer by
Level 1

Solved by Adobe Support – thank you! For posterity, the fix is to run the command in Docker detached mode either by:

dispatcher/bin/docker_run.sh path/to/dispatcher/src localhost:4503 80 &

or with docker directly:

docker -td dockerimage