Differenze

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

--- vlsi:workbook:computing:troubleshooting [11/06/2014 21:45]
pacher
+++ vlsi:workbook:computing:troubleshooting [01/02/2015 02:51] (versione attuale)
pacher
@@ Linea 27: / Linea 27: @@
-===== Introduction =====
+====== Introduction ======
 In this page we provide further information and guidelines you need to know about working with
@@ Linea 33: / Linea 33: @@
 arise working with VLSI lab tools.
-===== Shutdowns and reboots =====
+====== xauth: timeout in locking authority file errors ======
+<code>
+xauth: timeout in locking authority file /users/username/.serverauth.xxx
+xauth: timeout in locking authority file /users/username/.Xauthority
+</code>
+Due to UNIX ownership and permissions on ''.Xauthority'' file.
+======= Shutdowns and reboots ======
 Machines part of the VLSI cluster are always-on, providing a 24/7/365 service. Moreover, each machine is
@@ Linea 46: / Linea 58: @@
 In that cases, save your work, close all your running applications and then logout.
-===== Power outage =====
+====== 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,
+Always check that server machines are reacheable with the ''ping'' command,
 <code>
 ping elt59xl.to.infn.it
+ping elt95wx.to.infn.it
 </code>
@@ Linea 70: / Linea 80: @@
+See also:
+[[vlsi:private:computing:cluster#reboot_order_after_power_cuts]]
 ===== Available licenses =====
@@ Linea 126: / Linea 139: @@
 Contact the VLSI system administrator (//[[mazza@NOSPAMto.infn.it]]//, remove NOSPAM in the address).
-===== Clean the environment from lock files at startup =====
+====== 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.
+file prevents another user from opening up the same file for editing 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
@@ Linea 140: / Linea 153: @@
 manually, as cadence is not intelligent enough on its own to understand what is happening.
+This can be accomplished in two ways. From the Cadence IC main window (CIW) you can open the **File => Close Data** utility and then select the cell views you want to clean up from lock files and other temporary data:
+[[http://community.cadence.com/cadence_technology_forums/f/38/t/25778]]
+\\
+Alternatively you can manually remove the lock files from the UNIX command line.
 Exit Cadence software and type the following commands in the terminal:
 <code>
-find $HOME/ -name "*.cdslck" -exec rm {} \;
+linux% find $HOME/ -name "*.cdslck" -exec rm {} \;
-find $HOME/ -name "*.oacache" -exec rm {} \;
+linux% 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'')
+You can also cut and paste these instructions into an executable csh script (e.g. ''~/scratch/<tech_dir>/cdslk_clean.csh'')
 and call it in the ''~/.cshrc'' to delete all lock files at each login time:
 <code>
-sh ~/scratch/<tech_dir>/cdslk_clean.csh
+linux% sh ~/scratch/<tech_dir>/cdslk_clean.csh
 </code>
@@ Linea 159: / Linea 178: @@
 //[[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]]//
+//[[http://www.seas.gwu.edu/~vlsi/ece218/SPRING/reference/tutorial_removing_lock_files.txt]]//   \\
+//[[http://www.edaboard.com/thread56960.html]]//
+\\
+For more information about the Cadence Locking System (CLS), please refer to the official documentation:
+//Cadence Application Infrastructure User Guide// (''caiuser.pdf'')
 ====== Kill Cadence defunct processes ======
@@ Linea 201: / Linea 226: @@
 ====== Fixing SCP/SFTP ======
-[[http://thomas-cokelaer.info/blog/2011/09/scp-does-not-work-wrong-bashrc/]]
+<code>
+sftp pacher@to01xl.to.infn.it
+Connecting to to01xl.to.infn.it...
+pacher@to01xl.to.infn.it's password:
+Received message too long 1415934836
+</code>
 <code>
-[ -z "$PS1" ] && return
+scp
+...
 </code>
+The problem is related to the local shell environment, not to
+''/etc/ssh/ssh_config'' SSH server configuration!
+[[http://thomas-cokelaer.info/blog/2011/09/scp-does-not-work-wrong-bashrc/]] \\
+[[http://ubuntuforums.org/showthread.php?t=1656869]]
+Solution: don't use ''echo'' debugs in a ''.cshrc'' or ''.bashrc'' file!
 ====== ======