behinger

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: Broken Pipeline / Cannot write to FD#29 #38939
    behinger
    Participant

    ah sorry, we use Gnome

    in reply to: Broken Pipeline / Cannot write to FD#29 #38923
    behinger
    Participant

    Finally, when writing the support ticket I noticed I used nomachine *.7 something, instead *.9 – I updated and in that way had to restart the server.
    Now login works again, we’ll see what happens in the future.

    Cheers, Benedikt

    in reply to: Broken Pipeline / Cannot write to FD#29 #38920
    behinger
    Participant

    Thanks for the response. I will open a ticket then 🙂

    To answer your questions here:
    1) ubuntu session, but doesnt really matter, others dont work either
    2) yes, some sessions are established already and we can reconnect and only new sessions dont work
    3) nope, no updates, I try to update every few months as a server restart is typically necessary 🙂 At some point, disc space was running low, but that is fixed now. I do have the problem that the nvidia graphics driver stops working after some time, but havent found energy to investigate that. Given it is a live server, that makes such searches difficult

    in reply to: Ubuntu / gdm3 / headless crashes #30497
    behinger
    Participant

    I resolved my issues. a) I installed XFCE instead of Gnome, that resolved the issues. b) I then had troubles with virtualGL (graphics card was not found). After purging & reinstalling the nvidia drivers it works now, also in Gnome-shell.

     

    Thanks for your help!

    in reply to: Ubuntu / gdm3 / headless crashes #30397
    behinger
    Participant

    Hi!
    1. CreateDisplay is set to 0 and commented. I was writing headless, because there is no physical monitor/keyboard etc. connected (as written I do have a dedicated graphics card).

    2. No crash reports of nxnode/nxserver. If matlab/rstudio crashes I sometimes get a crash report here, if the whole session drops, I dont get one.
    Today I was looking at journalctl and found these errors:
    ——————————————————————————————————————————————
    Nov 16 12:39:02 ccs-srv-001 gnome-shell[743676]: NOTE: Not using GLX TFP!
    Nov 16 12:39:02 ccs-srv-001 org.gnome.Shell.desktop[743676]: GNOME Shell crashed with signal 11
    Nov 16 12:39:02 ccs-srv-001 org.gnome.Shell.desktop[743676]: == Stack trace for context 0x557ab880c5d0 ==
    Nov 16 12:39:02 ccs-srv-001 gnome-session[727116]: gnome-session-binary[727116]: WARNING: Application ‘org.gnome.Shell.desktop’ killed by signal 11
    Nov 16 12:39:02 ccs-srv-001 gnome-session[727116]: gnome-session-binary[727116]: WARNING: App ‘org.gnome.Shell.desktop’ respawning too quickly
    Nov 16 12:39:02 ccs-srv-001 gnome-session[727116]: gnome-session-binary[727116]: CRITICAL: We failed, but the fail whale is dead. Sorry….
    Nov 16 12:39:02 ccs-srv-001 gnome-session-binary[727116]: Unrecoverable failure in required component org.gnome.Shell.desktop
    Nov 16 12:39:02 ccs-srv-001 gnome-session-binary[727116]: WARNING: Application ‘org.gnome.Shell.desktop’ killed by signal 11
    Nov 16 12:39:02 ccs-srv-001 gnome-session-binary[727116]: WARNING: App ‘org.gnome.Shell.desktop’ respawning too quickly
    Nov 16 12:39:02 ccs-srv-001 gnome-session-binary[727116]: CRITICAL: We failed, but the fail whale is dead. Sorry….
    ——————————————————————————————————————————————

    I get the “”NOTE: Not using GLX TFP!”” error more regularly. Google told me to reinstall gnome-shell which I did (did not reboot because calculations are running though).

    I will send the log-files.

Viewing 5 posts - 1 through 5 (of 5 total)