Jump to content
Sign in to follow this  
Lindsay Robertson

[*] soccClose: shutdown() failed with error 0

Recommended Posts

I hope I'm doing the right thing here, I originally posted this by mistake in the windows forum, so have reposted in the correct place...

 

 

Although everything seems to be working fine, Im seeing this error message a lot in the retrospect log.

I've included a sample to show how it happens.

 

The clients all seem to be backing up ok. but it does have me worried.

 

Can anyone give a clue as to what may be going on here?

I cant even tell if its affecting the clients or not.

 

I run retrospect single server version 13.5.0 with about 50 clients backing up to two different media sets on separate qnap NAS SMB shares.

Server is a Mac mini late 2014, 2.6 Ghz core i5 with 16Gb ram running Mac OS X 10.12.5

I back up clients on an intranet spanning 12 buildings of a university campus, It doesn't seem to be any particular building area or switch. 

 

[*] soccClose: shutdown() failed with error 0 [*] soccClose: shutdown() failed with error 0 [*] soccClose: shutdown() failed with error 0 [*] soccClose: shutdown() failed with error 0 [*] soccClose: shutdown() failed with error 0 [*] soccClose: shutdown() failed with error 0 [*] soccClose: shutdown() failed with error 0 [*] soccClose: shutdown() failed with error 0
+ Normal backup using 24 hr, Labs set I at 11/07/17, 11:18:19 AM (Activity Thread 1)
11/07/17 11:18:20 AM: Finished scanning backup set data files
To Backup Set Media Set I...
- 11/07/17 11:18:19 AM: Copying Users on JHmMac11
11/07/17 11:18:37 AM: Found: 34179 files, 4104 folders, 19.7 GB
11/07/17 11:19:28 AM: Finished matching
11/07/17 11:19:32 AM: Copying: 48 files (154.3 MB) and 0 hard links
11/07/17 11:20:02 AM: Building Snapshot...
11/07/17 11:20:03 AM: Checking 4,104 folders for ACLs or extended attributes
11/07/17 11:20:04 AM: Finished copying 1,008 folders with ACLs or extended attributes
11/07/17 11:20:04 AM: Copying Snapshot: 2 files (10.2 MB)
11/07/17 11:20:07 AM: Snapshot stored, 10.2 MB
11/07/17 11:20:08 AM: Execution completed successfully
Completed: 48 files, 154.3 MB
Performance: 308.6 MB/minute
Duration: 00:01:48 (00:01:17 idle/loading/preparing)
[*] soccClose: shutdown() failed with error 0 [*] soccClose: shutdown() failed with error 0
+ Normal backup using 24 hr, Labs set I at 11/07/17, 12:15:06 PM (Activity Thread 1)
11/07/17 12:15:06 PM: Finished scanning backup set data files
To Backup Set Media Set I...
- 11/07/17 12:15:06 PM: Copying Users on TRmiMacf
11/07/17 12:15:23 PM: Found: 26160 files, 6699 folders, 62.8 GB
11/07/17 12:16:16 PM: Finished matching
11/07/17 12:16:17 PM: Copying: 599 files (98.5 MB) and 0 hard links
11/07/17 12:16:48 PM: Building Snapshot...
11/07/17 12:16:49 PM: Checking 6,699 folders for ACLs or extended attributes
11/07/17 12:16:52 PM: Finished copying 1,126 folders with ACLs or extended attributes
11/07/17 12:16:55 PM: Copying Snapshot: 2 files (8.9 MB)
11/07/17 12:16:58 PM: Snapshot stored, 8.9 MB
11/07/17 12:17:05 PM: Execution completed successfully
Completed: 599 files, 98.5 MB
Performance: 151.5 MB/minute
Duration: 00:01:59 (00:01:20 idle/loading/preparing)

+ Normal backup using 24 hr, academic desktop set I at 11/07/17, 1:11:33 PM (Activity Thread 1)
11/07/17 1:11:33 PM: Finished scanning backup set data files
To Backup Set Media Set I...
- 11/07/17 1:11:33 PM: Copying Users on JM-iMaca
11/07/17 1:13:50 PM: Found: 171157 files, 31238 folders, 41.4 GB
11/07/17 1:14:08 PM: Finished matching
11/07/17 1:14:20 PM: Copying: 711 files (361.7 MB) and 0 hard links
11/07/17 1:15:18 PM: Building Snapshot...
11/07/17 1:15:19 PM: Checking 31,238 folders for ACLs or extended attributes
11/07/17 1:15:25 PM: Finished copying 2,469 folders with ACLs or extended attributes
11/07/17 1:15:29 PM: Copying Snapshot: 2 files (51.6 MB)
11/07/17 1:15:37 PM: Snapshot stored, 51.6 MB
11/07/17 1:15:50 PM: Execution completed successfully
Completed: 711 files, 361.7 MB
Performance: 297.2 MB/minute
Duration: 00:04:16 (00:03:02 idle/loading/preparing)

  •  

 

 

 

Here is what may be another clue

 

[*] soccClose: shutdown() failed with error 0 [*] soccClose: shutdown() failed with error 0 [*] soccClose: shutdown() failed with error 0 [*] and 18 others [*] necoSoccTimer: connection failed (idle 302 seconds) [*] soccClose: shutdown() failed with error 0 [*] soccClose: shutdown() failed with error 0 [*] soccClose: shutdown() failed with error 0 [*] soccClose: shutdown() failed with error 0
+ Normal backup using 24 hr, Labs set G at 12/07/17, 8:30:22 AM (Activity Thread 2)
12/07/17 8:30:29 AM: Finished scanning backup set data files
To Backup Set Media Set g...
- 12/07/17 8:30:22 AM: Copying Users on RZmiMacc
Using Instant Scan data for Users on RZmiMacc
12/07/17 8:31:42 AM: Found: 146647 files, 34025 folders, 194.7 GB
12/07/17 8:33:01 AM: Finished matching
12/07/17 8:33:28 AM: Copying: 603 files (81 MB) and 0 hard links
12/07/17 8:34:12 AM: Building Snapshot...
12/07/17 8:34:12 AM: Checking 34,025 folders for ACLs or extended attributes
12/07/17 8:34:29 AM: Finished copying 3,012 folders with ACLs or extended attributes
12/07/17 8:34:32 AM: Copying Snapshot: 2 files (47.1 MB)
12/07/17 8:34:53 AM: Snapshot stored, 47.1 MB
12/07/17 8:34:56 AM: Execution completed successfully
Completed: 603 files, 81 MB, with 0% compression
Performance: 97.2 MB/minute
Duration: 00:04:33 (00:03:43 idle/loading/preparing
)

 

  • Like 1

Share this post


Link to post
Share on other sites

As suggested here: http://forums.retrospect.com/index.php?/topic/150327-media-set-error/ 

 

I'm definitely using disk sets, not file sets. I'm not at all clear that is related to either or backup set.

From the log, the error seems to happen between backups - I'm not sure if it relates to the previous backup or the next occurring one, which may be to different sets.

I know it definitely happens on one, because It happened when I only had one.

I'll try disabling that set for a couple of days and see what happens.

Maybe that'll narrow it down.

Share this post


Link to post
Share on other sites

If disabling that Media Set doesn't solve the problem, I strongly urge Lindsay Robertson to look at the second paragraph of the post linked-to at the top of post #2 in this thread.  twickland has a lot of experience with Retrospect, so it's probably worth doing what he/she suggests—even if it's a bit scary.

  • Like 1

Share this post


Link to post
Share on other sites

If, as it sounds, your backups are completing successfully, I'd be inclined to ignore the [*] soccClose: shutdown() failed with error X messages. We see those from time to time at the completion of a backup activity when there is no apparent problem. You should, of course, confirm that you can restore everything from your backups before deciding that they really ran successfully.

 

My response in the post that David Hertzberg cites above was related to the fact that the scheduled backups did not run. 

  • Like 1

Share this post


Link to post
Share on other sites

No, dagnabbit, don't ignore the "[*] soccClose: shutdown() failed with error 0" messages, even if the backups are completing successfully.  Instead report the messages as a bug to Retrospect Inc., by filing a Support Case.  If we don't report these Retrospect bugs, they'll never get fixed.  twickland—blessings be upon him—didn't report this as a bug four years ago, and look where that got us.

 

My next post in this thread will be my boilerplate instructions on why and how to file a Support Case.  Lindsay Robertson can simply copy portions of his/her first two posts in this thread as the "description of your issue" and "additional notes" for the Support Case, so his/her total elapsed time to file the Support Case will be less than 5 minutes.

 

P.S.: I forgot that, after I filed a Support Case on my -530 errors about 6 months ago, Retrospect Support asked me to upload copies of a couple of Retrospect files.  But uploading those files didn't take me more than 5 minutes apiece, so Lindsay Robertson shouldn't have to spend more than 15 minutes total on his/her Support Case—spread out over several days.

  • Like 1

Share this post


Link to post
Share on other sites

If you think this is a bug that should be fixed by Retrospect Inc., you will have to submit it as a Support Case.  For English speakers, that is done by going here http://www.retrospect.com/en/support/contact, and filling out the form (sorry, I don't know what the equivalent addresses are for non-English speakers, but they can figure it out from their appropriate Retrospect website address).  IMHO this is quite reasonable; obliging you to fill out the form provides Retrospect Inc. with useful details about your Retrospect installation that they would otherwise have to query you for.

 

As a result, Retrospect Inc. will pay no attention to your post in this forum.  On 12 December 2016, in response to a letter I snail-mailed to Mayoff,  I received an e-mail through a Mayoff account that was signed by JG Heithcock, CEO, Retrospect, Inc. http://www.retrospect.com/en/about#exec.  In it he says "From reading your letter, I think the main issue is that you view the forums as a good place to talk to us, Retrospect, Inc. But we view the audience of the forums as restricted to our customers [my emphasis]. The one caveat we have made on that is for feature requests, largely as we would like to see if other customers also agree on the desirability and feature set for these requests."

 

That means that the only audience for "Retrospect bug reports" in this forum will be other administrators of Retrospect.  Nevertheless, by posting in this forum you are providing a useful service to us fellow administrator peasants.  Thank you.

 

Please be aware that the "description of your issue" in the Support Case form is IME limited to about 2000 characters by the Support Case software.  If you go over that limit your "description" will be broken up into a "description" plus one or more "additional notes".  The same is true for any additional notes you may later post yourself.  I suggest that, to avoid the appearance of choppiness in your Support Case, you create your case in a post in this forum and then copy it paragraph-by-paragraph to your Support Case. 

 

Note that, despite the new dialogs in the Retrospect Inc. Support Case system urging you to sign up for Annual Support and Maintenance, Mayoff has verbally assured me that you don't need to be signed up for ASM to report a bug—only to get personal assistance with coping with it.

 

If this post sounds formulaic, that's because I intend it to be.  I intend to post it in every new thread that appears in this forum, unless the OP indicates that he/she has or will open a Support Case for the bug that the thread reports.  Of course, Mayoff could take 5 minutes of his time to post a slightly-more-polite version of this post as a  "sticky thread" that will always appear at the top of the forum.  I don't intend to hold my breath until that happens (insert appropriate smiley here).

 

 

Share this post


Link to post
Share on other sites

To Follow up:

 

I disabled media set G, and backups to media set I continued, without any errors at all for a week.

I'll try switching them around and disable set I for a week and see if set G produces that error.

 

I've done some testing and it appears the backups are working fine, but I'm not 100% confidant in the system yet.

 

Rigorous testing required, 'cos 100% confidence is the whole point of the system. Sleeping at night is nice.

 

Thanks for your advice so far, and if i cant isolate and fix the problem I will report a bug, but I need to be sure there's nothing broken at this end first.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×