VMware启动系统报错，reason: failed to lock the file.

最新推荐文章于 2020-06-05 13:33:40 发布
最新推荐文章于 2020-06-05 13:33:40 发布 · 100 阅读 · 0
文章标签：

#运维 #操作系统

本文解决了一个常见的VMware虚拟机启动问题，错误信息为无法打开磁盘文件或锁定文件失败。提供了包括删除锁定文件、重新映射虚拟硬盘等解决方案。
<!--新闻标题 end--><!--文章内容 begin-->

VMware启动系统报错，出错信息：

Cannot open the disk 'c:/leiansoft/Windows Vista.vmdk' or one of the snapshot disks it depends on.

reason: failed to lock the file.

解决办法：

1、在VMware该虚拟机路径下的所有.lck文件和文件夹下删除或迁移至其它目录，一般就可以解决了。

2、如果再次启动VMware的Windows Vista系统失败，尝试右键虚拟机出错的系统->Settings->Hardware->Hard Disk->Utilities->Map->映射虚拟硬盘到Z:/

3、断开虚拟硬盘，重新加载，启动。系统就可以正常启动了

iteye_3158
关注
在VMware安装K8S
富平男娃
03-03 1327
上面已完成Docker之前的所有安装
OpenStack Mitaka for Ubuntu 16.04 LTS 部署指南
热门推荐
Sam Wong
07-26 1万+
【声明】 欢迎转载，转载本文请注明作者和出处 https://www.zybuluo.com/ncepuwanghui/note/389373 http://blog.csdn.net/ncepuwanghui/article/details/52034515 本文主要参考OpenStack官方文档 OpenStack Documentation for Mitaka : Installati
vmware, failed to lock the file
surgent的专栏
10-31 1681
昨晚电脑死机，进不了桌面，今天早上实在不行就重启，但是在运行着虚拟机，重启后打开VMware虚拟机，提示failed to lock the file，进不去了，急阿，里面不少资料呢。。。问万能的Google，终于得到解答，将loc文件夹下面的loc文件删掉就好，再运行果然ok。。我的VMware是6.5.2。。。以后还是要加小心阿。
虚机打不开报failed to lock the file错误原因及解决方案
zsk804073087的博客
01-10 7248
问题出现的原因： 虚拟磁盘(.vmdk)本身有一个磁盘保护机制，为了防止多台虚拟机同时访问同一个虚拟磁盘(.vmdk)带来的数据丢失和性能削减方面的隐患，每次启动虚拟机的时候虚拟机会使用扩展名为.lck（磁盘锁）文件对虚拟磁盘(.vmdk)进行锁定保护。当虚拟机关闭时.lck（磁盘锁）文件自动删除。但是可能由于您非正常关闭虚拟机，这时虚拟机还没来得及删除您系统上的.lck（磁盘锁）文件，所以当下
VMware vmdk错误： Failed to lock the file.
ck1694的博客
12-13 287
问题： 打开VMware出现Cannot open the disk *.vmdk or one of the snapshot disks it depends on.Reason: Failed to lock t...
VM server磁盘：failed to lock the file.
DATA
04-11 1681
在使用VMserver 虚拟机上安装RAC，共享了磁盘，开机时出现这样的问题：   cannot open the disk '...' or one of the snapshot disks it depends on. reason:failed to lock the file.   在各个虚拟机中加入以下一条可解决： disk.locking = "FALSE"
运行rabbitmq日志2025-07-30 08:44:54.598 [debug] <0.287.0> Lager installed handler {lager_file_backend, "d:/Downloads/RabbitMQData/log/rabbit@LAPTOP-FU2L4D12.log"} into lager_event 2025-07-30 08:44:54.598 [debug] <0.290.0> Lager installed handler error_logger_lager_h into error_logger 2025-07-30 08:44:54.608 [debug] <0.293.0> Lager installed handler lager_forwarder_backend into error_logger_lager_event 2025-07-30 08:44:54.608 [debug] <0.296.0> Lager installed handler lager_forwarder_backend into rabbit_log_lager_event 2025-07-30 08:44:54.608 [debug] <0.299.0> Lager installed handler lager_forwarder_backend into rabbit_log_channel_lager_event 2025-07-30 08:44:54.608 [debug] <0.302.0> Lager installed handler lager_forwarder_backend into rabbit_log_connection_lager_event 2025-07-30 08:44:54.608 [debug] <0.305.0> Lager installed handler lager_forwarder_backend into rabbit_log_feature_flags_lager_event 2025-07-30 08:44:54.608 [debug] <0.308.0> Lager installed handler lager_forwarder_backend into rabbit_log_federation_lager_event 2025-07-30 08:44:54.608 [debug] <0.311.0> Lager installed handler lager_forwarder_backend into rabbit_log_ldap_lager_event 2025-07-30 08:44:54.608 [debug] <0.317.0> Lager installed handler lager_forwarder_backend into rabbit_log_prelaunch_lager_event 2025-07-30 08:44:54.608 [debug] <0.314.0> Lager installed handler lager_forwarder_backend into rabbit_log_mirroring_lager_event 2025-07-30 08:44:54.608 [debug] <0.320.0> Lager installed handler lager_forwarder_backend into rabbit_log_queue_lager_event 2025-07-30 08:44:54.608 [debug] <0.323.0> Lager installed handler lager_forwarder_backend into rabbit_log_ra_lager_event 2025-07-30 08:44:54.608 [debug] <0.326.0> Lager installed handler lager_forwarder_backend into rabbit_log_shovel_lager_event 2025-07-30 08:44:54.608 [debug] <0.329.0> Lager installed handler {lager_file_backend, "d:/Downloads/RabbitMQData/log/rabbit@LAPTOP-FU2L4D12_upgrade.log"} into rabbit_log_upgrade_lager_event 2025-07-30 08:44:54.619 [info] <0.44.0> Application lager started on node 'rabbit@LAPTOP-FU2L4D12' 2025-07-30 08:44:54.633 [info] <0.273.0> Log file opened with Lager 2025-07-30 08:44:54.996 [info] <0.44.0> Application mnesia started on node 'rabbit@LAPTOP-FU2L4D12' 2025-07-30 08:44:54.998 [info] <0.273.0> Starting RabbitMQ 3.8.8 on Erlang 23.3.4.18 Copyright (c) 2007-2020 VMware, Inc. or its affiliates. Licensed under the MPL 2.0. Website: https://rabbitmq.com 2025-07-30 08:44:54.998 [info] <0.273.0> node : rabbit@LAPTOP-FU2L4D12 home dir : C:\Users\小橙 config file(s) : (none) cookie hash : mkQxrMfpOoR5L3HCS5ZoGA== log(s) : d:/Downloads/RabbitMQData/log/rabbit@LAPTOP-FU2L4D12.log : d:/Downloads/RabbitMQData/log/rabbit@LAPTOP-FU2L4D12_upgrade.log database dir : d:/Downloads/RabbitMQData/db/rabbit@LAPTOP-FU2L4D12-mnesia 2025-07-30 08:44:55.053 [debug] <0.285.0> Lager installed handler lager_backend_throttle into lager_event 2025-07-30 08:44:59.279 [info] <0.273.0> Running boot step pre_boot defined by app rabbit 2025-07-30 08:44:59.279 [info] <0.273.0> Running boot step rabbit_core_metrics defined by app rabbit 2025-07-30 08:44:59.279 [info] <0.273.0> Running boot step rabbit_alarm defined by app rabbit 2025-07-30 08:44:59.281 [info] <0.361.0> Memory high watermark set to 6473 MiB (6787769958 bytes) of 16183 MiB (16969424896 bytes) total 2025-07-30 08:44:59.480 [info] <0.363.0> Enabling free disk space monitoring 2025-07-30 08:44:59.480 [info] <0.363.0> Disk free limit set to 50MB 2025-07-30 08:44:59.524 [info] <0.273.0> Running boot step code_server_cache defined by app rabbit 2025-07-30 08:44:59.524 [info] <0.273.0> Running boot step file_handle_cache defined by app rabbit 2025-07-30 08:44:59.524 [info] <0.366.0> Limiting to approx 65439 file handles (58893 sockets) 2025-07-30 08:44:59.524 [info] <0.367.0> FHC read buffering: OFF 2025-07-30 08:44:59.524 [info] <0.367.0> FHC write buffering: ON 2025-07-30 08:44:59.525 [info] <0.273.0> Running boot step worker_pool defined by app rabbit 2025-07-30 08:44:59.525 [info] <0.351.0> Will use 8 processes for default worker pool 2025-07-30 08:44:59.525 [info] <0.351.0> Starting worker pool 'worker_pool' with 8 processes in it 2025-07-30 08:44:59.525 [info] <0.273.0> Running boot step database defined by app rabbit 2025-07-30 08:44:59.526 [info] <0.273.0> Node database directory at d:/Downloads/RabbitMQData/db/rabbit@LAPTOP-FU2L4D12-mnesia is empty. Assuming we need to join an existing cluster or initialise from scratch... 2025-07-30 08:44:59.526 [info] <0.273.0> Configured peer discovery backend: rabbit_peer_discovery_classic_config 2025-07-30 08:44:59.526 [info] <0.273.0> Will try to lock with peer discovery backend rabbit_peer_discovery_classic_config 2025-07-30 08:44:59.526 [info] <0.273.0> Peer discovery backend does not support locking, falling back to randomized delay 2025-07-30 08:44:59.526 [info] <0.273.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping randomized startup delay. 2025-07-30 08:44:59.526 [info] <0.273.0> All discovered existing cluster peers: 2025-07-30 08:44:59.526 [info] <0.273.0> Discovered no peer nodes to cluster with. Some discovery backends can filter nodes out based on a readiness criteria. Enabling debug logging might help troubleshoot. 2025-07-30 08:44:59.533 [info] <0.44.0> Application mnesia exited with reason: stopped 2025-07-30 08:44:59.533 [info] <0.44.0> Application mnesia exited with reason: stopped 2025-07-30 08:44:59.553 [info] <0.44.0> Application mnesia started on node 'rabbit@LAPTOP-FU2L4D12' 2025-07-30 08:44:59.608 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left 2025-07-30 08:44:59.608 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.622 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left 2025-07-30 08:44:59.622 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.622 [info] <0.273.0> Feature flag `implicit_default_bindings`: supported, attempt to enable... 2025-07-30 08:44:59.622 [info] <0.273.0> Feature flag `implicit_default_bindings`: mark as enabled=state_changing 2025-07-30 08:44:59.626 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.626 [info] <0.273.0> Feature flags: [~] implicit_default_bindings 2025-07-30 08:44:59.627 [info] <0.273.0> Feature flags: [ ] maintenance_mode_status 2025-07-30 08:44:59.627 [info] <0.273.0> Feature flags: [ ] quorum_queue 2025-07-30 08:44:59.627 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata 2025-07-30 08:44:59.627 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.643 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 0 retries left 2025-07-30 08:44:59.643 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.643 [info] <0.273.0> Feature flag `implicit_default_bindings`: mark as enabled=true 2025-07-30 08:44:59.649 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.649 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.649 [info] <0.273.0> Feature flags: [ ] maintenance_mode_status 2025-07-30 08:44:59.649 [info] <0.273.0> Feature flags: [ ] quorum_queue 2025-07-30 08:44:59.649 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata 2025-07-30 08:44:59.649 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.661 [info] <0.273.0> Feature flag `maintenance_mode_status`: supported, attempt to enable... 2025-07-30 08:44:59.661 [info] <0.273.0> Feature flag `maintenance_mode_status`: mark as enabled=state_changing 2025-07-30 08:44:59.665 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.665 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.666 [info] <0.273.0> Feature flags: [~] maintenance_mode_status 2025-07-30 08:44:59.666 [info] <0.273.0> Feature flags: [ ] quorum_queue 2025-07-30 08:44:59.666 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata 2025-07-30 08:44:59.666 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.677 [info] <0.273.0> Creating table rabbit_node_maintenance_states for feature flag `maintenance_mode_status` 2025-07-30 08:44:59.680 [info] <0.273.0> Feature flag `maintenance_mode_status`: mark as enabled=true 2025-07-30 08:44:59.686 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.687 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.687 [info] <0.273.0> Feature flags: [x] maintenance_mode_status 2025-07-30 08:44:59.687 [info] <0.273.0> Feature flags: [ ] quorum_queue 2025-07-30 08:44:59.687 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata 2025-07-30 08:44:59.687 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.699 [info] <0.273.0> Feature flag `quorum_queue`: supported, attempt to enable... 2025-07-30 08:44:59.699 [info] <0.273.0> Feature flag `quorum_queue`: mark as enabled=state_changing 2025-07-30 08:44:59.704 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.704 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.704 [info] <0.273.0> Feature flags: [x] maintenance_mode_status 2025-07-30 08:44:59.704 [info] <0.273.0> Feature flags: [~] quorum_queue 2025-07-30 08:44:59.704 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata 2025-07-30 08:44:59.704 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.718 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left 2025-07-30 08:44:59.718 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.718 [info] <0.273.0> Feature flag `quorum_queue`: migrating Mnesia table rabbit_queue... 2025-07-30 08:44:59.734 [info] <0.273.0> Feature flag `quorum_queue`: migrating Mnesia table rabbit_durable_queue... 2025-07-30 08:44:59.751 [info] <0.273.0> Feature flag `quorum_queue`: Mnesia tables migration done 2025-07-30 08:44:59.751 [info] <0.273.0> Feature flag `quorum_queue`: mark as enabled=true 2025-07-30 08:44:59.755 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.756 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.756 [info] <0.273.0> Feature flags: [x] maintenance_mode_status 2025-07-30 08:44:59.756 [info] <0.273.0> Feature flags: [x] quorum_queue 2025-07-30 08:44:59.756 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata 2025-07-30 08:44:59.756 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.772 [info] <0.273.0> Feature flag `virtual_host_metadata`: supported, attempt to enable... 2025-07-30 08:44:59.772 [info] <0.273.0> Feature flag `virtual_host_metadata`: mark as enabled=state_changing 2025-07-30 08:44:59.775 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.775 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.775 [info] <0.273.0> Feature flags: [x] maintenance_mode_status 2025-07-30 08:44:59.775 [info] <0.273.0> Feature flags: [x] quorum_queue 2025-07-30 08:44:59.775 [info] <0.273.0> Feature flags: [~] virtual_host_metadata 2025-07-30 08:44:59.776 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.786 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left 2025-07-30 08:44:59.786 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.807 [info] <0.273.0> Feature flag `virtual_host_metadata`: mark as enabled=true 2025-07-30 08:44:59.812 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.812 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.812 [info] <0.273.0> Feature flags: [x] maintenance_mode_status 2025-07-30 08:44:59.812 [info] <0.273.0> Feature flags: [x] quorum_queue 2025-07-30 08:44:59.812 [info] <0.273.0> Feature flags: [x] virtual_host_metadata 2025-07-30 08:44:59.812 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.823 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left 2025-07-30 08:44:59.824 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.842 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left 2025-07-30 08:44:59.842 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.842 [info] <0.273.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping registration. 2025-07-30 08:44:59.842 [info] <0.273.0> Running boot step database_sync defined by app rabbit 2025-07-30 08:44:59.842 [info] <0.273.0> Running boot step feature_flags defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step codec_correctness_check defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step external_infrastructure defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_registry defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_auth_mechanism_cr_demo defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_queue_location_random defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_event defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_auth_mechanism_amqplain defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_auth_mechanism_plain defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_exchange_type_direct defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_exchange_type_fanout defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_exchange_type_headers defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_exchange_type_topic defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_mirror_queue_mode_all defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_mirror_queue_mode_exactly defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_mirror_queue_mode_nodes defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_priority_queue defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Priority queues enabled, real BQ is rabbit_variable_queue 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_queue_location_client_local defined by app rabbit 2025-07-30 08:44:59.844 [info] <0.273.0> Running boot step rabbit_queue_location_min_masters defined by app rabbit 2025-07-30 08:44:59.844 [info] <0.273.0> Running boot step kernel_ready defined by app rabbit 2025-07-30 08:44:59.844 [info] <0.273.0> Running boot step rabbit_sysmon_minder defined by app rabbit 2025-07-30 08:44:59.844 [info] <0.273.0> Running boot step rabbit_epmd_monitor defined by app rabbit 2025-07-30 08:44:59.845 [info] <0.605.0> epmd monitor knows us, inter-node communication (distribution) port: 25672 2025-07-30 08:44:59.845 [info] <0.273.0> Running boot step guid_generator defined by app rabbit 2025-07-30 08:44:59.848 [info] <0.273.0> Running boot step rabbit_node_monitor defined by app rabbit 2025-07-30 08:44:59.848 [info] <0.609.0> Starting rabbit_node_monitor 2025-07-30 08:44:59.848 [info] <0.273.0> Running boot step delegate_sup defined by app rabbit 2025-07-30 08:44:59.848 [info] <0.273.0> Running boot step rabbit_memory_monitor defined by app rabbit 2025-07-30 08:44:59.849 [info] <0.273.0> Running boot step core_initialized defined by app rabbit 2025-07-30 08:44:59.849 [info] <0.273.0> Running boot step upgrade_queues defined by app rabbit 2025-07-30 08:44:59.859 [info] <0.273.0> message_store upgrades: 1 to apply 2025-07-30 08:44:59.859 [info] <0.273.0> message_store upgrades: Applying rabbit_variable_queue:move_messages_to_vhost_store 2025-07-30 08:44:59.859 [info] <0.273.0> message_store upgrades: No durable queues found. Skipping message store migration 2025-07-30 08:44:59.859 [info] <0.273.0> message_store upgrades: Removing the old message store data 2025-07-30 08:44:59.860 [info] <0.273.0> message_store upgrades: All upgrades applied successfully 2025-07-30 08:44:59.878 [info] <0.273.0> Running boot step rabbit_connection_tracking defined by app rabbit 2025-07-30 08:44:59.879 [info] <0.273.0> Running boot step rabbit_connection_tracking_handler defined by app rabbit 2025-07-30 08:44:59.879 [info] <0.273.0> Running boot step rabbit_exchange_parameters defined by app rabbit 2025-07-30 08:44:59.879 [info] <0.273.0> Running boot step rabbit_mirror_queue_misc defined by app rabbit 2025-07-30 08:44:59.879 [info] <0.273.0> Running boot step rabbit_policies defined by app rabbit 2025-07-30 08:44:59.880 [info] <0.273.0> Running boot step rabbit_policy defined by app rabbit 2025-07-30 08:44:59.880 [info] <0.273.0> Running boot step rabbit_queue_location_validator defined by app rabbit 2025-07-30 08:44:59.880 [info] <0.273.0> Running boot step rabbit_quorum_memory_manager defined by app rabbit 2025-07-30 08:44:59.880 [info] <0.273.0> Running boot step rabbit_vhost_limit defined by app rabbit 2025-07-30 08:44:59.880 [info] <0.273.0> Running boot step recovery defined by app rabbit 2025-07-30 08:44:59.881 [info] <0.273.0> Running boot step empty_db_check defined by app rabbit 2025-07-30 08:44:59.881 [info] <0.273.0> Will seed default virtual host and user... 2025-07-30 08:44:59.881 [info] <0.273.0> Adding vhost '/' (description: 'Default virtual host') 2025-07-30 08:44:59.886 [info] <0.646.0> Making sure data directory 'd:/Downloads/RabbitMQData/db/rabbit@LAPTOP-FU2L4D12-mnesia/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L' for vhost '/' exists 2025-07-30 08:44:59.889 [info] <0.646.0> Starting message stores for vhost '/' 2025-07-30 08:44:59.889 [info] <0.650.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_transient": using rabbit_msg_store_ets_index to provide index 2025-07-30 08:44:59.891 [info] <0.646.0> Started message store of type transient for vhost '/' 2025-07-30 08:44:59.891 [info] <0.654.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": using rabbit_msg_store_ets_index to provide index 2025-07-30 08:44:59.892 [warning] <0.654.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": rebuilding indices from scratch 2025-07-30 08:44:59.893 [info] <0.646.0> Started message store of type persistent for vhost '/' 2025-07-30 08:44:59.896 [info] <0.273.0> Created user 'guest' 2025-07-30 08:44:59.896 [info] <0.273.0> Successfully set user tags for user 'guest' to [administrator] 2025-07-30 08:44:59.897 [info] <0.273.0> Successfully set permissions for 'guest' in virtual host '/' to '.*', '.*', '.*' 2025-07-30 08:44:59.897 [info] <0.273.0> Running boot step rabbit_looking_glass defined by app rabbit 2025-07-30 08:44:59.897 [info] <0.273.0> Running boot step rabbit_core_metrics_gc defined by app rabbit 2025-07-30 08:44:59.897 [info] <0.273.0> Running boot step background_gc defined by app rabbit 2025-07-30 08:44:59.897 [info] <0.273.0> Running boot step connection_tracking defined by app rabbit 2025-07-30 08:44:59.900 [info] <0.273.0> Setting up a table for connection tracking on this node: 'tracked_connection_on_node_rabbit@LAPTOP-FU2L4D12' 2025-07-30 08:44:59.902 [info] <0.273.0> Setting up a table for per-vhost connection counting on this node: 'tracked_connection_per_vhost_on_node_rabbit@LAPTOP-FU2L4D12' 2025-07-30 08:44:59.902 [info] <0.273.0> Running boot step routing_ready defined by app rabbit 2025-07-30 08:44:59.902 [info] <0.273.0> Running boot step pre_flight defined by app rabbit 2025-07-30 08:44:59.902 [info] <0.273.0> Running boot step notify_cluster defined by app rabbit 2025-07-30 08:44:59.902 [info] <0.273.0> Running boot step networking defined by app rabbit 2025-07-30 08:44:59.902 [info] <0.273.0> Running boot step definition_import_worker_pool defined by app rabbit 2025-07-30 08:44:59.902 [info] <0.351.0> Starting worker pool 'definition_import_pool' with 8 processes in it 2025-07-30 08:44:59.902 [info] <0.273.0> Running boot step cluster_name defined by app rabbit 2025-07-30 08:44:59.902 [info] <0.273.0> Initialising internal cluster ID to 'rabbitmq-cluster-id-vb7eUVm_pMu4vzxKD3W8-A' 2025-07-30 08:44:59.903 [info] <0.273.0> Running boot step direct_client defined by app rabbit 2025-07-30 08:44:59.903 [info] <0.44.0> Application rabbit started on node 'rabbit@LAPTOP-FU2L4D12' 2025-07-30 08:45:00.001 [info] <0.699.0> Ready to start client connection listeners 2025-07-30 08:45:00.015 [info] <0.714.0> started TCP listener on [::]:5672 2025-07-30 08:45:00.017 [info] <0.729.0> started TCP listener on 0.0.0.0:5672 2025-07-30 08:45:00.018 [notice] <0.282.0> Changed loghwm of d:/Downloads/RabbitMQData/log/rabbit@LAPTOP-FU2L4D12.log to 5000 2025-07-30 08:45:00.195 [info] <0.699.0> Server startup complete; 0 plugins started. 2025-07-30 08:45:00.195 [info] <0.699.0> Resetting node maintenance status
最新发布
07-31
Failed to start plugin 'rabbitmq_delayed_message_exchange' ``` 这种情况可能需要检查插件是否已正确安装，或者其依赖项是否满足 [^3]。 ### 示例代码：检查 RabbitMQ 状态的脚本 以下是一个简单的 Bash 脚本...
虚拟机—-出现解锁失败错误
10-12
Reason: Failed to lock the file." 指明了问题所在。这通常是由于虚拟机在关闭时未能正确清理 .lck 文件，这是 VMware 用来确保磁盘独占访问权的一种机制。如果虚拟机因异常情况（如电源故障、系统崩溃等）突然...
云安全：Cloudstack云平台搭建详解及经验总结
qq_37858047的博客
03-27 1万+
前言： 正在学习云安全，不搭建云平台，总感觉学的有些虚，没落到实处。在网上查资料了解到，Cloudstack产品比较成熟，已经有成熟的企业应用。而且相对OpenStack配置没那么复杂，所以就先从简单入门，不过实际搭建的时候还是遇到了很多坑。下面先写能够搭建的步骤，最后再写自己的失败尝试。 Cloudstack介绍： What is Apache CloudStack? Apache C...
打开VMware出现Reason: Failed to lock the file.错误的解决办法
晓风残露
01-12 807
启动虚拟机的时候出现了Cannot open the disk '*.vmdk' or one of the snapshot disks it depends on.Reason: Failed to lock the file.的错误，无法启动。 解决方法：将该虚拟机路径下的所有.lck后缀的文件和文件夹删除。
VMware 虚拟机启动Failed to lock the file
weixin_34290390的博客
08-28 208
VMware虚拟机启动Failedtolockthefile今日中午同事在迁移公司一台虚拟机时进度比较缓慢，后有人说需要使用这台内的文件，因无法预估迁移完成时间，就中断了迁移任务，打算开机让使用者使用,但是在Poweron时出现如下报错:Cannotopenthedisk'*.vmdk'oroneofthesnapshotdisksitde...
VMware出错 Reason Failed to lock the file
十年磨一剑，霜刃未曾试!
11-14 929
启动VMware虚拟机的时候出现了Cannot open the disk '*.vmdk' or one of the snapshot disks it depends on.Reason: Failed to lock the file.的错误。 解决方法：用记事本打开在对应的虚拟机系统的vmx文件，加入这条语句disk.locking = "FALSE"。下次启动就OK了。
VMware "Failed to lock the file" 错误
蜗牛x博客
03-18 1835
问题：当启动vmware启动虚拟机时出现”Failed to lock the file”错误解決方法一: 进到虚拟机文件夹中，将所有 *.lck 文件夹刪除解決方法二: 进到虚拟机文件夹中在*.vmk，最最后一行加入下面命令: disk.locking = “FALSE”推荐是用第一种方法，使用第二种方法不太安全，而且在使用Defragment时还会出现”Failed to lock the
VM 启动报错 "Failed to lock the file"
weixin_33972649的博客
12-02 152
错误：Failed to lock the file解决方法：打开VM的配置文件:VMX文件，在最后一行加入： disk.locking = "FALSE" 转载于:https://blog.51cto.com/tonyzeng/237627
Vmware Failed to lock the file Cannot open the disk xx.vmdk 解决办法
T型人小付的博客
06-05 1055
可能有几天没有关电脑导致电脑重启，再开机之后vmware的Centos7虚拟机就打不开了，吓了我一跳，以为保存在虚拟机里的东西全没了，后来一顿Google，终于成功化险为夷。 我是T型人小付，一位坚持终身学习的互联网从业者。喜欢我的博客欢迎在csdn上关注我，如果有问题欢迎在底下的评论区交流，谢谢。 文章目录报错原因解决问题总结 报错原因 尝试在Windows10机器打开Vmware中的一台Centos7虚拟机，报错如下图所示 显示错误Failed to lock the file，既然是跟lock相
VMware 启动报错 "Failed to lock the file"解决办法
weixin_33834679的博客
11-27 329
虚拟机启动后，出现Failed to lock the file报错，解决的办法：将”Windows XP Professional.vmdk.lck“文件夹下”M13197.lck“文件删掉或者把这个文件移走，就可以了。有没有负影响，在测试中。。。。。如果出问题，将VMWARE-TOOLS，重装一遍。问题出现的原因： 虚拟磁盘（.vmdk）本身有一个磁盘保护机制，为了防止...
虚拟机Failed to lock the file 和Reason: The file is too large错误的解决方法
weixin_34281477的博客
05-31 518
转自http://hi.baidu.com/perfectxyz/blog/item/23ac06f871720b04d8f9fd57.html 1、VMware 启动报错 "Failed to lock the file"解决办法： 将”Windows XP Professional.vmdk.lck“文件夹下”M13197.lck“文件删掉或者把这个文件移走，就可...
导入现成的安装有SAP的虚拟机报错：Failed to lock the file解决方法
wanghqapple88的博客
03-23 286
虚拟机文件来源：windows server 2003 32位中虚拟机 VMware Workstation 导入到win7 VMware Workstation中 在VMware里面 Open Existing WM or Team ->选择xxx.vmx->确定-> 启动报错 Cannot open the disk ‘F:xxx.vmdk’ or one of...
systemctl start vmware-tools 报错：failed to start vmware-tools.server:unit not found.
06-06
当使用 `systemctl start vmware-tools` 启动 VMware Tools 时出现 `failed to start vmware-tools.service: unit not found` 错误，通常是因为以下原因之一： #### 1. VMware Tools 的服务名称可能不正确 在某些 ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值