You can configure the IPv6 loopback interface by touching /etc/hostname6.<interfacename>, for example:
touch hostname6.hme0 Then reboot, or restart the loopback networks. It's a benign impact on the system. regards, -glenn -- Glenn Satchell mailto:[email protected] | The squeaky Uniq Advances Pty Ltd http://www.uniq.com.au | wheel is the one PO Box 70 Paddington NSW Australia 2021 | that makes the Mobile 0409 458 580 Ph 02 9380 6360 | most noise. > Thanks - I will give it a try. Is there any side effect of commenting > this > out? > As per the BugID the workaround was > > svccfg -s sendmail setprop config/local_only=false > > *Description* > > > -------------------------------- > sendmail[1581]: daemon MTA-v6: problem creating SMTP socket > sendmail[1581]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon > MTA-v6: cannot bind: Cannot assign requested address > -------------------------------- > > these are printed into console and cause problem during expect automation. > Similar problem is described in CR *6722022* but only on local zones > in Nevada, however root cause is the same ipv6 lo0 interface is not > present on S10, but value config/local_only is set to true, therefor > sendmail tries to bind to ipv6 interface which fails. > grep DaemonPortOptions /etc/mail/sendmail.cf on S10 nightly > s10u9_2010-02-18(RE) or s10u9_2010-02-21(RE) is reporting the same as > on Nevada: > ------------------------------- > # grep DaemonPortOptions /etc/mail/sendmail.cf > O DaemonPortOptions=Name=MTA-v4, Family=inet > O DaemonPortOptions=Name=MTA-v6, Family=inet6 > O DaemonPortOptions=Port=587, Name=MSA, M=E > ------------------------------- > > We did just the standard install, no modification to sendmail > configurations. > > *Work Around* > > change config/local_only property of sendmail to false or bring up > inet6 lo0 interface > > > > On Thu, Feb 17, 2011 at 2:25 PM, Jeff Wieland <[email protected]> wrote: > >> little help wrote: >> >>> It appears the latest solaris10 patches/kernel update split sendmail >>> into >>> two separate services (client and server). However, once I reboot my >>> host I >>> get the error below. I found a bug on this but it states it has been >>> fixed >>> in svn_103. Being that I am running an earlier version it appear my >>> only >>> option is a workaround noted on the bug report. Has anyone else seen >>> this >>> issue and do you know if there is a fix on the way? Thanks. >>> >>> opendaemonsocket: daemon MTA-v6: server SMTP socket wedged: exiting >>> daemon MTA-v6: problem creating SMTP socket >>> >> >> Yep. It's because you don't have IPv6 configured, but your sendmail.cf >> is trying to use it anyway. Check your sendmail.cf file for the >> following >> line: >> >> O DaemonPortOptions=Name=MTA-v6, Family=inet6 >> >> comment it out, and clear the error with svcadm. >> >> -- >> Jeff Wieland | Purdue University >> Network Systems Administrator | ITN&S Data Networks >> Voice: (765)496-8234 | 155 S. Grant Street >> FAX: (765)494-6620 | West Lafayette, IN 47907-2115 >> >> >> >
