Was working fine this morning on 4g in my car listening to music on a remote connection. Exited the app when entering my workplace. Now on wifi and attempting to connect and just hanging on waiting for connection. This has happened on multiple devices. Also, I've switched back to 4g to make sure it was not the network - no dice. Still doesn't work. I'm finding the support email address to be quite useless since I never get a response or if I do, it really isn't helpful. Forum responses seem to have slowed down as well. Hopefully this will change now that the holiday season is over.
Forums
A community for Skifta users to learn and share.
Waiting for Connection.......
-
Posted 1 year ago
RockyCJC
MemberGot it working about 15 minutes after the last post. I then exited when I had to go to a meeting. I just returned to my desk and now I am getting "No Media Sources Found" when looking under "Remote".
If all things remain the same, it will probably work again in an hour and I will have yet another issue later today. This has been my experience with this service for the last few weeks and unfortunately what I have come to expect from Skifta.
-
Posted 1 year ago
RockyCJC
MemberNow it appears your website is on the fritz again.....most of the links do not work (just keeps me on the main page) and I can't log in to see if the connections are showing on the "dashboard".
Also still unable to see any remote connections on my apps. Like I said, it was working fine this morning so it is odd to me that it just suddenly stops working on multiple devices and using different internet connections.
-
Posted 1 year ago
RockyCJC
Member2012-01-02 13:59:36,107 LOG_ERROR [SkiftaPeer.PeerStarter] com.skifta.peer.impl.SkiftaPeerImpl$PeerStarterThread.run:1129 An error occurred starting the Skifta p2p peer
java.lang.Throwable: An error occurred creating or starting the naming client service (com.skifta.p2p.peer.PeerException)
at com.skifta.p2p.peer.AbstractPeer.start(AbstractPeer.java:263)
at com.skifta.p2p.peer.Peer.start(Peer.java:32)
at com.skifta.peer.impl.SkiftaPeerImpl.startPeer(SkiftaPeerImpl.java:862)
at com.skifta.peer.impl.SkiftaPeerImpl.access$500(SkiftaPeerImpl.java:58)
at com.skifta.peer.impl.SkiftaPeerImpl$PeerStarterThread.run(SkiftaPeerImpl.java:1114)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.Throwable: An error occurred fetching the initial URIs (com.skifta.p2p.common.service.ServiceException)
at com.skifta.p2p.client.service.naming.DynamicNamingClientServiceImpl.start(DynamicNamingClientServiceImpl.java:313)
at com.skifta.p2p.peer.AbstractPeer.start(AbstractPeer.java:260)
... 5 more
Caused by: java.lang.Throwable: An error occurred getting all server URIs from the naming server (com.skifta.p2p.common.service.naming.NamingServiceException)
at com.skifta.p2p.client.service.naming.DynamicNamingClientServiceImpl.getInitialURIs(DynamicNamingClientServiceImpl.java:566)
at com.skifta.p2p.client.service.naming.DynamicNamingClientServiceImpl.start(DynamicNamingClientServiceImpl.java:310)
... 6 more
Caused by: java.lang.Throwable: null (java.lang.NullPointerException)
at java.net.URI$Parser.parse(Unknown Source)
at java.net.URI.<init>(Unknown Source)
at com.skifta.p2p.client.service.naming.DynamicNamingClientServiceImpl.getServerURIs(DynamicNamingClientServiceImpl.java:491)
at com.skifta.p2p.client.service.naming.DynamicNamingClientServiceImpl.parseInitialServerURI(DynamicNamingClientServiceImpl.java:593)
at com.skifta.p2p.client.service.naming.DynamicNamingClientServiceImpl.getInitialURIs(DynamicNamingClientServiceImpl.java:531)
... 7 more
2012-01-02 13:59:36,115 LOG_ERROR [SkiftaPeer.PeerStarter] com.skifta.peer.impl.SkiftaPeerImpl$PeerStarterThread.run:1129 An error occurred starting the Skifta p2p peer
java.lang.Throwable: An error occurred creating or starting the naming client service (com.skifta.p2p.peer.PeerException)
at com.skifta.p2p.peer.AbstractPeer.start(AbstractPeer.java:263)
at com.skifta.p2p.peer.Peer.start(Peer.java:32)
at com.skifta.peer.impl.SkiftaPeerImpl.startPeer(SkiftaPeerImpl.java:862)
at com.skifta.peer.impl.SkiftaPeerImpl.access$500(SkiftaPeerImpl.java:58)
at com.skifta.peer.impl.SkiftaPeerImpl$PeerStarterThread.run(SkiftaPeerImpl.java:1114)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.Throwable: An error occurred fetching the initial URIs (com.skifta.p2p.common.service.ServiceException)
at com.skifta.p2p.client.service.naming.DynamicNamingClientServiceImpl.start(DynamicNamingClientServiceImpl.java:313)
at com.skifta.p2p.peer.AbstractPeer.start(AbstractPeer.java:260)
... 5 more
Caused by: java.lang.Throwable: An error occurred getting all server URIs from the naming server (com.skifta.p2p.common.service.naming.NamingServiceException)
at com.skifta.p2p.client.service.naming.DynamicNamingClientServiceImpl.getInitialURIs(DynamicNamingClientServiceImpl.java:566)
at com.skifta.p2p.client.service.naming.DynamicNamingClientServiceImpl.start(DynamicNamingClientServiceImpl.java:310)
... 6 more
Caused by: java.lang.Throwable: null (java.lang.NullPointerException)
at java.net.URI$Parser.parse(Unknown Source)
at java.net.URI.<init>(Unknown Source)
at com.skifta.p2p.client.service.naming.DynamicNamingClientServiceImpl.getServerURIs(DynamicNamingClientServiceImpl.java:491)
at com.skifta.p2p.client.service.naming.DynamicNamingClientServiceImpl.parseInitialServerURI(DynamicNamingClientServiceImpl.java:593)
at com.skifta.p2p.client.service.naming.DynamicNamingClientServiceImpl.getInitialURIs(DynamicNamingClientServiceImpl.java:531) -
Posted 1 year ago
I'm on it - give me a couple of minutes and we should be running again. Something went a little broke with the backend network and needed a bit of a kick.
-
Posted 1 year ago
RockyCJC
MemberIts been up and I show online but now I am back to having the "Waiting for Connection....". Also tried making the connection through the website and it said connection failed. So I am back to the problem I was originally having this morning.
-
Posted 1 year ago
RockyCJC
MemberSaw the following in the logs on my last attempt to connect to the remote source:
2012-01-02 15:26:34,803 LOG_DEBUG [pool-54-thread-4] com.skifta.p2p.common.http.P2PHttpRequestSender.sendRequest:72 Received HTTP response -
HTTP/1.1 500 Internal Server Error
Connection: Close
Date: Mon, 02 Jan 2012 20:26:35 GMT
Server: SkiftaServer/1.1.1
Content-Length: 715
Content-Type: text/plain; charset=ISO-8859-1com.skifta.p2p.common.service.security.SecurityServiceException: The security credentials in the HTTP request do not correspond to a valid session [requester peerID: d7b503c0c7f6df1be77a6d1bd3d32a14, sessionToken: f16fc5f4-9e5f-43e4-bca8-dd67bcaa91f8]
at com.skifta.p2p.auth.server.http.AuthServerRequestHandler.handleRequest(AuthServerRequestHandler.java:264)
at com.skifta.p2p.common.http.server.AbstractP2PServerHttpRequestHandler$RequestHandler.run(AbstractP2PServerHttpRequestHandler.java:250)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)2012-01-02 15:26:34,804 LOG_DEBUG [pool-54-thread-4] com.skifta.p2p.common.service.security.impl.BasicSecurityServiceImpl.verifyHttpResponseHeaders:147 HTTP response server header: SkiftaServer/1.1.1
2012-01-02 15:26:34,804 LOG_DEBUG [pool-54-thread-4] com.skifta.p2p.common.service.security.impl.BasicSecurityServiceImpl.verifyHttpResponseHeaders:147 HTTP response server header: SkiftaServer/1.1.1
2012-01-02 15:26:34,805 LOG_ERROR [pool-54-thread-4] com.skifta.p2p.common.http.client.AbstractP2PClientHttpRequestHandler.handle:146 [RELAY-SERVER-CONN] HTTP request failed security validation - aborting request
java.lang.Throwable: An error occurred sending the validate session request (com.skifta.p2p.common.service.security.SecurityServiceException)
at com.skifta.p2p.client.service.security.impl.auth.AuthSecurityClientServiceImpl.isValidSession(AuthSecurityClientServiceImpl.java:288)
at com.skifta.p2p.common.http.client.AbstractP2PClientHttpRequestHandler.handle(AbstractP2PClientHttpRequestHandler.java:124)
at com.skifta.http.protocol.HttpService.doService(HttpService.java:293)
at com.skifta.http.protocol.HttpService.handleRequest(HttpService.java:212)
at com.skifta.common.network.http.server.HttpRequestReceiver.run(HttpRequestReceiver.java:109)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.Throwable: HTTP server returned an internal exception:
com.skifta.p2p.common.service.security.SecurityServiceException: The security credentials in the HTTP request do not correspond to a valid session [requester peerID: d7b503c0c7f6df1be77a6d1bd3d32a14, sessionToken: f16fc5f4-9e5f-43e4-bca8-dd67bcaa91f8]
at com.skifta.p2p.auth.server.http.AuthServerRequestHandler.handleRequest(AuthServerRequestHandler.java:264)
at com.skifta.p2p.common.http.server.AbstractP2PServerHttpRequestHandler$RequestHandler.run(AbstractP2PServerHttpRequestHandler.java:250)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
(com.skifta.common.network.http.exception.HttpServerException)
at com.skifta.p2p.common.http.P2PHttpRequestSender.sendRequest(P2PHttpRequestSender.java:93)
at com.skifta.p2p.client.service.security.impl.auth.AuthSecurityClientServiceImpl.isValidSession(AuthSecurityClientServiceImpl.java:285)
... 10 more
2012-01-02 15:26:34,812 LOG_ERROR [pool-54-thread-4] com.skifta.p2p.common.http.client.AbstractP2PClientHttpRequestHandler.handle:146 [RELAY-SERVER-CONN] HTTP request failed security validation - aborting request
java.lang.Throwable: An error occurred sending the validate session request (com.skifta.p2p.common.service.security.SecurityServiceException)
at com.skifta.p2p.client.service.security.impl.auth.AuthSecurityClientServiceImpl.isValidSession(AuthSecurityClientServiceImpl.java:288)
at com.skifta.p2p.common.http.client.AbstractP2PClientHttpRequestHandler.handle(AbstractP2PClientHttpRequestHandler.java:124)
at com.skifta.http.protocol.HttpService.doService(HttpService.java:293)
at com.skifta.http.protocol.HttpService.handleRequest(HttpService.java:212)
at com.skifta.common.network.http.server.HttpRequestReceiver.run(HttpRequestReceiver.java:109)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.Throwable: HTTP server returned an internal exception:
com.skifta.p2p.common.service.security.SecurityServiceException: The security credentials in the HTTP request do not correspond to a valid session [requester peerID: d7b503c0c7f6df1be77a6d1bd3d32a14, sessionToken: f16fc5f4-9e5f-43e4-bca8-dd67bcaa91f8]
at com.skifta.p2p.auth.server.http.AuthServerRequestHandler.handleRequest(AuthServerRequestHandler.java:264)
at com.skifta.p2p.common.http.server.AbstractP2PServerHttpRequestHandler$RequestHandler.run(AbstractP2PServerHttpRequestHandler.java:250)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
(com.skifta.common.network.http.exception.HttpServerException)
at com.skifta.p2p.common.http.P2PHttpRequestSender.sendRequest(P2PHttpRequestSender.java:93)
at com.skifta.p2p.client.service.security.impl.auth.AuthSecurityClientServiceImpl.isValidSession(AuthSecurityClientServiceImpl.java:285)
... 10 more
2012-01-02 15:26:34,813 LOG_DEBUG [pool-54-thread-4] com.skifta.p2p.client.service.relay.RelayInitConnectionRequestHandler.setErrorResponseCloseConnection:275 [RELAY-SERVER-CONN] Adding the relay session ID header to the error response, relaySessionID: 42b0fe48-656c-4144-aa78-a61169b1a5c9
2012-01-02 15:26:34,814 LOG_DEBUG [pool-54-thread-4] com.skifta.p2p.client.service.relay.RelayInitConnectionRequestHandler.setErrorResponseCloseConnection:275 [RELAY-SERVER-CONN] Adding the relay session ID header to the error response, relaySessionID: 42b0fe48-656c-4144-aa78-a61169b1a5c9
2012-01-02 15:26:34,815 LOG_DEBUG [pool-54-thread-4] com.skifta.common.network.http.server.AbstractHttpRequestHandler.setErrorResponseCloseConnection:73 Sending HTTP response status: HTTP/1.1 500 Internal Server Error
2012-01-02 15:26:34,816 LOG_DEBUG [pool-54-thread-4] com.skifta.common.network.http.server.AbstractHttpRequestHandler.setErrorResponseCloseConnection:73 Sending HTTP response status: HTTP/1.1 500 Internal Server Error
2012-01-02 15:26:34,817 LOG_INFO [pool-54-thread-4] com.skifta.common.network.http.server.HttpRequestReceiver.run:112 Completed handling request, sending response...
2012-01-02 15:26:34,817 LOG_INFO [pool-54-thread-4] com.skifta.common.network.http.server.HttpRequestReceiver.run:112 Completed handling request, sending response...
2012-01-02 15:26:36,355 LOG_DEBUG [RendezVousClientService.Heartbeat] com.skifta.p2p.common.http.P2PHttpRequestSender.sendRequest:65 Sending HTTP request -
GET /skifta/p2p/rdv/heartbeat HTTP/1.1
Connection: Keep-Alive
Host: 174.129.172.30:100
P2P-PeerID: d7b503c0c7f6df1be77a6d1bd3d32a14
P2P-SessionToken: f16fc5f4-9e5f-43e4-bca8-dd67bcaa91f8 -
Posted 1 year ago
RockyCJC
MemberGoing to try restarting the server to see if that fixes the issue. Seems like there is some sort of session issue.
-
Posted 1 year ago
RockyCJC
MemberOk - so a restart and then 2 attempts to make a connection on my Xoom tablet and I finally connected. However, now I am just Buffering a song. It has been buffering about 5 minutes (normally takes 15 seconds at most). So I am getting the sense that all is still not right.
-
Posted 1 year ago
So I have just verified this with two of my clients, shifting and playing audio content. It is buffering mp3's in what I would consider normal time (around 2-10 seconds for the complete mp3).
My systems are all also showing a full array of green lights right now, indicating no backend issues anywhere.
If the connection has been successfully made (and the virtual device shows up on your phone), the buffering wait is more likely to be a speed issue from you to the remote client. Assuming that our servers are working quickly enough (which from my test it looks like they are for me, at least), are you sure there isn't any network congestion your end somewhere causing an increased buffering period?
I'm also a little concerned that you needed to try the connection twice before you were successful. I'd be interested to see an Android log from Skifta startup with the connection being made and an attempted play taking place (do you have the Android adb tools handy?)
Rather than post here, you can email me at the address in my profile or at support@skifta.com if you like..
Allan.
-
Posted 1 year ago
RockyCJC
MemberI just forwarded the logcat fro my android device to support@skifta. I didn't see an e-mail for you in your profile. I will note that on both my logs from the server and the logcat I see that there are issues with the rendezvous server - seems the connections is closing.
Also, I don't believe it would be a speed issue given that I was connecting fine this morning. I exited the app because I was leaving my desk and when I came back, that is when I had all the problems.
-
Posted 1 year ago
Understood - I'll take a good look over this in the morning and get you some feedback.
In terms of network that the Android phone is running on - has anything changed that might affect outbound connections on port 80 (for example, addition of a transparent squid proxy or similar?). I know it's probably unrelated given that it worked in the morning then didn't, but this is the most common cause of rendezvous disconnects.
I'll feedback some more once I've looked through the log.
Allan.
-
Posted 1 year ago
Worm98
MemberGetting to creating connections as a remote then connection creation times out.
Service Provider: Suddenlink (Have two cable modems into the house)
Device: Kindle Fire
PC OS: Windows 7Can see the server, and stream data over Wi-Fi. But times out when connecting via remote server.
Don't know where the log is to review and dump.
Thanks,
Worm -
Posted 1 year ago
Install the free app 'log collector' from the marketplace, and immediately after you see the issue, switch to that app to get to the log.
Hold off for the moment though as our staff are investigating RockyCJC's logging.
Reply
You must log in to post.