This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
pespin gerrit-no-reply at lists.osmocom.orgpespin has submitted this change. ( https://gerrit.osmocom.org/c/osmo-gsm-tester/+/17487 ) Change subject: doc/manuals: Introduce Troubleshooting section about SIGKILL fix ...................................................................... doc/manuals: Introduce Troubleshooting section about SIGKILL fix Add a section describing how to clean up and recover osmo-gsm-tester state after a sigkill is used. Change-Id: I4841ab6d44a122140e6352df1fb6543418adc033 --- M doc/manuals/chapters/troubleshooting.adoc 1 file changed, 39 insertions(+), 0 deletions(-) Approvals: Jenkins Builder: Verified pespin: Looks good to me, approved diff --git a/doc/manuals/chapters/troubleshooting.adoc b/doc/manuals/chapters/troubleshooting.adoc index a3b5c8b..c7c6868 100644 --- a/doc/manuals/chapters/troubleshooting.adoc +++ b/doc/manuals/chapters/troubleshooting.adoc @@ -13,3 +13,42 @@ Careful: if a configuration item consists of digits and starts with a zero, you need to quote it, or it may be interpreted as an octal notation integer! Please avoid using the octal notation on purpose, it is not provided intentionally. + +=== {app-name} not running but resources still allocated + +The <<state_dir,reserved_resources.state>> is used to keep shared state of the +the resources allocated by any {app-name} instance. Each {app-name} instance +being run is responsible to de-allocate the used resources before exiting. In +general, upon receiving a shutdown action (ie. 'CTRL+C', 'SIGINT', python +exception, etc.), {app-name} is able to handle properly the situation and +de-allocate the resources before the process exits. Similarly, {app-name} also +takes care of terminating all its children processes being managed before +exiting itself. + +However, under some circumstances, {app-name} will be unable to de-allocate the +resources and they will remain allocated for subsequent {app-name} instances +which try to use them. That situation is usually reached when someone terminates +{app-name} in a hard way. Main reasons are {app-name} process receiving a +'SIGKILL' signal ('kill -9 $pid') which cannot be caught, or due to the entire +host being shut down in a non proper way. + +As a noticeable example, SIGKILL is known to be sent to {app-name} when it runs +under a jenkins shell script and any of the two following things happen: + +- User presses the red cross icon in the Jenkins UI to terminate the running + job. +- Connection between Jenkins master (UI) and Jenkins slave running the job is + lost. + +Once this situation is reached, one needs to follow 2 steps: + +- Gain console access to the <<install_main_unit,Main Unit>> and manually clean + or completely remove the 'reserved_resources.state' in the + <<state_dir,state_dir>>. In general it's a good idea to make sure no + {app-name} instance is running at all and then remove completely all files in + <<state_dir,state_dir>>, since {app-name} could theoretically have been killed + while writing some file and it may have ended up with corrupt content. +- Gain console access to the <<install_main_unit,Main Unit>> and each of the + <<install_slave_unit,Slave Units>> and kill any hanging long-termed processes + in there which may have been started by {app-name}. Some popular processes in + this list include 'tcpdump', 'osmo-\*', 'srs*', etc. -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-tester/+/17487 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-tester Gerrit-Branch: master Gerrit-Change-Id: I4841ab6d44a122140e6352df1fb6543418adc033 Gerrit-Change-Number: 17487 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: pespin <pespin at sysmocom.de> Gerrit-MessageType: merged -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20200317/54cb7028/attachment.htm>