Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
JAVA restart necessary to fix inactive Minimserver?
06-06-2013, 13:46
Post: #11
RE: JAVA restart necessary to fix inactive Minimserver?
(02-06-2013 17:21)hvaleton Wrote:  
(02-06-2013 17:17)simoncn Wrote:  Thanks! I got this attachment, and it shows there are 80 file and socket descriptors. Please run MinimServer for a few days and check this again to see whether the number of descriptors has increased significantly.

OK, Will do!

Hello Simon,

Reporting back for duty, so to speak, with the results of running the lsof command every day for the period of some 4 days. See the attachments.

Thanks in advance!

Hans
Find all posts by this user
Quote this message in a reply
06-06-2013, 13:49
Post: #12
RE: JAVA restart necessary to fix inactive Minimserver?
(02-06-2013 17:21)hvaleton Wrote:  
(02-06-2013 17:17)simoncn Wrote:  Thanks! I got this attachment, and it shows there are 80 file and socket descriptors. Please run MinimServer for a few days and check this again to see whether the number of descriptors has increased significantly.

OK, Will do!

Hello Simon,

Reporting back for duty, so to speak, with the results of running the lsof command every day for the period of some 4 days. See the attachments.

Thanks in advance!

Hans


Attached File(s)
.txt  lsof_2013_06_02_1232.txt (Size: 8.41 KB / Downloads: 1)
.txt  lsof_2013_06_03_0752.txt (Size: 10.28 KB / Downloads: 0)
.txt  lsof_2013_06_04_0013.txt (Size: 13.25 KB / Downloads: 0)
.txt  lsof_2013_06_04_1434.txt (Size: 13.25 KB / Downloads: 0)
.txt  lsof_2013_06_05_2106.txt (Size: 15.62 KB / Downloads: 1)
Find all posts by this user
Quote this message in a reply
06-06-2013, 13:51
Post: #13
RE: JAVA restart necessary to fix inactive Minimserver?
Forgot to add the last one. It seems to be impossible to add extra attachments after posting...


Attached File(s)
.txt  lsof_2013_06_06_1439.txt (Size: 17.63 KB / Downloads: 4)
Find all posts by this user
Quote this message in a reply
06-06-2013, 18:45
Post: #14
RE: JAVA restart necessary to fix inactive Minimserver?
(06-06-2013 13:51)hvaleton Wrote:  Forgot to add the last one. It seems to be impossible to add extra attachments after posting...

Thanks for doing this. It seems to show that the number of descriptors is increasing steadily, with this pattern as the cause of most of the increase:

java 31100 admin 148u sock 0,5 0t0 814979123 can't identify protocol
java 31100 admin 149r FIFO 0,7 0t0 814979124 pipe
java 31100 admin 150w FIFO 0,7 0t0 814979124 pipe

I'll try to recreate this myself, and I'll let you know how I get on.
Find all posts by this user
Quote this message in a reply
06-06-2013, 22:02
Post: #15
RE: JAVA restart necessary to fix inactive Minimserver?
(06-06-2013 18:45)simoncn Wrote:  I'll try to recreate this myself, and I'll let you know how I get on.

I'm not seeing this (so far) on my QNAP. Please can you run the command:

netstat -a

and post the output here. Thanks!
Find all posts by this user
Quote this message in a reply
06-06-2013, 22:25
Post: #16
RE: JAVA restart necessary to fix inactive Minimserver?
(06-06-2013 22:02)simoncn Wrote:  
(06-06-2013 18:45)simoncn Wrote:  I'll try to recreate this myself, and I'll let you know how I get on.

I'm not seeing this (so far) on my QNAP. Please can you run the command:

netstat -a

and post the output here. Thanks!

I've just run the netstat command and have attched the result.


Attached File(s)
.txt  netstat_2013_06_06_2323.txt (Size: 8 KB / Downloads: 1)
Find all posts by this user
Quote this message in a reply
06-06-2013, 23:04
Post: #17
RE: JAVA restart necessary to fix inactive Minimserver?
(06-06-2013 22:25)hvaleton Wrote:  I've just run the netstat command and have attched the result.

Thanks!

I see 7 connections from 192.168.1.57 to the QNAP's 9790 port (the MinimServer HTTP server), and one connection from 192.168.1.52 to the same port. What devices are these?

Other local devices with connections are 192.168.1.13 and 192.168.1.53. There isn't enough information to know whether these connections are for the MinimServer process. What devices are these?

There are also many connections to what appear to be internet addresses. Would you expect such a large number of these? Some examples:

tcp 0 1024 NasWeileton:51413 78-28-82-13.cdma.:60309 ESTABLISHED

(and 51 others from the same port 51413)

tcp 0 1 NasWeileton:60694 ip-81-11-216-231.:45359 SYN_SENT
tcp 0 0 NasWeileton:34844 121-99-61-86.bng1:15860 ESTABLISHED
tcp 0 1024 NasWeileton:53273 200.63.36.118:54199 ESTABLISHED
tcp 0 0 NasWeileton:38666 91.98.231.217.pol.:7881 ESTABLISHED
Find all posts by this user
Quote this message in a reply
07-06-2013, 10:05
Post: #18
RE: JAVA restart necessary to fix inactive Minimserver?
(06-06-2013 23:04)simoncn Wrote:  
(06-06-2013 22:25)hvaleton Wrote:  I've just run the netstat command and have attched the result.

Thanks!

I see 7 connections from 192.168.1.57 to the QNAP's 9790 port (the MinimServer HTTP server), and one connection from 192.168.1.52 to the same port. What devices are these?

192.168.1.57 is my Galaxy Nexus smartphone
192.168.1.52 is my Linn DS

(06-06-2013 23:04)simoncn Wrote:  Other local devices with connections are 192.168.1.13 and 192.168.1.53. There isn't enough information to know whether these connections are for the MinimServer process. What devices are these?
192.168.1.13 is unknown. I ran the netstat command a few times more after the initial one and this ip address never turns up again. I have a faint memory of having allocated a static 192.168.1.13 address within my home network to a specific device but I have racked my brain trying to remember what it was with no result, yet.
(The DHCP range of my router starts at 50)
192.168.1.53 is HAYDN, my own Win7 PC

(06-06-2013 23:04)simoncn Wrote:  There are also many connections to what appear to be internet addresses. Would you expect such a large number of these? Some examples:

tcp 0 1024 NasWeileton:51413 78-28-82-13.cdma.:60309 ESTABLISHED

(and 51 others from the same port 51413)

tcp 0 1 NasWeileton:60694 ip-81-11-216-231.:45359 SYN_SENT
tcp 0 0 NasWeileton:34844 121-99-61-86.bng1:15860 ESTABLISHED
tcp 0 1024 NasWeileton:53273 200.63.36.118:54199 ESTABLISHED
tcp 0 0 NasWeileton:38666 91.98.231.217.pol.:7881 ESTABLISHED

51413 is the port Qnap uses for bittorrent traffic. I have disabled these services (first "Download Station" and then "Transmission") and after a while this port number 51413 did not turn up anymore in the netstat output, as you can see in the various attachments to this post.
I do not know what the other four ports are used for on the Qnap, but they have disappeared from the radar as well, after disabling the bittorent services.
Perhaps the more recent netstat outputs are somewhat more informative to you for being less bulky?


Attached File(s)
.txt  netstat_2013_06_07_0929.txt (Size: 4 KB / Downloads: 1)
.txt  netstat_2013_06_07_0941_after_shutdown_download_station.txt (Size: 13.1 KB / Downloads: 0)
.txt  netstat_2013_06_07_0948_after_a_cooling_period.txt (Size: 4 KB / Downloads: 0)
.txt  netstat_2013_06_07_0951_after_shutdown_transmission.txt (Size: 8 KB / Downloads: 0)
.txt  netstat_2013_06_07_0953_after_a_colling_period.txt (Size: 5.01 KB / Downloads: 1)
Find all posts by this user
Quote this message in a reply
07-06-2013, 10:09
Post: #19
RE: JAVA restart necessary to fix inactive Minimserver?
Hi Simon,

I have attached the latest lsof output. It seems the number of entries (188) is stable now?

Hans


Attached File(s)
.txt  lsof_2013_06_07_1105.txt (Size: 17.63 KB / Downloads: 2)
Find all posts by this user
Quote this message in a reply
07-06-2013, 13:17
Post: #20
RE: JAVA restart necessary to fix inactive Minimserver?
(07-06-2013 10:05)hvaleton Wrote:  192.168.1.57 is my Galaxy Nexus smartphone

Thanks for all the very detailed information. What control point or other audio software are you running on the Galaxy Nexus? In the latest netstat output, this device has 14 established HTTP connections to Minimserver. I can't think of any good reason for this, and I think it's likely to be the cause of the descriptor leakage problem.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 2 Guest(s)