This task has a deadline on 15 May 2017, 0:06:02 UTC, i.e. several hours ago. The task is running fine on my machine, but without any panic mode.
It's now running for 3h, 17% and 7h still to go.

It even stopped crunching just now, and after I stopped every other CPU-Task besides my two LHC it began running in panic mode, strange. Switching the others on again removed panic mode, but after doing it again it stuck. Is this a problem with the WU or with BOINC? I'm running 7.2.42 under Mint 17.3, Vbox is 5.0.2.Grüße vom Sänger

I'm talking about Aktiv, hohe Priorität instead of just Aktiv, and it used both, just not in time. I just hope I'll get it ready before it's removed from the database, it's now at 43% and 7:45h, 3:40h remaining.Grüße vom Sänger

I am talking about the same thing. Later versions of Boinc do not show that anymore because it tends to cause a panic reaction in the users. The task may very well be in higher priority but you can't tell it. In Windows world there is a Boinc Manager replacement called BoincTasks which still shows this information. Unfortunately it is not available for Linux.

In Windows world there is a Boinc Manager replacement called BoincTasks which still shows this information. Unfortunately it is not available for Linux.

Yes, but you can run it on a Windows machine to monitor a Linux machine. You just place the necessary files in the BOINC folder on the Linux machine.

For me (Ubuntu 16), this is what I use to monitor Linux machines on the LAN from my main Windows PC. (I assume you are familiar with “gui_rpc_auth.cfg” file, which contains the password you choose, and you place the IP address of the local Windows PC in the "remote_hosts.cfg" file).

I have included my BOINC installation instructions for the Ubuntu Software Center to show the locations; your locations may be different.

Be sure to disable firewall on the remote PC (or create an exception for it).