You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by "A. Rothman" <am...@amichais.net> on 2009/06/29 13:41:41 UTC

ERROR James: Cannot get IP address(es) for domain.name

Hi,


I'm migrating JAMES (2.3.1) from Windows to Ubuntu Jaunty, installed as 
a daemon following the guidelines in the james wiki, and seem to have 
some DNS problems. If started from the command line, everyting runs 
fine. But when started by a reboot, the dnsserver* log show that no dns 
server was auto-detected, as well as java.net.PortUnreachableExceptions 
when trying to send a message, and the james* log shows the error: 
"ERROR James: Cannot get IP address(es) for domain.name". I tried to 
workaround this by explicitly specifying the dns server in the 
configuration, and now sending messages works ok (no exception), but the 
latter error remains. So -


1. What reasons might it have to fail at dns  autodiscovery only during 
boot time?

2. Is the error "Cannot get IP address(es) for domain.name" really an 
error? What implications might this have? Since with the explicitly 
configured dns server, both sending and receiving messages seem to be ok 
even with the error shown...

3. Is the dns component really a dns server (as the log name implies)? 
or a dns client? Should I configure the firewall for a dns server?


Any help would be much appreciated :-)


Amichai



Re: ERROR James: Cannot get IP address(es) for domain.name

Posted by Eric MacAdie <er...@MacAdie.net>.
It seems to work for me even without exporting CLASSPATH. I will add it 
just in case for the future. I know there has been some issue with 
PHOENIX_HOME, but I have not paid too much attention.

Eric MacAdie

A. Rothman wrote:
>
> I recreated the bug in a virtualbox, and PATH doesn't fix it.
>
>
> (btw shouldn't the CLASSPATH in your script be exported? does it do 
> anything?)
>
>
> Amichai
>
>
> A. Rothman wrote:
>
>> Thanks Eric, I'll try adding PATH next time I have some downtime...
>>
>>
>> I found out about not having environment variables set the hard way - 
>> when James wouldn't start at all at first. Then I added JAVA_HOME 
>> manually to phoenix.sh which fixed the problem. Are there any 
>> non-java components in James that would actually require a PATH?
>>
>>
>> btw, speaking of environment variables during bootup, I also found 
>> that PHOENIX_HOME is being mis-detected in phoenix.sh when booting - 
>> submitted a patch.
>>
>>
>> Amichai
>>
>>
>> Eric MacAdie wrote:
>>
>>> Here is a script that I use on Ubuntu for James:
>>> http://www.MacAdie.net/opencms/opencms/sites/MacAdie.dot.Net/Java/James/JamesStartScript.html 
>>>
>>>
>>> One problem might be that you are not including the PATH variable in 
>>> your script. If you are trying to run it as a daemon/service, then 
>>> the environment that James runs in is pretty empty. You do not get 
>>> the system variables (like PATH) that you get when you log in.
>>>
>>> Eric MacAdie
>>>
>>> A. Rothman wrote:
>>>> Hi,
>>>>
>>>>
>>>> I'm migrating JAMES (2.3.1) from Windows to Ubuntu Jaunty, 
>>>> installed as a daemon following the guidelines in the james wiki, 
>>>> and seem to have some DNS problems. If started from the command 
>>>> line, everyting runs fine. But when started by a reboot, the 
>>>> dnsserver* log show that no dns server was auto-detected, as well 
>>>> as java.net.PortUnreachableExceptions when trying to send a 
>>>> message, and the james* log shows the error: "ERROR James: Cannot 
>>>> get IP address(es) for domain.name". I tried to workaround this by 
>>>> explicitly specifying the dns server in the configuration, and now 
>>>> sending messages works ok (no exception), but the latter error 
>>>> remains. So -
>>>>
>>>>
>>>> 1. What reasons might it have to fail at dns  autodiscovery only 
>>>> during boot time?
>>>>
>>>> 2. Is the error "Cannot get IP address(es) for domain.name" really 
>>>> an error? What implications might this have? Since with the 
>>>> explicitly configured dns server, both sending and receiving 
>>>> messages seem to be ok even with the error shown...
>>>>
>>>> 3. Is the dns component really a dns server (as the log name 
>>>> implies)? or a dns client? Should I configure the firewall for a 
>>>> dns server?
>>>>
>>>>
>>>> Any help would be much appreciated :-)
>>>>
>>>>
>>>> Amichai

---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: ERROR James: Cannot get IP address(es) for domain.name

Posted by "A. Rothman" <am...@amichais.net>.
I recreated the bug in a virtualbox, and PATH doesn't fix it.


(btw shouldn't the CLASSPATH in your script be exported? does it do 
anything?)


Amichai


A. Rothman wrote:

> Thanks Eric, I'll try adding PATH next time I have some downtime...
>
>
> I found out about not having environment variables set the hard way - 
> when James wouldn't start at all at first. Then I added JAVA_HOME 
> manually to phoenix.sh which fixed the problem. Are there any non-java 
> components in James that would actually require a PATH?
>
>
> btw, speaking of environment variables during bootup, I also found 
> that PHOENIX_HOME is being mis-detected in phoenix.sh when booting - 
> submitted a patch.
>
>
> Amichai
>
>
> Eric MacAdie wrote:
>
>> Here is a script that I use on Ubuntu for James:
>> http://www.MacAdie.net/opencms/opencms/sites/MacAdie.dot.Net/Java/James/JamesStartScript.html 
>>
>>
>> One problem might be that you are not including the PATH variable in 
>> your script. If you are trying to run it as a daemon/service, then 
>> the environment that James runs in is pretty empty. You do not get 
>> the system variables (like PATH) that you get when you log in.
>>
>> Eric MacAdie
>>
>> A. Rothman wrote:
>>> Hi,
>>>
>>>
>>> I'm migrating JAMES (2.3.1) from Windows to Ubuntu Jaunty, installed 
>>> as a daemon following the guidelines in the james wiki, and seem to 
>>> have some DNS problems. If started from the command line, everyting 
>>> runs fine. But when started by a reboot, the dnsserver* log show 
>>> that no dns server was auto-detected, as well as 
>>> java.net.PortUnreachableExceptions when trying to send a message, 
>>> and the james* log shows the error: "ERROR James: Cannot get IP 
>>> address(es) for domain.name". I tried to workaround this by 
>>> explicitly specifying the dns server in the configuration, and now 
>>> sending messages works ok (no exception), but the latter error 
>>> remains. So -
>>>
>>>
>>> 1. What reasons might it have to fail at dns  autodiscovery only 
>>> during boot time?
>>>
>>> 2. Is the error "Cannot get IP address(es) for domain.name" really 
>>> an error? What implications might this have? Since with the 
>>> explicitly configured dns server, both sending and receiving 
>>> messages seem to be ok even with the error shown...
>>>
>>> 3. Is the dns component really a dns server (as the log name 
>>> implies)? or a dns client? Should I configure the firewall for a dns 
>>> server?
>>>
>>>
>>> Any help would be much appreciated :-)
>>>
>>>
>>> Amichai
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: ERROR James: Cannot get IP address(es) for domain.name

Posted by "A. Rothman" <am...@amichais.net>.
Thanks Eric, I'll try adding PATH next time I have some downtime...


I found out about not having environment variables set the hard way - 
when James wouldn't start at all at first. Then I added JAVA_HOME 
manually to phoenix.sh which fixed the problem. Are there any non-java 
components in James that would actually require a PATH?


btw, speaking of environment variables during bootup, I also found that 
PHOENIX_HOME is being mis-detected in phoenix.sh when booting - 
submitted a patch.


Amichai


Eric MacAdie wrote:

> Here is a script that I use on Ubuntu for James:
> http://www.MacAdie.net/opencms/opencms/sites/MacAdie.dot.Net/Java/James/JamesStartScript.html 
>
>
> One problem might be that you are not including the PATH variable in 
> your script. If you are trying to run it as a daemon/service, then the 
> environment that James runs in is pretty empty. You do not get the 
> system variables (like PATH) that you get when you log in.
>
> Eric MacAdie
>
> A. Rothman wrote:
>> Hi,
>>
>>
>> I'm migrating JAMES (2.3.1) from Windows to Ubuntu Jaunty, installed 
>> as a daemon following the guidelines in the james wiki, and seem to 
>> have some DNS problems. If started from the command line, everyting 
>> runs fine. But when started by a reboot, the dnsserver* log show that 
>> no dns server was auto-detected, as well as 
>> java.net.PortUnreachableExceptions when trying to send a message, and 
>> the james* log shows the error: "ERROR James: Cannot get IP 
>> address(es) for domain.name". I tried to workaround this by 
>> explicitly specifying the dns server in the configuration, and now 
>> sending messages works ok (no exception), but the latter error 
>> remains. So -
>>
>>
>> 1. What reasons might it have to fail at dns  autodiscovery only 
>> during boot time?
>>
>> 2. Is the error "Cannot get IP address(es) for domain.name" really an 
>> error? What implications might this have? Since with the explicitly 
>> configured dns server, both sending and receiving messages seem to be 
>> ok even with the error shown...
>>
>> 3. Is the dns component really a dns server (as the log name 
>> implies)? or a dns client? Should I configure the firewall for a dns 
>> server?
>>
>>
>> Any help would be much appreciated :-)
>>
>>
>> Amichai
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: ERROR James: Cannot get IP address(es) for domain.name

Posted by Eric MacAdie <er...@MacAdie.net>.
Here is a script that I use on Ubuntu for James:
http://www.MacAdie.net/opencms/opencms/sites/MacAdie.dot.Net/Java/James/JamesStartScript.html

One problem might be that you are not including the PATH variable in 
your script. If you are trying to run it as a daemon/service, then the 
environment that James runs in is pretty empty. You do not get the 
system variables (like PATH) that you get when you log in.

Eric MacAdie

A. Rothman wrote:
> Hi,
>
>
> I'm migrating JAMES (2.3.1) from Windows to Ubuntu Jaunty, installed 
> as a daemon following the guidelines in the james wiki, and seem to 
> have some DNS problems. If started from the command line, everyting 
> runs fine. But when started by a reboot, the dnsserver* log show that 
> no dns server was auto-detected, as well as 
> java.net.PortUnreachableExceptions when trying to send a message, and 
> the james* log shows the error: "ERROR James: Cannot get IP 
> address(es) for domain.name". I tried to workaround this by explicitly 
> specifying the dns server in the configuration, and now sending 
> messages works ok (no exception), but the latter error remains. So -
>
>
> 1. What reasons might it have to fail at dns  autodiscovery only 
> during boot time?
>
> 2. Is the error "Cannot get IP address(es) for domain.name" really an 
> error? What implications might this have? Since with the explicitly 
> configured dns server, both sending and receiving messages seem to be 
> ok even with the error shown...
>
> 3. Is the dns component really a dns server (as the log name implies)? 
> or a dns client? Should I configure the firewall for a dns server?
>
>
> Any help would be much appreciated :-)
>
>
> Amichai
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: ERROR James: Cannot get IP address(es) for domain.name

Posted by "A. Rothman" <am...@amichais.net>.
As promised, I'm writing back with the solution - at least it seems to 
work so far. The fix is to have james start with startup order number 91 
instead of 21 - the same number used for apache2, which I figured would 
have similar dependencies (networking up and running, and mysql if 
necessary). I'm having trouble updating the wiki page 
(http://wiki.apache.org/james/RunAsService) so if someone feels like 
adding this below the "Wrapper Instructions" section, that would be great:


Update for Ubuntu

Similar to the wrapper instructions, the following works for Ubuntu:
1. Edit phoenix.sh to set JAVA_HOME (somewhere near the top).
2. In versions prior to 2.3.2, edit phoenix.sh and change the command 
that sets PHOENIX_HOME to point directly to your james installation 
path. As of version 2.3.2 the script is fixed to detect this 
automatically, and so this step is unnecessary.
3. Run "sudo ln -s /path/to/james/bin/phoenix.sh /etc/init.d/james" 
(subsitute your james installation path)
4. Run "sudo update-rc.d james start 91 2 3 4 5 . stop 9 0 1 6 ."



Amichai






A. Rothman wrote:
> /etc/resolv.conf:
>
>
> # Generated by NetworkManager
> nameserver 192.168.80.1
>
>
> and when I try printing it out from the phoenix.sh script during 
> startup, it's overwritten and is empty, and gets filled up again by 
> the time the system is fully booted. I tried making James start after 
> network manager, which I assumed was the one causing this, but 
> strangely that didn't help. I also tried adding appropriate 
> nameservers to some dhcp config file (don't remember exactly, I just 
> did what someone suggested) but it didn't help either.
>
>
>
> Eric MacAdie wrote:
>
>> One question: Are the name servers in your /etc/resolv.conf file also 
>> in your James config.xml file in the config/dnsserver/servers tag? 
>> Those should be the same.
>>
>> Eric MacAdie
>>
>> A. Rothman wrote:
>>> Thanks for the follow up - no, I haven't found a solution yet, but 
>>> it seems to work ok even with the errors shown, so it got pushed 
>>> down my todo list...
>>>
>>> Regarding #1, I think this is not a James issue per-se (other than 
>>> an error in the wiki about how to set up James as a daemon), but 
>>> something about the ubuntu/debian startup sequence which causes 
>>> James to load before the appropriate network services are set up - 
>>> I've discussed this with some linux ppl, tried a few configuration 
>>> changes, but still haven't nailed it. I'll keep at it when I have 
>>> the time, and when I come up with a solution, I'll update the wiki 
>>> and/or reply to this thread...
>>>
>>> Of course, if anyone has suggestions in the meanwhile, I'd very much 
>>> appreciate help :-)
>>>
>>> As for #2 and #3, I didn't get an authoritative reply, but I'm 
>>> assuming for the time being that it is not in fact an error (I 
>>> didn't notice any side effects yet), and that the dnsserver 
>>> component is in fact a dns client (it makes more sense).
>>>
>>>
>>> Amichai
>>>
>>> Eric MacAdie wrote:
>>>> Did you ever solve this issue? Looking at the thread it looks like 
>>>> you may not have (at least no such notice was sent to the list).
>>>>
>>>> Eric MacAdie
>>>>
>>>> A. Rothman wrote:
>>>>> Hi,
>>>>>
>>>>>
>>>>> I'm migrating JAMES (2.3.1) from Windows to Ubuntu Jaunty, 
>>>>> installed as a daemon following the guidelines in the james wiki, 
>>>>> and seem to have some DNS problems. If started from the command 
>>>>> line, everyting runs fine. But when started by a reboot, the 
>>>>> dnsserver* log show that no dns server was auto-detected, as well 
>>>>> as java.net.PortUnreachableExceptions when trying to send a 
>>>>> message, and the james* log shows the error: "ERROR James: Cannot 
>>>>> get IP address(es) for domain.name". I tried to workaround this by 
>>>>> explicitly specifying the dns server in the configuration, and now 
>>>>> sending messages works ok (no exception), but the latter error 
>>>>> remains. So -
>>>>>
>>>>>
>>>>> 1. What reasons might it have to fail at dns  autodiscovery only 
>>>>> during boot time?
>>>>>
>>>>> 2. Is the error "Cannot get IP address(es) for domain.name" really 
>>>>> an error? What implications might this have? Since with the 
>>>>> explicitly configured dns server, both sending and receiving 
>>>>> messages seem to be ok even with the error shown...
>>>>>
>>>>> 3. Is the dns component really a dns server (as the log name 
>>>>> implies)? or a dns client? Should I configure the firewall for a 
>>>>> dns server?
>>>>>
>>>>>
>>>>> Any help would be much appreciated :-)
>>>>>
>>>>>
>>>>> Amichai
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: ERROR James: Cannot get IP address(es) for domain.name

Posted by "A. Rothman" <am...@amichais.net>.
/etc/resolv.conf:


# Generated by NetworkManager
nameserver 192.168.80.1


and when I try printing it out from the phoenix.sh script during 
startup, it's overwritten and is empty, and gets filled up again by the 
time the system is fully booted. I tried making James start after 
network manager, which I assumed was the one causing this, but strangely 
that didn't help. I also tried adding appropriate nameservers to some 
dhcp config file (don't remember exactly, I just did what someone 
suggested) but it didn't help either.



Eric MacAdie wrote:

> One question: Are the name servers in your /etc/resolv.conf file also 
> in your James config.xml file in the config/dnsserver/servers tag? 
> Those should be the same.
>
> Eric MacAdie
>
> A. Rothman wrote:
>> Thanks for the follow up - no, I haven't found a solution yet, but it 
>> seems to work ok even with the errors shown, so it got pushed down my 
>> todo list...
>>
>> Regarding #1, I think this is not a James issue per-se (other than an 
>> error in the wiki about how to set up James as a daemon), but 
>> something about the ubuntu/debian startup sequence which causes James 
>> to load before the appropriate network services are set up - I've 
>> discussed this with some linux ppl, tried a few configuration 
>> changes, but still haven't nailed it. I'll keep at it when I have the 
>> time, and when I come up with a solution, I'll update the wiki and/or 
>> reply to this thread...
>>
>> Of course, if anyone has suggestions in the meanwhile, I'd very much 
>> appreciate help :-)
>>
>> As for #2 and #3, I didn't get an authoritative reply, but I'm 
>> assuming for the time being that it is not in fact an error (I didn't 
>> notice any side effects yet), and that the dnsserver component is in 
>> fact a dns client (it makes more sense).
>>
>>
>> Amichai
>>
>> Eric MacAdie wrote:
>>> Did you ever solve this issue? Looking at the thread it looks like 
>>> you may not have (at least no such notice was sent to the list).
>>>
>>> Eric MacAdie
>>>
>>> A. Rothman wrote:
>>>> Hi,
>>>>
>>>>
>>>> I'm migrating JAMES (2.3.1) from Windows to Ubuntu Jaunty, 
>>>> installed as a daemon following the guidelines in the james wiki, 
>>>> and seem to have some DNS problems. If started from the command 
>>>> line, everyting runs fine. But when started by a reboot, the 
>>>> dnsserver* log show that no dns server was auto-detected, as well 
>>>> as java.net.PortUnreachableExceptions when trying to send a 
>>>> message, and the james* log shows the error: "ERROR James: Cannot 
>>>> get IP address(es) for domain.name". I tried to workaround this by 
>>>> explicitly specifying the dns server in the configuration, and now 
>>>> sending messages works ok (no exception), but the latter error 
>>>> remains. So -
>>>>
>>>>
>>>> 1. What reasons might it have to fail at dns  autodiscovery only 
>>>> during boot time?
>>>>
>>>> 2. Is the error "Cannot get IP address(es) for domain.name" really 
>>>> an error? What implications might this have? Since with the 
>>>> explicitly configured dns server, both sending and receiving 
>>>> messages seem to be ok even with the error shown...
>>>>
>>>> 3. Is the dns component really a dns server (as the log name 
>>>> implies)? or a dns client? Should I configure the firewall for a 
>>>> dns server?
>>>>
>>>>
>>>> Any help would be much appreciated :-)
>>>>
>>>>
>>>> Amichai
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: ERROR James: Cannot get IP address(es) for domain.name

Posted by Eric MacAdie <er...@MacAdie.net>.
One question: Are the name servers in your /etc/resolv.conf file also in 
your James config.xml file in the config/dnsserver/servers tag? Those 
should be the same.

Eric MacAdie

A. Rothman wrote:
> Thanks for the follow up - no, I haven't found a solution yet, but it 
> seems to work ok even with the errors shown, so it got pushed down my 
> todo list...
>
> Regarding #1, I think this is not a James issue per-se (other than an 
> error in the wiki about how to set up James as a daemon), but 
> something about the ubuntu/debian startup sequence which causes James 
> to load before the appropriate network services are set up - I've 
> discussed this with some linux ppl, tried a few configuration changes, 
> but still haven't nailed it. I'll keep at it when I have the time, and 
> when I come up with a solution, I'll update the wiki and/or reply to 
> this thread...
>
> Of course, if anyone has suggestions in the meanwhile, I'd very much 
> appreciate help :-)
>
> As for #2 and #3, I didn't get an authoritative reply, but I'm 
> assuming for the time being that it is not in fact an error (I didn't 
> notice any side effects yet), and that the dnsserver component is in 
> fact a dns client (it makes more sense).
>
>
> Amichai
>
> Eric MacAdie wrote:
>> Did you ever solve this issue? Looking at the thread it looks like 
>> you may not have (at least no such notice was sent to the list).
>>
>> Eric MacAdie
>>
>> A. Rothman wrote:
>>> Hi,
>>>
>>>
>>> I'm migrating JAMES (2.3.1) from Windows to Ubuntu Jaunty, installed 
>>> as a daemon following the guidelines in the james wiki, and seem to 
>>> have some DNS problems. If started from the command line, everyting 
>>> runs fine. But when started by a reboot, the dnsserver* log show 
>>> that no dns server was auto-detected, as well as 
>>> java.net.PortUnreachableExceptions when trying to send a message, 
>>> and the james* log shows the error: "ERROR James: Cannot get IP 
>>> address(es) for domain.name". I tried to workaround this by 
>>> explicitly specifying the dns server in the configuration, and now 
>>> sending messages works ok (no exception), but the latter error 
>>> remains. So -
>>>
>>>
>>> 1. What reasons might it have to fail at dns  autodiscovery only 
>>> during boot time?
>>>
>>> 2. Is the error "Cannot get IP address(es) for domain.name" really 
>>> an error? What implications might this have? Since with the 
>>> explicitly configured dns server, both sending and receiving 
>>> messages seem to be ok even with the error shown...
>>>
>>> 3. Is the dns component really a dns server (as the log name 
>>> implies)? or a dns client? Should I configure the firewall for a dns 
>>> server?
>>>
>>>
>>> Any help would be much appreciated :-)
>>>
>>>
>>> Amichai
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: ERROR James: Cannot get IP address(es) for domain.name

Posted by "A. Rothman" <am...@amichais.net>.
Thanks for the follow up - no, I haven't found a solution yet, but it 
seems to work ok even with the errors shown, so it got pushed down my 
todo list...

Regarding #1, I think this is not a James issue per-se (other than an 
error in the wiki about how to set up James as a daemon), but something 
about the ubuntu/debian startup sequence which causes James to load 
before the appropriate network services are set up - I've discussed this 
with some linux ppl, tried a few configuration changes, but still 
haven't nailed it. I'll keep at it when I have the time, and when I come 
up with a solution, I'll update the wiki and/or reply to this thread...

Of course, if anyone has suggestions in the meanwhile, I'd very much 
appreciate help :-)

As for #2 and #3, I didn't get an authoritative reply, but I'm assuming 
for the time being that it is not in fact an error (I didn't notice any 
side effects yet), and that the dnsserver component is in fact a dns 
client (it makes more sense).


Amichai

Eric MacAdie wrote:
> Did you ever solve this issue? Looking at the thread it looks like you 
> may not have (at least no such notice was sent to the list).
>
> Eric MacAdie
>
> A. Rothman wrote:
>> Hi,
>>
>>
>> I'm migrating JAMES (2.3.1) from Windows to Ubuntu Jaunty, installed 
>> as a daemon following the guidelines in the james wiki, and seem to 
>> have some DNS problems. If started from the command line, everyting 
>> runs fine. But when started by a reboot, the dnsserver* log show that 
>> no dns server was auto-detected, as well as 
>> java.net.PortUnreachableExceptions when trying to send a message, and 
>> the james* log shows the error: "ERROR James: Cannot get IP 
>> address(es) for domain.name". I tried to workaround this by 
>> explicitly specifying the dns server in the configuration, and now 
>> sending messages works ok (no exception), but the latter error 
>> remains. So -
>>
>>
>> 1. What reasons might it have to fail at dns  autodiscovery only 
>> during boot time?
>>
>> 2. Is the error "Cannot get IP address(es) for domain.name" really an 
>> error? What implications might this have? Since with the explicitly 
>> configured dns server, both sending and receiving messages seem to be 
>> ok even with the error shown...
>>
>> 3. Is the dns component really a dns server (as the log name 
>> implies)? or a dns client? Should I configure the firewall for a dns 
>> server?
>>
>>
>> Any help would be much appreciated :-)
>>
>>
>> Amichai
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: ERROR James: Cannot get IP address(es) for domain.name

Posted by Eric MacAdie <er...@MacAdie.net>.
Did you ever solve this issue? Looking at the thread it looks like you 
may not have (at least no such notice was sent to the list).

Eric MacAdie

A. Rothman wrote:
> Hi,
>
>
> I'm migrating JAMES (2.3.1) from Windows to Ubuntu Jaunty, installed 
> as a daemon following the guidelines in the james wiki, and seem to 
> have some DNS problems. If started from the command line, everyting 
> runs fine. But when started by a reboot, the dnsserver* log show that 
> no dns server was auto-detected, as well as 
> java.net.PortUnreachableExceptions when trying to send a message, and 
> the james* log shows the error: "ERROR James: Cannot get IP 
> address(es) for domain.name". I tried to workaround this by explicitly 
> specifying the dns server in the configuration, and now sending 
> messages works ok (no exception), but the latter error remains. So -
>
>
> 1. What reasons might it have to fail at dns  autodiscovery only 
> during boot time?
>
> 2. Is the error "Cannot get IP address(es) for domain.name" really an 
> error? What implications might this have? Since with the explicitly 
> configured dns server, both sending and receiving messages seem to be 
> ok even with the error shown...
>
> 3. Is the dns component really a dns server (as the log name implies)? 
> or a dns client? Should I configure the firewall for a dns server?
>
>
> Any help would be much appreciated :-)
>
>
> Amichai
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org