ubuntu-push-client is writing frequent debug messages to logs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
Unassigned | ||
Ubuntu Push Notifications |
Fix Released
|
High
|
John Lenton | ||
ubuntu-push (Ubuntu RTM) |
Fix Released
|
High
|
John Lenton |
Bug Description
I was trying to figure out where excessive file system writes were coming from (to try to reduce flash writes and hence reduce power consumption) and I spotted that /home/phablet/
Example:
2014/10/01 13:40:20.041291 DEBUG polld Done.
2014/10/01 13:40:25.049221 DEBUG requested wakeup at 2014-10-01 13:45:25 +0000 UTC
2014/10/01 13:40:25.059697 DEBUG cleared wakelock cookie 9138b63f-
2014/10/01 13:44:27.637939 DEBUG May be connected; checking...
2014/10/01 13:44:27.710221 DEBUG Connection check says: true
2014/10/01 13:44:29.850224 DEBUG ping.
2014/10/01 13:45:25.004012 DEBUG got woken up; time is 2014-10-01 13:45:25.00389046 +0000 UTC
2014/10/01 13:45:25.014506 DEBUG got wakelock cookie of fdb062ee-
2014/10/01 13:45:25.035442 DEBUG poking polld.
2014/10/01 13:45:25.039985 DEBUG waiting for polld to signal Done.
2014/10/01 13:45:25.040297 DEBUG polld Done.
2014/10/01 13:45:30.047281 DEBUG requested wakeup at 2014-10-01 13:50:30 +0000 UTC
2014/10/01 13:45:30.056927 DEBUG cleared wakelock cookie fdb062ee-
2014/10/01 13:49:29.872030 DEBUG ping.
2014/10/01 13:50:30.004014 DEBUG got woken up; time is 2014-10-01 13:50:30.003893093 +0000 UTC
2014/10/01 13:50:30.014151 DEBUG got wakelock cookie of d249f247-
2014/10/01 13:50:30.035255 DEBUG poking polld.
2014/10/01 13:50:30.040046 DEBUG waiting for polld to signal Done.
2014/10/01 13:50:30.040348 DEBUG polld Done.
2014/10/01 13:50:35.047158 DEBUG requested wakeup at 2014-10-01 13:55:35 +0000 UTC
2014/10/01 13:50:35.058081 DEBUG cleared wakelock cookie d249f247-
2014/10/01 13:54:27.710627 DEBUG May be connected; checking...
2014/10/01 13:54:27.800558 DEBUG Connection check says: true
2014/10/01 13:54:29.898814 DEBUG ping.
2014/10/01 13:55:35.002961 DEBUG got woken up; time is 2014-10-01 13:55:35.002834341 +0000 UTC
2014/10/01 13:55:35.008301 DEBUG got wakelock cookie of b4e43b6f-
2014/10/01 13:55:35.028824 DEBUG poking polld.
2014/10/01 13:55:35.030867 DEBUG waiting for polld to signal Done.
2014/10/01 13:55:35.031011 DEBUG polld Done.
2014/10/01 13:55:40.038362 DEBUG requested wakeup at 2014-10-01 14:00:40 +0000 UTC
2014/10/01 13:55:40.046331 DEBUG cleared wakelock cookie b4e43b6f-
2014/10/01 13:59:29.926215 DEBUG ping.
Seems a bit too chatty IMHO
Are the DEBUG messages necessary? Each write will cause flash writes and this uses up space and consumes power.
Related branches
- Samuele Pedroni: Approve
-
Diff: 88 lines (+10/-10)4 files modifiedclient/session/session.go (+3/-3)
debian/config.json (+1/-1)
launch_helper/kindpool.go (+3/-2)
launch_helper/legacy/legacy.go (+3/-4)
- Roberto Alsina (community): Approve
-
Diff: 88 lines (+10/-10)4 files modifiedclient/session/session.go (+3/-3)
debian/config.json (+1/-1)
launch_helper/kindpool.go (+3/-2)
launch_helper/legacy/legacy.go (+3/-4)
Changed in ubuntu-push (Ubuntu RTM): | |
importance: | Undecided → High |
assignee: | nobody → John Lenton (chipaca) |
Changed in ubuntu-push: | |
status: | Triaged → In Progress |
Changed in ubuntu-push (Ubuntu RTM): | |
status: | New → In Progress |
Changed in canonical-devices-system-image: | |
milestone: | ww03-2015 → ww05-2015 |
Changed in ubuntu-push: | |
status: | In Progress → Fix Committed |
Changed in canonical-devices-system-image: | |
status: | Confirmed → Fix Released |
Changed in ubuntu-push: | |
status: | Fix Committed → Fix Released |
We will move out of DEBUG and ensure we have enough logs in INFO.