Differenze

Queste sono le differenze tra la revisione selezionata e la versione attuale della pagina.

--- vlsi:computing_troubleshooting [01/05/2013 21:14]
pacher
+++ — (versione attuale)
@@ Linea 1: / Linea 1: @@
-====== Troubleshooting ======
-[ __[[vlsi:home|Home]]__ ]
-[ __[[vlsi:workbook|VLSI Design WorkBook]]__ ]
-[ __[[vlsi:computing_main#contents|Back to index]]__ ]
-== Contents ==
-   * [[vlsi:computing_troubleshooting#introduction|Introduction]]
-   * [[vlsi:computing_troubleshooting#shutdowns_and_reboots|Shutdowns and reboots]]
-   * [[vlsi:computing_troubleshooting#power_outage|Power outage]]
-   * [[vlsi:computing_troubleshooting#available_licenses|Available licenses]]
-   * [[vlsi:computing_troubleshooting#missing_fonts|Missing fonts]]
-   * [[vlsi:computing_troubleshooting#crashes_hangs_and_freezes|Crashes, hangs and freezes]]
-   * [[vlsi:computing_troubleshooting#clean_the_environment_from_lock_files_at_startup|Clean the environment from lock files at startup]]
-   * [[vlsi:computing_troubleshooting#kill_cadence_defunct_processes|Kill Cadence defunct processes]]
-**Keywords:** missing fonts, lock files, processes
-===== Introduction =====
-In this page we provide further information and guidelines you need to know about working with
-VLSI computing resources, along with a collection of some common issues and troubles which can
-arise working with VLSI lab tools.
-===== Shutdowns and reboots =====
-Machines part of the VLSI cluster are always-on, providing a 24/7/365 service. Each machine is
-a multi-user system and different users might have jobs running on the same machine. Thus if you are
-physically working in the VLSI lab **never shutdown yourself a machine** at the end of your session work!
-Just perform a logout instead.
-Machine **reboots** migh be required in case of crashes, hangs or freezes, but always address
-your request to the VLSI system administrator before (//[[mazza@NOSPAMto.infn.it]]//, remove NOSPAM in the address).
-===== Power outage =====
-In case of a **power outage** you have nothing to do, just wait that the system administrator
-has restored the cluster.
-Se la corrente va via bisogna aspettare che il sysadmin tiri su le macchine
-loss of the electric power to VLSI area
-Always check that the server machine is reacheable with the ''ping'' command,
-<code>
-ping elt59xl.to.infn.it
-</code>
-e controllare i link simbolici in /usr, se il server e' giu' (non riesco a pingarlo)
-allora i link sono highlighted di rosso e non raggiungibili
-<code>
-ls -l /usr
-</code>
-===== Available licenses =====
-You can check the state of the licence server or the number of available licences
-if you run into trouble opening a program.
-The lmstat command can be used to track token license activity from the command line
-<code>
-lmstat [-help]
-</code>
-To view the number of available licences for each program,
-<code>
-lmstat -a
-</code>
-===== Missing fonts =====
-Users working remotely from a machine running a fresh installation of **Scientific Linux 6.x** might need some additional fonts
-required by Cadence graphical front ends. If you have administration privileges install the missing fonts using the yum package manager:
-<code>
-sudo yum install xorg-x11-font*
-# yum install xorg-x11-font*
-</code>
-===== Crashes, hangs and freezes =====
-Cadence crashes, hangs or freezes. In general, open a termional and **kill all your Cadence processes**
-using the ''kill'' command,
-<code>
-ps aux | grep <username>
-</code>
-<code>
-kill <process id>
-</code>
-For more details see
-__[[vlsi:computing_troubleshooting#kill_cadence_defunct_processes|Kill Cadence defunct processes]]__.
-Contact the VLSI system administrator (//[[mazza@NOSPAMto.infn.it]]//, remove NOSPAM in the address).
-===== Clean the environment from lock files at startup =====
-When a user opens a cell view for editing (schematic, layout, symbol, etc)
-Cadence automatically creates a temporary file called a **lock file**. The lock
-file prevents another user from opening up the same file for edit at the same time.
-When one saves and closes the cell view, the lock file is deleted, so that in the
-future it can be opened for edit again. If one is editing the inverter's layout in cadence, and for some reason cadence crashes
-or exits for some unexpected reason, the "layout.cdb.cdslck" file may not be deleted, due
-to the crash.
-When this happens, once cadence is restarted, the lock file is still in place.  This
-will make it so you cannot open the inverter's layout.  We must remove this lock file
-manually, as cadence is not intelligent enough on its own to understand what is happening.
-Exit Cadence software and type the following commands in the terminal:
-<code>
-find $HOME/ -name "*.cdslck" -exec rm {} \;
-find $HOME/ -name "*.oacache" -exec rm {} \;
-</code>
-\\
-You can also cut and paste these instructions into an executable csh script (e.g. ''~/scatch/<tech_dir>/cdslk_clean.csh'')
-and call it in the ''~/.cshrc'' to delete all lock files at each login time:
-<code>
-sh ~/scatch/<tech_dir>/cdslk_clean.csh
-</code>
-\\
-Se also
-//[[https://secure.engr.oregonstate.edu/wiki/ams/index.php/Cadence/TipsAndTricks]]//   \\
-//[[http://www.seas.gwu.edu/~vlsi/ece218/SPRING/reference/tutorial_removing_lock_files.txt]]//
-===== Kill Cadence defunct processes =====
-due to a Cadence crash
-See also //[[https://intranet.ece.cornell.edu/computing/kb_articles/kba_detail.cfm?article_id=11]]//
- Each time you logout, kill all process that you have started including "defunct" process.
-kill -9 -1
-or
-ps -ef | grep <username>
-kill -9 <process id>
-**zombie** process or **defunct** proces
-[[http://en.wikipedia.org/wiki/Zombie_process|zombie]] process
-Assicurarsi di non avere processi zombi magari dopo che cadence si pianta all'improvviso!
-Visualizzare l'elenco dei processi con ''ps'' e killare tutto cio' che riguarda Cadence:
-<code>
-ps aux | grep <username>
-</code>
-<code>
-kill <process id>
-</code>
-====== ======
-\\
-----
-Last update: [[pacher@NOSPAMto.infn.it|Luca Pacher]] - May 1, 2013
-~~NOTOC~~