Opened 10 years ago
Closed 10 years ago
#3705 closed defect (invalid)
OScam Crash
Reported by: | a1001 | Owned by: | |
---|---|---|---|
Priority: | critical | Component: | General |
Severity: | high | Keywords: | oscam crash |
Cc: | Sensitive: | no |
Description
Revision
<Oscam r9604>
Issue Description
<after a days or hours oscam crash. usually this issue comes up whenever one of my readers down. this is more details about this crash that is from VAR/LOG/APPROT:
ERROR: apport (pid 6092) Tue Apr 8 20:19:19 2014: called for pid 3114, signal 6
ERROR: apport (pid 6092) Tue Apr 8 20:19:19 2014: executable: /usr/bin/oscam (command line "/usr/bin/oscam -b -p2048 -c /usr/local/etc")
ERROR: apport (pid 6092) Tue Apr 8 20:19:19 2014: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 6092) Tue Apr 8 20:19:19 2014: apport: report /var/crash/_usr_bin_oscam.0.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 1913) Wed Apr 9 01:45:32 2014: called for pid 900, signal 11
ERROR: apport (pid 1913) Wed Apr 9 01:45:32 2014: executable: /usr/bin/oscam (command line "/usr/bin/oscam -b -p2048 -c /usr/local/etc")
ERROR: apport (pid 1913) Wed Apr 9 01:45:32 2014: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1913) Wed Apr 9 01:45:32 2014: apport: report /var/crash/_usr_bin_oscam.0.crash already exists and unseen, doing nothing to avoid disk usage DoS>
When the issue occurs
<various times>
How the issue is reproducable
<its not up to me>
<Don't forget to ATTACH (NOT post here as text) a log file of oscam in debug mode (start oscam with -d255) and to remove the brackets around the fields! Otherwise, your ticket will be closed as you seem to be unable to read.>
Change History (1)
comment:1 by , 10 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
- use latest trunk
- provide gdb log for your crash