Running Cadence in the background of the server and successfully reconnect it after network stops

Hi Mingqiang,

This rather depends on how you are connecting to this graphical session. If you are just doing a remote X display, then this will indeed happen with any graphical program. If you are using something like VNC, Exceed Turbo X, NoMachine NX, or various others then you can probably disconnect the session.

There was an issue recently with IC6.1.8/ICADVM20.1 with Exceed on Demand (old tool from OpenText, replaced by Exceed on Demand) due to OpenGL and a bug in Exceed on Demand - covered in When using OpenText Exceed on Demand (EoD), Virtuoso 18.1/6.1.8 ISR9 will crash when EoD is Suspended. However, you're using a very old IC version, so that's not going to be it.

I don't know how you're connecting to this X server - you'll need to explain how you're running the tools so that we can advise you appropriately.

Andrew.

Hi Mr. Andrew,

Thank you very much for helping me again!

The way of connection is the following:

1. add my username to my university server that installs Cadence.

2: On MobaXTerm, accessing the server after logging in.

3: After logging in, using the command:

cd nfshome,

cd CadenceLab (This is the directory create myself)

pdk gpdk

cadence gpdk18

Then the Cadence graphical interface is displayed.

Thank you very much!

Mingqiang

Hi Mr. Andrew,

Here is an update.

As you mentioned the remote X connection does not support this reattachment.

I tried to access the server using ssh -Y server_name

Then use the command below to access to Cadence.

cd nfshome,

cd CadenceLab 

pdk gpdk

cadence gpdk18

However, after detach the session, I found an interesting thing: the GUI was still open and I cannot exit the server from the terminal normally.

When I closed the entire server and connects to the detached session again, I got exactly the same error as before.

So probably there are some other reasons behind that?

Could you please kindly explain a bit more?

Thank you!

Mingqiang

Hi Mingqiang,

I had a look earlier at MobaXTerm - this is running an X server on your Windows machine by the looks of things (I wasn't familiar with this tool) and so regardless of whether you start virtuoso in an Xterm launched from that tool, or use ssh to connect remotely and uses X forwarding, the connection to the application relies on the server being accessible. This cannot do anything other than kill the session when you close the server, because there's nothing for the X (graphics) events to be channeled to.

The only solution is to use some kind of solution which runs a virtual X server on the remote machine and displays to your end via some protocol that allows disconnection. There are numerous solutions for this, including VNC (various flavours), NoMachine NX, Exceed TurboX, and so on. VNC is pretty easy to install and use - you simply run a "vncserver" on the remote end and then use a VNC viewer to connect from your Windows machine to the virtual server on the remote end. Since the X server stays active, nothing is lost when you disconnect. There are numerous flavours (both free and commercial) of VNC (a google search for VNC would find www.realvnc.com and www.tightvnc.com as common variants), but other solutions may be better for you.

Regards,

Andrew.

Hi Mingqiang,

I had a look earlier at MobaXTerm - this is running an X server on your Windows machine by the looks of things (I wasn't familiar with this tool) and so regardless of whether you start virtuoso in an Xterm launched from that tool, or use ssh to connect remotely and uses X forwarding, the connection to the application relies on the server being accessible. This cannot do anything other than kill the session when you close the server, because there's nothing for the X (graphics) events to be channeled to.

The only solution is to use some kind of solution which runs a virtual X server on the remote machine and displays to your end via some protocol that allows disconnection. There are numerous solutions for this, including VNC (various flavours), NoMachine NX, Exceed TurboX, and so on. VNC is pretty easy to install and use - you simply run a "vncserver" on the remote end and then use a VNC viewer to connect from your Windows machine to the virtual server on the remote end. Since the X server stays active, nothing is lost when you disconnect. There are numerous flavours (both free and commercial) of VNC (a google search for VNC would find www.realvnc.com and www.tightvnc.com as common variants), but other solutions may be better for you.

Regards,

Andrew.