Operating System - HP-UX
1838196 Members
3912 Online
110125 Solutions
New Discussion

make_recovery -A executes with warnings and errors

 
Marcin Wicinski
Trusted Contributor

make_recovery -A executes with warnings and errors

Hi,
HP-UX 10.20
make_recovery -A executes but produces following warnings and errors:

WARNING: Invalid value defined for the keyword "tag", at line 28305.Valid values for this keyword are: Tag strings containing a subset of ASCII characters. A tag string requires one or more characters from "A"-"Z", "a"-"z", "0"-"9", including the first character. No white space characters are allowed. The directory path character "/" is not allowed. The following SDU and shell metacharacters are not allowed:

. , : # ; & ( ) { } | < > " ` '
The maximum length of a tag string is 16 characters.

ERROR: Incomplete definition for the bundle "?", beginning at line 28304. The following attributes are not defined: tag the identifier (short name) for the bundle. The attribute(s) must be defined before the parsing can continue.

ERROR: Invalid definition for the bundle "?", beginning at line 28304. Details described above. The bundle has been marked as corrupt."

Any clues ?
Thanks in advance.
Marcin Wicinski
2 REPLIES 2
eran maor
Honored Contributor

Re: make_recovery -A executes with warnings and errors

Hi

i have to say that i have never seem this eror in ignite but few thing that i will check .

1. check if the PAX patch is install and config

2. i will check the SD to see if there is a problem , see also that the ignite was install
and config ( with swlist -l fileset -a state )

3. i will check the files in /var/adm/sw
swinstall.log
swagentd.log
to see if there is problem .

from what i seatch in k-maine i can see all this eror with installing software .

i will try to find more info .
love computers
Marcin Wicinski
Trusted Contributor

Re: make_recovery -A executes with warnings and errors

Thank you Eran !
I think I've found the cause: swlist gives the same error, so the problem lays on the SD side. I think that SD database has been corrupted during last swinstall session.
Regards,
Marcin Wicinski