Error: Authorization required

Errors
1

Hi All,
I am Yuji from Japan.
I tyr to get some benchmarks using GPU on cube_hex24.msh made by Dr. Park. Howenver I get some problems.
When singel calclation is going, the terminal shows how much this calclation is done. like below;

$ pyfr run -b cuda -p cube_hex24.pyfrm config.ini

Authorization required, but no authorization protocol specified
Authorization required, but no authorization protocol specified
Authorization required, but no authorization protocol specified
 100.0% [===========================================================================>] 3.00/3.00 ela: 00:02:35 rem: 00:00:00 
$

When more than 2mpi calclation are going, the terminal does not show how much this calclation is done. like below;

$mpiexec -n 2 pyfr run -b cuda cube_hex24_p2.pyfr mconfig.ini

Authorization required, but no authorization protocol specified
Authorization required, but no authorization protocol specified
$

Do you know why it occurs?
I attach my config.ini below

[backend]
precision = double
rank-allocator = linear

[backend-openmp]
;cblas-st = Enter path to local single-threaded BLAS library for OpenMP backend
;cblas-mt = Enter path to local multi-threaded BLAS library for OpenMP backend

[constants]
gamma = 1.4
mu = 0.001
Pr = 0.72

; Convergence paramters
k = 3.14159265358979323846
omega = 3.14159265358979323846
a = 3

[solver]
system = navier-stokes
order = 4
;anti-alias = flux, surf-flux

[solver-time-integrator]
scheme = rk4
controller = none
t0 = 0.0
dt = 2e-4
tstart = 0.0
tend = 3.0

[solver-interfaces]
riemann-solver = rusanov
ldg-beta = 0.5
ldg-tau = 0.1

[solver-interfaces-tri]
flux-pts = williams-shunn

[solver-interfaces-quad]
flux-pts = gauss-legendre

[solver-elements-tet]
soln-pts = shunn-ham

[solver-elements-hex]
soln-pts = gauss-legendre

;[soln-output]
;format = pyfrs-dir
;basedir = .
;basename = run-%(t).2f
;times = range(0.0, 0.1, 2)
[soln-plugin-writer]
dt-out = 0.1
basedir = .
basename = runout-{t:.2f}

[soln-ics]
f = (sin(k*(x + y + z)) + a)

rho = %(f)s
u   = 1
v   = 1
w   = 1
p   = (gamma - 1)*(%(f)s*%(f)s - 1.5*%(f)s)

[solver-source-terms]
theta = (k*(x + y + z) - omega*t)
rho  = (3.0*k - omega)*cos(%(theta)s)
rhou = (-omega + 3.0*k + 2.0*(gamma-1.0)*a*k - 1.5*k*(gamma-1.0))*cos(%(theta)s) + k*(gamma-1.0)*sin(2.0*%(theta)s)
rhov = (-omega + 3.0*k + 2.0*(gamma-1.0)*a*k - 1.5*k*(gamma-1.0))*cos(%(theta)s) + k*(gamma-1.0)*sin(2.0*%(theta)s)
rhow = (-omega + 3.0*k + 2.0*(gamma-1.0)*a*k - 1.5*k*(gamma-1.0))*cos(%(theta)s) + k*(gamma-1.0)*sin(2.0*%(theta)s)
; Euler prolbem without last term of E
E    = (6.0*k*a*gamma - 4.5*(gamma-1.0)*k - 2.0*omega*a)*cos(%(theta)s) + (3.0*gamma*k - omega)*sin(2.0*%(theta)s) + sin(%(theta)s)*(3.0*k*k*mu*gamma/Pr)

Best,
Yuji

2

In response to your second question about why the progress bar is missing from the run, this is because you are missing the -p flag.

To answer your first question, a little more information would be useful. What OS are you running on? Do you have permissions write data files to wherever you’re trying to write them?

Having a look online I suspect that you may be running as root on WSL, this seems to be a known error message in that circumstance.

3

Thank you for quick replying.

Ohh, I will add -p flag towards $mpiexec -n 2 pyfr run -b cuda -p cube_hex24_p2.pyfr mconfig.ini

I use Ubuntu2204LTS not WSL2.
Moreover the permissions are like these,

directory permission that I use for calclation in,
drwxrwxr-x 2 test test 4096 Dec 27 08:54 cuda2_cube_hex24

input files permission
-rw-rw-r-- 1 test test 3591681 Dec 27 07:45 cube_hex24.pyfrm
lrwxrwxrwx 1 test test 13 Dec 27 07:59 config.ini
out files files permission
-rw-rw-r-- 1 test test 69127605 Dec 27 08:50 runout-3.00.pyfrs
.
.
.
.
.
-rw-rw-r-- 1 test test 69127592 Dec 27 08:48 runout-0.00.pyfrs

Are these permisions not enough ?

Best,
Yuji

4

Those seem fine. I’m fairly sure this is an OS/environment problem and not an issue with PyFR.
There are a few discussions on stack overflow about this issue that you might like to checkout and see if those fix your problem. The fix that seems to have worked for some people is just turning your machine on and off again.

5

Copy.
I will turn my machine on and off. Thank you so much for your quick reaction.
I appriciate it.
Yuji

6

Can you confirm if you get the authorization related message when running another MPI related application (such as the examples which are part of the mpi4py documentation)?

Regards, Freddie.

7

Thank you for repling.
I will confirm it using by mpi4py.
Please give me some time.
Best,
Yuji

8

Dear Prof. Freddie,

I found that the GPU that I used was rental one. Since I have not had it now, I cannot confirm it.
I am sorry.