RALUS Ver.12.1364 - Crash on SLES 10 SP1

Hi !
If someone can tell me why my RALUS AGENT crash on my SLES 10 SP1 server. I don't understant why a product like BE12 + Ralus Agent is so cheap. Can't believe !!! Now l'm looking for HP Data Proctector or IBM Tivoli Storage Manager if no want at Symantec can help me with this issue. I'm very fed up.

If someone can take a lot on this short log file, i just paste the lastest line before the agent crashed down.

I put few lines in BOLD ... Who need to be analyse.

Any help will be appreciated.

Log File :

b456eba0 Tue Jul 1 17:34:50 2008 : ====> VX_OpenObj returning 0
b456eba0 Tue Jul 1 17:34:53 2008 : ReadObject: Beginning of EA cur_stream_len 240
b456eba0 Tue Jul 1 17:34:53 2008 : ReadObject: Beginning of EA cur_stream_len 240
b456eba0 Tue Jul 1 17:34:53 2008 : VX_SetupWorkPath: dss_cur_dir is not valid
b456eba0 Tue Jul 1 17:34:53 2008 : VX_SetupWorkPath: req size is 141
b456eba0 Tue Jul 1 17:34:53 2008 : VX_SetupWorkPath: req size after strsize(sname) is 218
b456eba0 Tue Jul 1 17:34:53 2008 : VX_SetupWorkPath: path is /. copying cur dir and sname
b456eba0 Tue Jul 1 17:34:53 2008 : VX_SetupWorkPath: path with cur dir is /data/Users/Julie/music
b456eba0 Tue Jul 1 17:34:53 2008 : VX_SetupWorkPath: path with cur dir & sname is /data/Users/Julie/music/Megadeth & Nine Inch Nails - Symphony Of Destruction (industrial remix).mp3
b456eba0 Tue Jul 1 17:34:53 2008 : vx_stat_by_name: Getting stat of /data/Users/Julie/music/Megadeth & Nine Inch Nails - Symphony Of Destruction (industrial remix).mp3
b456eba0 Tue Jul 1 17:34:53 2008 : Versioned file dblk osinfo, os_spec_size=72
b456eba0 Tue Jul 1 17:34:53 2008 : Unix_SetInfo: file (Megadeth & Nine Inch Nails - Symphony Of Destruction (industrial remix).mp3), native (NULL)-(0) setting uid=0 gid=0 type=1 mode(inp)=33188, mode(out)=33188
b456eba0 Tue Jul 1 17:34:53 2008 : ====> VX_FindClose
b456eba0 Tue Jul 1 17:34:53 2008 : ====> VX_CloseDir
*** glibc detected *** ./beremote: double free or corruption (!prev): 0x0818d178 ***
======= Backtrace: =========
/lib/libc.so.6[0xb69f2851]
/lib/libc.so.6(__libc_free+0x84)[0xb69f3eb4]
/opt/VRTSralus/bin/libbedsvx.so(_Z12VX_free_hdirPP11HDIR_STRUCT+0x67)[0xb6d7e89f]
/opt/VRTSralus/bin/libbedsvx.so(_Z12VX_FindCloseP16FSYS_HAND_STRUCTP4DBLK+0x4a)[0xb6d7fe2e]
/opt/VRTSralus/bin/libndmp_loops.so(_ZN27SpecialObjectsBufferVisitorI11BaseMatcherEclEv+0x702)[0xb6cae30e]
/opt/VRTSralus/bin/libndmp_loops.so(_ZN14BackupDirectorI11BaseMatcher7FsActorE16PerformCDBBackupEv+0x160)[0xb6cab22c]
/opt/VRTSralus/bin/libndmp_loops.so(_ZN14BackupDirectorI11BaseMatcher7FsActorEclEv+0x3cf)[0xb6ca8eb3]
/opt/VRTSralus/bin/libndmp_loops.so(_Z12LP_BackupDLEP3BSDP6LP_ENVtPvP16HANDLER_RESPONSE+0x56f)[0xb6ca7c6f]
/opt/VRTSralus/bin/libndmp_loops.so(_Z11LP_DoBackupP17NdmpdModuleParams+0x86d)[0xb6cba289]
./beremote[0x8064592]
./beremote[0x80579df]
/opt/VRTSralus/bin/libndmpcomm.so[0xb6c6339c]
/opt/VRTSralus/bin/libndmpcomm.so(_Z19ndmpProcessRequestsPv+0x30)[0xb6c62784]
./beremote[0x8053d25]
./beremote[0x806b13a]
./beremote[0x8053c4b]
/opt/VRTSralus/bin/libvxACE.so.3(_ZN18ACE_Thread_Adapter8invoke_iEv+0x52)[0xb7e6a84e]
/opt/VRTSralus/bin/libvxACE.so.3(_ZN18ACE_Thread_Adapter6invokeEv+0x61)[0xb7e6a7b9]
/opt/VRTSralus/bin/libvxACE.so.3(ace_thread_adapter+0xe)[0xb7e33b86]
/lib/libpthread.so.0[0xb71e82ab]
/lib/libc.so.6(__clone+0x5e)[0xb6a4d58e]
======= Memory map: ========
08048000-08082000 r-xp 00000000 08:02 218485 /opt/VRTSralus/bin/beremote
08082000-08085000 rw-p 00039000 08:02 218485 /opt/VRTSralus/bin/beremote
08085000-08257000 rw-p 08085000 00:00 0 [heap]
b3547000-b3548000 ---p b3547000 00:00 0
b3548000-b3d48000 rwxp b3548000 00:00 0
b3d48000-b3d4f000 r-xp 00000000 08:02 89437 /opt/VRTSvxms/lib/map/librawp.so
b3d4f000-b3d50000 rw-p 00007000 08:02 89437 /opt/VRTSvxms/lib/map/librawp.so
b3d50000-b3d5d000 r-xp 00000000 08:02 89434 /opt/VRTSvxms/lib/map/libext2fs.so
b3d5d000-b3d5e000 rw-p 0000c000 08:02 89434 /opt/VRTSvxms/lib/map/libext2fs.so
b3d5e000-b3d6d000 r-xp 00000000 08:02 89435 /opt/VRTSvxms/lib/map/libgfsp.so
b3d6d000-b3d6e000 rw-p 0000e000 08:02 89435 /opt/VRTSvxms/lib/map/libgfsp.so
b3d6e000-b3d6f000 ---p b3d6e000 00:00 0
b3d6f000-b456f000 rwxp b3d6f000 00:00 0
b456f000-b45a4000 r--s 00000000 08:02 68178 /var/run/nscd/dbcOSDA9 (deleted)
b45a4000-b45a5000 ---p b45a4000 00:00 0
b45a5000-b4da5000 rwxp b45a5000 00:00 0
b4da5000-b4da6000 ---p b4da5000 00:00 0
b4da6000-b55a6000 rwxp b4da6000 00:00 0
b55a6000-b55a7000 ---p b55a6000 00:00 0
b55a7000-b5da7000 rwxp b55a7000 00:00 0
b5da7000-b5dc0000 r-xp 00Aborted
2 Replies

Re: RALUS Ver.12.1364 - Crash on SLES 10 SP1

Hi all,

Past the all dawn night on this issue !!! Bascally, RALUS AGENT 12.1364 + HOTFIX are not able to backup files with a path more long then 255 charaters !!! This is a really bad thing !!!

 

I have some path with "french caracters like é or ô" and seems to have the same problem. I started BEREMOTE ./beremote --log-console to see why the RALUS AGENT crash all the time.

 

The symptom : RALUS AGENT crash ! (see below) at least passing over the files will be better.

 

Hope, they will fix this issue soon. I can't believe a version like BE12 still have this kind of problem. Smiley Sad

Highlighted

Re: RALUS Ver.12.1364 - Crash on SLES 10 SP1

Adaris,

 

could you post the long directory paths. (ls –Rasl >longpaths.log)

 

Also does the RALUS cause a segmentation fault even when you backup just a single directory with long paths? Have you tried running a backup of just directories without long paths and paths without the french characters?

 

I would need to research on this. Maybe I could create a directory structure with long paths.

 

Also a coredump creation would help.

 

. How to Enable Core File Generation on a Linux Operating System
http://support.veritas.com/docs/290695 

 

* Set the following env vars before you start RALUS in debug mode. Please start RALUS in the console mode (./beremote --log-console )

 

# export _VRTS_ALLOW_SIGSEGV_DFL_ACTION=1 # export _VRTS_ALLOW_SIGINT_DFL_ACTION=1 # ulimit –c unlimited 

 

If the coredump is written, run an analysis in GDB by running the following commands and post it here:

bt
info threads
info stack
info registers
info target
thread apply all info stack

 

I can conitnue to try and assist you with this, but it may reach a point where the best solution will be to call into Technical Support. And if it turns out to be a product defect you get your money refunded for the support incident.