- This topic has 3 replies, 2 voices, and was last updated 6 years ago by
.
-
Posts
-
I’m trying to use NoMachine 6.2.4-1.x86_64 to connect to a fedora 27.
On node.cfg i’ve hardcoded “DefaultDesktopCommand “/usr/bin/startxfce4” (even if xfce is the default DE), when i try to connect i get the followin error:
abrt-notification[3949]: Process 25004 (nxnode.bin) crashed in CRYPTO_free()and a lot of coredump like this:
systemd-coredump[3879]: Process 3855 (nxnode.bin) of user 949008323 dumped core.
Stack trace of thread 3855:
#0 0x00007f3232199750 raise (libc.so.6)
#1 0x00007f323219ad31 abort (libc.so.6)
#2 0x00007f32321dbff7 __libc_message (libc.so.6)
#3 0x00007f32321e22fa malloc_printerr (libc.so.6)
#4 0x00007f32321e3e3c _int_free (libc.so.6)
#5 0x00007f322e374b1d CRYPTO_free (libcrypto.so)
#6 0x00007f32232ff634 krb5int_aes_encrypt (libk5crypto.so.3)
#7 0x00007f3223304334 krb5int_derive_random (libk5crypto.so.3)
#8 0x00007f32233044ac krb5int_derive_keyblock (libk5crypto.so.3)
#9 0x00007f322330464b krb5int_derive_key (libk5crypto.so.3)
#10 0x00007f3223309f8c krb5int_dk_prf (libk5crypto.so.3)
#11 0x00007f3223309c32 krb5_c_prf (libk5crypto.so.3)
#12 0x00007f3223301244 krb5_c_prfplus (libk5crypto.so.3)
#13 0x00007f322330166d krb5_c_fx_cf2_simple (libk5crypto.so.3)
#14 0x00007f322355e570 krb5int_fast_tgs_armor (libkrb5.so.3)
#15 0x00007f322357f525 k5_make_tgs_req (libkrb5.so.3)
#16 0x00007f32235608fe krb5_get_cred_via_tkt_ext (libkrb5.so.3)
#17 0x00007f3223560a8b krb5_get_cred_via_tkt (libkrb5.so.3)
#18 0x00007f3223584285 get_new_creds (libkrb5.so.3)
#19 0x00007f322358447e get_valrenewed_creds (libkrb5.so.3)
#20 0x00007f32331e9fce NodeRenewKerberosTicket (libnxhn.so)
#21 0x00007f32331ea939 XS_libnxhn_NXRenewKerberosTicket (libnxhn.so)
#22 0x00007f32336c1bab Perl_pp_entersub (libperl.so)
#23 0x00007f32336ba360 Perl_runops_standard (libperl.so)
#24 0x00007f323366cc1c perl_run (libperl.so)
#25 0x0000000000406752 main (nxnode.bin)
#26 0x00007f3232185fea __libc_start_main (libc.so.6)
#27 0x0000000000405f7a n/a (nxnode.bin)on nxerror.log:
Info: Handler started with pid 26257 on Wed Oct 10 12:37:03 2018.
Info: Handling connection from 10.168.1.140 port 57988 on Wed Oct 10 12:37:03 2018.
RetrieveKerberosTicket: ERROR! Failed to readkerberos principal.
RetrieveKerberosTicket: Kerberos error is -1765328189.
nxexecRemoveKerberosTicket: ERROR! Invalid ticket.
/bin/xauth: file .Xauthority does not exist
free(): invalid pointer
/bin/xauth: file .Xauthority does not exist
free(): invalid pointer
/bin/xauth: file .Xauthority does not exist
/bin/xauth: file .Xauthority does not exist
free(): invalid pointer
/bin/xauth: file .Xauthority does not existon nxserver.log:
2018-10-10 12:50:40 554.996 979 NXSERVER WARNING! Process '/usr/NX/bin/nxexec --node --user user.name --priority realtime --mode 0 --pid 17' with pid '11726/11726' finished with exit code 6 after 0,710 seconds.
2018-10-10 12:50:40 555.210 979 NXSERVER WARNING! 34368EA57308D1BC0852F2695BDA6489 nxnode died with exit code 6.
2018-10-10 12:50:40 555.349 979 NXSERVER WARNING! Display not defined, drop start node cleaner.
2018-10-10 12:50:40 584.338 979 NXSERVER WARNING! Session 34368EA57308D1BC0852F2695BDA6489 crashed on display 0.
2018-10-10 12:50:41 291.502 979 NXSERVER WARNING! Process '/usr/NX/bin/nxexec --node --user user.name --priority realtime --mode 0 --pid 17' with pid '11794/11794' finished with exit code 6 after 0,699 seconds.I’ve already tried disabling UDP.
We are using SSSD for central authentication (that uses kerberos) to our Active Directory server.
How can I solve it?
Thank you,
Regards
There’s a Trouble Report open for this bug, https://www.nomachine.com/TR07P08710, and its fix will be available in the next release which is planned for this week. Keep your eyes on our news channel or sign up to receive notification of the patch with the ‘notify me’ utility you can see on the web page of the TR.
A temporary workaround we found was to download the krb5-workstation package from:
Version : 1.15.2
Release : 9.fc27to:
Version : 1.15.2
Release : 2.fc27
This topic was marked as solved, you can't post.