Welcome to iraf.net Friday, May 17 2024 @ 04:05 AM GMT


 Forum Index > Help Desk > Systems New Topic Post Reply
 Numbers instead of error messages
   
pweilbacher
 07/24/2006 09:34AM (Read 4676 times)  
++---
Junior

Status: offline


Registered: 03/07/2006
Posts: 19
In one of my IRAF installations (version 2.12.2a on Linux) all error messages appears as numbers instead of text, e.g. when querying an extension that isn't there I get:[code:1:1e69a7b3ff]> imhead image[1] l+
image[1]: 1121 image[1][/code:1:1e69a7b3ff]I found the corresponding error message using[code:1:1e69a7b3ff]> match 1121 lib$syserrmsg
1121 FXF: EOF encountered while reading FITS file[/code:1:1e69a7b3ff]but I have no idea what is wrong with this install so that it doesn't look that up automatically. Any hints?

 
Profile Email
 Quote
fitz
 07/24/2006 09:34AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
Looking at the code which formats the error message (etc$xerfmt.x), the cause of this is any of 1) a missing 'iraf' in the environment (in which case you wouldn't be able to login), 2) a missing 'lib' subdirectory of that $iraf, or 3) and unreadable 'syserrmsg' file in that lib subdirectory.You can use the command "cl> =osfn("iraf$lib/syserrmsg")' to print the host path to the file, then check that all the elements of that path are readable. Since you were able to MATCH the file to get the code string it doesn't seem likely it is a permission problem, but check anyway. I do recall that some linux systems default to a restrictive umask, so if you installed as the 'iraf' user but are running as yourself you might not see the files/paths properly.Also check your environment for values of 'iraf' and 'lib". Post a linux 'env' output if you're not sure what to look for. Hope this helps.Cheers,
-Mike

 
Profile Email
 Quote
pweilbacher
 07/24/2006 09:34AM  
++---
Junior

Status: offline


Registered: 03/07/2006
Posts: 19
OK, many thanks for that hint! I did "!ls -ld" on every part of the path in =osfn("iraf$lib/syserrmsg") and discovered that on the machine with the problem the directory above $iraf was actually set to point to a link [code:1:1b31fb7b8c]cl> show iraf
/home/peter/iraf/iraf/
cl> !ls -ld /home/peter/iraf
lrwxrwxrwx 1 peter gal 25 2005-04-11 19:30 /home/peter/iraf -> /net/hercules/iraf[/code:1:1b31fb7b8c] whereas on a working machine it wasn't. Once I changed $iraf from /home/peter/iraf/iraf/ to /net/hercules/iraf/iraf/ I got the error message in text form, which is more understandable in most cases. Smile

 
Profile Email
 Quote
   
Content generated in: 0.10 seconds
New Topic Post Reply

Normal Topic Normal Topic
Sticky Topic Sticky Topic
Locked Topic Locked Topic
New Post New Post
Sticky Topic W/ New Post Sticky Topic W/ New Post
Locked Topic W/ New Post Locked Topic W/ New Post
View Anonymous Posts 
Anonymous users can post 
Filtered HTML Allowed 
Censored Content 
dog allergies remedies cialis 20 mg chilblain remedies


Privacy Policy
Terms of Use

User Functions

Login