SafeExamBrowser / seb-win-refactoring

Safe Exam Browser for Windows.
https://www.safeexambrowser.org/news_en.html
Mozilla Public License 2.0
193 stars 128 forks source link

SEB quits unexpectedly: Moodle-Test #550

Closed moehzhaw closed 1 year ago

moehzhaw commented 1 year ago

We have some issues within the following setting:

We have problems as follows: 1) Students in an exam-setting (some of them with HP Core i7 zBook ): Problem on Windows with SEB-Version 3.4.0: It is not possible to fill in the second test. (The first tests worked out well. But then with the second test, the students have access to the test but, they can't give any answers.) The students changed the device and then it worked out well. (About 5-10% of the students had this problem. The rest of the students were all fine.) At the moment, Log-Files are not available. 2) Manager (doing some review-tests with DELL Latitude 7420): Problem on Windows 10 Enterprise with SEB-Version 3.4.1: The second test crashed either a) during giving answers or b) while handing in. This results in the SEB finishing automaticly (without exit-password). It is possible to restart the exam and catch up at the point when the system crashed. Finishing the test and handing it in for a second time worked out without error. (The manager did 4 review-tests and had each problem twice...) Log-Files are send directly to dbuchel.

= Do we know these issues already? = Are these issues comparable with the discussion here? Or is it anything else? = Do we know a solution for these issues?

Best regards, Marcel

Originally posted by @moehzhaw in https://github.com/SafeExamBrowser/seb-win-refactoring/issues/522#issuecomment-1357650026

dbuechel commented 1 year ago

Thanks for your report. We'll have a look at the issue, though I can't promise that we have the time to do so before February 2023.

dbuechel commented 1 year ago

There definitely have been two abnormal issues:

Session 1

2022-11-16 17:43:12.466 [15] - WARNING: [ClientProxy] Communication channel has faulted!
2022-11-16 17:43:12.467 [15] - ERROR: Lost connection to the client application!
2022-11-16 17:43:12.468 [15] - INFO: ### ------------------------------------- Session Stop Procedure ------------------------------------- ###
2022-11-16 17:43:12.478 [15] - INFO: Instructing client to initiate shutdown procedure.
2022-11-16 17:43:12.501 [15] - ERROR: [ClientProxy] Failed to perform 'InitiateShutdown'
...
2022-11-16 17:43:27.529 [15] - ERROR: Client failed to disconnect within 15 seconds!
2022-11-16 17:43:27.532 [15] - INFO: Waiting for client process to terminate...
2022-11-16 17:43:42.535 [15] - ERROR: Client failed to terminate within 15 seconds!
2022-11-16 17:43:42.538 [15] - WARNING: Attempting to kill client process since graceful termination failed!
2022-11-16 17:43:42.541 [15] - INFO: Attempt 1/5 to kill client process with ID = 3796.
2022-11-16 17:43:42.706 [15] - INFO: Client process has terminated.

Session 2

2022-11-16 15:55:48.034 [17] - ERROR: Client application has unexpectedly terminated with exit code -532462766!
2022-11-16 15:55:48.034 [17] - INFO: ### ------------------------------------- Session Stop Procedure ------------------------------------- ###
2022-11-16 15:55:48.034 [17] - INFO: Reverting kiosk mode 'CreateNewDesktop'...
2022-11-16 15:55:48.034 [17] - INFO: [DesktopMonitor] Stopped monitoring desktop 'SafeExamBrowser' [632].
2022-11-16 15:55:48.043 [17] - INFO: Switched back to original desktop 'Default' [232].
2022-11-16 15:55:48.051 [17] - INFO: Closed new desktop 'SafeExamBrowser' [632].
2022-11-16 15:55:48.052 [17] - INFO: Finalizing service...
2022-11-16 15:55:48.053 [17] - INFO: ### --------------------------------------- Session Terminated --------------------------------------- ###

For the first session, the user appears to have attempted to switch to another user account:

2022-11-16 16:14:08.982 [01] - INFO: [SystemMonitor] User session switch detected! Reason: SessionLock
2022-11-16 16:14:08.983 [43] - WARNING: Detected user session switch!
2022-11-16 16:14:08.999 [43] - INFO: Showing lock screen...

The second session appears to have encountered a crash of the client component and / or browser engine. To be able to better understand what might be the underlying reason for both cases, we'd need the application log of the event viewer of Windows itself; there we should be able to determine the exact reason of failure.

dbuechel commented 1 year ago

@moehzhaw Were you able to retrieve the application log of the event viewer of Windows of the affected devices? I'm afraid we can't do much without the crash details they should provide.

moehzhaw commented 1 year ago

Application log of the event viewer of Windows: private message to dbuechel

dbuechel commented 1 year ago

It turns out that the underlying issue was a PDF document which had been created or manipulated with a legal password cracker utility.