Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 14570
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Running ocean jobs without starting X server

Wonyoung

Hello,

I noticed that whenever I run ocean using the -nograph option, Cadence starts a "null" X server as described in the following link. 

www.cadence.com/.../19401.aspx

I was wondering if there is any way to prevent Cadence from starting X server when running ocean. I am trying to run a bunch of ocean jobs at the same time in multiple compute nodes that do that support graphical modes. The problem is that I can't run ocean in these compute nodes because it wants to start an X server. It's very difficult for me to change these compute nodes to support graphics since these nodes are meant to run batch jobs that do not require graphics. Any help is appreciated in solving this. Thank you very much.

Regards,

Wonyoung 

Parents

  • Dear Andrew,

    Sorry about the very late reply. I was trying to solve this on my own, left the problem for a while and now struggling with it again. I'll try to explain more precisely what problem I am facing.

    I am using sub-version IC6.1.5-64b.500.7. Using 4 servers with 12 cores each, I run 48 ocean simulations simultaneously using the following command.

    ocean -nograph -log log.<sim_num> -restore <name_of_ocn_file>

    I use different log file names and .ocn file names for all 48 simulations to avoid any conflict. The problem is that for some of the 48 simulations, the ocean simulations never start and I instead get the following message.

     *WARNING* Could not open display golden.eecs.harvard.edu:80. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X80. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:81. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X81. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:82. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X82. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:83. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X83. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:84. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X84. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:85. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X85. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:86. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X86. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:87. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X87. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:88. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X88. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:89. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X89. *WARNING* Trying another display.

    *WARNING* Unable to connect to a non-graphical X Window Display server.

      

    I tried inserting a command before every simulation to remove /tmp/.X11-unix/X8* to see if that solves the problem. Doing so made the message above go away and allowed all 48 ocean simulations to start, but some of them would crash with the following message.

    \e IO Error 32 (Broken pipe) on Display "macabre.eecs.harvard.edu:80.0"
    \e Aborting due to fatal X IO error.

     

    All the crashed simulations had one thing in common - they all shared the same X display name. The following is an excerpt from one of the simulation log files.

    \o Sub version: sub-version  IC6.1.5-64b.500.7  (64-bit addresses)
    \# Host name (type): macabre.eecs.harvard.edu (x86_64)
    \# Operating system: Linux 2.6.18-308.20.1.el5 #1 SMP Tue Nov 13 10:15:12 EST 2012
    \# X display name (WxH): macabre.eecs.harvard.edu:80.0 (1024x868)
    \# Available geometry: TL(0:0) BR(1023:867)
    \# X server: RealVNC Ltd (VNC nograph server)
    \# Depth of Visual (Root): 16 (16)
    \# Number of Planes Used: 16
    \# X version: 11.0 (vendor release 3370)

    There were 5 simulations running simultaneously that had the same "X display name (WxH): macabre.eecs.harvard.edu:80.0 (1024x868)", and only one of them finished while the other 4 crashed with the log message I attached above. My guess is that different ocean simulations should not use the same X display name when running simultaneously. I was wondering if there is a way to run multiple ocean simulations simultaneously without having X display issues. Thank you very much!

    Regards,

    Wonyoung 

Reply

  • Dear Andrew,

    Sorry about the very late reply. I was trying to solve this on my own, left the problem for a while and now struggling with it again. I'll try to explain more precisely what problem I am facing.

    I am using sub-version IC6.1.5-64b.500.7. Using 4 servers with 12 cores each, I run 48 ocean simulations simultaneously using the following command.

    ocean -nograph -log log.<sim_num> -restore <name_of_ocn_file>

    I use different log file names and .ocn file names for all 48 simulations to avoid any conflict. The problem is that for some of the 48 simulations, the ocean simulations never start and I instead get the following message.

     *WARNING* Could not open display golden.eecs.harvard.edu:80. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X80. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:81. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X81. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:82. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X82. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:83. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X83. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:84. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X84. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:85. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X85. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:86. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X86. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:87. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X87. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:88. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X88. *WARNING* Trying another display.

    *WARNING* Could not open display golden.eecs.harvard.edu:89. If no X server is running for *WARNING* this display, please remove the file /tmp/.X11-unix/X89. *WARNING* Trying another display.

    *WARNING* Unable to connect to a non-graphical X Window Display server.

      

    I tried inserting a command before every simulation to remove /tmp/.X11-unix/X8* to see if that solves the problem. Doing so made the message above go away and allowed all 48 ocean simulations to start, but some of them would crash with the following message.

    \e IO Error 32 (Broken pipe) on Display "macabre.eecs.harvard.edu:80.0"
    \e Aborting due to fatal X IO error.

     

    All the crashed simulations had one thing in common - they all shared the same X display name. The following is an excerpt from one of the simulation log files.

    \o Sub version: sub-version  IC6.1.5-64b.500.7  (64-bit addresses)
    \# Host name (type): macabre.eecs.harvard.edu (x86_64)
    \# Operating system: Linux 2.6.18-308.20.1.el5 #1 SMP Tue Nov 13 10:15:12 EST 2012
    \# X display name (WxH): macabre.eecs.harvard.edu:80.0 (1024x868)
    \# Available geometry: TL(0:0) BR(1023:867)
    \# X server: RealVNC Ltd (VNC nograph server)
    \# Depth of Visual (Root): 16 (16)
    \# Number of Planes Used: 16
    \# X version: 11.0 (vendor release 3370)

    There were 5 simulations running simultaneously that had the same "X display name (WxH): macabre.eecs.harvard.edu:80.0 (1024x868)", and only one of them finished while the other 4 crashed with the log message I attached above. My guess is that different ocean simulations should not use the same X display name when running simultaneously. I was wondering if there is a way to run multiple ocean simulations simultaneously without having X display issues. Thank you very much!

    Regards,

    Wonyoung 

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.