XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Logs Partition Full

    Scheduled Pinned Locked Moved Xen Orchestra
    59 Posts 6 Posters 25.2k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • X Offline
      x-rayd
      last edited by

      No idea?

      1 Reply Last reply Reply Quote 0
      • DanpD Online
        Danp Pro Support Team
        last edited by

        May want to review this thread. What version of Xentools / XCPTools are you running on each VM?

        1 Reply Last reply Reply Quote 0
        • X Offline
          x-rayd
          last edited by

          @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

          1 Reply Last reply Reply Quote 0
          • X Offline
            x-rayd
            last edited by

            xentools is from citrix-xenserver. must change?

            1 Reply Last reply Reply Quote 0
            • DanpD Online
              Danp Pro Support Team
              last edited by

              Probably... you should check to see what version is running on each VM and report back.

              1 Reply Last reply Reply Quote 0
              • X Offline
                x-rayd
                last edited by

                @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?

                1 Reply Last reply Reply Quote 0
                • DanpD Online
                  Danp Pro Support Team
                  last edited by

                  Easiest option is to check each VM's Advanced tab in XO.

                  1 Reply Last reply Reply Quote 0
                  • X Offline
                    x-rayd
                    last edited by

                    Xen Tools version is 6.1 and 6.5

                    1 Reply Last reply Reply Quote 0
                    • X Offline
                      x-rayd
                      last edited by

                      no idea?

                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO Offline
                        olivierlambert Vates 🪐 Co-Founder CEO
                        last edited by

                        It might be related to the PV drivers inside a Windows guest I suppose.

                        1 Reply Last reply Reply Quote 0
                        • X Offline
                          x-rayd
                          last edited by

                          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?

                          DanpD 1 Reply Last reply Reply Quote 0
                          • stormiS Offline
                            stormi Vates 🪐 XCP-ng Team
                            last edited by

                            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.

                            1 Reply Last reply Reply Quote 0
                            • olivierlambertO Offline
                              olivierlambert Vates 🪐 Co-Founder CEO
                              last edited by

                              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.

                              1 Reply Last reply Reply Quote 0
                              • DanpD Online
                                Danp Pro Support Team @x-rayd
                                last edited by

                                @x-rayd Try with XT 6.5 (this is what I use on the one 2003 server that I still support).

                                1 Reply Last reply Reply Quote 0
                                • X Offline
                                  x-rayd
                                  last edited by

                                  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]#
```~~~~
                                  1 Reply Last reply Reply Quote 0
                                  • X Offline
                                    x-rayd
                                    last edited by

                                    @x-rayd said in Logs Partition Full:

                                    squeezed: [debug|df-c01-node04|3 ||xenops] watch /data/updated

                                    no idea?

                                    1 Reply Last reply Reply Quote 0
                                    • stormiS Offline
                                      stormi Vates 🪐 XCP-ng Team
                                      last edited by stormi

                                      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.

                                      1 Reply Last reply Reply Quote 0
                                      • X Offline
                                        x-rayd
                                        last edited by

                                        Im delete daemon.log, but command df -h say partition is full, why?
                                        /dev/sda5 3.9G 3.9G 0 100% /var/log

                                        1 Reply Last reply Reply Quote 0
                                        • stormiS Offline
                                          stormi Vates 🪐 XCP-ng Team
                                          last edited by

                                          You can check what takes space with du -sh /var/log/*

                                          1 Reply Last reply Reply Quote 0
                                          • X Offline
                                            x-rayd
                                            last edited by

                                            @stormi said in Logs Partition Full:

                                            du -sh /var/log/*

                                            [5.1M    /var/log/audit.log
24M     /var/log/audit.log.1
0       /var/log/audit.log.1.gz
3.5M    /var/log/audit.log.2.gz
0       /var/log/audit.log.3.gz
9.3M    /var/log/blktap
0       /var/log/boot.log
24K     /var/log/boot.log.1
4.0K    /var/log/boot.log.2.gz
4.0K    /var/log/boot.log.3.gz
4.0K    /var/log/boot.log.4.gz
4.0K    /var/log/boot.log.5.gz
4.0K    /var/log/btmp
4.0K    /var/log/btmp.1
0       /var/log/btmp.1.gz
4.0K    /var/log/cluster
8.0K    /var/log/crit.log
0       /var/log/crit.log.1
0       /var/log/crit.log.1.gz
2.9M    /var/log/cron
40K     /var/log/cron.1
0       /var/log/cron.1.gz
4.0K    /var/log/grubby_prune_debug
1004K   /var/log/installer
4.0K    /var/log/interface-rename.log
0       /var/log/interface-rename.log.1
0       /var/log/interface-rename.log.1.gz
1.3M    /var/log/kern.log
20K     /var/log/kern.log.1
0       /var/log/kern.log.1.gz
16K     /var/log/lost+found
164K    /var/log/maillog
4.0K    /var/log/maillog.32.gz
0       /var/log/messages
0       /var/log/messages.1
0       /var/log/messages.1.gz
4.0K    /var/log/ntpstats
4.0K    /var/log/openvswitch
4.0K    /var/log/ovs-ctl.log
4.0K    /var/log/ovs-ctl.log.32.gz
4.0K    /var/log/ovsdb-server.log
4.0K    /var/log/ovsdb-server.log.1
0       /var/log/ovsdb-server.log.1.gz
60K     /var/log/ovs-vswitchd.log
4.0K    /var/log/ovs-vswitchd.log.1
0       /var/log/ovs-vswitchd.log.1.gz
4.0K    /var/log/ovs-xapi-sync.log
4.0K    /var/log/ovs-xapi-sync.log.32.gz
8.0K    /var/log/pbis-open-install.log
4.0K    /var/log/pyperthreading-plugin.log
114M    /var/log/sa
8.0K    /var/log/samba
37M     /var/log/secure
5.6M    /var/log/SMlog
29M     /var/log/SMlog.1
0       /var/log/SMlog.1.gz
5.0M    /var/log/SMlog.2.gz
0       /var/log/spooler
4.0K    /var/log/spooler.32.gz
0       /var/log/tallylog
0       /var/log/updater-plugin.log
972K    /var/log/user.log
4.0K    /var/log/user.log.1
0       /var/log/user.log.1.gz
696K    /var/log/VMSSlog
20K     /var/log/VMSSlog.1
0       /var/log/VMSSlog.1.gz
68K     /var/log/wtmp
8.0K    /var/log/xcp-rrdd-plugins.log
13M     /var/log/xcp-rrdd-plugins.log.1
0       /var/log/xcp-rrdd-plugins.log.1.gz
240K    /var/log/xcp-rrdd-plugins.log.2.gz
0       /var/log/xcp-rrdd-plugins.log.3.gz
220K    /var/log/xen
96M     /var/log/xensource.log
18M     /var/log/xensource.log.1
0       /var/log/xensource.log.1.gz
8.2M    /var/log/xensource.log.2.gz
9.2M    /var/log/xensource.log.3.gz
6.5M    /var/log/xensource.log.4.gz
8.0M    /var/log/xenstored-access.log
33M     /var/log/xenstored-access.log.1
0       /var/log/xenstored-access.log.1.gz
2.3M    /var/log/xenstored-access.log.2.gz
4.0K    /var/log/yum.log
36K     /var/log/yum.log.1

                                            Filesystem Size Used Avail Use% Mounted on
                                            devtmpfs 3.9G 112K 3.9G 1% /dev
                                            tmpfs 3.9G 1004K 3.9G 1% /dev/shm
                                            tmpfs 3.9G 12M 3.9G 1% /run
                                            tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
                                            /dev/sda1 18G 2.4G 15G 14% /
                                            xenstore 3.9G 0 3.9G 0% /var/lib/xenstored
                                            /dev/sda5 3.9G 3.9G 0 100% /var/log

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post