Jump to content


Photo

Air Video Server HD UI all greyed out.


  • Please log in to reply
44 replies to this topic

#1 bagel

bagel

    Member

  • Members
  • PipPip
  • 16 posts

Posted 24 October 2013 - 04:00 PM

Not sure if it's actually started or not.  I looked for a proper executible.  The AirVideoServerStarter.exe is running but doesn't appear to be doing anything and the entire UI is greyed out.  I have yet to get this to work.

 

Please advise.

 

avs-notstart.jpg



#2 admin

admin

    Administrator

  • Administrators
  • 2585 posts

Posted 25 October 2013 - 10:01 AM

The UI is greyed out when Air Video Server HD is not allowed to create any listening sockets. There must be some software installed on your computer (i.e. 3rd party firewall software) that interferes badly with Air Video Server HD preventing it from working normally. Alternatively there might have been such software installed in past and not removed properly.



#3 bagel

bagel

    Member

  • Members
  • PipPip
  • 16 posts

Posted 25 October 2013 - 04:57 PM

The UI is greyed out when Air Video Server HD is not allowed to create any listening sockets. There must be some software installed on your computer (i.e. 3rd party firewall software) that interferes badly with Air Video Server HD preventing it from working normally. Alternatively there might have been such software installed in past and not removed properly.

There is nothing preventing opening sockets on my workstation.  There is no software firewall or antivirus running on my system.  Air Server had zero problems starting.  Is there any event log created by this issue or some logging that can be enabled with a command line switch?



#4 admin

admin

    Administrator

  • Administrators
  • 2585 posts

Posted 25 October 2013 - 05:05 PM

There are logs in the Application Data folder. If you navigate to

 

http://localhost:45601/verify

 

do you get any response?



#5 bagel

bagel

    Member

  • Members
  • PipPip
  • 16 posts

Posted 25 October 2013 - 05:40 PM

Yes, I get the Server ID immediately, that means the server is running.  The UI is still greyed out.



#6 bagel

bagel

    Member

  • Members
  • PipPip
  • 16 posts

Posted 25 October 2013 - 06:33 PM

Also, I can connect with my iPhone but it shows no shared folders.



#7 bagel

bagel

    Member

  • Members
  • PipPip
  • 16 posts

Posted 25 October 2013 - 07:23 PM

This is appearing repeatedly in the log.  Is the UI exe attempting to connected to the back end server and for whatever reason it's not able to bind to that port when starting?

 

11:57:12 DEBUG client.managerState ManagerStateClient.cpp:202 - Attempting connection to:
                                                                127.0.0.1:45602
11:57:12 DEBUG client.managerState ManagerStateClient.cpp:203 - ======================================
11:57:12 DEBUG client.managerState ManagerStateClient.cpp:214 - protocol: https
11:57:13 ERROR client.serverProcedureCall ServerProcedureCall.cpp:141 Error while connection to the server: I/O error: Bad address
11:57:13 ERROR client.managerState MainWindow.cpp:490 - - - - - updateServerStateMessage
11:57:13 ERROR client.serverProcedureCall ServerProcedureCall.cpp:141 Error while connection to the server: I/O error: Bad address
11:57:13 ERROR client.managerState MainWindow.cpp:490 - - - - - updateServerStateMessage
11:57:13 INFO  client.managerState ManagerStateClient.cpp:274 - Connection refused: Connection refused
11:57:13 INFO  client.managerState ManagerStateClient.cpp:501 - Unable to connection to the manager state server
11:57:13 INFO  client.managerState ManagerStateClient.cpp:502 - Repeating connection attempt in 100 ms
11:57:13 INFO  client.managerState ManagerStateClient.cpp:557 - Reconnection timeout expired. Repeating connection attempt ()
11:57:13 DEBUG client.managerState ManagerStateClient.cpp:561 - Connection stopped by external event. Stopping thread
11:57:13 DEBUG client.managerState ManagerStateClient.cpp:201 - ======================================


#8 admin

admin

    Administrator

  • Administrators
  • 2585 posts

Posted 25 October 2013 - 07:32 PM

This is extremely weird. The address in question (bad address) is 127.0.0.1 - localhost. There is no reason why the process shouldn't be able to connect to it.



#9 admin

admin

    Administrator

  • Administrators
  • 2585 posts

Posted 25 October 2013 - 07:34 PM

I assume http://127.0.0.1:45601/verify gives you same response as the URL with localhost?



#10 bagel

bagel

    Member

  • Members
  • PipPip
  • 16 posts

Posted 28 October 2013 - 12:30 AM

Yes it does.  127.0.0.1 is properly looping back.



#11 admin

admin

    Administrator

  • Administrators
  • 2585 posts

Posted 28 October 2013 - 11:01 AM

Given that I can't see how to reproduce this locally, the only thing I can think of is to create some builds with very verbose logging so that we can pinpoint where exactly the WSAEFAULT (Bad Address) error happens. It is really strange that it only happens in one instance. 



#12 bagel

bagel

    Member

  • Members
  • PipPip
  • 16 posts

Posted 28 October 2013 - 07:09 PM

Let's go over some of the things that might make my machine unique:

 

I have a PCI-e SSD for a boot device C:

 

My %programfiles% have been redirected to spindel disk array as the P: drive.

%userprofile% is on the U: drive, a different volume from P and C.

There is a 50TB SAN volume attached via fiber channel as the I: drive.

12 core machine with 48GB of RAM.

 

Would the redirection of the program files folder cause any issue?  I've had very limited issues with that and I use a wide variety of software (CGI, Film and Video production, Adobe Suite, Music Production Software).

 

Windows 8 x64

 

thoughts?



#13 admin

admin

    Administrator

  • Administrators
  • 2585 posts

Posted 28 October 2013 - 07:32 PM

Thanks for the details, although I don't think any of those can cause unexpected winsock error. Is there anything special about your computer network configuration?



#14 bagel

bagel

    Member

  • Members
  • PipPip
  • 16 posts

Posted 29 October 2013 - 11:17 AM

Not at all, using onboard LAN on an ASUS mobo.  No vlan tagging or weird protocols.



#15 bagel

bagel

    Member

  • Members
  • PipPip
  • 16 posts

Posted 29 October 2013 - 11:26 AM

Does the app use a named pipe to connect?  I just did some sniffing and I don't see any traffic on any of the ports used by the app.  45601 or 45602.

 

Thoughts?



#16 admin

admin

    Administrator

  • Administrators
  • 2585 posts

Posted 29 October 2013 - 11:49 AM

Hi,

 

it doesn't use named pipe. It uses regular sockets. It creates server socket on port 45601 and connects to it. It seems to be failing when establishing the connection (before it sends / receives any data). We're working on a way to isolate this issue, but it is a bit tricky because the error happens in one of the underlying frameworks that Air Video Server HD uses.



#17 admin

admin

    Administrator

  • Administrators
  • 2585 posts

Posted 30 October 2013 - 10:35 PM

Hi,

 

can you please try this version

 

https://s3.amazonaws....0.12-beta2.exe

 

and let me know if there is any difference in the behavior?



#18 bagel

bagel

    Member

  • Members
  • PipPip
  • 16 posts

Posted 31 October 2013 - 11:05 PM

Same behavior in the Other.log:  

 

19:04:39 DEBUG client.managerState ManagerStateClient.cpp:202 - Attempting connection to:

                                                                127.0.0.1:45602
19:04:39 DEBUG client.managerState ManagerStateClient.cpp:203 - ======================================
19:04:39 DEBUG client.managerState ManagerStateClient.cpp:214 - protocol: https
19:04:40 INFO  client.managerState ManagerStateClient.cpp:274 - Connection refused: Connection refused
19:04:40 INFO  client.managerState ManagerStateClient.cpp:501 - Unable to connection to the manager state server
19:04:40 INFO  client.managerState ManagerStateClient.cpp:502 - Repeating connection attempt in 100 ms
19:04:40 INFO  client.managerState ManagerStateClient.cpp:557 - Reconnection timeout expired. Repeating connection attempt ()
19:04:40 DEBUG client.managerState ManagerStateClient.cpp:561 - Connection stopped by external event. Stopping thread
19:04:40 DEBUG client.managerState ManagerStateClient.cpp:201 - ======================================


#19 admin

admin

    Administrator

  • Administrators
  • 2585 posts

Posted 31 October 2013 - 11:37 PM

Is there only one AirVideoServerUI.exe instance running? Can you send the complete other.log and network.log to support (at) inmethod.com ?



#20 bagel

bagel

    Member

  • Members
  • PipPip
  • 16 posts

Posted 31 October 2013 - 11:47 PM

That is correct.  

AirVideoServerStarter.exe

AirVideoServerUI.exe

ExternalEncoder.exe are running.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users