Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: SLES 12 Failed to start X Display Manager.

Hybrid View

  1. #1
    Join Date
    Nov 2014
    Location
    Pleasant Valley, New York 12569
    Posts
    167

    SLES 12 Failed to start X Display Manager.

    Fresh install.
    display-manager.service - X Display Manager
    Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled)
    Active: failed (Result: exit-code) since Fri 2014-11-28 08:18:44 EST; 39min ago
    Process: 1594 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=6)

    Nov 28 08:18:44 linux-rsvc systemd[1]: Starting X Display Manager...
    Nov 28 08:18:44 linux-rsvc display-manager[1594]: /etc/vconsole.conf available
    Nov 28 08:18:44 linux-rsvc display-manager[1594]: KEYMAP: us
    Nov 28 08:18:44 linux-rsvc display-manager[1594]: Command: localectl set-keymap us
    Nov 28 08:18:44 linux-rsvc display-manager[1594]: Starting service gdm..unused
    Nov 28 08:18:44 linux-rsvc systemd[1]: display-manager.service: control process exited, code=exited status=6
    Nov 28 08:18:44 linux-rsvc systemd[1]: Failed to start X Display Manager.
    Nov 28 08:18:44 linux-rsvc systemd[1]: Unit display-manager.service entered failed state.

  2. #2

    Re: SLES 12 Failed to start X Display Manager.

    Mike,

    I am also running SLES 12 on System z (base install with no maintenance) but I don't have a major problem with xwindows. I was able to launch the xclock program after starting Xming on my PC. I checked the output of 'ps efH' and there aren't many entries containing 'x' and none with 'disp'. I found that I can't launch firefox. I simply get 'Killed' back a few seconds after trying to launch it.

    Will xclock launch on your PC? Maybe the display-manager daemon doesn't need to be running in SLES 12. IDK.

    I went to yast | System | Services Manager and Enabled then Started 'display-manager'. When I issued the Start the display showed that it was Enabled and Active. I selected Show Details and the pop-up appeared
    Code:
    display-manager.service - X Display Manager 
       Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled)
       Active: inactive (dead)
    I clicked OK to save the configuration and 'ps -efH' still shows nothing. I then reentered Services Manager in yast and display-manager is Inactive.

    Harley

  3. #3
    Join Date
    Nov 2014
    Location
    Pleasant Valley, New York 12569
    Posts
    167

    Re: SLES 12 Failed to start X Display Manager.

    Hello Harley, I apologize for not replying but I did not have anything to add. I am a new to Linux environment and did not understand what you were doing with the xclock program. I also posted in the boot install forum with out any response that would assist me with debugging this error. Have you made any progress. Any suggestions to gather diagnostic information. Any information about how the display manager process initialization is suppose to work that may determine where it went wrong?

  4. Re: SLES 12 Failed to start X Display Manager.

    Hi mikenash,
    Quote Originally Posted by mikenash View Post
    Hello Harley, I apologize for not replying but I did not have anything to add. I am a new to Linux environment and did not understand what you were doing with the xclock program. I also posted in the boot install forum with out any response that would assist me with debugging this error. Have you made any progress. Any suggestions to gather diagnostic information. Any information about how the display manager process initialization is suppose to work that may determine where it went wrong?
    I'd suggest to have a look into /var/log/Xorg.0.log (or whichever log file relates to your X-server instance - use "ls -lrt /var/log" to receive a file listing with the most recently updated log files at the end of the list). That's the log file of the X server, which usually lists errors via entries marked "EE".

    Regards,
    Jens
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

  5. #5
    Join Date
    Nov 2014
    Location
    Pleasant Valley, New York 12569
    Posts
    167

    Re: SLES 12 Failed to start X Display Manager.

    Quote Originally Posted by jmozdzen View Post
    Hi mikenash,


    I'd suggest to have a look into /var/log/Xorg.0.log (or whichever log file relates to your X-server instance - use "ls -lrt /var/log" to receive a file listing with the most recently updated log files at the end of the list). That's the log file of the X server, which usually lists errors via entries marked "EE".

    Regards,
    Jens
    Hello Jens, thank you for your response. I do not have any Xorg log files in this directory. Is there a configuration file to turn logging/debugging on? Are there items to check with the initialization of the X display manager. This is a fresh install with YAST but could I have missed checking off something?

  6. Re: SLES 12 Failed to start X Display Manager.

    Hi mikenash,
    Quote Originally Posted by mikenash View Post
    Hello Jens, thank you for your response. I do not have any Xorg log files in this directory. Is there a configuration file to turn logging/debugging on? Are there items to check with the initialization of the X display manager. This is a fresh install with YAST but could I have missed checking off something?
    I have to admit that I have yet to lay my hands on SLES12 - there's a chance that the file is located elsewhere or named differently. Maybe someone else with SLES12 hands-on experience could confirm this, please?

    My assumption is that the desiplay manager failed to start an X server, and was after the X server's error messages. As there might be no X server log file, it might be a failure even before that. Maybe the info from https://help.gnome.org/admin/gdm/sta...ooting.html.en helps debugging this? (It says that gdm error messages go to syslog, which will store those in /var/log/messages by default.)

    Regrds,
    Jens
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

  7. #7
    Join Date
    Nov 2014
    Location
    Pleasant Valley, New York 12569
    Posts
    167

    Re: SLES 12 Failed to start X Display Manager.

    Hello Jens, thank you for your reply. I do not have any X server log messages. I found the /etc/gdm/custom.conf file. I add eEnable=TRUE under [DEBUG]. All other entries are empty. I then rebooted the system and still nothing. I went to the documentation that you pointed to. As I was reviewing I find that there is not /etc/gdm/autostart directory. I then tried starting xdm and display-manager from within yast and received the same error messages. The gdm service was not listed. Next was to start gdm manually. It was not in /sbin/gdm but I did find it in /usr/sbin/gdm. I then received several pages of messages on the console and then the console stall where I had to cntl-c to get out. Also found log files in /var/log/gdm. Most were of the format :0.log... There was one unreadable file called ystemd[1]: Starting X Display Manager... Probably when the terminal hung. I am not sure how to append a file but within the several pages of output I find one common error.
    <7>GdmServer: Opening logfile for server /var/log/gdm/:0.log
    Failed to execute child process "/usr/bin/X" (No such file or directory)
    <5>Could not start the X server (your graphical environment) due to an internal error. Please contact your system administrator or check your syslog to diagnose. In the meantime this display will be disabled. Please restart GDM when the problem is corrected. So I think that missing the autostart directory the configuration was never performed? This created the missing /usr/bin/X file or directory?

  8. Re: SLES 12 Failed to start X Display Manager.

    Hi Mike,
    Quote Originally Posted by mikenash View Post
    [...] I do not have any X server log messages.
    Failed to execute child process "/usr/bin/X" (No such file or directory)
    [...]
    So I think that missing the autostart directory the configuration was never performed? This created the missing /usr/bin/X file or directory?
    now this explains the missing log file from the X server... *there is no X server*

    Going back through this thread, I noticed this is on System Z - as far as I know there is no X server on that type of Linux systems, instead you need to run that on your local machine (PC, X Station or similar). So the question is, why does your system try to start an X server at all?

    As you are new to Linux, here's some background informartion:

    - the X Server is a piece of software that provides facilities to display graphical content and to interact with HIDs (human interface devices, like mouse, keyboard and alike). This software runs on the machine that has graphics hardware, i.e. a PC... but not on System Z, as far as I can tell.

    - the X display manager (xdm) is a piece of software that interfaces between the X server and the (Linux) system. Most notably it will present the "login screen" on an X server (not to be confused with the login on non-graphical terminals, where no xdm is involved). Xdm *can* be used to start X servers, which is a typical setup on Linux systems with graphics hardware (i.e. workstations and PCs).

    - X programs (like the "xclock" program mentioned by Harley (x0500hl)) run on i.e. a Linux system (your System Z) and use an X Server to provide their graphical output. Hence Harley's mention of xclock was merely that of some simple test program, to prove the functionality of the X Server connection.

    Unfortunately, my "big machines" experience ended more than 15 years ago, prior to Linux on System Z times - rather than issuing nonsense configuration recommendations here, I rather offer to ask for someone else to help out.

    Are you eligible for SUSE support? In that case you might consider opening a "service request" with SuSE.

    Regards,
    Jens
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

  9. Re: SLES 12 Failed to start X Display Manager.

    Hi mikenash

    Does the system have a graphics adapter as in your sitting in front of
    the system with a keyboard, monitor etc?

    If so, what does the following command show?
    Code:
    lspci
    Else if your using remote access, then how are you accessing the system?

    --
    Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
    SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


  10. #10
    Join Date
    Nov 2014
    Location
    Pleasant Valley, New York 12569
    Posts
    167

    Re: SLES 12 Failed to start X Display Manager.

    The command lspci does nothing on the putty session. I connect to the server using putty, using a PCOMM session to log onto the 3270 console and VNC. Since this is a new install I was reviewing /var/log/messages file and noticed the Failed to start X Display Manager error after the display manager started the gdm service.
    Jan 15 14:35:24 linux234 display-manager[663]: Starting service gdm..unused
    Jan 15 14:35:24 linux234 systemd[1]: Failed to start X Display Manager.
    The reason I was reviewing the /var/log/messages file was because I was working with the VNC server. I was unable to start a second session and I made changes to the /etc/xinetd.d/vnc file to allow a second session. This worked but the vnc sessions did not logout and remain running. This behavior was the same before I made any changes. I found the display manager failure to start and started there. This message was always there. I can do another install and it will be there. So, starting gdm is something Suse does and nothing I initiated. Where would this be initiated from during the boot process?

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •