fbackup error Exit Code = 137

[José Rigoberto Barocio]

Hello everybody, when i try to do full backup in my system, the result is ...

Exit Code = 137

The process still run about 9 hours and still running until kill -9 %p.

I need some patch?

[Sanjay_6]

Hi Jose,

Maybe this link will help,

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062972954

The itrc doc id is KBRC00000427.

The doc says,

/quote/

A primary example of an unsupported exit code returned from fbackup is exit code 137. An exit code of 137 indicates a kill signal from the fbackup process. The signal that was caught is 137-128 = 9, i.e. kill -9. The most common cause of this exit code is full storage media (dev/rmt/0m -- tape is full). Other signal exit codes can be solved for similarly. A complete list of signals can be found in /usr/include/sys/signal.h

/EndQuote/

Hope this helps.

Regds

[bhavin asokan]

hi,

see the following links,

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=36290

http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0x8d6637f45ef7d4118fef0090279cd0f9%2C00.html&admit=716493758+1101180293634+28353475


regds,

[bhavin asokan]

hi,

use following command to get a full list of error codes

dumpmsg /usr/lib/nls/C/fbackup.cat | more

regds,

[Thierry Poels_1]

FYI:
fbackup allocates resources that are not returned to the system if it is killed in an ungraceful manner. If it is necessary to kill fbackup, send it a SIGTERM, not a SIGKILL.

regards,
Thierry.