Firefly disabled after portscan (8.2 Beta-4)

[talon42]

After this Beta 4 upgrade, I've had some weird plugin issues. As I mentioned in another thread, I couldn't get transmission to start. I finally got that plugin to work, and moved on to setting up a second plugin. I couldn't get firefly's gui to show up in my web brower so started doing port scans. What I noticed was that whenever I scanned it using nmap the first scan would show 3389 as open and the second scan would show it closed 3389. I checked the plugin settings and noticed that the plugin was actually being turned off. I have not setup any music with it so the database is empty. Not sure if this is a plugin error or a mt-daap error, but here what shows up in the mt-daapd.log after a port scan.

2012-06-20 06:47:28 (4a6b7f1f): Dispatcher: accept failed: Unknown error
2012-06-20 06:47:28 (4a6b7f1f): Dispatcher: Aborting
2012-06-20 06:47:28: Aborting
2012-06-20 06:47:28 (18a217af): Rendezvous socket closed (daap server crashed?)
Aborting.
2012-06-20 06:47:28: Aborting

 

[talon42]

Made a mistake in that last post. Meant to say port 3689.

I rebooted a few times again and I thought I had it working however, neither Firefly or minidlna were auto reenabled. Transmission was enabled but the 9091 reported as closed even though RPC/WebUI is enabled. I disabled then reenabled the transmission plugin and now 9091 and 8200 show open but 3689 is closed again. This is odd.