[SOLVED] Server restarting problem

L

lucascatani

Member
May 28, 2021
11
0
6
39
My server is restarting without my authorization. I need to disable this feature.

Here is the log:

Bash: 
Dec 12 00:00:57 pve systemd[1]: Starting Rotate log files...
Dec 12 00:00:57 pve systemd[1]: Starting Daily man-db regeneration...
Dec 12 00:00:58 pve systemd[1]: Reloading PVE API Proxy Server.
Dec 12 00:00:58 pve systemd[1]: man-db.service: Succeeded.
Dec 12 00:00:58 pve systemd[1]: Finished Daily man-db regeneration.
Dec 12 00:00:59 pve pveproxy[175497]: send HUP to 1385
Dec 12 00:00:59 pve pveproxy[1385]: received signal HUP
Dec 12 00:00:59 pve pveproxy[1385]: server closing
Dec 12 00:00:59 pve pveproxy[1385]: server shutdown (restart)
Dec 12 00:00:59 pve systemd[1]: Reloaded PVE API Proxy Server.
Dec 12 00:00:59 pve systemd[1]: Reloading PVE SPICE Proxy Server.
Dec 12 00:01:00 pve spiceproxy[175500]: send HUP to 1392
Dec 12 00:01:00 pve spiceproxy[1392]: received signal HUP
Dec 12 00:01:00 pve spiceproxy[1392]: server closing
Dec 12 00:01:00 pve spiceproxy[1392]: server shutdown (restart)
Dec 12 00:01:00 pve systemd[1]: Reloaded PVE SPICE Proxy Server.
Dec 12 00:01:00 pve pvefw-logger[984]: received terminate request (signal)
Dec 12 00:01:00 pve pvefw-logger[984]: stopping pvefw logger
Dec 12 00:01:00 pve systemd[1]: Stopping Proxmox VE firewall logger...
Dec 12 00:01:00 pve systemd[1]: pvefw-logger.service: Succeeded.
Dec 12 00:01:00 pve systemd[1]: Stopped Proxmox VE firewall logger.
Dec 12 00:01:00 pve systemd[1]: pvefw-logger.service: Consumed 6.797s CPU time.
Dec 12 00:01:00 pve systemd[1]: Starting Proxmox VE firewall logger...
Dec 12 00:01:00 pve pvefw-logger[175509]: starting pvefw logger
Dec 12 00:01:00 pve systemd[1]: Started Proxmox VE firewall logger.
Dec 12 00:01:00 pve systemd[1]: rsyslog.service: Sent signal SIGHUP to main process 1001 (rsyslogd) on client request.
Dec 12 00:01:00 pve systemd[1]: logrotate.service: Succeeded.
Dec 12 00:01:00 pve systemd[1]: Finished Rotate log files.
Dec 12 00:01:00 pve spiceproxy[1392]: restarting server
Dec 12 00:01:00 pve spiceproxy[1392]: starting 1 worker(s)
Dec 12 00:01:00 pve spiceproxy[1392]: worker 175520 started
Dec 12 00:01:01 pve pveproxy[1385]: restarting server
Dec 12 00:01:01 pve pveproxy[1385]: starting 3 worker(s)
Dec 12 00:01:01 pve pveproxy[1385]: worker 175521 started
Dec 12 00:01:01 pve pveproxy[1385]: worker 175522 started
Dec 12 00:01:01 pve pveproxy[1385]: worker 175523 started
Dec 12 00:01:05 pve spiceproxy[1393]: worker exit
Dec 12 00:01:05 pve spiceproxy[1392]: worker 1393 finished
Dec 12 00:01:06 pve pveproxy[1386]: worker exit
Dec 12 00:01:06 pve pveproxy[1388]: worker exit
Dec 12 00:01:06 pve pveproxy[1387]: worker exit
Dec 12 00:01:06 pve pveproxy[1385]: worker 1386 finished
Dec 12 00:01:06 pve pveproxy[1385]: worker 1388 finished
Dec 12 00:01:06 pve pveproxy[1385]: worker 1387 finished
Dec 12 00:11:00 pve rsyslogd[1001]: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="1001" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
Dec 12 00:17:01 pve CRON[177713]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 12 00:17:01 pve CRON[177714]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 12 00:17:01 pve CRON[177713]: pam_unix(cron:session): session closed for user root
Dec 12 00:24:01 pve CRON[178680]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 12 00:24:01 pve CRON[178681]: (root) CMD (if [ $(date +%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ]; then /usr/lib/zfs-linux/scrub; fi)
Dec 12 00:24:01 pve CRON[178680]: pam_unix(cron:session): session closed for user root
Dec 12 00:30:57 pve systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab...
Dec 12 00:30:57 pve systemd[1]: fstrim.service: Succeeded.
Dec 12 00:30:57 pve systemd[1]: Finished Discard unused blocks on filesystems from /etc/fstab.
Dec 12 01:17:01 pve CRON[185976]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 12 01:17:01 pve CRON[185977]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 12 01:17:01 pve CRON[185976]: pam_unix(cron:session): session closed for user root
Dec 12 01:30:11 pve systemd[1]: Starting Daily PVE download activities...
Dec 12 01:30:14 pve pveupdate[187794]: <root@pam> starting task UPID:pve:0002DD97:00794216:6396AE56:aptupdate::root@pam:
Dec 12 01:30:17 pve pveupdate[187799]: update new package list: /var/lib/pve-manager/pkgupdates
Dec 12 01:30:21 pve pveupdate[187794]: <root@pam> end task UPID:pve:0002DD97:00794216:6396AE56:aptupdate::root@pam: OK
Dec 12 01:30:21 pve systemd[1]: pve-daily-update.service: Succeeded.
Dec 12 01:30:21 pve systemd[1]: Finished Daily PVE download activities.
Dec 12 01:30:21 pve systemd[1]: pve-daily-update.service: Consumed 5.973s CPU time.
Dec 12 02:17:01 pve CRON[194580]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 12 02:17:01 pve CRON[194581]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 12 02:17:01 pve CRON[194580]: pam_unix(cron:session): session closed for user root
Dec 12 03:00:09 pve kernel: tg3 0000:01:00.0 eno1: Link is down
Dec 12 03:00:09 pve kernel: vmbr0: port 1(eno1) entered disabled state
Dec 12 03:01:12 pve kernel: tg3 0000:01:00.0 eno1: Link is up at 1000 Mbps, full duplex
Dec 12 03:01:12 pve kernel: tg3 0000:01:00.0 eno1: Flow control is off for TX and off for RX
Dec 12 03:01:12 pve kernel: tg3 0000:01:00.0 eno1: EEE is disabled
Dec 12 03:01:12 pve kernel: vmbr0: port 1(eno1) entered blocking state
Dec 12 03:01:12 pve kernel: vmbr0: port 1(eno1) entered forwarding state
Dec 12 03:10:01 pve CRON[201851]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 12 03:10:01 pve CRON[201852]: (root) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /sbin/e2scrub_all -A -r)
Dec 12 03:10:01 pve CRON[201851]: pam_unix(cron:session): session closed for user root
Dec 12 03:17:01 pve CRON[202814]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 12 03:17:01 pve CRON[202815]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 12 03:17:01 pve CRON[202814]: pam_unix(cron:session): session closed for user root
Dec 12 03:41:47 pve systemd[1]: Starting Cleanup of Temporary Directories...
Dec 12 03:41:47 pve systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Dec 12 03:41:47 pve systemd[1]: Finished Cleanup of Temporary Directories.
Dec 12 04:17:01 pve CRON[211127]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 12 04:17:01 pve CRON[211128]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 12 04:17:01 pve CRON[211127]: pam_unix(cron:session): session closed for user root
Dec 12 05:17:01 pve CRON[219357]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
 
There is no feature that would come out of the box with proxmox that would restart your server, except for fencing when running a HA cluster and losing communication to the other nodes.
Are you running a cluster?
 
Dunuin said:
There is no feature that would come out of the box with proxmox that would restart your server, except for fencing when running a HA cluster and losing communication to the other nodes.
Are you running a cluster?
Click to expand...
Standalone node - no cluster defined
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom