Re: Unable to boot Solaris 10 after adding recommended patches
- From: "extraspecialbitter" <extraspecialbitter@xxxxxxxxx>
- Date: 26 Aug 2006 09:17:38 -0700
Thank you for the swift replies!
extraspecialbitter@xxxxxxxxx wrote:
A few days ago I installed Solaris 10 on my Pentium 4-based PC. After
a day of customization, I elected to install the patches recommended by
the Update Center. I haven't been able to reboot since.
The process gets as far as the "console login" prompt, after which I
get the errors:
syslogd: line 24: WARNING: loghost could not be resolved
sendmail[371]: My unqualified host name (solaris) unknown; sleeping for
retry
sendmail[372]: My unqualified host name (solaris) unknown; sleeping for
retry
"solaris", by the way, is the hostname of the PC. I am using DHCP on a
small LAN behind a Netgear FVS318 that is functioning both as a router
and a firewall.
/var/adm/messages features the same to sendmail errors, but with the
following variation:
sendmail[371]: My unqualified host name (solaris) unknown -- using
short name
sendmail[372]: My unqualified host name (solaris) unknown -- using
short name
Probably the contents of /etc/nodename??
That would be "solaris", terminated with carriage return.
solaris-sys-suspend:[ID221072 daemon.notice] System is being shut down
Any clues would be greatly appreciated.
This is something else that needs to be fixed : / .Probably. man
sys-suspend
If only I could boot in multi-user I could read the man page!
Seriously, I could always google for the answer.
what setup, if any, have you done for sendmail?
None. I don't plan to use it on my desktop, so perhaps disabling it
would be a good idea. Is there an easy way to do this?
Have you put the FQD name of your system in /etc/hosts? That usually
fixes sendmail complaints. Boot single-user, edit /etc/hosts, then exit
single-user and see if it comes up. DHCP creates an /etc/hosts but it does not add loghost > > or a FQDN necessarily.
DHCP creates an entry with the hostname "unknown" assigned to the IP
address.
As far as I can tell it never adds a loghost entry ... the FQDN is relative
to what ends up in /etc/resolv.conf which dhcpagent may also add or alter.
Best to do a Google search on Solaris Rite DHCP and walk through Rich's tutorial.
Rich's tutorial was excellent, but apparently I'm not executing the
"set_hostname" script he recommended using. He mentions that it
shouldn't be necessary in Solaris 10, but I decided to implement it
anyway when none of the other suggestions worked. At the moment I'm
back on my BLAG Linux desktop, which has been 100% predictable and
reliable.
As this is a private home LAN, I didn't do anything special with
/etc/resolv.conf, but I will continue to look for DHCP troubleshooting
posts.
.
- Follow-Ups:
- Re: Unable to boot Solaris 10 after adding recommended patches
- From: Dave Littell
- Re: Unable to boot Solaris 10 after adding recommended patches
- References:
- Unable to boot Solaris 10 after adding recommended patches
- From: extraspecialbitter
- Re: Unable to boot Solaris 10 after adding recommended patches
- From: gerryt
- Unable to boot Solaris 10 after adding recommended patches
- Prev by Date: Re: Finding commands run under root in bash shell
- Next by Date: Re: Unable to boot Solaris 10 after adding recommended patches
- Previous by thread: Re: Unable to boot Solaris 10 after adding recommended patches
- Next by thread: Re: Unable to boot Solaris 10 after adding recommended patches
- Index(es):
Relevant Pages
|