# Errors on quit/disconnect

**URL:** https://forums.plex.tv/t/errors-on-quit-disconnect/35612
**Category:** Apps & Creations
**Created:** [June 6, 2013, 7:49pm UTC](https://forums.plex.tv/t/errors-on-quit-disconnect/35612 "2013-06-06T19:49:41Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![alias\_rex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/alias_rex/32/887_2.png) [@alias\_rex](https://forums.plex.tv/u/alias_rex)
#### Post date: [June 6, 2013, 7:49pm UTC](https://forums.plex.tv/t/errors-on-quit-disconnect/35612/1 "2013-06-06T19:49:41Z")

</div>

I'm getting error messages in the Terminal when I quit PlexConnect using control-C. When I first tried out PlexConnect on my MacBook Pro (OS X )10.8.3, I never saw these errors. Are these messages normal? PlexConnect seems to be working fine for me otherwise as long as I don't install it on my OS X Server.

&nbsp;

> WebServer : ^C received.
> 
> WebServer : Shutting down.
> 
> DNSServer : ^C received.
> 
> DNSServer : Shutting down.
> 
> Traceback (most recent call last):
> 
> &nbsp; File "/Users/user/PlexConnect/PlexConnect.py", line 72, in 
> 
> &nbsp; &nbsp; key = raw\_input()
> 
> KeyboardInterrupt
> 
> Exception in thread QueueFeederThread (most likely raised during interpreter shutdown):
> 
> Traceback (most recent call last):
> 
> &nbsp; File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 552, in \_\_bootstrap\_inner
> 
> &nbsp; File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 505, in run
> 
> &nbsp; File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/multiprocessing/queues.py", line 259, in \_feed
> 
> : 'NoneType' object is not callable
> 
> Exception in thread QueueFeederThread (most likely raised during interpreter shutdown):
> 
> Traceback (most recent call last):
> 
> &nbsp; File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 552, in \_\_bootstrap\_inner
> 
> &nbsp; File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 505, in run
> 
> &nbsp; File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/multiprocessing/queues.py", line 259, in \_feed
> 
> : 'NoneType' object is not callable

&nbsp;

---

<div class="post-metadata">

### Author: ![f00b4r](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/f00b4r/32/768_2.png) [@f00b4r](https://forums.plex.tv/u/f00b4r)
#### Post date: [June 6, 2013, 10:38pm UTC](https://forums.plex.tv/t/errors-on-quit-disconnect/35612/2 "2013-06-06T22:38:18Z")

</div>

PlexConnect is currently designed to exit gracefully if you hit enter when the terminal window is focused.

---

<div class="post-metadata">

### Author: ![alias\_rex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/alias_rex/32/887_2.png) [@alias\_rex](https://forums.plex.tv/u/alias_rex)
#### Post date: [June 6, 2013, 11:08pm UTC](https://forums.plex.tv/t/errors-on-quit-disconnect/35612/3 "2013-06-06T23:08:23Z")

</div>

Very nice. It wasn't in the FAQ so I assumed I had to kill it like any other Terminal process.

> PlexConnect is currently designed to exit gracefully if you hit enter when the terminal window is focused.

---

<div class="post-metadata">

### Author: ![f00b4r](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/f00b4r/32/768_2.png) [@f00b4r](https://forums.plex.tv/u/f00b4r)
#### Post date: [June 6, 2013, 11:11pm UTC](https://forums.plex.tv/t/errors-on-quit-disconnect/35612/4 "2013-06-06T23:11:30Z")

</div>

It does output info about it when it starts up but it is easy to miss.

---

<div class="post-metadata">

### Author: ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)
#### Post date: [December 20, 2019, 11:28pm UTC](https://forums.plex.tv/t/errors-on-quit-disconnect/35612/5 "2019-12-20T23:28:22Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
