Opened 3 years ago

Closed 15 months ago

#745 closed defect (fixed)

Hang Following Restore Session

Reported by: ibwilson Owned by: bruno
Priority: high Milestone: 3.3.0
Component: mindi Version: 3.2.2
Severity: minor Keywords:
Cc:

Description

When completing a restore session the system hangs at the following point:

Type 'less /var/log/mondorestore.log' to see the output log
Type 'exit' to reboot the PC

sh-4.2# exit
exit
trap: usage: trap [-lp] [[arg] signal_spec ...]

Note: A workaround is to type 'reboot' instead of 'exit' at the prompt.

I'm running 64-bit RHEL 6.5 Server (2.6.32-431.el6.x86_64), and I have the following items installed:

  • mindi-2.1.7-1.rhel6.x86_64
  • mindi-busybox-1.18.5-3.rhel6.x86_64
  • mondo-3.0.4-1.rhel6.x86_64

Change History (5)

comment:1 Changed 2 years ago by bruno

  • Milestone changed from 3.0.5 to 3.2.3
  • Status changed from new to assigned
  • Version changed from 3.0.4 to 3.2.0

Running with 64-bit RHEL6.6 and the following packages: mindi-3.0.0-1 mondo-3.2.0-1 mindi-busybox-1.21.1-1

When exiting a restore session, the system still hangs at the following point:

  • Type 'less /var/log/mondorestore.log' to see the output log
  • Type 'exit' to reboot the PC
  • sh-4.2# exit

The difference now is that you don't get the 'trap' error message; you get nothing at all.

There used to be a workaround in which you could type 'reboot' instead of 'exit' to reboot the PC after a restore session, now that doesn't work either.

comment:2 Changed 15 months ago by bruno

Problem seems to still occur with 3.2.2

comment:3 Changed 15 months ago by bruno

  • Component changed from mondo to mindi
  • Priority changed from normal to high
  • Severity changed from trivial to minor
  • Version changed from 3.2.0 to 3.2.2

comment:4 Changed 15 months ago by bruno

Make tests again with code from [2888]

Make tests with Alt-Sysrq B

comment:5 Changed 15 months ago by bruno

  • Resolution set to fixed
  • Status changed from assigned to closed

Fixed with rev [3593]. Will be in 3.2.2

Note: See TracTickets for help on using tickets.