Re: tcp errors killing osx client

It may be worth while looking in ~/Library/Logs/CrashReporter/ or
/Library/Logs/CrashReporter/ for dumps, if enabled. To enable, open
the "Console" app, under preferences check "Enable crash reporting".

If nothing else, this info could be valuable to IBM to determine the
cause of the problem.

Also, check /var/log/system.log and /var/tmp/console.log for anything
anomalous.

On Thursday, Aug 7, 2003, at 06:31 Australia/Sydney, Alexander
Lazarevich wrote:

We've got TSM 5.1.6.5 server on Windows 2K server. It's been running
great, most clients are backing up just fine, except for a Mac OSX
client
- the only OSX client in our environment at the moment.

The Mac is: G4 v3.3 1.4GHz, 2GB RAM, OSX 10.2.6(6L60), darwin kernel
version 6.6.

I've installed the TSM client (5.1.5) twice, per the manual. I set the
preferences, start the client, it starts backing up maybe 100-200MB,
and
then dies. It dies in two ways:

1) The little rainbow/circle mouse pointer spins endlessly. No error
message.
2) The client program drops entirely. Gone. No error message.

The error log on the client doesn't exist. I'm not sure why. There is
just
nothing there, even though I've set it to put the error log in the
application/tsm.. directory, it just doesn't ever get created. I assume
that's because it dies before it can be created.

The logs on the server show these two errors from that client:

ANR8218W Session terminated when no data read on socket xxxxxxx
ANR0480W Session terminated - connection severed

Both those messages indicate some kind of network problem on the
client.
But the client NIC is fine. FTP works, ssh works, IE works, nfs works,
all getting good performance too. And TSM works too, until it crashes
hard.

Any ideas what to do? Try a different NIC?

Any help is appreciated.

Alex
---                                                               ---
   Alex Lazarevich | Systems Administrator | Imaging Technology Group
            Beckman Institute - University of Illinois
       alazarev AT itg.uiuc DOT edu | (217)244-1565 | www.itg.uiuc.edu
---                                                               ---

--
Paul Ripke
Unix/OpenVMS/TSM/DBA
101 reasons why you can't find your Sysadmin:
68: It's 9AM. He/She is not working that late.
-- Koos van den Hout