Logs Partition Full
-
now problem with log again!
deamon.log is 1.7 GBlast 100 entries:
Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.460587:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.460752:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.460890:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.461047:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.461313:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.461465:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.461686:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.461814:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.461966:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.462051:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.462235:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.462342:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.463051:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.463198:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Jun 11 23:56:34 df-c01-node04 qemu-dm-1[15460]: 15460@1591912594.463294:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2
Idea why?
-
@x-rayd I edited your post, please use Markdown syntax next time for logs, it's easier to read
-
No idea?
-
May want to review this thread. What version of Xentools / XCPTools are you running on each VM?
-
@Danp said in Logs Partition Full:
May want to review this thread. What version of Xentools / XCPTools are you running on each VM?
We migrade all vmยดs from citrix xenserver 6.0
-
xentools is from citrix-xenserver. must change?
-
Probably... you should check to see what version is running on each VM and report back.
-
@Danp said in Logs Partition Full:
Probably... you should check to see what version is running on each VM and report back.
What is command for check?
-
Easiest option is to check each VM's Advanced tab in XO.
-
Xen Tools version is 6.1 and 6.5
-
no idea?
-
It might be related to the PV drivers inside a Windows guest I suppose.
-
we have one VM Windows Server2003 with old Xen Tools.
But if uninstall old xen tool and install new XCP Tools, after reboor VM not work. Why? -
You can find information about the guest tools at https://xcp-ng.org/docs/guests.html#windows
If the XCP-ng tools do not work for you, you can very well install recent Citrix tools (they are present on any Citrix Hypervisor installation ISO, for example) instead. If that fails too, then check the clean-up instructions in ours docs.
-
I'm not surprised you have issues with Windows Server 2003 (this is probably generating a ton of logs).
After all, this OS is 17 years old, so "why it doesn't work" after you install modern tools on it seems a rhetorical question.
It's also not officially supported by Citrix anymore, so I suppose there's good reasons (like Windows XP).
The real question is: should it rotate the logs anyway before it's full? I think it should yes, and that's the problem.
-
@x-rayd Try with XT 6.5 (this is what I use on the one 2003 server that I still support).
-
last daemon.log
Jun 17 00:23:08 df-c01-node04 squeezed[1275]: [4150926.54] watch /control/feature-balloon <- 1 Jun 17 00:23:08 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /control/feature-balloon <- 1 Jun 17 00:23:08 df-c01-node04 squeezed[1275]: [4150926.58] watch /data/updated <- Wed Jun 17 00:23:08 2020 Jun 17 00:23:08 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated <- Wed Jun 17 00:23:08 2020 Jun 17 00:23:08 df-c01-node04 squeezed[1275]: [4150926.75] watch /data/updated <- Wed Jun 17 00:23:08 CEST 2020 Jun 17 00:23:08 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated <- Wed Jun 17 00:23:08 CEST 2020 Jun 17 00:23:10 df-c01-node04 squeezed[1275]: [4150928.15] watch /data/updated <- Wed Jun 17 00:23:10 2020 Jun 17 00:23:10 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated <- Wed Jun 17 00:23:10 2020 Jun 17 00:23:10 df-c01-node04 squeezed[1275]: [4150928.15] watch /data/updated <- Wed Jun 17 00:23:10 2020 Jun 17 00:23:10 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated <- Wed Jun 17 00:23:10 2020 Jun 17 00:23:16 df-c01-node04 squeezed[1275]: [4150934.19] watch /control/feature-balloon <- 1 Jun 17 00:23:16 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /control/feature-balloon <- 1 Jun 17 00:23:16 df-c01-node04 squeezed[1275]: [4150934.26] watch /data/updated <- Wed Jun 17 00:23:16 2020 Jun 17 00:23:16 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated <- Wed Jun 17 00:23:16 2020 Jun 17 00:23:30 df-c01-node04 squeezed[1275]: [4150948.51] watch /data/updated <- Wed Jun 17 00:23:30 CEST 2020 Jun 17 00:23:30 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated <- Wed Jun 17 00:23:30 CEST 2020 Jun 17 00:23:41 df-c01-node04 squeezed[1275]: [4150958.91] watch /data/updated <- 1 Jun 17 00:23:41 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated <- 1 Jun 17 00:23:41 df-c01-node04 squeezed[1275]: [4150959.51] watch /data/updated <- Wed Jun 17 00:23:41 CEST 2020 Jun 17 00:23:41 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated <- Wed Jun 17 00:23:41 CEST 2020 Jun 17 00:23:45 df-c01-node04 squeezed[1275]: [4150963.15] watch /control/feature-balloon <- 1 Jun 17 00:23:45 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /control/feature-balloon <- 1 Jun 17 00:23:45 df-c01-node04 squeezed[1275]: [4150963.26] watch /data/updated <- Wed Jun 17 00:23:45 2020 Jun 17 00:23:45 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated <- Wed Jun 17 00:23:45 2020 Jun 17 00:23:45 df-c01-node04 squeezed[1275]: [4150963.33] watch /data/updated <- Wed Jun 17 00:23:45 CEST 2020 Jun 17 00:23:45 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated <- Wed Jun 17 00:23:45 CEST 2020 Jun 17 00:23:50 df-c01-node04 squeezed[1275]: [4150967.96] watch /data/updated <- Wed Jun 17 00:23:50 CEST 2020 Jun 17 00:23:50 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated <- Wed Jun 17 00:23:50 CEST 2020 Jun 17 00:23:52 df-c01-node04 squeezed[1275]: [4150970.10] watch /data/updated <- Wed Jun 17 00:23:52 2020 Jun 17 00:23:52 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated <- Wed Jun 17 00:23:52 2020 Jun 17 00:23:53 df-c01-node04 squeezed[1275]: [4150971.35] watch /data/updated <- Wed Jun 17 00:23:53 2020 Jun 17 00:23:53 df-c01-node04 squeezed: [debug|df-c01-node04|3 ||xen[16:56 df-c01-node04 log]# ```~~~~
-
@x-rayd said in Logs Partition Full:
squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated
no idea?
-
Is the last lost indicating a problem to you? One message per second remains a lot but not enough to fill your log partition, contrarily to the messages that you posted earlier about XENBUS and XENVIF, that were flooding at a really quick pace.
-
Im delete daemon.log, but command df -h say partition is full, why?
/dev/sda5 3.9G 3.9G 0 100% /var/log