|
Replies:
6
-
Last Post:
Dec 13, 2007 5:27 PM
by: darrenr
|
|
|
Posts:
2,173
From:
US
Registered:
6/24/05
|
|
|
|
"loghost could not be resolved"
Posted:
Dec 13, 2007 11:31 AM
To: Communities » networking » discuss
|
|
I was playing with my dhcp client and when I rebooted, I saw the following message:
" unknown syslogd: line 24: WARNING: loghost could not be resolved "
What could have I done wrong? Any suggestions to remove this problem? Apologize for the terse info I am providing.
|
|
|
Posts:
491
From:
US
Registered:
3/9/05
|
|
|
|
Re: "loghost could not be resolved"
Posted:
Dec 13, 2007 11:34 AM
in response to: waynel
|
|
On Thu, Dec 13, 2007 at 11:31:16AM -0800, W. Wayne Liauh wrote:
> " unknown syslogd: line 24: WARNING: loghost could not be resolved "
>
> What could have I done wrong? Any suggestions to remove this problem? Apologize for the terse info I am providing.
syslogd requires that one of your entries in /etc/hosts be assigned the name
"loghost" as well. I'm not sure how to fix syslog, but a workaround is to
alias localhost to loghost as well:
127.0.0.1 localhost loghost
Dan
_______________________________________________
networking-discuss mailing list
networking-discuss at opensolaris dot org
|
|
|
|
|
Posts:
6,807
From:
US
Registered:
3/9/05
|
|
|
|
Re: "loghost could not be resolved"
Posted:
Dec 13, 2007 12:20 PM
in response to: waynel
|
|
W. Wayne Liauh writes:
> I was playing with my dhcp client and when I rebooted, I saw the following message:
>
> " unknown syslogd: line 24: WARNING: loghost could not be resolved "
>
> What could have I done wrong? Any suggestions to remove this problem? Apologize for the terse info I am providing.
This is CR 4351417, an ancient problem. The system scripts just don't
populate the loghost entry.
To work around it, you can add "loghost" to the localhost line in
/etc/hosts.
--
James Carlson, Solaris Networking <james dot d dot carlson at sun dot com>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
networking-discuss at opensolaris dot org
|
|
|
|
|
Posts:
3,422
From:
Austin, TX, USA
Registered:
6/15/05
|
|
|
|
Re: "loghost could not be resolved"
Posted:
Dec 13, 2007 1:13 PM
in response to: carlsonj
|
|
On Thu, Dec 13, 2007 at 03:20:07PM -0500, James Carlson wrote:
> W. Wayne Liauh writes:
> > I was playing with my dhcp client and when I rebooted, I saw the following message:
> >
> > " unknown syslogd: line 24: WARNING: loghost could not be resolved "
> >
> > What could have I done wrong? Any suggestions to remove this problem? Apologize for the terse info I am providing.
>
> This is CR 4351417, an ancient problem. The system scripts just don't
> populate the loghost entry.
>
> To work around it, you can add "loghost" to the localhost line in
> /etc/hosts.
Devil's advocate: but why should they? If I have a loghost or if I
will have one, then I don't want localhost to be aliased as loghost.
/etc/syslog.conf already deals with loghost being defined or not. So
why not just remove the warning instead?
Another issue is that one might like secure syslogging, including
secure discovery and authentication of loghosts. I think Secure By
Default provides the best rationale to do something about this.
So why not this instead:
- add a property to svc:/system/system-log to toggle whether insecure
lookup of loghost and logging to loghost is allowed, default to no
Nico
--
_______________________________________________
networking-discuss mailing list
networking-discuss at opensolaris dot org
|
|
|
|
|
Posts:
6,807
From:
US
Registered:
3/9/05
|
|
|
|
Re: "loghost could not be resolved"
Posted:
Dec 13, 2007 1:22 PM
in response to: nico
|
|
Nicolas Williams writes:
> - add a property to svc:/system/system-log to toggle whether insecure
> lookup of loghost and logging to loghost is allowed, default to no
I'd be fine with that as well. The current work-around using
/etc/hosts is just adequate.
--
James Carlson, Solaris Networking <james dot d dot carlson at sun dot com>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
networking-discuss at opensolaris dot org
|
|
|
|
|
Posts:
3,422
From:
Austin, TX, USA
Registered:
6/15/05
|
|
|
|
Re: "loghost could not be resolved"
Posted:
Dec 13, 2007 1:59 PM
in response to: carlsonj
|
|
On Thu, Dec 13, 2007 at 04:22:24PM -0500, James Carlson wrote:
> Nicolas Williams writes:
> > - add a property to svc:/system/system-log to toggle whether insecure
> > lookup of loghost and logging to loghost is allowed, default to no
>
> I'd be fine with that as well. The current work-around using
> /etc/hosts is just adequate.
The workaround certainly is. I think a property of system-log seems
like a better architecture than having install or dhcp scripts update
/etc/inet/hosts because it puts the decision of what to do into the
hands of the admin via SMF profiles (though, IIRC, today SMF profiles
can't update such properties, but eventually they will be able to).
_______________________________________________
networking-discuss mailing list
networking-discuss at opensolaris dot org
|
|
|
|
|
Posts:
2,060
From:
Registered:
6/8/05
|
|
|
|
Re: "loghost could not be resolved"
Posted:
Dec 13, 2007 5:27 PM
in response to: carlsonj
|
|
James Carlson wrote:
> W. Wayne Liauh writes:
>
>> I was playing with my dhcp client and when I rebooted, I saw the following message:
>>
>> " unknown syslogd: line 24: WARNING: loghost could not be resolved "
>>
>> What could have I done wrong? Any suggestions to remove this problem? Apologize for the terse info I am providing.
>>
>
> This is CR 4351417, an ancient problem. The system scripts just don't
> populate the loghost entry.
>
> To work around it, you can add "loghost" to the localhost line in
> /etc/hosts.
>
IMHO, this is somewhat backwards. Or at least the "amiloghost()" logic is.
I'd argue that amiloghost() should return "true" if there is no
mapping for loghost/syslog found in the name service table,
not just if it can bind loghost/syslog locally.
Darren
_______________________________________________
networking-discuss mailing list
networking-discuss at opensolaris dot org
|
|
|
|
|
