Ошибка 255 returned 255

In my code I have the following to run a remote script.

ssh root@host.domain.com "sh /home/user/backup_mysql.sh"

For some reason it keeps 255’ing on me. Any ideas?

I can SSH into the box just fine (passless keys setup)

REMOTE SCRIPT:

MUSER='root' 
MPASS='123123'
MHOST="127.0.0.1"
VERBOSE=0

### Set bins path ###
GZIP=/bin/gzip
MYSQL=/usr/bin/mysql
MYSQLDUMP=/usr/bin/mysqldump
RM=/bin/rm
MKDIR=/bin/mkdir
MYSQLADMIN=/usr/bin/mysqladmin
GREP=/bin/grep

### Setup dump directory ###
BAKRSNROOT=/.snapshots/tmp

#####################################
### ----[ No Editing below ]------###
#####################################
### Default time format ###
TIME_FORMAT='%H_%M_%S%P'

### Make a backup ###
backup_mysql_rsnapshot(){
        local DBS="$($MYSQL -u $MUSER -h $MHOST -p$MPASS -Bse 'show databases')"
        local db="";
        [ ! -d $BAKRSNROOT ] && ${MKDIR} -p $BAKRSNROOT
        ${RM} -f $BAKRSNROOT/* >/dev/null 2>&1
#       [ $VERBOSE -eq 1 ] && echo "*** Dumping MySQL Database ***"
#       [ $VERBOSE -eq 1 ] && echo -n "Database> "
        for db in $DBS
        do
                local tTime=$(date +"${TIME_FORMAT}")
                local FILE="${BAKRSNROOT}/${db}.${tTime}.gz"
#               [ $VERBOSE -eq 1 ] && echo -n "$db.."
                ${MYSQLDUMP} --single-transaction -u ${MUSER} -h ${MHOST} -p${MPASS} $db | ${GZIP} -9 > $FILE
        done
#               [ $VERBOSE -eq 1 ] && echo ""
#               [ $VERBOSE -eq 1 ] && echo "*** Backup done [ files wrote to $BAKRSNROOT] ***"
}

### Die on demand with message ###
die(){
        echo "$@"
        exit 999
}

### Make sure bins exists.. else die
verify_bins(){
        [ ! -x $GZIP ] && die "File $GZIP does not exists. Make sure correct path is set in $0."
        [ ! -x $MYSQL ] && die "File $MYSQL does not exists. Make sure correct path is set in $0."
        [ ! -x $MYSQLDUMP ] && die "File $MYSQLDUMP does not exists. Make sure correct path is set in $0."
        [ ! -x $RM ] && die "File $RM does not exists. Make sure correct path is set in $0."
        [ ! -x $MKDIR ] && die "File $MKDIR does not exists. Make sure correct path is set in $0."
        [ ! -x $MYSQLADMIN ] && die "File $MYSQLADMIN does not exists. Make sure correct path is set in $0."
        [ ! -x $GREP ] && die "File $GREP does not exists. Make sure correct path is set in $0."
}

### Make sure we can connect to server ... else die
verify_mysql_connection(){
        $MYSQLADMIN  -u $MUSER -h $MHOST -p$MPASS ping | $GREP 'alive'>/dev/null
        [ $? -eq 0 ] || die "Error: Cannot connect to MySQL Server. Make sure username and password are set correctly in $0"
}

### main ####
verify_bins
verify_mysql_connection
backup_mysql_rsnapshot

 EXIT STATUS

     ssh exits with the exit status of the remote command or
     with 255 if an error occurred.

ssh: connect to host host.domain.com port 22: No route to host

ssh: connect to host HOSTNAME port 22: Connection refused

6

1

If there’s a problem with authentication or connection, such as not being able to read a password from the terminal, ssh will exit with 255 without being able to run your actual script. Verify to make sure you can run ‘true’ instead, to see if the ssh connection is established successfully.

### Die on demand with message ###
die(){
  echo "$@"
  exit 999
}

1

I was stumped by this. Once I got passed the 255 problem… I ended up with a mysterious error code 1. This is the foo to get that resolved:

 pssh -x '-tt' -h HOSTFILELIST -P "sudo yum -y install glibc"

-P means write the output out as you go and is optional. But the -x ‘-tt’ trick is what forces a psuedo tty to be allocated.

You can get a clue what the error code 1 means this if you try:

ssh AHOST "sudo yum -y install glibc"

You may see:

[slc@bastion-ci ~]$ ssh MYHOST "sudo yum -y install glibc"
sudo: sorry, you must have a tty to run sudo
[slc@bastion-ci ~]$ echo $?
1

Notice the return code for this is 1, which is what pssh is reporting to you.

I found this -x -tt trick here. Also note that turning on verbose mode (pssh —verbose) for these cases does nothing to help you.

It can very much be an ssh-agent issue.
Check whether there is an ssh-agent PID currently running with eval "$(ssh-agent -s)"

Check whether your identity is added with ssh-add -l and if not, add it with ssh-add <pathToYourRSAKey>.

Then try again your ssh command (or any other command that spawns ssh daemons, like autossh for example) that returned 255.

### Die on demand with message ###
die(){
        echo "$@"
        exit 999
}

1

SUSE Linux Enterprise Server 11 Service Pack 4 (SLES 11 SP4)

Upon right-clicking a folder in Gnome’s Nautilus file manager, choosing «Sharing Options,» selecting the «Share this folder» box and clicking the «Create Share» button in the open dialog, the following error is returned:

‘net usershare’ returned error 255:  net usershare add: cannot convert name «Everyone» to a SID. Access denied.

Since samba-client version 3.6.3-76.1, a new global option is required in smb.conf.

hostname:~ # vi /etc/samba/smb.conf

Add this option under the [global] section:

client ipc signing = auto

After the change is written, restart the samba service:

hostname:~ # rcsmb restart

Answers

• Tosten’s point is that all ConfigMgr can do (and does) is run the command-line that you tell it. The error code 255 returned is from the command-line that you gave it and is not specific to ConfigMgr in any way.

  Since the error code is specific to the exe you are running, that’s what you need to troubleshoot. A first good step is to add some logging to the command-line — once again this is specific to the command-line that you are running so we can’t tell you how
  to do that.

  Also, to properly simulate how ConfigMgr runs a program, you must run it in the System context (use psexec -s to launch a command-prompt running as System). On occasion, a poorly crafted installer makes some bad assumptions about the operating environment
  and thus fails when run as System.

  ---

  Jason | http://blog.configmgrftw.com

  • Marked as answer by

    Tuesday, March 11, 2014 12:16 AM

• • Marked as answer by
    Richard Bradley — St Catherine’s School
    Tuesday, March 11, 2014 12:16 AM

• Hi Guys,

  Thanks for letting me know about PSEXEC. I didn’t know before now how it was actually loading the installers/commands, now I have another test I an use to ensure they work before putting them into SCCM.

  I have been able to work out how to get the installer for the program I need working. I was googling InstallSield installs (as I have found out it is a InstallShield Installer) and unlike usual where I could just run the /s switch to run the installer silently
  I created a recorded install for it which gave me a setup.iss file and used that.

  It has taken over prompts and anything in the background and has fixed the install issue.

  I can almost guarantee that he installer is behaving badly but by using the recorded install and the silent flag it is running correctly and successfully installing.

  Thanks again,

  Richard

  • Marked as answer by
    Richard Bradley — St Catherine’s School
    Tuesday, March 11, 2014 12:15 AM

I recently compiled a PHP 5.2.9 binary, and I tried to execute some PHP scripts with it. I can execute some scripts without problems, but one of them halts its execution midway, exiting with no errors or warnings. The returned status code of the process is 255.

I’ve read in the manual that such status is ‘reserved’. The question is: for what?

I believe it’s got something to do with missing dependencies in the PHP executable, but I can’t be sure.

Anyone knows what does an exit code of 255 mean?

P.S. There are no errors in the PHP scripts, they run OK on other machines.

1

2

In my case that was xDebug death because of low xdebug.max_nesting_level value.