blocks|key|2427788|text|您可以使用专门制作的图像来处理此类问题，比如抛锚/基象-码头。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2427789|参见"PID+1僵尸收割问题"：通过将脚本声明为守护进程，您将确保图像正确处理关机信号。|2427790|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/phusion/baseimage-docker|1|https://stackoverflow.com/a/33119321/6309|2|https://github.com/phusion/baseimage-docker#adding_additional_daemons^0|M|8|0|0|3|B|1|I|A|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]|$A|Z|B|10|1|11]]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

You can use a dedicated image made to handle that kind of issue, like <a href="https://github.com/phusion/baseimage-docker" rel="nofollow noreferrer"><code>phusion/baseimage-docker</code></a>. 

See "<a href="https://stackoverflow.com/a/33119321/6309">PID 1 zombie reaping issue</a>": by <a href="https://github.com/phusion/baseimage-docker#adding_additional_daemons" rel="nofollow noreferrer">declaring your script as a daemon</a>, you will make sure the image handles the shutdown signal properly.

blocks|key|1871165|text|最后，我在容器中创建了runstardog.sh脚本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1871166|set+-e
function+shutdown()+{++++++++
+$STARDOG_BINARIES/bin/stardog-admin+server+stop++-p+xxx+-u+admin++++
}

$STARDOG_BINARIES/bin/stardog-admin+server+start+&&+(tail+-f+/storage/stardog.log+&)+&&+while+(pidof+java+>+/dev/null);+do+sleep+1;+done

trap+"{+shutdown+}"+EXIT
exit+0|code-block|syntax|javascript|1871167|由包含以下陷阱的startup.sh脚本执行|1871168|trap+'kill+-TERM+$PID'+TERM+INT
$STARDOG_BINARIES/runstardog.sh+&
PID=$!
wait+$PID
trap+-+TERM+INT
wait+$PID
EXIT_STATUS=$?|1871169|然后，当我想停止服务器时，我在托管容器的服务器上调用stop.sh，该容器标识stardog容器的CID，使用docker关闭stardog，停止并删除容器。|1871170|replace="\1"
find="([a-z0-9]{12})\s%2Bplatform_stardog.*"
CID=$(+docker+ps+%7C+tail+--lines=%2B2+%7C+sed+"/platform_stardog/!d"++%7C+perl+-lpe++"s@$find@$replace@g"++)

if+[+-z+"$CID"+];+
then
++++echo+"No+existing+container+named+platform_stardog+was+found"
else
++++echo+"docker+exec++/stardog_binaries/stopstardog.sh+in+platform_stardog+Container+$CID:"
++++docker+exec+${CID}+/stardog_binaries/stopstardog.sh
++++echo+"stop+and+delete+docker+container."
++++/usr/local/bin/docker-compose+-p+platform+-f+docker-compose.yml+stop+-t+30+stardog+&&+/usr/local/bin/docker-compose+-p+platform+-f+docker-compose.yml+rm+--force+-v+stardog
fi|1871171|我得到确认，这是因为Stardog的输出“Stardog服务器成功地接收了关机请求”，并且关闭过程不需要很长时间。它用来挂起通过码头指定的30秒的停止-t+30。|1871172|谢谢@VonC+--我接下来要试试这个方法。|1871173|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

In the end I created a runstardog.sh script in the container. 

<pre><code>set -e
function shutdown() { 
 $STARDOG_BINARIES/bin/stardog-admin server stop -p xxx -u admin 
}

$STARDOG_BINARIES/bin/stardog-admin server start &amp;&amp; (tail -f /storage/stardog.log &amp;) &amp;&amp; while (pidof java &gt; /dev/null); do sleep 1; done

trap "{ shutdown }" EXIT
exit 0
</code></pre>

Which is executed by a startup.sh script that contains the following trap

<pre><code>trap 'kill -TERM $PID' TERM INT
$STARDOG_BINARIES/runstardog.sh &amp;
PID=$!
wait $PID
trap - TERM INT
wait $PID
EXIT_STATUS=$?
</code></pre>

and then when I want to stop the server I call stop.sh on the server hosting the container which identifies the CID for the stardog container, shuts down stardog using docker exec and the stops and deletes the container.

<pre><code>replace="\1"
find="([a-z0-9]{12})\s+platform_stardog.*"
CID=$( docker ps | tail --lines=+2 | sed "/platform_stardog/!d" | perl -lpe "s@$find@$replace@g" )

if [ -z "$CID" ]; 
then
 echo "No existing container named platform_stardog was found"
else
 echo "docker exec /stardog_binaries/stopstardog.sh in platform_stardog Container $CID:"
 docker exec ${CID} /stardog_binaries/stopstardog.sh
 echo "stop and delete docker container."
 /usr/local/bin/docker-compose -p platform -f docker-compose.yml stop -t 30 stardog &amp;&amp; /usr/local/bin/docker-compose -p platform -f docker-compose.yml rm --force -v stardog
fi
</code></pre>

I get confirmation that this works due to stardog's output '
Stardog server successfully received the shutdown request' and that the shutdown process does not take long. It used to hang for the 30 seconds specified via the docker compose stop -t 30

Thanks @VonC I'll try that method next.

I'm running Stardog 4.0 in an Ubuntu 15.04 container with open jdk8 which runs fine. I want to handle <a href="https://www.ctl.io/developers/blog/post/gracefully-stopping-docker-containers/" rel="nofollow">gracefully shutting down stardog</a> using a trap.

To execute stardog in a container so that it continues to run I've been using the following which works well

<pre><code>$SBIN/bin/stardog-admin server start &amp;&amp; (tail -f /storage/stardog.log &amp;) &amp;&amp; while (pidof java &gt; /dev/null); do sleep 1; done
</code></pre>

Without the following the container will run for a few seconds and stop

<pre><code>&amp;&amp; (tail -f /storage/stardog.log &amp;) &amp;&amp; while (pidof java &gt; /dev/null); do sleep 1; done
</code></pre>

However this leads to multiple PID's within the container

<pre><code>root 1 0.0 0.0 18384 3236 ? Ss 14:04 0:02 /bin/bash /stardog_binaries/startup.sh
root 45 0.1 4.9 4619052 406940 ? Sl 14:04 0:10 java -Xms2g -Xmx2g -XX:MaxDirectMemorySize=4g -XX:SoftRefLRUPolicyMSPerMB=1 -XX:+UseParallelOldGC -XX:+UseCompressedOops -Djavax.xml.datatype.DatatypeFactory=org.apache.xerc
root 97 0.0 0.0 4412 740 ? S 14:04 0:00 tail -f /storage/stardog.log
root 12108 0.2 0.0 18184 3100 ? Ss 15:44 0:00 bash
root 12122 0.0 0.0 4376 784 ? S 15:44 0:00 sleep 1
</code></pre>

And the following trap does not work to shutdown stardog when the container is shutting down

<pre><code>trap 'kill -TERM $PID' TERM INT
$SBIN/bin/stardog-admin server start &amp;&amp; (tail -f /storage/stardog.log &amp;) &amp;&amp; while (pidof java &gt; /dev/null); do sleep 1; done
PID=$!
wait $PID
trap - TERM INT
wait $PID
EXIT_STATUS=$?
</code></pre>

So my question is how do I properly trap the $SBIN/bin/stardog-admin server start such that when the container shuts downs, stardog gracefully exits.

Regards
Conteh

How do I create a PID trap for multiple commands separated by &&

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我在一个打开jdk8的Ubuntu15.04容器中运行StarDoG4.0，运行良好。我想用陷阱来处理。为了在容器中执行stardog，使它继续运行，我一直在使用以下操作，它运行得很好$SBIN/bin/stardog-admin server start && (tail -f /storage/stardog.lo...

问如何为由&&分隔的多个命令创建PID陷阱
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何为由&&分隔的多个命令创建PID陷阱EN