SnapCreator CLI - lost connection with RC 255

togeis · ‎2014-11-11

Hi,

I am using the SnapCreator 4.1.1 CLI to start backups with crontab.

Sometimes the CLI aborts with an bash RC 255. The backup ist still running, but the CLI return rc255 which provides a wrapper script to send an error email.

Sometimes it happens after 9-10 minutes then CLI is running, and today after 2 minutes.

I user -verbose in then CLI, but there is no error message any logfile.

The CLI is called on the same host where the scServer is running in the background.

Here is the warpper output with the CLI output:

[Tue Nov 11 05:10:52 2014] WARN: SnapVault update on destination /vol/na23_gfa_HT7_d_backup/gfb is running, status [transferring]! Sleeping 1 minut

e

########## Checking SnapVault status for source relationship franap99:/vol/fn99_gfa_HT7_d_01/gfb ##########

[Tue Nov 11 05:12:04 2014] INFO: STORAGE-02110: Retrieving SnapVault status

[Tue Nov 11 05:12:04 2014] INFO: STORAGE-02111: Retrieving SnapVault status on controller [nnadep23] finished successfully.

[Tue Nov 11 05:11:59 2014] WARN: SnapVault update on destination /vol/na23_gfa_HT7_d_backup/gfb is running, status [transferring]! Sleeping 1 minut

e

---> Thats the point the CLI breaks up with RC 255 an the warpper sends an email and is ending too

## Ende der Verabeitung /home/smsapos/snapcreator_schedules/exe/backup_daily_full.sh - 2014-11-11_05-12

Debug-Log from then engine/log/<PROFILE>/

2014-11-11 05:11:59,626] DEBUG: <snapvault-secondary-relationship-status-list-iter-next>

</snapvault-secondary-relationship-status-list-iter-next>

[2014-11-11 05:11:59,626] INFO: STORAGE-02111: Retrieving SnapVault status on controller [nnadep23] finished successfully.

[2014-11-11 05:11:59,626] WARN: SnapVault update on destination /vol/na23_gfa_HT7_d_backup/gfb is running, status [transferring]! Sleeping 1 minute

----> That's the point when the CLI aborts, and the Backup is still running....

########## Checking SnapVault status for source relationship franap99:/vol/fn99_gfa_HT7_d_01/gfb ##########

[2014-11-11 05:13:06,893] INFO: STORAGE-02110: Retrieving SnapVault status

[2014-11-11 05:13:06,894] DEBUG: <snapvault-secondary-relationship-status-list-iter-start/>

[2014-11-11 05:13:06,894] DEBUG: <snapvault-secondary-relationship-status-list-iter-next>

</snapvault-secondary-relationship-status-list-iter-next>

[2014-11-11 05:13:06,894] INFO: STORAGE-02111: Retrieving SnapVault status on controller [nnadep23] finished successfully.

Is there any option to get more debug Output from the CLI ?

Regards

Tobias

spinks · ‎2014-11-11

Tobias,

You can check the server.log and the agent.log files to see if you can get additional information.

check: /path/to/scServer4.1.1/engine/logs

There you will find the engine.log and server.log files

on the Agent side check: /path/to/scAgent4.1.1/logs

There you will find the agent.log file.

You can also try to run the agent in the foreground so that you can see all messages, even the ones not logged.

video on this is on our YouTube channel: http://youtu.be/rYqzw0pP0WA

If you continue to have issues please consider opening a support case.

John

togeis · ‎2014-11-11

Hi John,

thanks for your answer.

The scAgent doesn't seems to be the problem. The CLI aborts and the backup is still running and the scAgent is called/used again, after the CLI has broken.

The scAgent logs an scServer logs are fine, then backup ends up successfully.

Tobias

togeis · ‎2015-03-02

It was as JAVA Version issue.

The scServer used JAVA 1.7 (default on host). After setting the PATH variable in the scServer Starting-Script to a JAVA 1.6u43, the CLI never looses connection to the scServer.