gbak in service mode hangs the SuperServer with 100% CPU usage [CORE1294] #1715
Comments
Modified by: @pcisarAttachment: process_list.jpg [ 10403 ] |
Modified by: @pcisarAttachment: top_list.jpg [ 10404 ] |
|
Commented by: @AlexPeshkoff Pavel, is that bug reproducible? Not necessary to mention that with trivial samples bug is not reproduced. |
Modified by: @pcisardescription: When gbak is started in service mode (se option), it "hangs" the SuperServer with 100% CPU usage and the backup is never created. It works just fine in standard mode. Attachments: => When gbak is started in service mode (se option), it "hangs" the SuperServer with 100% CPU usage and the backup is never created. It works just fine in standard mode. Attachments: The problem is not repeatable (i.e. happens randomly, so it very likely depends on SMP conditions). environment: CentOS Linux, kernel version kernel-smp-2.6.9-42.EL => CentOS 4.4 and 4.1 Linux, |
Modified by: @pcisarAttachment: top_list.jpg [ 10404 ] => |
Modified by: @pcisarAttachment: process_list.jpg [ 10403 ] => |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pcisarWorkflow: jira [ 12251 ] => Firebird [ 15594 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: @pcisar
Duplicates CORE1302
Attachments:
strace_fb2.log
strace_gbak.log
When gbak is started in service mode (se option), it "hangs" the SuperServer with 100% CPU usage and the backup is never created. It works just fine in standard mode.
Attachments:
- strace logs for Firebird server and gbak processes
- screen shots of ps and top outputs.
The problem is not repeatable (i.e. happens randomly, so it very likely depends on SMP conditions).
The text was updated successfully, but these errors were encountered: