NIS and automount Daemon won't work with static IP 64 bit *buntu

[James Sparenberg]

Problem:
with 9.10 Kubuntu, Ubuntu and Xubuntu 64 bit version I'm unable to aquire the NIS server or NFS mounts aren't working with am-utils IF I attempt to set a static IP address. I am able to set the static IP, sometimes, (Ubunut boxes yes, Kubuntu no) But when I do it is no longer able to join the Domain. I then take the same box. Drop it back to dhcp and poof I grab NIS and AMD no problem.

Unfortunately I have to have static addresses on a number of these boxes due to their usage and environment. (Stupid propitiatory development software requires a static IP. even a dhcp assigned static IP won't work.)

32 bit systems do it just fine. It is only the 64 bit ones I'm cursing at the moment. My company can hold for a while with 9.04 but if this is a sign of the future we'll need to find another distro. Not a threat just a sign of the severity for us.

Symptoms: NIS-When a static IP is set and you attempt to restart NIS it restarts, notes that it is trying to startup, and then goes into an endless cycle of repeated "...." line after line . The only mention in syslog is that it is unable to find the NIS server for the Domain. If I take it off of static, and assign the same IP etc via DHCP it finds it immediately, or if I go full DHCP same positive result.

AMD-(am-utils) Starting the application goes without error. No error in logs but none of the NFS mounts are created. If I go to dynamic or statically assigned DHCP this works as expected. We do not push the volume maps via NIS.

Other: I don't think this is a bug in either am-utils or NIS. If it was I would expect one to work not the other. Again noting that we do not use NIS to push volume maps (Old school network created when grey beards were still dark and young *grin*)

Additional. Using NIS and AMD for around 300 systems with only the 2 64 bit *buntu systems failing. The other systems are FreeBSD, CentOS, and Ubuntu 9.04.

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.

There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 475659, and any other logs that are relevant for this particular issue.

[James Sparenberg (james-linuxrebel)]

Charlie,

   I'm in the process of "building" a test environment for 10.10 now. Will this mean that you will then be backporting the fix to LTS? (10.04)

[James Sparenberg (james-linuxrebel)]

Currently no 10.4 does not work. On this. Since this is a corporate environment I don't want to move to 10.10 we wanted to stick with the LTS system for the duration, only migrating to 12.04 I've been keeping one system as my test bed, But so far none of the updates have fixed this. Thanks.

[Charlie Kravetz (cjkgeek)]

 Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!