5.0238 client on 10.2.8 crashing on start

[craigontour]

10.2.8 on G4

 

Installed Retrospect 5.0 client and updated to 5.0528 (form the Retrospect Server 5.0238 update).

 

A few seconds after activation it crashes with Crash report written to: /Library/Logs/CrashReporter/pitond.crash.log (see below).

 

I found some suggestions from people who had probs with client also, including:

- Moving active network configuration to top of list in Sys Prefs (see http://www.expeditionoutfitters.org/help/helpdesk5.html#network)

- Changing file & folder permissions (see http://my.brandeis.edu/faq/one?faq_id=203#8)

 

Hopefully someone has experienced something similar and offer a solution.

 

regards

Craig.

 

 

**********

 

Date/Time: 2003-11-04 13:13:11 +0000

OS Version: 10.2.8 (Build 6R73)

Host: ericadmin.local.

 

Command: pitond

PID: 785

 

Exception: EXC_BAD_ACCESS (0x0001)

Codes: KERN_INVALID_ADDRESS (0x0001) at 0x0020e0c4

 

Thread 0 Crashed:

#0 0x00009c78 in getPID (main.c:269)

#1 0x00009894 in bindToValidBootPort (main.c:199)

#2 0x00009804 in eventLoop (main.c:177)

#3 0x00009780 in main (main.c:153)

#4 0x00003e4c in _start

#5 0x00003c7c in start

 

Thread 1:

#0 0x90006a28 in clock_sleep_trap

#1 0x9000672c in nanosleep

#2 0x90006670 in sleep

#3 0x000109c0 in netEnumInterfaces (net_interfaces.c:455)

#4 0x00009fa0 in threadSpawner (object.c:91)

#5 0x90020c28 in _pthread_body

 

Thread 2:

#0 0x9002560c in recvfrom

#1 0x000086b0 in iplud (ip_nameservice.c:288)

#2 0x00009fa0 in threadSpawner (object.c:91)

#3 0x90020c28 in _pthread_body

 

Thread 3:

#0 0x9003130c in accept

#1 0x0000658c in connListener (connection.c:952)

#2 0x00009fa0 in threadSpawner (object.c:91)

#3 0x90020c28 in _pthread_body

 

Thread 4:

#0 0x9002560c in recvfrom

#1 0x00004798 in ConnReadData (connection.c:126)

#2 0x000056d8 in connTCPConnection (connection.c:623)

#3 0x000062c0 in connAccept (connection.c:891)

#4 0x00009fa0 in threadSpawner (object.c:91)

#5 0x90020c28 in _pthread_body

 

Thread 5:

#0 0x90006a28 in clock_sleep_trap

#1 0x9000672c in nanosleep

#2 0x90006670 in sleep

#3 0x0000f64c in notifyThreadTop (notify.c:176)

#4 0x00009fa0 in threadSpawner (object.c:91)

#5 0x90020c28 in _pthread_body

 

PPC Thread State:

srr0: 0x00009c78 srr1: 0x0000d030 vrsave: 0x00000000

xer: 0x00000000 lr: 0x00009c74 ctr: 0x90073ba0 mq: 0x00000000

r0: 0x00009c74 r1: 0xbffffc70 r2: 0x00167010 r3: 0x00000000

r4: 0x00000003 r5: 0x00000028 r6: 0x0000002c r7: 0x00000a03

r8: 0x00000000 r9: 0x0020e0ac r10: 0x00000001 r11: 0xa0004898

r12: 0x90073ba0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000

r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000

r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000

r24: 0x00000000 r25: 0x00000000 r26: 0xbffffeb4 r27: 0x00000008

r28: 0x00000001 r29: 0xbffffec0 r30: 0xbffffc70 r31: 0x00009ae8

 

[natew]

Hi

 

The 5.1 client is backwards compatible with Retrospect 5.0 so I would give that a shot.

ftp://ftp.dantz.com/pub/updates/51_client_en.sit

 

Make sure you run the uninstaller program from the 5.0 client install and reboot the machine before reinstalling.

 

Nate