Bug beim beenden von DoorPi als Anwendung

**Nea** · 7. April 2016

Nach dem Beenden von DoorPi, als Anwendung, bekomme ich ab und an kein prompt mehr. Hier kann ich nur noch die Sitzung schliesen etwas anderes geht nicht mehr. Diese Problem tritt zwar sehr selten auf trotzdem weiß ich nicht was ich davon halten soll:

Code

2016-04-07 22:13:57,983 [TRACE]         [doorpi.action.handler] event_source doorpi.sipphone.from_linphone was removed for event OnSipPhoneRecorderCreate
2016-04-07 22:13:57,984 [TRACE]         [doorpi.action.handler] event_source doorpi.sipphone.from_linphone was removed
2016-04-07 22:13:57,985 [TRACE]         [doorpi.action.handler] [0W2B2T] finished fire_event for event_name OnShutdown
2016-04-07 22:13:57,985 [TRACE]         [doorpi.action.handler] fire Event AfterShutdown from doorpi.doorpi asyncron
2016-04-07 22:13:57,987 [DEBUG]         [doorpi.action.handler] no actions for event AfterShutdown - skip fire_event AfterShutdown from doorpi.doorpi
2016-04-07 22:13:58,165 [DEBUG]         [doorpi.keyboard.from_rdm6300] readUART thread ended
2016-04-07 22:13:58,488 [DEBUG]         [doorpi.doorpi] wait 5 seconds for threads 1 and 1 event
2016-04-07 22:13:58,489 [TRACE]         [doorpi.doorpi] still existing threads:       [<Thread(OnCallStateConnect from doorpi.sipphone.linphone_lib.CallBacks, started 1801450592)>]
2016-04-07 22:13:58,491 [TRACE]         [doorpi.doorpi] still existing event sources: ['doorpi.doorpi']
2016-04-07 22:13:58,993 [DEBUG]         [doorpi.doorpi] wait 4.5 seconds for threads 1 and 1 event
2016-04-07 22:13:58,994 [TRACE]         [doorpi.doorpi] still existing threads:       [<Thread(OnCallStateConnect from doorpi.sipphone.linphone_lib.CallBacks, started 1801450592)>]
2016-04-07 22:13:58,996 [TRACE]         [doorpi.doorpi] still existing event sources: ['doorpi.doorpi']
2016-04-07 22:13:59,498 [DEBUG]         [doorpi.doorpi] wait 4.0 seconds for threads 1 and 1 event
2016-04-07 22:13:59,500 [TRACE]         [doorpi.doorpi] still existing threads:       [<Thread(OnCallStateConnect from doorpi.sipphone.linphone_lib.CallBacks, started 1801450592)>]
2016-04-07 22:13:59,501 [TRACE]         [doorpi.doorpi] still existing event sources: ['doorpi.doorpi']
2016-04-07 22:14:00,003 [DEBUG]         [doorpi.doorpi] wait 3.5 seconds for threads 1 and 1 event
2016-04-07 22:14:00,005 [TRACE]         [doorpi.doorpi] still existing threads:       [<Thread(OnCallStateConnect from doorpi.sipphone.linphone_lib.CallBacks, started 1801450592)>]
2016-04-07 22:14:00,006 [TRACE]         [doorpi.doorpi] still existing event sources: ['doorpi.doorpi']
2016-04-07 22:14:00,508 [DEBUG]         [doorpi.doorpi] wait 3.0 seconds for threads 1 and 1 event
2016-04-07 22:14:00,510 [TRACE]         [doorpi.doorpi] still existing threads:       [<Thread(OnCallStateConnect from doorpi.sipphone.linphone_lib.CallBacks, started 1801450592)>]
2016-04-07 22:14:00,511 [TRACE]         [doorpi.doorpi] still existing event sources: ['doorpi.doorpi']
2016-04-07 22:14:01,013 [DEBUG]         [doorpi.doorpi] wait 2.5 seconds for threads 1 and 1 event
2016-04-07 22:14:01,015 [TRACE]         [doorpi.doorpi] still existing threads:       [<Thread(OnCallStateConnect from doorpi.sipphone.linphone_lib.CallBacks, started 1801450592)>]
2016-04-07 22:14:01,018 [TRACE]         [doorpi.doorpi] still existing event sources: ['doorpi.doorpi']
2016-04-07 22:14:01,520 [DEBUG]         [doorpi.doorpi] wait 2.0 seconds for threads 1 and 1 event
2016-04-07 22:14:01,522 [TRACE]         [doorpi.doorpi] still existing threads:       [<Thread(OnCallStateConnect from doorpi.sipphone.linphone_lib.CallBacks, started 1801450592)>]
2016-04-07 22:14:01,524 [TRACE]         [doorpi.doorpi] still existing event sources: ['doorpi.doorpi']
2016-04-07 22:14:02,027 [DEBUG]         [doorpi.doorpi] wait 1.5 seconds for threads 1 and 1 event
2016-04-07 22:14:02,029 [TRACE]         [doorpi.doorpi] still existing threads:       [<Thread(OnCallStateConnect from doorpi.sipphone.linphone_lib.CallBacks, started 1801450592)>]
2016-04-07 22:14:02,031 [TRACE]         [doorpi.doorpi] still existing event sources: ['doorpi.doorpi']
2016-04-07 22:14:02,534 [DEBUG]         [doorpi.doorpi] wait 1.0 seconds for threads 1 and 1 event
2016-04-07 22:14:02,536 [TRACE]         [doorpi.doorpi] still existing threads:       [<Thread(OnCallStateConnect from doorpi.sipphone.linphone_lib.CallBacks, started 1801450592)>]
2016-04-07 22:14:02,538 [TRACE]         [doorpi.doorpi] still existing event sources: ['doorpi.doorpi']
2016-04-07 22:14:03,041 [DEBUG]         [doorpi.doorpi] wait 0.5 seconds for threads 1 and 1 event
2016-04-07 22:14:03,043 [TRACE]         [doorpi.doorpi] still existing threads:       [<Thread(OnCallStateConnect from doorpi.sipphone.linphone_lib.CallBacks, started 1801450592)>]
2016-04-07 22:14:03,045 [TRACE]         [doorpi.doorpi] still existing event sources: ['doorpi.doorpi']
2016-04-07 22:14:03,547 [WARNING]       [doorpi.doorpi] waiting for threads to time out - there are still threads: [<Thread(OnCallStateConnect from doorpi.sipphone.linphone_lib.CallBacks, started 1801450592)>]
2016-04-07 22:14:03,550 [INFO]          [doorpi.doorpi] ======== DoorPi successfully shutdown ========

Alles anzeigen

Unter htop ist auch nichts zu erkennen, Doorpi wurde sauber beendet.

motom001 · 7. April 2016

Zitat von Nea

bekomme ich ab und an kein prompt mehr.

Problem ist bekannt...

Zitat von Nea

Unter htop ist auch nichts zu erkennen

Das glaube ich Dir nicht - da gibt es noch Zombie-Threads, die auf Rückmeldung warten...

In DoorPi 3 hab ich das Thema bereits gelöst, aber die Änderungen sind zu umfangreich um es auf die 2.5.x zu übertragen.
In Deinem Fall steht sogar da:
<Thread(OnCallStateConnect from doorpi.sipphone.linphone_lib.CallBacks, started 1801450592)>
Also irgendwas ist da schief gegangen - hatte DoorPi genug Zeit um Gespräche zu beenden oder hast Du im Gespräch DoorPi beendet (z.B. mit [strg]+[c])?

// EDIT \\

Unter htop hilft die Taste um die Prozesse als tree darzustellen.

**Nea** · 7. April 2016

Zitat von motom001

Das glaube ich Dir nicht - da gibt es noch Zombie-Threads, die auf Rückmeldung warten...

Hehe, ich wusste das Du das sagst. Wie sollen denn Deine Zombie-Threads aussehen?
Ich habe htop noch offen, weil ich mir schon dachte das sowas kommt.

@motom001
Schau mal hier habe ich eine Fehlermeldung:

Code

2016-04-07 22:15:48,281 [DEBUG]         [doorpi.keyboard.from_gpio] out(pin = 12, value = True, log_output = True)
2016-04-07 22:15:48,282 [ERROR]         [doorpi.action.handler] [0URIR5] error while fire action OutTriggeredAction with args () and kwargs {'stop_pin': 'NoStopPinSet', 'end_value': '0', 'timeout': 200.0, 'pin': 'Verstaerker', 'start_value': '1'} for event_name OnCallStateConnect
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/doorpi/action/handler.py", line 284, in fire_event_synchron
    result = action.run(silent)
  File "/usr/local/lib/python2.7/dist-packages/doorpi/action/base.py", line 48, in run
    return self.__callback(**self.__kwargs)
  File "/usr/local/lib/python2.7/dist-packages/doorpi/action/SingleActions/out_triggered.py", line 18, in out_triggered
    doorpi.DoorPi().keyboard.set_output(pin, end_value)
  File "/usr/local/lib/python2.7/dist-packages/doorpi/keyboard/KeyboardInterface.py", line 134, in set_output
    self.__keyboards[self.__OutputMappingTable[pin]].set_output(pin, value, log_output)
  File "/usr/local/lib/python2.7/dist-packages/doorpi/keyboard/from_gpio.py", line 121, in set_output
    RPiGPIO.output(pin, value)
RuntimeError: Please set pin numbering mode using GPIO.setmode(GPIO.BOARD) or GPIO.setmode(GPIO.BCM)
2016-04-07 22:15:48,296 [TRACE]         [doorpi.action.handler] [0URIR5] finished fire_event for event_name OnCallStateConnect

Alles anzeigen

Teilen