OVH Have you guys encounter this on OVH dedicated server?

Maybe related to CentOS 7 fix update for Polkit ? https://rhn.redhat.com/errata/RHBA-2017-0392.html

tried a hard reboot via OVH control panel ?

 

tried centos 6 os install ? if same happens then probably OVH server/network related

 

what you doing from initial Centmin Mod install leading up to server reboot ? or is this problem happening without Centmin Mod install and just first CentOS 7.3 login on fresh install ?

Tried CentOS 7.3 fresh install and yum update and reboot without install Centmin Mod ?

 

Also check your dmesg logs in /var/log for clues. See 7 'dmesg' Commands for Troubleshooting and Collecting Information of Linux Systems

On CentOS 7 can also be inspected for dmesg via journalctl kernel flag

I filter out Firewall: related entries for today only

Code (Text):

journalctl -k --no-pager --since "today" | grep -v 'Firewall:'

and boot log on CentOS 7

Code (Text):

journalctl -b --no-pager | grep -v 'Firewall:'

Be care not to post these logs publicly as they can contain sensitive info, ips, ssh port numbers etc.

 

Sounds like a probably specific to your OVH server then !

 

I'd contact OVH tech support

 

Oooh CentOS 7 has systemd analyse feature systemd-analyze

lists the time portion for boot up routines

Code (Text):

systemd-analyze blame --no-pager

Code (Text):

systemd-analyze blame --no-pager
         40.046s home.mount
          6.237s network.service
          5.245s backup.mount
           868ms mariadb.service
           310ms postfix.service
           253ms dev-md1.device
           246ms lvm2-monitor.service
           238ms csf.service
           219ms microcode.service
           191ms gssproxy.service
           157ms rhel-dmesg.service
           156ms ip6tables.service
           135ms lfd.service
           128ms osqueryd.service
           115ms systemd-logind.service
           112ms nginx.service
           108ms polkit.service
           106ms rpc-statd-notify.service
           102ms dev-sda3.swap
            84ms tuned.service
            82ms systemd-fsck@dev-md2.service
            78ms iptables.service
            75ms rc-local.service
            72ms ntpd.service
            70ms php-fpm.service
            65ms dev-sdb3.swap
            63ms mdmonitor.service
            55ms sysstat.service
            52ms sshd.service
            47ms systemd-vconsole-setup.service
            37ms auditd.service
            37ms var-lib-nfs-rpc_pipefs.mount
            32ms systemd-udevd.service
            30ms systemd-update-utmp.service
            30ms proc-fs-nfsd.mount
            30ms rsyslog.service
            24ms kmod-static-nodes.service
            22ms systemd-tmpfiles-setup-dev.service
            21ms sys-kernel-debug.mount
            20ms systemd-readahead-collect.service
            19ms nfs-config.service
            19ms systemd-tmpfiles-setup.service
            18ms systemd-udev-trigger.service
            17ms dev-hugepages.mount
            15ms systemd-sysctl.service
            15ms dev-mqueue.mount
            15ms systemd-journal-flush.service
            13ms systemd-readahead-replay.service
            13ms systemd-remount-fs.service
            12ms systemd-user-sessions.service
            12ms memcached.service
            10ms rhel-readonly.service
             9ms systemd-journald.service
             8ms systemd-fsck-root.service
             7ms systemd-update-utmp-runlevel.service
             3ms systemd-tmpfiles-clean.service
             2ms systemd-random-seed.service
             1ms sys-kernel-config.mount
             1ms systemd-readahead-done.service
           925us mdadm-last-resort@md2.service

Code (Text):

systemd-analyze --no-pager    
Startup finished in 572ms (kernel) + 632ms (initrd) + 12.971s (userspace) = 14.176s

Code (Text):

systemd-analyze critical-chain --no-pager
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

multi-user.target @12.951s
└─nginx.service @12.832s +112ms
  └─memcached.service @12.813s +12ms
    └─php-fpm.service @12.736s +70ms
      └─remote-fs.target @12.723s
        └─backup.mount @7.470s +5.245s
          └─network-online.target @7.463s
            └─network.target @7.364s
              └─network.service @1.111s +6.237s
                └─iptables.service @988ms +78ms
                  └─basic.target @793ms
                    └─paths.target @785ms
                      └─brandbot.path @785ms
                        └─sysinit.target @738ms
                          └─systemd-update-utmp.service @698ms +30ms
                            └─auditd.service @650ms +37ms
                              └─systemd-tmpfiles-setup.service @601ms +19ms
                                └─local-fs.target @591ms
                                  └─local-fs-pre.target @427ms
                                    └─lvm2-monitor.service @125ms +246ms
                                      └─lvm2-lvmetad.service @162ms
                                        └─lvm2-lvmetad.socket @115ms
                                          └─-.slice