| Summary: | Gstreamer errors fill up disk space, in loop with knotify4 recording same error messages over and over | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bill C. Riemers <briemers> |
| Component: | gstreamer | Assignee: | Benjamin Otte <otte> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | hansecke, nathanael, otte, rdieter |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-14 02:08:51 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Bill C. Riemers
2012-01-13 14:37:33 UTC
Here is some fresh information. Currently this bug is happening right now. I have in one terminal: watch truncate --size=0 .xsession-errors So every two seconds the .xsession-errors file is truncated. Everytime I check the file is back to a significant size. When I do head .xsession-errors I see something like: [briemers@briemersw ~]$ head .xsession-errors (knotify4:3136): GStreamer-WARNING **: gstsystemclock: write control failed in wakeup_async, trying again : 28:No space left on device (knotify4:3136): GStreamer-CRITICAL **: gst_poll_write_control: assertion `set != NULL' failed (knotify4:3136): GStreamer-WARNING **: gstsystemclock: write control failed in wakeup_async, trying again : 28:No space left on device (knotify4:3136): GStreamer-CRITICAL **: gst_poll_write_control: assertion `set != NULL' failed I then did: killall knotify4 Now I see: [briemers@briemersw ~]$ ls -la .xsession-errors -rw-------. 1 briemers briemers 0 Feb 10 21:30 .xsession-errors I also see knotify4 has restarted. I killed my watch process, and the file size has remained at zero. So it looks like a HUGE part of the problem is gstreamer is ending up in a loop with knotify4 where it keeps logging same error over and over, even after the error condition that caused the error has been resolved... gstreamer-plugins-bad-free-0.10.23-2.fc17,gstreamer-plugins-good-0.10.31-1.fc17,gstreamer-plugins-base-0.10.36-1.fc17,gstreamer-0.10.36-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/gstreamer-plugins-bad-free-0.10.23-2.fc17,gstreamer-plugins-good-0.10.31-1.fc17,gstreamer-plugins-base-0.10.36-1.fc17,gstreamer-0.10.36-1.fc17 Package gstreamer-plugins-bad-free-0.10.23-2.fc17, gstreamer-plugins-good-0.10.31-1.fc17, gstreamer-plugins-base-0.10.36-1.fc17, gstreamer-0.10.36-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gstreamer-plugins-bad-free-0.10.23-2.fc17 gstreamer-plugins-good-0.10.31-1.fc17 gstreamer-plugins-base-0.10.36-1.fc17 gstreamer-0.10.36-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-2823/gstreamer-plugins-bad-free-0.10.23-2.fc17,gstreamer-plugins-good-0.10.31-1.fc17,gstreamer-plugins-base-0.10.36-1.fc17,gstreamer-0.10.36-1.fc17 then log in and leave karma (feedback). Package gstreamer-plugins-bad-free-0.10.23-2.fc17, gstreamer-plugins-good-0.10.31-1.fc17, gstreamer-plugins-base-0.10.36-1.fc17, gstreamer-0.10.36-1.fc17, qt-mobility-1.2.0-10.20110922.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gstreamer-plugins-bad-free-0.10.23-2.fc17 gstreamer-plugins-good-0.10.31-1.fc17 gstreamer-plugins-base-0.10.36-1.fc17 gstreamer-0.10.36-1.fc17 qt-mobility-1.2.0-10.20110922.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-2823/gstreamer-plugins-bad-free-0.10.23-2.fc17,gstreamer-plugins-good-0.10.31-1.fc17,gstreamer-plugins-base-0.10.36-1.fc17,gstreamer-0.10.36-1.fc17,qt-mobility-1.2.0-10.20110922.fc17 then log in and leave karma (feedback). Could we please get this for F15/F16 as well? Today this filled a .xsession file with 24GB of junk, then /home was entirely full, then sendmail could not deliver email anymore, then the NFS server locked up, and then all hell broke lose. I am marking this back to assigned, as this is a bug report for F16, but the fix that is ON_QA is for F17. To work around first turn off notifications on your login account. I've only seen this happen once since I turned off notifications... To avoid having it fill up your disk completely in that rare instance make a scheduled job that does the following: killall knotify4 truncate --size=0 ~/.xsessionerrors gstreamer-plugins-bad-free-0.10.23-2.fc17, gstreamer-plugins-good-0.10.31-1.fc17, gstreamer-plugins-base-0.10.36-1.fc17, gstreamer-0.10.36-1.fc17, qt-mobility-1.2.0-10.20110922.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. Can we get a fedora 16 build for this fix? I don't know why our systems would be so susceptible to this problem, but it just happened again. If not for a script along the lines of what Bill provided above, we would have been hosed again. (See my whine above) So *please* fix this for F15/F16 as well! Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |