Attachment 256370 Details for Bug 440809

Detailed notes re hostname changes in RC1.

TroubleshootingHostname-11.1-RC1-28Nov08 (text/plain), 4.92 KB, created by Geoff Farrell on 2008-11-28 04:32:16 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Geoff Farrell

Created: 2008-11-28 04:32:16 UTC

Size: 4.92 KB

patch

obsolete

>1. On Konsole login, get prompt:
>geoff@linux-0mh9:~>
>
>2. > cat /etc/hosts:
>#
># hosts         This file describes a number of hostname-to-address
>#               mappings for the TCP/IP subsystem.  It is mostly
>#               used at boot time, when no name servers are running.
>#               On small systems, this file can be used instead of a
>#               "named" name server.
># Syntax:
>#
># IP-Address  Full-Qualified-Hostname  Short-Hostname
>#
>
>127.0.0.1       localhost
>
># special IPv6 addresses
>::1             localhost ipv6-localhost ipv6-loopback
>
>fe00::0         ipv6-localnet
>
>ff00::0         ipv6-mcastprefix
>ff02::1         ipv6-allnodes
>ff02::2         ipv6-allrouters
>ff02::3         ipv6-allhosts
>
>127.0.0.2       linux-0mh9.site linux-0mh9
>
>3. > cat /etc/HOSTNAME:
>linux-0mh9.site
>
>4. > hostname:
>linux-0mh9
>
>5.  cat /proc/sys/kernel/hostname:
>linux-0mh9
>
>6. # echo "HomeLin11-1RC1.HomeNetwork" > /etc/HOSTNAME:
>7. # cat /etc/HOSTNAME:
>HomeLin11-1RC1.HomeNetwork
>
>8. Exited Konsole, restarted it. Login prompt:
>geoff@linux-0mh9:~>
>
>9. # cat /etc/hosts:
>#
># hosts         This file describes a number of hostname-to-address
>#               mappings for the TCP/IP subsystem.  It is mostly
>#               used at boot time, when no name servers are running.
>#               On small systems, this file can be used instead of a
>#               "named" name server.
># Syntax:
>#
># IP-Address  Full-Qualified-Hostname  Short-Hostname
>#
>
>127.0.0.1       localhost
>
># special IPv6 addresses
>::1             localhost ipv6-localhost ipv6-loopback
>
>fe00::0         ipv6-localnet
>
>ff00::0         ipv6-mcastprefix
>ff02::1         ipv6-allnodes
>ff02::2         ipv6-allrouters
>ff02::3         ipv6-allhosts
>
>127.0.0.2       linux-0mh9.site linux-0mh9
>(Ie, unchanged)
>
>10. # hostname:
>linux-0mh9
>
>11. # cat /proc/sys/kernel/hostname:
>linux-0mh9
>
>12. So, only thing changed is /etc/HOSTNAME. NetworkMangager has not detected the change. Trying restart of NetworkManager:
># rcnetwork restart:
>Shutting down the NetworkManager                                                                                                              done
>Shutting down network interfaces:
>    eth0      device: nVidia Corporation CK804 Ethernet Controller (rev a3)                                                                   done
>Shutting down service network  .  .  .  .  .  .  .  .  .                                                                                      done
>Starting the NetworkManager                                                                                                                   done
>
>13. # cat /etc/hosts:
>
># hosts         This file describes a number of hostname-to-address
>#               mappings for the TCP/IP subsystem.  It is mostly
>#               used at boot time, when no name servers are running.
>#               On small systems, this file can be used instead of a
>#               "named" name server.
># Syntax:
>#
># IP-Address  Full-Qualified-Hostname  Short-Hostname
>#
>
>127.0.0.1       localhost
>
># special IPv6 addresses
>::1             localhost ipv6-localhost ipv6-loopback
>
>fe00::0         ipv6-localnet
>
>ff00::0         ipv6-mcastprefix
>ff02::1         ipv6-allnodes
>ff02::2         ipv6-allrouters
>ff02::3         ipv6-allhosts
>
>127.0.0.2       linux-0mh9.site linux-0mh9
>(Ie, nothing changed)
>
>14. # hostname:
>linux-0mh9
>
>15. # cat /proc/sys/kernel/hostname:
>linux-0mh9
>
>16. # cat /etc/HOSTNAME:
>HomeLin11-1RC1.HomeNetwork
>
>17. So, NetworkManager has not detected the change, and hostname is not synchronised in its three locations.
>
>18. YaST-> Network Devices-> Network Settings has hostname and domainname correctly set in the 'Hostname/DNS' tab. But the user is warned off making changes here, told to configure with NetworkManager.
>
>19. Rebooting. On login, get prompt:
>geoff@HomeLin11-1RC1:~>
>
>20. # cat /etc/hosts:
># cat /etc/hosts
>#
># hosts         This file describes a number of hostname-to-address
>#               mappings for the TCP/IP subsystem.  It is mostly
>#               used at boot time, when no name servers are running.
>#               On small systems, this file can be used instead of a
>#               "named" name server.
># Syntax:
>#
># IP-Address  Full-Qualified-Hostname  Short-Hostname
>#
>
>127.0.0.1       localhost
>
># special IPv6 addresses
>::1             localhost ipv6-localhost ipv6-loopback
>
>fe00::0         ipv6-localnet
>
>ff00::0         ipv6-mcastprefix
>ff02::1         ipv6-allnodes
>ff02::2         ipv6-allrouters
>ff02::3         ipv6-allhosts
>
>127.0.0.2       linux-0mh9.site linux-0mh9
>(Ie, nothing changed)
>
>21. # hostname:
>HomeLin11-1RC1
>
>22. # cat /proc/sys/kernel/hostname:
>HomeLin11-1RC1
>
>23. # cat /etc/HOSTNAME:
>HomeLin11-1RC1.HomeNetwork
>
>24. So, all have changed, except for /etc/hosts, which is still has 127.0.0.2 line set to 'linux-0mh9.site linux-0mh9'.
>
>25. Therefore, NetworkManager does NOT look after hostname changes in all locations where it needs to change. Programs which rely on /etc/hosts will get the wrong hostname.

Actions: View

Attachments on bug 440809: 249229 | 254526 | 256370