In our $BSE/tmp directory there are several files named:

tracea#####

where ##### is a five digit number.

The contents of this file is as such:

( 0) 0x000c4c18 create_stack_trace + 0x8c [/app/baan4/bse/bin/bshell6.1]
( 1) 0x000c4a30 log_stack_trace + 0x10 [/app/baan4/bse/bin/bshell6.1]
( 2) 0x000c4db4 crash_notification + 0x10 [/app/baan4/bse/bin/bshell6.1]
( 3) 0x000d8500 do_emergency + 0x34 [/app/baan4/bse/bin/bshell6.1]
( 4) 0x000d86a8 core_dumped + 0x28 [/app/baan4/bse/bin/bshell6.1]
( 5) 0xc020b648 _sigreturn [/usr/lib/libc.2]
( 6) 0xc01f5090 __doprnt_wide + 0x2f18 [/usr/lib/libc.2]
( 7) 0xc01f2168 _doprnt + 0x48 [/usr/lib/libc.2]
( 8) 0xc0203ac0 sprintf + 0x60 [/usr/lib/libc.2]
( 9) 0x000c442c log_start_mesg + 0x2d0 [/app/baan4/bse/bin/bshell6.1]
(10) 0x000c3f50 log_mesg + 0x3a8 [/app/baan4/bse/bin/bshell6.1]
(11) 0x0016bbf4 fd_write + 0xbc [/app/baan4/bse/bin/bshell6.1]
(12) 0x000d3444 sflush + 0x48 [/app/baan4/bse/bin/bshell6.1]
(13) 0x0009c0b4 SendShellCommand + 0xb8 [/app/baan4/bse/bin/bshell6.1]
(14) 0x0009bfd4 SsrvDisconnect + 0x54 [/app/baan4/bse/bin/bshell6.1]
(15) 0x0009b778 close_shell_server + 0x14 [/app/baan4/bse/bin/bshell6.1]
(16) 0x0003c15c stop + 0xc0 [/app/baan4/bse/bin/bshell6.1]
(17) 0xc020b648 _sigreturn [/usr/lib/libc.2]
(18) 0xc020e508 _msgrcv_sys + 0x10 [/usr/lib/libc.2]
(19) 0xc0216ab8 _msgrcv + 0xe8 [/usr/lib/libc.2]
(20) 0x000c79b8 MSltRecv + 0x128 [/app/baan4/bse/bin/bshell6.1]
(21) 0x00083710 pbx_m_recv + 0xbc [/app/baan4/bse/bin/bshell6.1]
(22) 0x0002e0ec baan_cpu + 0x494c [/app/baan4/bse/bin/bshell6.1]
(23) 0x0003ba68 main + 0xc18 [/app/baan4/bse/bin/bshell6.1]
(24) 0xc0143430 _start + 0xc0 [/usr/lib/libc.2]
(25) 0x00020e48 $START$ + 0x178 [/app/baan4/bse/bin/bshell6.1]


What causes this and what is it for?

Are you using software that starts Baan? Maybe OpenWorld or any tools created by your own. It lok likes that the bshell dumps core when this product is used. You can expect a core dump in the directory where this product is started e.g. the home directory of a user.

Hope this helps,
Dick

We do not use Openworld. I will do some checking and see. We just had an installation of a BridgeLogix product. Perhaps that could be the cause.

Thanks.

Hi there,

have you tried the fuser command to find out which process is writing to the logfile?

hth

Norbert