Home Community Discussion Forums Most Active Software Boards LabVIEW Topic

LabVIEW

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

TIME_WAIT connections on port 3580

TIME_WAIT connections on port 3580

‎08-20-2015 12:28 PM

I disabled all NI services with the exception of:

  • NI Configuration Manager
  • NI GPIB Enumeration Service
  • NI Service Locator

After rebooting the machine, logging in, letting things settle,  if I run:

  • netstat -o -b

I get two entries relating to NI software, specifically nimxs.exe (MXS Service😞

  • TCP 127.0.0.1:49577 hostname:49578 ESTABLISHED 1912 [nimxs.exe]
  • TCP 127.0.0.1:49578 hostname:49577 ESTABLISHED 1912 [nimxs.exe]

I then start NI MAX, let it settle, expand my Devices and Interfaces, expand and rescan all my GPIB buses, and exit NI MAX.

After wating a bit if I rerun

  • netstat -o -b

I now get four entries relating to nimxs.exe:

  • TCP 127.0.0.1:49577 hostname:49578 ESTABLISHED 1912 [nimxs.exe]
  • TCP 127.0.0.1:49578 hostname:49577 ESTABLISHED 1912 [nimxs.exe]
  • TCP 127.0.0.1:50157 hostname:50158 ESTABLISHED 1912 [nimxs.exe]
  • TCP 127.0.0.1:50158 hostname:50157 ESTABLISHED 1912 [nimxs.exe]

and 96!! entries, I believe from nipalsm.exe (NI -PAL Service Manager):

  • TCP 127.0.0.1:3580 hostname:50213 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50214 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50215 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50216 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50217 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50218 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50219 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50220 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50221 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50222 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50223 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50224 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50226 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50227 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50228 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50229 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50230 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50231 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50232 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50233 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50234 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50236 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50237 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50238 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50239 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50240 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50241 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50242 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50243 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50244 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50246 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50247 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50248 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50249 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50250 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50251 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50252 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50253 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50254 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50255 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50256 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50257 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50258 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50259 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50260 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50261 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50262 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50263 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50264 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50265 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50266 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50267 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50268 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50269 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50270 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50271 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50272 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50273 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50274 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50275 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50276 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50277 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50278 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50279 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50280 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50281 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50282 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50283 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50284 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50285 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50286 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50287 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50288 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50289 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50290 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50291 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50292 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50293 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50294 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50295 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50296 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50297 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50298 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50299 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50300 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50301 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50302 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50303 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50304 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50305 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50306 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50307 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50308 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50309 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50310 TIME_WAIT 0
  • TCP 127.0.0.1:3580 hostname:50311 TIME_WAIT 0

And these connections don't go away even after a long time.  I've just waited 15 minutes before typing this last line and they are still there.

Don't think this is expected behavior.  What is going on?

0 Kudos
Message 1 of 10
(19,274 Views)
Reply

Re: TIME_WAIT connections on port 3580

‎08-20-2015 12:30 PM

WOW, Strike one for this web forum.  It looks fine in Rich Text and HTML and looks all garbled after posting ....

0 Kudos
Message 2 of 10
(19,269 Views)
Reply

Re: TIME_WAIT connections on port 3580

‎08-20-2015 12:46 PM

Stoping and restarting the service locator (nipalsm.exe) then waiting for a bit, and eventually all TIME_WAIT connections go away, but shouldn't go away anyway?  Or is the time out set to an unreasonable long period?

0 Kudos
Message 3 of 10
(19,259 Views)
Reply

Re: TIME_WAIT connections on port 3580

‎08-22-2015 09:28 AM

@instrumento wrote:

WOW, Strike one for this web forum.  It looks fine in Rich Text and HTML and looks all garbled after posting ....

Well, strike one for the browser where I was doing the post 🙂  It looks fine from home.

 

Anyone knows what is going on?

0 Kudos
Message 4 of 10
(19,180 Views)
Reply

Re: TIME_WAIT connections on port 3580

‎08-24-2015 04:29 PM

 

Hi instrumento,

 

Are you still having this? 

 

It is normal to see multiple instances of the nipalsm, but I have not seen what you experience. Are you running something?

 

Why Do I See Multiple Instances of nipalsm in the Windows Task Manager?
http://digital.ni.com/public.nsf/allkb/1212376A1C10A99B86256D12006C79EA?OpenDocument

 

Regards,

Carolina 

 

0 Kudos
Message 5 of 10
(19,122 Views)
Reply

Re: TIME_WAIT connections on port 3580

‎08-24-2015 07:50 PM

caro16av wrote:

Are you still having this?

It is normal to see multiple instances of the nipalsm, but I have not seen what you experience. Are you running something?

My first post described what I did, i.e. reboot, run NI-MAX, expand and rescan all GPIB buses, exit NI-MAX, nothing else is running except normal Win7 tasks.

0 Kudos
Message 6 of 10
(19,106 Views)
Reply

Re: TIME_WAIT connections on port 3580

‎10-28-2015 07:28 PM

Am I the only one seeing this? 

I'm not sure it is a problem to begin with, but it is like some NI software is just dropping a tcp connection without closing it, and then the TCP stack never cleans it until reboot.

I'm having a problem with one of my servers eventually not responding, and not sure if this is related.

0 Kudos
Message 7 of 10
(18,910 Views)
Reply

Re: TIME_WAIT connections on port 3580

‎10-29-2015 03:31 PM

Hi instrumento,

 

Expected behavior for your system will depend on the hardware you have in NI MAX. To help determine what is expected behavior, can you please upload an NI MAX technical report? This link will walk you through creating one. Please generate a technical support report for your system. Thanks!

 

Christine S

Applications Engineer

0 Kudos
Message 8 of 10
(18,881 Views)
Reply

Re: TIME_WAIT connections on port 3580

‎10-29-2015 04:07 PM

Generated the NI Max report, opened a ticket with support.

0 Kudos
Message 9 of 10
(18,872 Views)
Reply

Re: TIME_WAIT connections on port 3580

‎12-02-2015 06:52 PM

Bug in NI MAXs interaction with the NI PXI Resource Manager.

To check it out, disable NI PXI Resource Manager, reboot, then run  NI-MAX.

No need to click on anything and a few socket connections to port 3580 should be there in TIME_WAIT state, for ever.

NI R&D acknowledged the bug and a Corrective Action Report (CAR) has been filed.

 

0 Kudos
Message 10 of 10
(18,761 Views)
Reply