On 09/09/10 00:10, Frank Allan wrote:
I spoke too soon. :-[
I now get a successful AI installation with no errors, however, when I
reboot, after the loading services but before 'Configuring devices', I
get:
Error configuring interface
/sbin/ipadm create-addr -T static -a local=123.231.123.100/24 net0/v4
Seems like the svc:/network/install:default service is having issues...
this message repeats again a few lines later
The system comes up with GUI login, but I cannot login. I just get
'Authentication failed' popup.
jack/jack does not work - I tried changing the default user to
admin/admin123 (with appropriate encrypted password) and this does not
work either. root/opensolaris obviously doesn't work since root is a role.
The password string is correct in the sc_manifest in /tmp during the
installation.
inserting the encrypted password string for jack into /etc/shadow on
my running b147 system allows me to login with password 'jack' so
there appears to be an issue with either the password evaluation on
the AI image or something else in the GUI login is screwing it up. I
don't get the option to login on the command line and I can't connect
via network. Extremely secure system, but not very useful :-(
Where to from here?
Does booting single-user mode help at this point? (I don't know if
sulogin enables root to login even if its set up as a role in this mode.)
If that doesn't work, can you boot back into the install boot image but
don't do the install (by removing the 'install' flag from the boot
args), and then import the pool, mount the BE, and then inspect what's
in /var/svc/log/system-install-config:default.log to see if there were
any issues in processing the user account configuration. Also look at
/var/svc/log/network-install:default.log to see why its complaining above.
-ethan
Cheers
Frank
On 09/ 9/10 09:06 AM, Frank Allan wrote:
Jan, Etahn
I have solved my problem. It was my incomplete knowledge of XML syntax.
When I included the static network example, I removed the comment
markings above and below the the service_bundle tags.
I was not aware that the embedded manifest had to be a comment. Once
I replaced the comment tags, all is working as expected.
In regards to the default.xml in /var/ai/<port-no>, is there any
issue with modifying this to point to my internal repository instead
of pkg.opensolaris.org ?
I would like to find a way to configure the system so that each time
I create a new service it automatically uses my repository instead of
the default one, so where do I change the 'default' to make this happen?
I am on a totally non-connected network with no access to the public
internet and consequently will only ever have access to my internal
repository, so pkg.opensolaris.org will never work.
Cheers
Frank
On 09/ 8/10 09:35 PM, Frank Allan wrote:
Hi Jan
I am running b147 on my AI server, which is also the repo server,
serving b147 repository.
I created my services in /aiserver, using
# installadm create-service -n b147sparc -s
/aiimages/sol-11-dev-147-ai-sparc.iso /aiserver/b147sparc
(I think this is right syntax - I am at home at the moment, so going
from memory)
so in /aiserver I have b137sparc, b137x86, b147sparc, b147x86
I edited the default.xml in /aiserver/b147sparc/auto_install
If this is not used by the installation, then why is it there and
what is it used for?
I have the sample file, but can't find a way to include it in the
client ai_manifest which doesn't fail syntax checking, or the
correct way to reference it from the client ai_manifest.
I was using a copy of the default.xml file and attempted to replace
the embedded sc manifest with the provided static_network.xml file
but kept getting syntax errors when I ran the 'installadm
create-manifest' command.
I had previously read the Flag Day message, but even after
re-reading it I am unclear as to what needs to be removed from the
default file if I wish to use the static networking example, and how
to actually reference it without including it in the ai manifest.
That was why I asked about an example which actually includes the
static networking in the ai manifest, either as a complete
insertion, or as a reference.
I guess I am doing something stupid, but I can't seem to include it
without getting syntax errors, and I can't find the correct way to
reference it without including it, and what needs to be
removed/commented in the default if I wish to include the static
example.
I tried replacing the complete <service_bundle> ... </service_bundle>
section of the default file with the same section of the static
networking example but no joy.
What I have tried is:
installadm create-service (as above - works ok)
installadm create-client -e <MAC-address> -n <svc-name> (works ok)
I have an /aimanifests directory, with sub-directories for each
client, and in one of these I tried:
installadm create-manifest -m <edited-default-ai.xml> -n <svc-name>
-C static_network.xml (this is the part I can't get to work)
I can get the -C option to accept an xml file which just has the MAC
address specified in it, but anything else either gives a syntax
error or a message telling me this is not the right place for this
type of option.
Thanks for pointing me to the /var/ai/ directories. When I get to
work tomorrow, I will try editing the file in /var/ai... and see if
this solves some of my problems, but I still don't know the correct
way to either include or reference the static networking in the ai
manifest.
Thanks for your patience.
Cheers
Frank
On 8/09/10 18:53 , Jan Damborsky wrote:
Hi Frank,
On 09/ 8/10 09:40 AM, Frank Allan wrote:
Jan
the system is on an internal customer network and I cannot get the
files off without an extended security process.
The install log shows a lot of detail about the disk
identification and selection and ends up selecting the requested
disk (c3t2d0) and using the entire disk.
the only things in the log after that are the same three AI lines
as before - no extra info.
sc_manifest.xml is empty
That is the problem - we need to find out, why you ended up with
empty file.
I am thinking my client manifests are bad/incorrect.
I tried deleting the manifest I created for the client and just
using the defaults.
Even though default.xml in the /aiserver/<svcname> has been
modified to use my local repository instead of
pkg.opensolaris.org/release, the ai_combined_manifest.xml file
does not pick up the modifications.
Could you please elaborate more on how you configured install service
and what version of installadm(1m) tools you use on AI server ?
I am asking, since you mention you edited default.xml in
/aiserver/<svcname> directory which does not sound familiar to me,
instead it should be something like
/var/ai/<port_number>/AI_data/default.xml
I had tried creating a manifest file for the client, and this is
obviously what has caused the timezone error.
I did a boot net:dhcp using the default manifest, then edited the
ai_combined_manifest.xml to point to my local repository before I
enabled auto-installer service and the system is booting using the
default.
Note that the default manifest that was loaded onto the booting
system still referenced pkg.opensolaris.org rather than my
internal repo. Do I have to restart pkg/server after modifying
default.xml?
Nope, you do not need to restart neither pkg/server (which serves
IPS repository) neither install/server (which serves AI imagest and
manifests).
I am still unsure how i go about getting the modified default
manifest to be picked up automatically.
default.xml is located in
/var/ai/<port_number>/AI_data/default.xml, where
<port_number> for appropriate install services could be obtained by
running
# installadm list -n <install_service>
I also want to use static networking, but I am obviously missing
something, as my attempts to include the static networking
template failed with a "StartTag invalid element name message".
In this case, I might recommend not to edit default.xml directly,
but instead let installadm(1m) syntactically validate it - you
could do something like:
# cp /var/ai/<port_number>/AI_data/default.xml /tmp/
# vi /tmp/default.xml <--- edit what you need, do not change
manifest name
# installadm add -m /tmp/default.xml -n <install_service>
Are there any sample client manifests which include the static
networking option?
If you have on your AI server installadm(1m) tools based at least
on build 146,
then sample sc manifest with static network configuration is
available at
/usr/share/auto_install/sc_profiles/static_network.xml
Alternatively, it could be downloaded from
http://hub.opensolaris.org/bin/download/Project+caiman/System+Configuration+Project/staticnetwork.xml
You can either keep it as separate file and reference it in AI
manifest
or directly embed it in AI manifest.
Previously (b137) I had an ai manifest, an sc manifest and a
criteria manifest which referenced the previous two, but my
reading of the new setup seemed to imply that the sc manifest
could be included in the ai manifest, however, I can't seem to get
this to work with b147.
AI manifest as well as the way how criteria could be specified
underwent significant
changes in 147 - see following flag day for more details:
http://hub.opensolaris.org/bin/view/Project+caiman/Pre-Flag+Day+for+bug+16423
That said, SC manifest still could be either included as external
file or directly
embedded into AI manifest.
I am unsure whether I am just confused or whether there has been a
change in the way things work.
Bunch of things have changed in recent couple of builds :-)
Jan
Cheers
Frank
On 09/ 8/10 04:16 PM, Jan Damborsky wrote:
Hi Frank,
On 09/ 8/10 04:10 AM, Frank Allan wrote:
This looks like bug 4629 which was supposed to have been fixed
in March 2009.
Has it resurfaced, or is this something else?
It seems that the issue you are encountering is not related to
4629, as it is not
seen on all machines (I have successfully installed sun4u
machines with 147).
In order to be able to evaluate what's going on, could you please
rerun the
installer in debug mode ? It is enabled by passing
'install_debug' from OBP prompt:
{0} ok boot net:dhcp - install install_debug
After the installation fails, could you please log to the machine
(jack/jack)
and attach following files ?
/tmp/ai_combined_manifest.xml
/tmp/sc_manifest.xml
/tmp/install_log
Thank you,
Jan
Cheers
Frank
On 09/ 8/10 10:29 AM, Frank Allan wrote:
I am attempting to use AI with b147 to load a SPARC system
(Ultra 45, 6Gb, XVR-300, 4*250Gb disk).
The system is on an internal network with a local repository.
The default manifests have been configured to access the
internal repository.
wanboot works, the system loads the client-specific manifest,
finds the target disk, reports enough physical memory for
installation, then I get:
<AI Sep 8 00:42:07> Parsing system configuration manifest
<AI Sep 8 00:42:07> Detected the latest format of System
Configuration manifest.
<AI Sep 8 00:42:07> Setting of OM_ATTR_TIMEZONE_INFO failed
Automated Installation failed
in the property_group "other_sc_params" I have:
<propval name="timezone" type="astring" value="GMT"/>
any ideas on why I am getting this error, and any way to
resolve it?
Cheers
Frank
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
