bollman Posted April 28, 2009 Report Share Posted April 28, 2009 So, Retro 8 seems to be puking all over me here. Almost all clients (updated, restarted, reinstalled, Mac OS X 10.4, 10.5, Vista, XP, 2000, no clear connection on the client side) cannot be backed up and retro i reporting -557 (transaction already complete). I can't really see any connection at all. Some clients are on the same subnet, some are not and as stated above it occurs on all different operating systems. Exactly what does this strange message mean? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 28, 2009 Report Share Posted April 28, 2009 You are seeing this error on all your clients? Have you tried to restart the computer running the Retrospect engine? What edition of Retrospect are you using? Are you able to browse any of the client disks from the Sources list? What OS is the Retrospect engine running on? Quote Link to comment Share on other sites More sharing options...
bollman Posted April 29, 2009 Author Report Share Posted April 29, 2009 No, not on all clients, it doesn't seem to be consistent either, sometimes it will work, sometimes it stops after "scanning" and gives the error. The backup server has been restarted and even reinstalled. Latest version 8 (can't remember the version, but it was the latest available from the site), it's the one server, unlimited clients-edition. It is backing up one osxs server, works most of the time, it's not backing up itself. Yes, some are browseable, but those that has given the error is not. Rterospect is running on a 2008 Mac Pro, MOSXS 10.5.6 Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 30, 2009 Report Share Posted April 30, 2009 Do you see the same thing if the Retrospect Engine is installed on a different computer? You can try turning up the Networking logging to 7 and create a debug log. We may be able to use that to narrow down a cause: Directions are at: http://kb.dantz.com/article.asp?article=9718&p=2 Quote Link to comment Share on other sites More sharing options...
bollman Posted April 30, 2009 Author Report Share Posted April 30, 2009 Here you go! Before this, the "Preparing" and the "retropds" parts keep repeating for a while. I like the part about "socket closed cleanly", "socket closed unexpectedly" necoSetReserve: reserved for "Preparing..." necoWritePacket: cmd 101 [ 0 bytes]: necoIncoming: cmd 201 [ 218 bytes]: 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00: %*$] necoWritePacket: cmd 158 [ 0 bytes]: necoIncoming: cmd 216 [ 218 bytes]: db 37 fe 34 27 54 60 de af b5 33 e9 bc 69 31 9c: %*$] necoWritePacket: cmd 120 [ 44 bytes]: 74 65 47 56 01 00 00 00 02 00 00 00 00 00 00 00: %*$] necoCmd: transaction 14: 'VGet' on "retropds" necoIncoming: cmd 300 [ 236 bytes]: 66 6e 49 56 00 00 00 00 00 00 00 01 8a 8c 0f 3d: %*$] necoIncoming: cmd 203 [ 4 bytes]: 00 00 00 00: %*$] necoDispatch: transaction 14: result 0 necoWritePacket: cmd 108 [ 0 bytes]: necoIncoming: cmd 202 [ 4 bytes]: 00 00 00 00: %*$] necoSetRelease: unreserved necoWritePacket: cmd 101 [ 0 bytes]: necoIncoming: cmd 201 [ 218 bytes]: 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00: %*$] necoWritePacket: cmd 158 [ 0 bytes]: necoIncoming: cmd 216 [ 218 bytes]: db 37 fe 34 27 54 61 df ae b4 32 e8 bd 68 30 9d: %*$] necoReserve: 2aac008 claimed necoWritePacket: cmd 101 [ 0 bytes]: necoIncoming: cmd 201 [ 218 bytes]: 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00: %*$] necoWritePacket: cmd 158 [ 0 bytes]: necoIncoming: cmd 216 [ 218 bytes]: db 37 fe 34 27 54 61 df ae b4 32 e8 bd 68 30 9d: %*$] necoWritePacket: cmd 106 [ 36 bytes]: 00 00 00 00 50 72 65 70 61 72 69 6e 67 2e 2e 2e: %*$] necoIncoming: cmd 202 [ 4 bytes]: 00 00 00 00: %*$] necoSetReserve: reserved for "Preparing..." necoWritePacket: cmd 101 [ 0 bytes]: necoIncoming: cmd 201 [ 218 bytes]: 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00: %*$] necoWritePacket: cmd 158 [ 0 bytes]: necoIncoming: cmd 216 [ 218 bytes]: db 37 fe 34 27 54 60 de af b5 33 e9 bc 69 31 9c: %*$] necoWritePacket: cmd 120 [ 44 bytes]: 74 65 47 56 01 00 00 00 02 00 00 00 00 00 00 00: %*$] necoCmd: transaction 15: 'VGet' on "retropds" necoIncoming: cmd 300 [ 236 bytes]: 66 6e 49 56 00 00 00 00 00 00 00 01 8a 8c 0f 3d: %*$] necoIncoming: cmd 203 [ 4 bytes]: 00 00 00 00: %*$] necoDispatch: transaction 15: result 0 necoWritePacket: cmd 108 [ 0 bytes]: necoIncoming: cmd 202 [ 4 bytes]: 00 00 00 00: %*$] necoSetRelease: unreserved necoWritePacket: cmd 101 [ 0 bytes]: necoIncoming: cmd 201 [ 218 bytes]: 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00: %*$] necoWritePacket: cmd 158 [ 0 bytes]: necoIncoming: cmd 216 [ 218 bytes]: db 37 fe 34 27 54 61 df ae b4 32 e8 bd 68 30 9d: %*$] soccRecv: connection closed cleanly soccRecv: connection unexpectedly closed necoWritePacket: cmd 101 [ 0 bytes]: necoWritePacket: cmd 101 [ 0 bytes]: necoWritePacket: cmd 101 [ 0 bytes]: soctPreDispose: maximum queue depth was 3 napiRvSetup: collisionID is 0x745e2f8e ifacOptValue: 'WFDy' undefined, using default value 2 soctSetThread: socket thread now 0xb0687000 mcipXmitNow: sendto() failed with h_errno=0, errno=65 soctPreDispose: maximum queue depth was 1 ifacOptValue: 'WODy' undefined, using default value 2 soctSetThread: socket thread now 0xb1697000 soccOpen: socket send buffer size is 65536 soccOpen: socket recv buffer size is 65536 soccCallback: kNetSelectorWrite failed, error 51 necoWritePacket: cmd 101 [ 0 bytes]: necoWritePacket: cmd 101 [ 0 bytes]: soctPreDispose: maximum queue depth was 4 napiRvSetup: collisionID is 0x2b4f2f8e ifacOptValue: 'WFDy' undefined, using default value 2 soctSetThread: socket thread now 0xb0687000 mcipXmitNow: sendto() failed with h_errno=0, errno=65 soctPreDispose: maximum queue depth was 1 ifacOptValue: 'WODy' undefined, using default value 2 soctSetThread: socket thread now 0xb1697000 soccOpen: socket send buffer size is 65536 soccOpen: socket recv buffer size is 65536 soccCallback: kNetSelectorWrite failed, error 51 necoWritePacket: cmd 101 [ 0 bytes]: necoWritePacket: cmd 101 [ 0 bytes]: soctPreDispose: maximum queue depth was 4 ifacOptValue: 'WODy' undefined, using default value 2 soctSetThread: socket thread now 0xb1697000 soccOpen: socket send buffer size is 65536 soccOpen: socket recv buffer size is 65536 soccCallback: kNetSelectorWrite failed, error 51 necoWritePacket: cmd 101 [ 0 bytes]: necoWritePacket: cmd 101 [ 0 bytes]: soctPreDispose: maximum queue depth was 4 ifacOptValue: 'WODy' undefined, using default value 2 soctSetThread: socket thread now 0xb1697000 soccOpen: socket send buffer size is 65536 soccOpen: socket recv buffer size is 65536 soccCallback: kNetSelectorWrite failed, error 51 necoWritePacket: cmd 101 [ 0 bytes]: necoWritePacket: cmd 101 [ 0 bytes]: soctPreDispose: maximum queue depth was 4 ifacOptValue: 'WODy' undefined, using default value 2 soctSetThread: socket thread now 0xb1697000 soccOpen: socket send buffer size is 65536 soccOpen: socket recv buffer size is 65536 soccCallback: kNetSelectorWrite failed, error 51 necoWritePacket: cmd 101 [ 0 bytes]: necoWritePacket: cmd 101 [ 0 bytes]: soctPreDispose: maximum queue depth was 4 napiRvSetup: collisionID is 0x47fb0f8e ifacOptValue: 'WFDy' undefined, using default value 2 soctSetThread: socket thread now 0xb0687000 soctPreDispose: maximum queue depth was 1 napiRvSetup: collisionID is 0xe12d0f8e ifacOptValue: 'WFDy' undefined, using default value 2 soctSetThread: socket thread now 0xb0687000 Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 30, 2009 Report Share Posted April 30, 2009 I sort of expected the debug log to include the -557 error. Do you have a debug log that reproduced and shows the error? Please attach the operations_log.utx file Quote Link to comment Share on other sites More sharing options...
bollman Posted May 4, 2009 Author Report Share Posted May 4, 2009 (edited) Wow, that was one heavy log. Ok, I think I've found a relevant part of the log: See attached file. It contains some strange characters so it wouldn't paste. Still no mention of -557 though. Edited May 4, 2009 by Guest Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 4, 2009 Report Share Posted May 4, 2009 This still does not seem like the full log. You may want to call TS directly and we can help with troubleshooting and maybe getting the software configured to save enough log details to help narrow down a cause. Quote Link to comment Share on other sites More sharing options...
bollman Posted May 5, 2009 Author Report Share Posted May 5, 2009 Ouch, I'm in Sweden. Not easy to call at the right times. I'm thinking about reinstalling on a different machine to see if it makes any difference. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.