Troubleshooting
Matières
Troubleshooting
Disk quota exceeded in your home
WARNING: exceeding the disk quota in your home ($HOME) may induce damage to configuration files
When rewriting a configuration file, a lot of utilities will remove the old file and create a new one.
The removal will get done without problem, but the writing af the new file may fail due to an exceeded quota.
a) Check your home quota with the command: quota You will, for example, get something like this: Filesystem blocks quota limit grace files quota limit grace nas24-10:/nethome/sca 226388* 200000 250000 49652days 4161 0 0 This means: - currently you are using 226388 kB. The '*' indicates you are over your quota - your quota is 200000 kB - for some time you can use up to 250000 kB
b) Find your large files and directories du -hsc ~/.[a-z]* ~/*
c) (Re)move files and directories 1. Remove whatever you do not need anymore. (this is a form of infinite compression) 2. Put whatever does not need to be in your home under your data space. (e.g. /snow /zwack ....) 3. Use /extras/$USER Move large software directories like .local, .cache, .python, etc. under /extras/$USER/ to move directory xxx : cd $HOME mv xxx /extras/$USER/. # move the directory ln -s /extras/$USER/xxx xxx # create a "soft link" in $HOME cd $HOME/xxx will still bring you to that directory but will not affect your HOME quota
Cannot open window
a) When using ssh make sure you used it either with the ' -X ' or the ' -Y ' key! ssh -Y ... b) Check your home quota with (see "Disk quota exceeded in your home" above for more info): quota If you are over quota in your home you cannot open any windows. To reduce the data in your home check point "Disk quota exceeded in your home" above.
CRCM5 problems
Error message:
"stack overflow: thread 0, max 10228KB, used 1147KB, request 37324944B"
=> unlimit your stack by setting:
ulimit -s unlimited
Other problems
Error message:
"X11 connection rejected because of wrong authentication."
You might be over your quota in your HOME.
Check with: quota -v
Error message:
"Error: Can't open display: localhost:..."
Connect with "ssh -Y ..." instead of "ssh -X ...".