/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: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
