Re: several issues with f34

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Here's the info:

systemctl status ntpd
○ ntpd.service - Network Time Service
     Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled)
     Active: inactive (dead)
       Docs: man:ntpd(8)

At this point here's the current network config:

ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.66  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::4741:dbcc:7824:9f5  prefixlen 64  scopeid 0x20<link>
        ether 4c:d9:8f:6d:87:21  txqueuelen 1000  (Ethernet)
        RX packets 1067  bytes 125274 (122.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 725  bytes 95167 (92.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17

eno2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 4c:d9:8f:6d:87:22  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 18

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 503  bytes 40302 (39.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 503  bytes 40302 (39.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:ba:c1:00  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

The wifi interface does not exist, at this point I started ntpd

sudo systemctl start ntpd

● ntpd.service - Network Time Service
     Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled)
     Active: active (running) since Sun 2021-12-05 09:09:37 PST; 2s ago
       Docs: man:ntpd(8)
    Process: 3288 ExecStart=/usr/sbin/ntpd -g -N -u ntp:ntp (code=exited, status=0/SUCCESS)
   Main PID: 3289 (ntpd)
      Tasks: 2 (limit: 37863)
     Memory: 11.8M
        CPU: 52ms
     CGroup: /system.slice/ntpd.service
             └─3289 /usr/sbin/ntpd -g -N -u ntp:ntp

Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listen normally on 3 eno1 192.168.10.66:123 Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listen normally on 4 lo [::1]:123 Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listen normally on 5 eno1 [fe80::4741:dbcc:7824:9> Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listening on routing socket on fd #22 for interfa> Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: SYNC: Found 5 servers, suggest minsane at least 3 Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: INIT: MRU 10922 entries, 13 hash bits, 65536 bytes Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: INIT: Built with OpenSSL 1.1.1k  FIPS 25 Mar 2021, 10> Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: INIT: Running with OpenSSL 1.1.1l  FIPS 24 Aug 2021, > Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: NTSc: Using system default root certificates. Dec 05 09:09:38 truckin.homenet192-10.com ntpd[3289]: DNS: dns_probe: 0.pool.ntp.org, cast_flags:1, flags:2>

I went and looked in /var/log/messages to see if there was anything there that might indicate the problem.  What I found is that the only time I see:

Dec  5 09:09:37 truckin systemd[1]: Starting Network Time Service...

is when I do it manually.

I rebooted the system at 9:37 AM and there is no entry indicating ntpd was started after this time.

Paolo

On 12/4/21 09:38, Ed Greshko wrote:
On 05/12/2021 00:27, Paolo Galtieri wrote:
This isn't true.  I stopped ntpd, stopped the wifi connection and restarted ntpd and ntpd started fine with no wifi connection.  It should only need a network connection to synchronize the time.

That is why I asked you to provide the output of

systemctl status ntpd

before you restart manually.  That way we may see the error causing it to fail to start initially.



Paolo

On 12/3/21 10:15, Joe Zeff wrote:
On 12/3/21 11:05 AM, Paolo Galtieri wrote:
Next issue. This same system is configured to start ntpd at boot, but it doesn't start.  I need to start it manually after the system is booted.

Of course it doesn't.  That service requires a network connection and can't start until you've unplugged your wireless adapter and plugged it back in.  Fix that and this issue should solve itself.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

--
Did 황준호 die?
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux