Hi,
Below are the messages I get when I issue command 'systemctl status network.service'. The time stamp on the messages is incorrect by 1 hour, can anyone tell me why?
Also the messages have indicated that interface Linksys07468_5Ghz was able to be activated ok (this is the 5GHz wifi interface to my router), if that is the case why is that wifi connection not usable, and why has it not listed the Linksys07468 interface which my 2.4GHz wifi interface to my router, which networkmanager will quite happily activate, whereas networkmanager refuses to activate the Linksys07468_5Ghz interface.
bash-4.3$ systemctl status network.service ● network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled) Active: active (exited) since Thu 2016-07-14 06:55:58 AEST; 58min ago Docs: man:systemd-sysv-generator(8) Process: 1074 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 512)
Jul 14 06:55:55 localhost.localdomain systemd[1]: Starting LSB: Bring up/down networking... Jul 14 06:55:56 localhost.localdomain network[1074]: Bringing up loopback interface: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo' Jul 14 06:55:56 localhost.localdomain network[1074]: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo' Jul 14 06:55:56 localhost.localdomain network[1074]: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo' Jul 14 06:55:56 localhost.localdomain network[1074]: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo' Jul 14 06:55:57 localhost.localdomain network[1074]: [ OK ] Jul 14 06:55:57 localhost.localdomain network[1074]: Bringing up interface Linksys07468_5Ghz: [ OK ] Jul 14 06:55:57 localhost.localdomain network[1074]: Bringing up interface enp7s0: [ OK ] Jul 14 06:55:58 localhost.localdomain systemd[1]: Started LSB: Bring up/down networking. bash-4.3$
regards,
Steve
On 07/14/16 06:08, Stephen Morris wrote:
Below are the messages I get when I issue command 'systemctl statusnetwork.service'. The time stamp on the messages is incorrect by 1 hour, can anyone tell me why?
Sounds like the system processes think they are in a different time zone than user processes. This can sometimes happen when system time is set to a UTC offset while users have their zones set to a local zone which has "standard" time as well as "summer" time.
But, your email address would suggest you're located in Australia and now on "standard" time so they should match up.
So, it isn't clear why this is happening in your case.
I would check the output of "hwclock" as well as check what /etc/localtime links to as a start.
On 14/07/16 09:54, Ed Greshko wrote:
On 07/14/16 06:08, Stephen Morris wrote:
Below are the messages I get when I issue command 'systemctl statusnetwork.service'. The time stamp on the messages is incorrect by 1 hour, can anyone tell me why?
Sounds like the system processes think they are in a different time zone than user processes. This can sometimes happen when system time is set to a UTC offset while users have their zones set to a local zone which has "standard" time as well as "summer" time.
But, your email address would suggest you're located in Australia and now on "standard" time so they should match up.
So, it isn't clear why this is happening in your case.
I would check the output of "hwclock" as well as check what /etc/localtime links to as a start.
Thanks Ed, the output from both commands is below, but they are both showing what I expect them to show based on what local time is and the timezone location I have set.
hwclock hwclock: Sorry, only the superuser can use the Hardware Clock. bash-4.3$ sudo hwclock [sudo] password for steve: 2016-07-15 07:05:30.593023+10:00 bash-4.3$ less /etc/localtime "/etc/localtime" may be a binary file. See it anyway? bash-4.3$ ll /etc/localtime lrwxrwxrwx. 1 root root 41 Jun 3 07:40 /etc/localtime -> ../usr/share/zoneinfo/Australia/Melbourne
regards, Steve
On 14/07/16 09:54, Ed Greshko wrote:
On 07/14/16 06:08, Stephen Morris wrote:
Below are the messages I get when I issue command 'systemctl statusnetwork.service'. The time stamp on the messages is incorrect by 1 hour, can anyone tell me why?
Sounds like the system processes think they are in a different time zone than user processes. This can sometimes happen when system time is set to a UTC offset while users have their zones set to a local zone which has "standard" time as well as "summer" time.
But, your email address would suggest you're located in Australia and now on "standard" time so they should match up.
So, it isn't clear why this is happening in your case.
I would check the output of "hwclock" as well as check what /etc/localtime links to as a start.
I think I now understand what the timestamp issue is, it looks like it is my lack of understanding of what the command is showing. I thought the timestamp was the time the command was issued, but it appears from the output below where I issued the command several minutes apart, that the timestamp reflects when the network was physically started at boot time. Looking at the output again it looks like the information in the 3rd output line (the Active: line) is key as to what the timestamp on the messages actually is.
sudo systemctl status network.service ● network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled) Active: active (exited) since Fri 2016-07-15 07:01:22 AEST; 11min ago Docs: man:systemd-sysv-generator(8) Process: 1099 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 512)
Jul 15 07:01:20 localhost.localdomain systemd[1]: Starting LSB: Bring up/down networking... Jul 15 07:01:20 localhost.localdomain network[1099]: Bringing up loopback interface: Could not loa Jul 15 07:01:21 localhost.localdomain network[1099]: Could not load file '/etc/sysconfig/network-sc Jul 15 07:01:21 localhost.localdomain network[1099]: Could not load file '/etc/sysconfig/network-sc Jul 15 07:01:21 localhost.localdomain network[1099]: Could not load file '/etc/sysconfig/network-sc Jul 15 07:01:21 localhost.localdomain network[1099]: [ OK ] Jul 15 07:01:22 localhost.localdomain network[1099]: Bringing up interface Linksys07468_5Ghz: [ O Jul 15 07:01:22 localhost.localdomain network[1099]: Bringing up interface enp7s0: [ OK ] Jul 15 07:01:22 localhost.localdomain systemd[1]: Started LSB: Bring up/down networking. bash-4.3$ sudo systemctl status network.service ● network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled) Active: active (exited) since Fri 2016-07-15 07:01:22 AEST; 13min ago Docs: man:systemd-sysv-generator(8) Process: 1099 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 512)
Jul 15 07:01:20 localhost.localdomain systemd[1]: Starting LSB: Bring up/down networking... Jul 15 07:01:20 localhost.localdomain network[1099]: Bringing up loopback interface: Could not loa Jul 15 07:01:21 localhost.localdomain network[1099]: Could not load file '/etc/sysconfig/network-sc Jul 15 07:01:21 localhost.localdomain network[1099]: Could not load file '/etc/sysconfig/network-sc Jul 15 07:01:21 localhost.localdomain network[1099]: Could not load file '/etc/sysconfig/network-sc Jul 15 07:01:21 localhost.localdomain network[1099]: [ OK ] Jul 15 07:01:22 localhost.localdomain network[1099]: Bringing up interface Linksys07468_5Ghz: [ O Jul 15 07:01:22 localhost.localdomain network[1099]: Bringing up interface enp7s0: [ OK ] Jul 15 07:01:22 localhost.localdomain systemd[1]: Started LSB: Bring up/down networking.
regards, Steve
-
Ed Greshko -
Stephen Morris