I woke up this morning to no internet. ifconfig showed an IPv6 address, but no IPv4 IP.. systemctl restart network didn't do anything.. so I rebooted & got network back. Is there a better way? fedora 21 amd_64 is there a /var/log entry that might show something??
On Sunday, October 05, 2014 07:03:10 AM Paul Cartwright wrote:
I woke up this morning to no internet. ifconfig showed an IPv6 address, but no IPv4 IP.. systemctl restart network didn't do anything.. so I rebooted & got network back. Is there a better way? fedora 21 amd_64 is there a /var/log entry that might show something??
Take a look in the journal using journalctl, also you probably want to run systemctl restart NetworkManager unless you have disabled that for some reason.
-Erinn
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/05/2014 10:39 AM, Erinn Looney-Triggs wrote:
Take a look in the journal using journalctl, also you probably want to run systemctl restart NetworkManager unless you have disabled that for some reason.
-Erinn
journalctl is.... overwhelmingly large.... page after page... I did -r and it was still over 100 pages to get back to where I rebooted this morning...
- -- Paul Cartwright Registered Linux User #367800 and new counter #561587
The motherboard on my server has two NICS, one driven by an Intel chip and the other by a Realtek chip. The Intel chip would stop working fairly often. I disabled the Intel chip and added an ethernet board. This solved the problem.
On Sun, 2014-10-05 at 11:08 -0400, Paul Cartwright wrote:
On 10/05/2014 10:39 AM, Erinn Looney-Triggs wrote:
Take a look in the journal using journalctl, also you probably want to run systemctl restart NetworkManager unless you have disabled that for some reason.
-Erinn
journalctl is.... overwhelmingly large.... page after page... I did -r and it was still over 100 pages to get back to where I rebooted this morning...
well, what messages are in there that make it so long? journalctl is just the system log, like /var/log/messages used to be.