Proxmox 4 : Reboot after logrotate !!

hregis

hregis

Well-Known Member
Feb 11, 2011
49
1
46
France
www.inodbox.com
Hello

the host server reboot after logrotate ???

logs before logrotate :

Code: 
Apr  4 06:25:01 ns3006172 CRON[27080]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Apr  4 06:25:03 ns3006172 pveproxy[19518]: received signal TERM
Apr  4 06:25:03 ns3006172 pveproxy[19518]: server closing
Apr  4 06:25:03 ns3006172 pveproxy[19519]: worker exit
Apr  4 06:25:03 ns3006172 pveproxy[21915]: worker exit
Apr  4 06:25:03 ns3006172 pveproxy[19521]: worker exit
Apr  4 06:25:03 ns3006172 pveproxy[19518]: worker 19519 finished
Apr  4 06:25:03 ns3006172 pveproxy[19518]: worker 21915 finished
Apr  4 06:25:03 ns3006172 pveproxy[19518]: worker 19521 finished
Apr  4 06:25:03 ns3006172 pveproxy[19518]: server stopped
Apr  4 06:25:08 ns3006172 pveproxy[27885]: starting server
Apr  4 06:25:08 ns3006172 pveproxy[27885]: starting 3 worker(s)
Apr  4 06:25:08 ns3006172 pveproxy[27885]: worker 27886 started
Apr  4 06:25:08 ns3006172 pveproxy[27885]: worker 27887 started
Apr  4 06:25:08 ns3006172 pveproxy[27885]: worker 27888 started
Apr  4 06:25:09 ns3006172 spiceproxy[19770]: received signal TERM
Apr  4 06:25:09 ns3006172 spiceproxy[19770]: server closing
Apr  4 06:25:09 ns3006172 spiceproxy[19771]: worker exit
Apr  4 06:25:09 ns3006172 spiceproxy[19770]: worker 19771 finished
Apr  4 06:25:09 ns3006172 spiceproxy[19770]: server stopped
Apr  4 06:25:10 ns3006172 spiceproxy[28017]: starting server
Apr  4 06:25:10 ns3006172 spiceproxy[28017]: starting 1 worker(s)
Apr  4 06:25:10 ns3006172 spiceproxy[28017]: worker 28018 started
Apr  4 06:25:10 ns3006172 pvepw-logger[19804]: received terminate request (signal)
Apr  4 06:25:10 ns3006172 pvepw-logger[19804]: stopping pvefw logger
Apr  4 06:25:11 ns3006172 pvepw-logger[28059]: starting pvefw logger
Apr  4 06:25:11 ns3006172 rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="4232" x-info="http://www.rsyslog.com"] rsyslogd was HUPed

logs after rotation :

Code: 
-- Logs begin at Mon 2016-04-04 06:36:43 CEST, end at Mon 2016-04-04 09:55:51 CEST. --
Apr 04 06:36:43 ns3006172 systemd-journal[2156]: Runtime journal is using 8.0M (max allowed 641.2M, trying to leave 961.8M free of 6.2G available → current limit 641.2M).
Apr 04 06:36:43 ns3006172 systemd-journal[2156]: Runtime journal is using 8.0M (max allowed 641.2M, trying to leave 961.8M free of 6.2G available → current limit 641.2M).
Apr 04 06:36:43 ns3006172 kernel: Initializing cgroup subsys cpuset
Apr 04 06:36:43 ns3006172 kernel: Initializing cgroup subsys cpu
Apr 04 06:36:43 ns3006172 kernel: Initializing cgroup subsys cpuacct
Apr 04 06:36:43 ns3006172 kernel: Linux version 4.2.8-1-pve (root@elsa) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Sat Mar 19 10:44:29 CET 2016 ()
Apr 04 06:36:43 ns3006172 kernel: Command line: BOOT_IMAGE=/ROOT/pve-1@/boot/vmlinuz-4.2.8-1-pve root=ZFS=rpool/ROOT/pve-1 ro boot=zfs root=ZFS=rpool/ROOT/pve-1 boot=zfs quiet
Apr 04 06:36:43 ns3006172 kernel: KERNEL supported cpus:
Apr 04 06:36:43 ns3006172 kernel:  Intel GenuineIntel
Apr 04 06:36:43 ns3006172 kernel:  AMD AuthenticAMD
Apr 04 06:36:43 ns3006172 kernel:  Centaur CentaurHauls
Apr 04 06:36:43 ns3006172 kernel: x86/fpu: xstate_offset[2]: 0240, xstate_sizes[2]: 0100
Apr 04 06:36:43 ns3006172 kernel: x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
Apr 04 06:36:43 ns3006172 kernel: x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
Apr 04 06:36:43 ns3006172 kernel: x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
Apr 04 06:36:43 ns3006172 kernel: x86/fpu: Enabled xstate features 0x7, context size is 0x340 bytes, using 'standard' format.
Apr 04 06:36:43 ns3006172 kernel: x86/fpu: Using 'eager' FPU context switches.
Apr 04 06:36:43 ns3006172 kernel: e820: BIOS-provided physical RAM map:
Apr 04 06:36:43 ns3006172 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009abff] usable
Apr 04 06:36:43 ns3006172 kernel: BIOS-e820: [mem 0x000000000009ac00-0x000000000009ffff] reserved
Apr 04 06:36:43 ns3006172 kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Apr 04 06:36:43 ns3006172 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000078f89fff] usable
Apr 04 06:36:43 ns3006172 kernel: BIOS-e820: [mem 0x0000000078f8a000-0x00000000798b8fff] reserved
Apr 04 06:36:43 ns3006172 kernel: BIOS-e820: [mem 0x00000000798b9000-0x0000000079d4efff] ACPI NVS
Apr 04 06:36:43 ns3006172 kernel: BIOS-e820: [mem 0x0000000079d4f000-0x000000008fffffff] reserved
Apr 04 06:36:43 ns3006172 kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed44fff] reserved
Apr 04 06:36:43 ns3006172 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Apr 04 06:36:43 ns3006172 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Apr 04 06:36:43 ns3006172 kernel: NX (Execute Disable) protection: active
Apr 04 06:36:43 ns3006172 kernel: SMBIOS 3.0 present.
Apr 04 06:36:43 ns3006172 kernel: DMI: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
Apr 04 06:36:43 ns3006172 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Apr 04 06:36:43 ns3006172 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Apr 04 06:36:43 ns3006172 kernel: e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Apr 04 06:36:43 ns3006172 kernel: MTRR default type: write-back
Apr 04 06:36:43 ns3006172 kernel: MTRR fixed ranges enabled:
Apr 04 06:36:43 ns3006172 kernel:  00000-9FFFF write-back
Apr 04 06:36:43 ns3006172 kernel:  A0000-BFFFF uncachable
Apr 04 06:36:43 ns3006172 kernel:  C0000-FFFFF write-protect
Apr 04 06:36:43 ns3006172 kernel: MTRR variable ranges enabled:
Apr 04 06:36:43 ns3006172 kernel:  0 base 000080000000 mask 3FFF80000000 uncachable
Apr 04 06:36:43 ns3006172 kernel:  1 base 380000000000 mask 3FC000000000 uncachable
Apr 04 06:36:43 ns3006172 kernel:  2 base 0000FBE00000 mask 3FFFFFF00000 write-through
Apr 04 06:36:43 ns3006172 kernel:  3 disabled
Apr 04 06:36:43 ns3006172 kernel:  4 disabled
Apr 04 06:36:43 ns3006172 kernel:  5 disabled
Apr 04 06:36:43 ns3006172 kernel:  6 disabled
Apr 04 06:36:43 ns3006172 kernel:  7 disabled
Apr 04 06:36:43 ns3006172 kernel:  8 disabled
Apr 04 06:36:43 ns3006172 kernel:  9 disabled
Apr 04 06:36:43 ns3006172 kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
Apr 04 06:36:43 ns3006172 kernel: e820: last_pfn = 0x78f8a max_arch_pfn = 0x400000000
Apr 04 06:36:43 ns3006172 kernel: found SMP MP-table at [mem 0x000fd970-0x000fd97f] mapped at [ffff8800000fd970]
Apr 04 06:36:43 ns3006172 kernel: Scanning 1 areas for low memory corruption
Apr 04 06:36:43 ns3006172 kernel: Base memory trampoline at [ffff880000094000] 94000 size 24576
Apr 04 06:36:43 ns3006172 kernel: Using GB pages for direct mapping
Apr 04 06:36:43 ns3006172 kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Apr 04 06:36:43 ns3006172 kernel:  [mem 0x00000000-0x000fffff] page 4k
Apr 04 06:36:43 ns3006172 kernel: BRK [0x0220d000, 0x0220dfff] PGTABLE
Apr 04 06:36:43 ns3006172 kernel: BRK [0x0220e000, 0x0220efff] PGTABLE
Apr 04 06:36:43 ns3006172 kernel: BRK [0x0220f000, 0x0220ffff] PGTABLE
Apr 04 06:36:43 ns3006172 kernel: init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Apr 04 06:36:43 ns3006172 kernel:  [mem 0x87fe00000-0x87fffffff] page 1G
Apr 04 06:36:43 ns3006172 kernel: init_memory_mapping: [mem 0x860000000-0x87fdfffff]
Apr 04 06:36:43 ns3006172 kernel:  [mem 0x860000000-0x87fdfffff] page 1G
Apr 04 06:36:43 ns3006172 kernel: init_memory_mapping: [mem 0x00100000-0x78f89fff]
Apr 04 06:36:43 ns3006172 kernel:  [mem 0x00100000-0x001fffff] page 4k
Apr 04 06:36:43 ns3006172 kernel:  [mem 0x00200000-0x78dfffff] page 2M
Apr 04 06:36:43 ns3006172 kernel:  [mem 0x78e00000-0x78f89fff] page 4k
Apr 04 06:36:43 ns3006172 kernel: init_memory_mapping: [mem 0x100000000-0x85fffffff]
Apr 04 06:36:43 ns3006172 kernel:  [mem 0x100000000-0x85fffffff] page 1G
Apr 04 06:36:43 ns3006172 kernel: RAMDISK: [mem 0x34fe0000-0x367e7fff]
Apr 04 06:36:43 ns3006172 kernel: ACPI: Early table checksum verification disabled
Apr 04 06:36:43 ns3006172 kernel: ACPI: RSDP 0x00000000000F0580 000024 (v02 SUPERM)
Apr 04 06:36:43 ns3006172 kernel: ACPI: XSDT 0x00000000798B9098 0000B4 (v01                01072009 AMI  00010013)

etc.. etc..
 
screenshots in attach-files

Capture d’écran 2016-04-04 à 10.14.48.png
Capture d’écran 2016-04-04 à 10.14.24.png

# pveversion --verbose
proxmox-ve: 4.1-41 (running kernel: 4.2.8-1-pve)
pve-manager: 4.1-22 (running version: 4.1-22/aca130cf)
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.2.8-1-pve: 4.2.8-41
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-36
qemu-server: 4.0-64
pve-firmware: 1.1-7
libpve-common-perl: 4.0-54
libpve-access-control: 4.0-13
libpve-storage-perl: 4.0-45
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-9
pve-container: 1.0-52
pve-firewall: 2.0-22
pve-ha-manager: 1.0-25
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie
Click to expand...
 
You must log in or register to reply here.
Top Bottom