Linux RedHat9 client experiencing connection failures etc...

[Saccardi]

Linux RedHat9 client experiencing connection failures and unacceptable slow response times.

NOTE: Some of the issues we see could be resolved by moving to the 4.1 client (maybe) and server, however, there is not a RedHat9 version now available as there has previously been. While the Fedora CLC is not functional with RedHat9, our business needs for RND require that we continue to use and support older O/S’s and environments. In review of the documentation for fixes for 4.0 to 4.1 may or may not solve some of the issues we experience.

1. The length of protocol headers are no longer limited to 1024 characters, which caused problems with long comment strings and multiple database aliases.

10. Command Line Client (CLC) - No longer leaks memory during Get Latest and other operations.

11. CLC - Secure connections now work using database aliases.

12. CLC - "time" option now works independently of the "soshome" option.

Do you have a client for 4.1 that will work with RedHat9 and can we resolve these CPU hogging issues?

and we require confirmation if there are any incompatibilities with upgrading the server to 4.1 while keeping the clients at 4.0. in the event there is no RedHat9 further supported.

please assist.

SAccardi

Status of System:

Server running VSS 6
Database is 5.X

.Net framework 1.1 installed vs1.1.4322.573

Server is Win2k3

NIC and Switch set to 100 Full Duplex

Antivirus is active and excluding all activity in these folders
VSS
SOS
TempSOS


SOS server version: 4.0.2
CLC version: sos-4.0.0-1.i386.rpm
Unsecured port 8080

Telnet active and fully functional
200
Protocol-Version:2.0
Message-ID:00000000
Database Aliases:<Alias-Name>
Content-Length:22


Symptoms:

Server CPU running at 60% or above when a recursive uncompressed script is run.

The Script will abort on the Linux machine (Fail) and not release the process on the server.

Memory is unaffected.

The service has had to be restarted to release the CPU and/or the server has been rebooted since this has started to happen.

SOSservice.exe is at 30%

No other process is running that is utilizing portions of the CPU.


Troubleshooting done:

1.
Activity changed service credentials on the server from System to Domain account.

Conclusion: Not an issue

2.
Posted: Thu Dec 18, 2003 10:40 am Post subject: SOS concurrency crash when using VSS 6.0d
http://support.sourcegear.com/viewtopic.php?t=10

Regedit key HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32
"ThreadingModel" Key, set to both

Conclusion: Not an issue

3.
Posted: Tue Sep 14, 2004 11:45 am Post subject: SOS Server hangs or needs to be restarted often

http://support.sourcegear.com/viewtopic.php?t=1866

downloaded and installed the VSS patch to VSS\Win32
issue with Linux not resolved

Conclusion: Not an issue

4.
Set the NIC and switch to 100 full duplex.
Did not resolve.

Conclusion: Not an issue

Code used by the Linux RedHat 9. Client

/usr/bin/clc -command GetProject -server 192.168.XXX.XXX:8080 -name $XXXXXX -password $XXXXXXXX -database \\\\Server\\ShareName\\vss\\srcsafe.ini -project $1 -verbose ${checkout_opts}

The typical ${checkout_opts} are "-recursive -nocompress"

Errors include:

The first error usually reported:

Got file: /home/UserName/tstx50ccm/cpsapp/FILENAME/BUILD/XXXXXXX.dsw
Net error during attempt to read headers. (RH1). Error: 2 No such file or directory
Got file: /home/UserName/tstx50ccm/cpsapp/FILENAME/BUILD/XXXXXXX.dsw
Could not open file /tmp/file08xdx1. Error Num=2
Error: Server response = 203 File
Closed connection to server 192.168.XXX.XXX at port 8080.

The second repeating error(s)

SourceOffSite Command Line Client: 128 bit Encryption version 4.0
Connected to server 192.168.XXX.XXX at port 8080.
Received Challenge from server
Net error during attempt to read headers. (RH1). Error: 0 Success
Closed connection to server 192.168.XXX.XXX at port 8080.

Server Log during one of these errors:

12/29/2004 1:20:07 PM - 44: Error removing temp file 'D:\Folder\Share\SOS_TEMPFILE\User632399225472812500\raminit.inc':The process cannot access the file

" D:\Folder\Share\SOS_TEMPFILE\User632399225472812500\raminit." because it is being used by another process.

12/29/2004 1:20:07 PM - 44: Error removing user temp folder

'D:\Folder\Share\SOS_TEMPFILE\User632399225472812500'.
12/29/2004 1:20:07 PM - The process cannot access the file "raminit.inc" because it is being used by another process.

12/29/2004 1:20:07 PM - Connection accepted from 192.168.XXX.XXX:10483 on local address 192.168.XXX.Server:8080, session id is 45.

12/29/2004 1:20:07 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:07 PM - Connection accepted from 192.168.XXX.XXX:10484 on local address 192.168.XXX.Server:8080, session id is 46.

12/29/2004 1:20:07 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:07 PM - Connection accepted from 192.168.XXX.XXX:10485 on local address 192.168.XXX.Server:8080, session id is 47.

12/29/2004 1:20:07 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:07 PM - Connection accepted from 192.168.XXX.XXX:10486 on local address 192.168.XXX.Server:8080, session id is 48.

12/29/2004 1:20:11 PM - 45: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:11 PM - 45: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:11 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:11 PM - 46: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:11 PM - 46: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:11 PM - Connection accepted from 192.168.XXX.XXX:10487 on local address 192.168.XXX.Server:8080, session id is 49.

12/29/2004 1:20:11 PM - 47: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:11 PM - 47: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:11 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:11 PM - 48: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:11 PM - 48: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:12 PM - Connection accepted from 192.168.XXX.XXX:10488 on local address 192.168.XXX.Server:8080, session id is 50.

12/29/2004 1:20:16 PM - 49: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:16 PM - 49: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:16 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:16 PM - 50: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:16 PM - 50: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:16 PM - Connection accepted from 192.168.XXX.XXX:10489 on local address 192.168.XXX.Server:8080, session id is 51.

12/29/2004 1:20:20 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:20 PM - Connection accepted from 192.168.XXX.XXX:10490 on local address 192.168.XXX.Server:8080, session id is 52.

12/29/2004 1:20:20 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:20 PM - Connection accepted from 192.168.XXX.XXX:10491 on local address 192.168.XXX.Server:8080, session id is 53.
12/29/2004 1:20:21 PM - 51: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:21 PM - 51: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:21 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:21 PM - Connection accepted from 192.168.XXX.XXX:10492 on local address 192.168.XXX.Server:8080, session id is 54.

12/29/2004 1:20:24 PM - 52: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:24 PM - 52: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:24 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:24 PM - 53: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:24 PM - 53: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:24 PM - Connection accepted from 192.168.XXX.XXX:10493 on local address 192.168.XXX.Server:8080, session id is 55.

12/29/2004 1:20:25 PM - 54: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:25 PM - 54: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:25 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:25 PM - Connection accepted from 192.168.XXX.XXX:10494 on local address 192.168.XXX.Server:8080, session id is 56.

12/29/2004 1:20:29 PM - 55: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:29 PM - 55: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:29 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:29 PM - Connection accepted from 192.168.XXX.XXX:10495 on local address 192.168.XXX.Server:8080, session id is 57.

12/29/2004 1:20:30 PM - 56: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:30 PM - 56: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:30 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:30 PM - Connection accepted from 192.168.XXX.XXX:10496 on local address 192.168.XXX.Server:8080, session id is 58.

12/29/2004 1:20:34 PM - 57: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:34 PM - 57: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:34 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:34 PM - Connection accepted from 192.168.XXX.XXX:10497 on local address 192.168.XXX.Server:8080, session id is 59.

12/29/2004 1:20:35 PM - 58: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:35 PM - 58: Exception processing messages: Object reference not set to an instance of an object.

12/29/2004 1:20:35 PM - Killing disconnected or idle client - (192.168.XXX.XXX)

12/29/2004 1:20:38 PM - 59: Unable to get hostname from address: 192.168.XXX.XXX

12/29/2004 1:20:38 PM - 59: Exception processing messages: Object reference not set to an instance of an object.

[quote][b]In the words of Our Linux users of this product:

1) Its performance is unacceptably slow when transferring large directory trees of files. - I frequently see delays of .3 to .5 seconds between files, with one delay as long as 40 seconds. These delays are on the server end, while transferring files for a single project

2) It does not work reliably - It frequently does not successfully transfer the complete project, but aborts part way through. At that point, it typically aborts all subsequent project transfers without transferring a single file from the project.

Can you please ask SourceGear to supply the following:

- A current (4.1) version of the client software (Linux and Windows)
- This must include both the command-line client and the gui client
- This must be in an rpm file suitable for direct installation on a standard RedHat 9 Linux system[/b][/quote]

[lbauer]

While we don't have a build for Red Hat, we do make available the SOS Unix Client code so that you can build what you need.

We'd rather troubleshoot these issues on SOS 4.1, since there have been improvements in CPU utilization, etc.

If you'd like the Unix client code, email linda at sourcegear.com.

[Saccardi]

in the interim can you confirm if the 4.1 server is compatible with the 4.0 client for Linux?

Thank you for your prompt assistance.
12/30/04 @ 12:05PM EST

Shannon

[lbauer]

Yes, the 4.0 Linux client will work with SOS 4.1

[Saccardi]

Thank you

Shannon