Am 02.07.2015 um 20:16 schrieb Gordon Messmer:> Have you yet: > setsebool -P use_samba_home_dirs 1 > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > >No, I didn't set it. Now I've set it and when logging into text console I no longer have the problem with the home directory. That's fine now. Thanks a lot! But the other problem remains, that very soon after startup I can't log into the GUI. I think the remaining problem doesn't has to do something with Samba/Autofs. It looks as if the network becomes ready very late (after autofs started), which perhaps would explain my problem. In the /var/log/boot.log I see: ... Schnittstelle eth0 hochfahren: IP-Informationen f?r eth0 werden bestimmt ... fehlgeschlagen; keine Verbindung vorhanden. Kabel pr?fen? FEHLGESCHLAGEN ... Netzwerkparameter einstellen ... OK NetworkManager-Daemon starten: OK Loading autofs4: OK automount starten: OK In /var/log/messages I see: Jul 5 16:36:08 meikel-pc kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 5 16:36:23 meikel-pc kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready It takes 15 seconds between the two messages until it becomes ready. I have no idea why it first says that the link is not ready. Any ideas? Regards, Meikel
On 07/05/2015 07:57 AM, Meikel wrote:> Jul 5 16:36:08 meikel-pc kernel: ADDRCONF(NETDEV_UP): eth0: link is not > ready > Jul 5 16:36:23 meikel-pc kernel: ADDRCONF(NETDEV_CHANGE): eth0: link > becomes ready > > It takes 15 seconds between the two messages until it becomes ready. I > have no idea why it first says that the link is not ready.It's probably autonegotiation of link speed. I'm not sure why it'd take that long. I'd think the most likely explanation would be a bad cable. Could also be a flaky port on the switch, or a flaky Ethernet card. What brand is the local interface?
> > Jul 5 16:36:08 meikel-pc kernel: ADDRCONF(NETDEV_UP): eth0: link is not > ready > Jul 5 16:36:23 meikel-pc kernel: ADDRCONF(NETDEV_CHANGE): eth0: link > becomes ready > > It takes 15 seconds between the two messages until it becomes ready. I > have no idea why it first says that the link is not ready. > > Any ideas? >What is the upstream switch? If it is a Cisco switch does the configuration have `spanning-tree portfast` enabled? http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/10553-12.html
Am 05.07.2015 um 21:13 schrieb Steven Tardy:> What is the upstream switch? If it is a Cisco switch does the configuration > have `spanning-tree portfast` enabled? > http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/10553-12.html > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >It's a D-Link DGS-1210-16 Switch.
Am 05.07.2015 um 20:52 schrieb Gordon Messmer:> On 07/05/2015 07:57 AM, Meikel wrote: >> Jul 5 16:36:08 meikel-pc kernel: ADDRCONF(NETDEV_UP): eth0: link is not >> ready >> Jul 5 16:36:23 meikel-pc kernel: ADDRCONF(NETDEV_CHANGE): eth0: link >> becomes ready >> >> It takes 15 seconds between the two messages until it becomes ready. I >> have no idea why it first says that the link is not ready. > > It's probably autonegotiation of link speed. I'm not sure why it'd > take that long. I'd think the most likely explanation would be a bad > cable. Could also be a flaky port on the switch, or a flaky Ethernet > card. What brand is the local interface? > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > >I'll check the cable (not clear how I can do that, probably using another cable and connecting to another outlet). I think the local interface is directly integrated into the Intel Desktop Board DH87RL. dmesg | grep eth e1000e 0000:00:19.0: eth0: registered PHC clock e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:22:4d:b0:e0:e1 e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection e1000e 0000:00:19.0: eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF ADDRCONF(NETDEV_UP): eth0: link is not ready e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready eth0: no IPv6 routers present lspci | grep Ether 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) It says that it has a speed of 10/100, but I definitely expect 1000 Mbps!