Crash on Check Out

Moderator: SourceGear


Posts: 81
Joined: Sun Aug 06, 2006 12:51 am
PostPosted: Mon Jun 22, 2009 9:13 pm
I tried to perform Check Out, it asked me to specify working folder, I did, then it crashed on Windows 7 while it was trying to Get updated list on the first sub-directory. It was simply recursive checkout on basic .SQL files + 1 sub-directory.

Posts: 3486
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
PostPosted: Tue Jun 23, 2009 5:56 am
Jared:

Can you reproduce this on a restart of the client? Also, check your %TEMP%\.SOS\sosgui_log.txt file. Is there anything in there that shows what was happening?
Jeff Clausius
SourceGear

Posts: 3486
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
PostPosted: Tue Jun 23, 2009 8:17 am
Jared:

One other thing to check.... Can you look at the server log for the corresponding time period. Is there anything regarding a SOS server restart or dropped client network connection?
Jeff Clausius
SourceGear

Posts: 81
Joined: Sun Aug 06, 2006 12:51 am
PostPosted: Tue Jun 23, 2009 2:35 pm
1. GET /mana
2. GET http:
3. GET /mana

** BANG** Some web crawler bot or random user directly hit my IP, This often happens and sure I logged plenty of bugs about it.

Whats the chances of that happening while I am checking out 50K of text documents.




[18/06/2009 9:01:07 AM] ### Starting SourceOffSite Client ###
[18/06/2009 9:01:40 AM] Connecting to 127.0.0.1:8080...
[18/06/2009 9:01:51 AM] Server closed connection
[18/06/2009 9:01:58 AM] Connecting to 127.0.0.1:8080...
[18/06/2009 9:01:58 AM] Server closed connection
[18/06/2009 9:02:17 AM] Connecting to 127.0.0.1:8080...
[23/06/2009 1:04:35 PM] ### Starting SourceOffSite Client ###
[23/06/2009 1:04:42 PM] Connecting to 127.0.0.1:8080...
[23/06/2009 1:07:22 PM] ### Starting SourceOffSite Client ###
[23/06/2009 1:07:27 PM] Connecting to 127.0.0.1:8080...




23/06/2009 2:38:48 AM - E:\vss\srcsafe.ini

23/06/2009 2:38:48 AM - BLITZEN is attempting to listen for connections on secure port 8081
23/06/2009 2:38:48 AM - BLITZEN is attempting to listen for connections on unsecure port 8080

23/06/2009 2:38:48 AM - Waiting for a connection....secure = True

23/06/2009 2:38:48 AM - Waiting for a connection....secure = False
23/06/2009 4:21:59 AM - Connection accepted from 210.201.172.81:2512 on local address 202.55.154.198:8080, session id is 1.
23/06/2009 4:21:59 AM - 23/06/2009 4:21:59 AM - Server Exception (407): [GET /mana - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
23/06/2009 4:21:59 AM - 1: Exception processing messages: UNRECOGNIZED_MESSAGE
23/06/2009 7:44:30 AM - Connection accepted from 203.16.208.179:49418 on local address 202.55.154.198:8080, session id is 2.
23/06/2009 8:07:16 AM - Connection accepted from 203.16.208.179:49423 on local address 202.55.154.198:8080, session id is 3.
23/06/2009 8:32:37 AM - Connection accepted from 222.186.13.75:2868 on local address 202.55.154.198:8080, session id is 4.
23/06/2009 8:32:41 AM - 4: Unable to get hostname from address: 222.186.13.75
23/06/2009 8:32:41 AM - 23/06/2009 8:32:41 AM - Server Exception (407): [GET http: - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
23/06/2009 8:32:41 AM - 4: Exception processing messages: UNRECOGNIZED_MESSAGE
23/06/2009 8:32:42 AM - Connection accepted from 222.186.13.75:2730 on local address 202.55.154.198:8080, session id is 5.
23/06/2009 8:32:46 AM - 5: Unable to get hostname from address: 222.186.13.75
23/06/2009 8:32:47 AM - 5: Exception processing messages: An existing connection was forcibly closed by the remote host
23/06/2009 8:32:47 AM - Connection accepted from 222.186.13.75:3444 on local address 202.55.154.198:8080, session id is 6.
23/06/2009 8:32:52 AM - 6: Unable to get hostname from address: 222.186.13.75
23/06/2009 8:32:52 AM - 6: Exception processing messages: An existing connection was forcibly closed by the remote host
23/06/2009 12:04:49 PM - Connection accepted from 203.16.208.179:49667 on local address 202.55.154.198:8080, session id is 7.
23/06/2009 12:42:21 PM - Connection accepted from 203.16.208.179:49685 on local address 202.55.154.198:8080, session id is 8.
23/06/2009 1:01:47 PM - Connection accepted from 203.16.208.179:49709 on local address 202.55.154.198:8080, session id is 9.
23/06/2009 1:04:42 PM - Connection accepted from 127.0.0.1:53685 on local address 127.0.0.1:8080, session id is 10.
23/06/2009 1:06:49 PM - 10: Exception: An existing connection was forcibly closed by the remote host
23/06/2009 1:07:27 PM - Connection accepted from 127.0.0.1:53686 on local address 127.0.0.1:8080, session id is 11.
23/06/2009 2:26:41 PM - Connection accepted from 203.16.208.179:49921 on local address 202.55.154.198:8080, session id is 12.
23/06/2009 4:00:12 PM - Connection accepted from 222.66.13.82:3160 on local address 202.55.154.198:8080, session id is 13.
23/06/2009 4:00:14 PM - 23/06/2009 4:00:14 PM - Server Exception (407): [GET /mana - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
23/06/2009 4:00:14 PM - 13: Exception processing messages: UNRECOGNIZED_MESSAGE
23/06/2009 4:28:42 PM - ****************************************************
23/06/2009 4:28:42 PM - SourceOffSite Server 4.2 Professional - With Cryptography

23/06/2009 4:28:42 PM - CurrentCulture is en-AU.


23/06/2009 4:28:45 PM - Server Information
23/06/2009 4:28:45 PM - Operating System: Microsoft Windows 7 Ultimate
23/06/2009 4:28:45 PM - Service Pack: 0.0
23/06/2009 4:28:45 PM - OS Version: 6.1.7127
23/06/2009 4:28:45 PM - Locale: Ox0c09
23/06/2009 4:28:45 PM - OSLanguage: 1033
23/06/2009 4:28:45 PM - Total Physical Memory: 2 GB
23/06/2009 4:28:45 PM - Time Zone: (UTC+10:00) Canberra, Melbourne, Sydney
23/06/2009 4:28:45 PM -
23/06/2009 4:28:45 PM - SSAPI.dll Information:
23/06/2009 4:28:45 PM - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
23/06/2009 4:28:45 PM - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
23/06/2009 4:28:45 PM -
23/06/2009 4:28:45 PM - Started at 23/06/2009 4:28:45 PM

23/06/2009 4:28:45 PM - General logging level is Error. Method logging is Disabled.

Posts: 3486
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
PostPosted: Tue Jun 23, 2009 4:04 pm
Were there files on disk where the status was unknown or renegade?

If not, what happens when you GET to an empty directory?

FWIW, this bug came up in QA - "SOS CTP crashes when doing a getlatest from a folder if folder contains renegade file and prompt for each is chosen."
Jeff Clausius
SourceGear

Posts: 81
Joined: Sun Aug 06, 2006 12:51 am
PostPosted: Tue Jun 23, 2009 4:16 pm
Status is null.

Thats what I did, deleted my copies of files and performed Check Out on empty folder, it worked.

>23/06/2009 8:32:41 AM - 23/06/2009 8:32:41 AM - Server Exception (407): [GET http: - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE

Wouldn't the above message suggest that port 8080 has internet traffic comming through. I may change port, but far to busy to risk SCC curruption right now.

Haven't seen message again.

Whats Vault like for stability/speed?

-JS

Posts: 3486
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
PostPosted: Wed Jun 24, 2009 5:34 am
So, if the status of all messages were blank. We'll keep looking. In the mean time, we may want to try the increasing the level of logging. In the Options, try moving to "Verbose" level logging for the client to see if we can capture the state of things if you run into this again.

Also, we are starting work on the SOS 5.0 server. We will be trying some different caching strategies to speed things up. The networking code has also been improved for connectivity and other types of issues. I understand a lot of frustration is coming from this part of SourceOffSite, and we are addressing the problems. More news on this Preview in the upcoming weeks.

Also, in regards to the other network traffic, I'd suggest setting your server to timeout any idle connections and configure all clients to send a keep-alive. These connections are a plaque build-up which need to be brushed away after a given amount of inactivity.



In regards to Vault, stability is not a problem as its technology stack is based on Web services and .NET platform. It has a different caching model than SOS, so it is hard to make an apples to apples comparison for speed. If you're interested, I would recommend downloading and trying it out. It is free for a single user, so it might be something you add to your version control tool box.
Jeff Clausius
SourceGear

Posts: 3486
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
PostPosted: Mon Jul 06, 2009 10:18 am
Jared:

One problem with recursive GETs was fixed, and a new update is available in the same location as the CTP release.
Jeff Clausius
SourceGear

Return to SourceOffSite 5 Preview

Who is online

Users browsing this forum: No registered users and 1 guest

cron