problem with ag_diag_comm output

kjamsheed · Post by **kjamsheed** » 09 May 2010 12:43

Till last week the out put of ag_diag_comm was normal and now its throwing the below output

# ./ag_diag_comm

This procedure runs for about 30 seconds. Please wait
grep: /data/CONFIG.dat: No such file or directory
./ag_diag_comm: line 47: sharch: command not found
./ag_diag_comm: line 55: [: too many arguments
./ag_diag_comm: line 60: [: =: unary operator expected
./ag_diag_comm: line 65: [: =: unary operator expected
./ag_diag_comm: line 70: [: too many arguments
./ag_diag_comm: line 75: [: =: unary operator expected
./ag_diag_comm: line 80: [: =: unary operator expected
./ag_diag_comm: line 85: [: =: unary operator expected
./ag_diag_comm: line 90: [: too many arguments
./ag_diag_comm: line 95: [: =: unary operator expected
./ag_diag_comm: line 100: [: =: unary operator expected
./ag_diag_comm: line 105: [: =: unary operator expected
./ag_diag_comm: line 116: [: =: unary operator expected

Unsupported architecture

#

Any suggestions?

nakul · Post by **nakul** » 09 May 2010 2:06

Hi ,

please check the file CONFIG.dat present or not also its not corrupted, let me know on the same.

baralem · Post by **baralem** » 10 May 2010 2:28

It looks like variable $CONTROL isn't set for the user.
Check if you can find this file: $CONTROLM/data/CONFIG.dat

Here it looks like CM is looking for CONFIG.dat in /data directory:
grep: /data/CONFIG.dat: No such file or directory

regards.
martin

nakul · Post by **nakul** » 16 May 2010 11:13

i haven't noticed that jamsheed hope its clear now