pespin has uploaded this change for review.
bts: limit stderr logging to NOTICE to avoid long write() to ext4 fs
stderr being redirected to a file in the ext4 filesystem sometimes ends
up in write() syscall taking >500ms, which means the entire osmo-bts
process stalls during that time and we miss clock updates up to a
threshold which makes osmo-bts process exit with an error.
Let's decrease logging verbosity to NOTICE for now with the aim to not
run into those stalls during normal operation, while we can re-eanble
this manually when debugging the write() issue.
Related: OS#6794
Change-Id: I74c4abf7571d2a0f9ee22402a949dbde02896d7d
---
M bts/osmo-bts.cfg
1 file changed, 11 insertions(+), 10 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/26/41926/1
diff --git a/bts/osmo-bts.cfg b/bts/osmo-bts.cfg
index c583d32..7ac38a1 100644
--- a/bts/osmo-bts.cfg
+++ b/bts/osmo-bts.cfg
@@ -17,16 +17,17 @@
logging print level 1
!
logging level set-all notice
- logging level rsl info
- logging level meas info
- logging level pag info
- logging level l1c info
- logging level dsp info
- logging level pcu info
- logging level trx info
- logging level osmux info
- logging level lmib info
- logging level lmux info
+ !Disabled due to stderr redirect to ext4 filesystem creating long writes of >500ms (OS#6794):
+ !logging level rsl info
+ !logging level meas info
+ !logging level pag info
+ !logging level l1c info
+ !logging level dsp info
+ !logging level pcu info
+ !logging level trx info
+ !logging level osmux info
+ !logging level lmib info
+ !logging level lmux info
!
line vty
no login
To view, visit change 41926. To unsubscribe, or for help writing mail filters, visit settings.