Differences

This shows you the differences between two versions of the page.

--- wiki:logs1 [2026/09/04 07:50] – wagner.jer
+++ wiki:logs1 [2026/09/04 08:51] (current) – wagner.jer
@@ Line 1: / Line 1: @@
-<code>
+<code>root@localhost [ ~ ]# service-control --status vmdird
-root@LX-VV-VC-001 [ ~ ]# ps aux | grep -i upgrade
+Stopped:
-root     64061  0.0  0.0  14032   764 pts/0    S+   09:46   0:00 grep --color=auto -i upgrade
+ vmdird
-root@LX-VV-VC-001 [ ~ ]# df -h
+root@localhost [ ~ ]# service-control --start vmdird
-Filesystem                                Size  Used Avail Use% Mounted on
+Operation not cancellable. Please wait for it to finish...
-devtmpfs                                   13G     0   13G   0% /dev
+Performing start operation on service vmdird...
-tmpfs                                      13G  1.4M   13G   1% /dev/shm
+Successfully started service vmdird
-tmpfs                                      13G  1.2M   13G   1% /run
+root@localhost [ ~ ]# /usr/lib/vmware-vmafd/bin/vmafd-cli get-machine-id --server-name localhost
-tmpfs                                      13G     0   13G   0% /sys/fs/cgroup
+Error 90021: The system is not joined to a domain
-/dev/mapper/vg_root_0-lv_root_0            47G   12G   33G  27% /
+root@localhost [ ~ ]# /usr/lib/vmware-vmafd/bin/vmafd-cli get-domain-name --server-name localhost
-tmpfs                                      13G  6.7M   13G   1% /tmp
+Error 2: Object/Configuration not found.
-/dev/mapper/imagebuilder_vg-imagebuilder  9.8G   44K  9.3G   1% /storage/imagebuilder
+Verify configuration value has been set.
-/dev/mapper/db_vg-db                      9.8G  3.0G  6.3G  33% /storage/db
+root@localhost [ ~ ]# /usr/lib/vmware-vmafd/bin/vmafd-cli get-pnid --server-name localhost
-/dev/mapper/dblog_vg-dblog                 15G  241M   14G   2% /storage/dblog
+Error 2: Object/Configuration not found.
-/dev/mapper/core_vg-core                   49G  1.8G   45G   4% /storage/core
+Verify configuration value has been set.
-/dev/mapper/lifecycle_vg-lifecycle         98G  4.5G   89G   5% /storage/lifecycle
+root@localhost [ ~ ]# service-control --start applmgmt
-/dev/mapper/archive_vg-archive             49G   25G   23G  53% /storage/archive
+Operation not cancellable. Please wait for it to finish...
-/dev/mapper/netdump_vg-netdump            982M   24K  915M   1% /storage/netdump
+Performing start operation on service applmgmt...
-/dev/mapper/autodeploy_vg-autodeploy      9.8G   40K  9.3G   1% /storage/autodeploy
+Error executing start on service applmgmt. Details {
-/dev/mapper/vtsdblog_vg-vtsdblog           15G   33M   14G   1% /storage/vtsdblog
+    "detail": [
-/dev/mapper/updatemgr_vg-updatemgr         98G  2.3G   91G   3% /storage/updatemgr
+        {
-/dev/mapper/log_vg-log                     50G   15G   33G  31% /storage/log
+            "id": "install.ciscommon.service.failstart",
-/dev/sda3                                 488M   30M  422M   7% /boot
+            "translatable": "An error occurred while starting service '%(0)s'",
-/dev/mapper/vtsdb_vg-vtsdb                541G   34M  513G   1% /storage/vtsdb
+            "args": [
-/dev/mapper/seat_vg-seat                  541G  1.2G  512G   1% /storage/seat
+                "applmgmt"
-/dev/sda2                                  10M  2.2M  7.9M  22% /boot/efi
+            ],
-root@LX-VV-VC-001 [ ~ ]# free -m
+            "localized": "An error occurred while starting service 'applmgmt'"
-              total        used        free      shared  buff/cache   available
+        }
-Mem:          25085       12493        1500         706       11091       11555
+    ],
-Swap:         25591         210       25381
+    "componentKey": null,
-root@LX-VV-VC-001 [ ~ ]# dmesg | tail -50
+    "problemId": null,
-[    5.311621] systemd[1]: Detected virtualization vmware.
+    "resolution": null
-[    5.311623] systemd[1]: Detected architecture x86-64.
+}
-[    5.311921] systemd[1]: Set hostname to <LX-VV-VC-001.d7029d001.bradesco.lu>.
+Service-control failed. Error: {
-[    5.514025] systemd[1]: File /lib/systemd/system/systemd-journald.service:36 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
+    "detail": [
-[    5.514027] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
+        {
-[    5.518935] systemd[1]: /lib/systemd/system/systemd-udevd.service:32: Unknown lvalue 'RestrictSUIDSGID' in section 'Service'
+            "id": "install.ciscommon.service.failstart",
-[    5.533689] systemd[1]: /lib/systemd/system/systemd-networkd.service:37: Unknown lvalue 'RestrictSUIDSGID' in section 'Service'
+            "translatable": "An error occurred while starting service '%(0)s'",
-[    5.544608] systemd[1]: Configuration file /lib/systemd/system/vmware-pod.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
+            "args": [
-[    5.550680] systemd[1]: Configuration file /lib/systemd/system/observability.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
+                "applmgmt"
-[    5.609987] audit: type=1305 audit(1788363976.287:7): audit_enabled=1 old=1 auid=4294967295 ses=4294967295 subj=unconfined res=1
+            ],
-[    5.615780] EXT4-fs (dm-0): re-mounted. Opts: (null)
+            "localized": "An error occurred while starting service 'applmgmt'"
-[    5.620456] Adding 26206204k swap on /dev/mapper/swap_vg-swap1.  Priority:-2 extents:1 across:26206204k
+        }
-[    5.634576] systemd-journald[1328]: Received request to flush runtime journal from PID 1
+    ],
-[    5.716822] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
+    "componentKey": null,
-[    5.716861] ACPI: Power Button [PWRF]
+    "problemId": null,
-[    5.721366] ACPI: AC Adapter [ACAD] (on-line)
+    "resolution": null
-[    5.796245] piix4_smbus 0000:00:07.3: SMBus Host Controller not enabled!
+}
-[    5.796928] vmw_vmci 0000:00:07.7: Found VMCI PCI device at 0x11080, irq 16
+root@localhost [ ~ ]#
-[    5.797034] vmw_vmci 0000:00:07.7: Using capabilities 0x8000000c
-[    5.797501] Guest personality initialized and is active
-[    5.797617] VMCI host device registered (name=vmci, major=10, minor=58)
-[    5.797617] Initialized host personality
-[    5.797693] agpgart-intel 0000:00:00.0: Intel 440BX Chipset
-[    5.798402] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0x0
-[    6.077133] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4
-[    6.079578] mousedev: PS/2 mouse device common for all mice
-[    6.369590] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
-[    6.374030] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
-[    6.376632] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
-[    6.377012] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
-[    6.377248] EXT4-fs (dm-13): mounted filesystem with ordered data mode. Opts: (null)
-[    6.377380] EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: (null)
-[    6.377604] EXT4-fs (dm-9): mounted filesystem with ordered data mode. Opts: (null)
-[    6.377815] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
-[    6.378914] EXT4-fs (dm-8): mounted filesystem with ordered data mode. Opts: (null)
-[    6.380295] EXT4-fs (dm-11): mounted filesystem with ordered data mode. Opts: (null)
-[    6.380456] EXT4-fs (sda3): Mount option "noacl" will be removed by 3.5
-               Contact linux-ext4@vger.kernel.org if you think we should keep it.
-[    6.384695] EXT4-fs (dm-14): mounted filesystem with ordered data mode. Opts: (null)
-[    6.391012] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: noacl
-[    6.391158] EXT4-fs (dm-7): mounted filesystem with ordered data mode. Opts: (null)
-[    6.392230] EXT4-fs (dm-12): mounted filesystem with ordered data mode. Opts: (null)
-[    6.407048] FAT-fs (sda2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
-[    6.438317] vmxnet3 0000:03:00.0 eth0: intr type 3, mode 0, 5 vectors allocated
-[    6.439183] vmxnet3 0000:03:00.0 eth0: NIC Link is Up 10000 Mbps
-[    6.506457] NET: Registered protocol family 40
-[    6.897796] bpfilter: Loaded bpfilter_umh pid 1778
-[    7.878299] vmxnet3 0000:03:00.0 eth0: intr type 3, mode 0, 5 vectors allocated
-[    7.879470] vmxnet3 0000:03:00.0 eth0: NIC Link is Up 10000 Mbps
-root@LX-VV-VC-001 [ ~ ]# tail -100 /var/log/vmware/upgrade/upgrade-requirements.log | grep -i -E
-Usage: grep [OPTION]... PATTERN [FILE]...
-tail: cannot open '/var/log/vmware/upgrade/upgrade-requirements.log' for reading: No such file or directory
-Try 'grep --help' for more information.
-root@LX-VV-VC-001 [ ~ ]# cd /var/log/vmware/upgrade/
-root@LX-VV-VC-001 [ /var/log/vmware/upgrade ]# ls
-bootstrap.log                                                                     CollectRequirements_com.vmware.vcha_2026_09_04_09_20.log
-CollectRequirements_com.vmware.analytics_2026_09_04_09_20.log                     CollectRequirements_com.vmware.vcIntegrity_2026_09_04_09_20.log
-CollectRequirements_com.vmware.applmgmt_2026_09_04_09_20.log                      CollectRequirements_com.vmware.vdtc_2026_09_04_09_20.log
-CollectRequirements_com.vmware.backup_restore_2026_09_04_09_20.log                CollectRequirements_com.vmware.vlcm_2026_09_04_09_20.log
-CollectRequirements_com.vmware.cls_2026_09_04_09_20.log                           CollectRequirements_com.vmware.vmafd_2026_09_04_09_20.log
-CollectRequirements_com.vmware.common_upgrade_2026_09_04_09_20.log                CollectRequirements_com.vmware.vmon_2026_09_04_09_20.log
-CollectRequirements_com.vmware.eam_2026_09_04_09_20.log                           CollectRequirements_com.vmware.vpxd_2026_09_04_09_20.log
-CollectRequirements_com.vmware.infraprofile_2026_09_04_09_20.log                  CollectRequirements_com.vmware.vsan-health_2026_09_04_09_20.log
-CollectRequirements_com.vmware.license_2026_09_04_09_20.log                       CollectRequirements_com.vmware.vsphere-ui_2026_09_04_09_20.log
-CollectRequirements_com.vmware.netdump_2026_09_04_09_20.log                       CollectRequirements_com.vmware.vstats_2026_09_04_09_20.log
-CollectRequirements_com.vmware.observability_2026_09_04_09_20.log                 CollectRequirements_com.vmware.vtsdb_2026_09_04_09_20.log
-CollectRequirements_com.vmware.rbd_2026_09_04_09_20.log                           CollectRequirements_com.vmware.wcp_2026_09_04_09_20.log
-CollectRequirements_com.vmware.rhttpproxy_2026_09_04_09_20.log                    requirements-upgrade-runner.log
-CollectRequirements_com.vmware.second_party_product_upgrade_2026_09_04_09_20.log  upgrade-post-import.log
-CollectRequirements_com.vmware.snmpd_2026_09_04_09_20.log                         upgrade-source-requirements.log
-CollectRequirements_com.vmware.sps_2026_09_04_09_20.log                           ur-shutdown-GkWeHgbpw9.log
-CollectRequirements_com.vmware.sso_2026_09_04_09_20.log                           vcdb_req.err
-CollectRequirements_com.vmware.syslog_2026_09_04_09_20.log                        vcdb_req.out
-CollectRequirements_com.vmware.vcdb_2026_09_04_09_20.log                          vcdb_warning.log
-root@LX-VV-VC-001 [ /var/log/vmware/upgrade ]# tail -100 /var/log/vmware/upgrade/upgrade-source-requirements.log | grep -i -E
-Usage: grep [OPTION]... PATTERN [FILE]...
-Try 'grep --help' for more information.
-root@LX-VV-VC-001 [ /var/log/vmware/upgrade ]# tail -100 bootstraper.log
-tail: cannot open 'bootstraper.log' for reading: No such file or directory
 </code>