Differenze
Queste sono le differenze tra la revisione selezionata e la versione attuale della pagina.
Entrambe le parti precedenti la revisione Revisione precedente Prossima revisione | Revisione precedente | ||
vlsi:workbook:computing:troubleshooting [18/09/2014 20:01] 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 | 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. | 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 | 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. | 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 | In case of a **power outage** you have nothing to do, just wait that the system administrator | ||
Linea 53: | Linea 65: | ||
loss of the electric power to VLSI area | 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> | <code> | ||
ping elt59xl.to.infn.it | ping elt59xl.to.infn.it | ||
+ | ping elt95wx.to.infn.it | ||
</code> | </code> | ||
Linea 140: | Linea 153: | ||
manually, as cadence is not intelligent enough on its own to understand what is happening. | 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. | + | 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. | Alternatively you can manually remove the lock files from the UNIX command line. | ||
Exit Cadence software and type the following commands in the terminal: | Exit Cadence software and type the following commands in the terminal: | ||
Linea 151: | Linea 167: | ||
\\ | \\ | ||
- | 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: | and call it in the ''~/.cshrc'' to delete all lock files at each login time: | ||
<code> | <code> | ||
- | sh ~/scratch/<tech_dir>/cdslk_clean.csh | + | linux% sh ~/scratch/<tech_dir>/cdslk_clean.csh |
</code> | </code> | ||