vim /usr/lib/rabbitmq/lib/rabbitmq_server-3.6.5/ebin/rabbit.app
5.修改配置文件
这里面修改{loopback_users, [<<“guest”>>]}改为{loopback_users, []}
{application, rabbit, %% -- erlang --
[{description, “RabbitMQ”},
{id, “RabbitMQ”},
{vsn, “3.6.5”},
{modules, [‘background_gc’,‘delegate’,‘delegate_sup’,‘dtree’,‘file_handle_cache’,‘file_handle_cache_stats’,‘gatherer’,‘gm’,‘lqueue’,‘mirrored_supervisor_sups’,‘mnesia_sync’,‘mochinum’,‘pg2_fixed’,‘pg_local’,‘rabbit’,‘rabbit_access_control’,‘rabbit_alarm’,‘rabbit_amqqueue_process’,‘rabbit_amqqueue_sup’,‘rabbit_amqqueue_sup_sup’,‘rabbit_auth_mechanism_amqplain’,‘rabbit_auth_mechanism_cr_demo’,‘rabbit_auth_mechanism_plain’,‘rabbit_autoheal’,‘rabbit_binding’,‘rabbit_boot_steps’,‘rabbit_channel_sup’,‘rabbit_channel_sup_sup’,‘rabbit_cli’,‘rabbit_client_sup’,‘rabbit_connection_helper_sup’,‘rabbit_connection_sup’,‘rabbit_control_main’,‘rabbit_ctl_usage’,‘rabbit_dead_letter’,‘rabbit_diagnostics’,‘rabbit_direct’,‘rabbit_disk_monitor’,‘rabbit_epmd_monitor’,‘rabbit_error_logger’,‘rabbit_error_logger_file_h’,‘rabbit_exchange’,‘rabbit_exchange_parameters’,‘rabbit_exchange_type_direct’,‘rabbit_exchange_type_fanout’,‘rabbit_exchange_type_headers’,‘rabbit_exchange_type_invalid’,‘rabbit_exchange_type_topic’,‘rabbit_file’,‘rabbit_framing’,‘rabbit_guid’,‘rabbit_hipe’,‘rabbit_limiter’,‘rabbit_log’,‘rabbit_memory_monitor’,‘rabbit_mirror_queue_coordinator’,‘rabbit_mirror_queue_master’,‘rabbit_mirror_queue_misc’,‘rabbit_mirror_queue_mode’,‘rabbit_mirror_queue_mode_all’,‘rabbit_mirror_queue_mode_exactly’,‘rabbit_mirror_queue_mode_nodes’,‘rabbit_mirror_queue_slave’,‘rabbit_mirror_queue_sync’,‘rabbit_mnesia’,‘rabbit_mnesia_rename’,‘rabbit_msg_file’,‘rabbit_msg_store’,‘rabbit_msg_store_ets_index’,‘rabbit_msg_store_gc’,‘rabbit_node_monitor’,‘rabbit_parameter_validation’,‘rabbit_password’,‘rabbit_password_hashing_md5’,‘rabbit_password_hashing_sha256’,‘rabbit_password_hashing_sha512’,‘rabbit_plugins’,‘rabbit_plugins_main’,‘rabbit_plugins_usage’,‘rabbit_policies’,‘rabbit_policy’,‘rabbit_prelaunch’,‘rabbit_prequeue’,‘rabbit_priority_queue’,‘rabbit_queue_consumers’,‘rabbit_queue_index’,‘rabbit_queue_location_client_local’,‘rabbit_queue_location_min_masters’,‘rabbit_queue_location_random’,‘rabbit_queue_location_validator’,‘rabbit_queue_master_location_misc’,‘rabbit_recovery_terms’,‘rabbit_registry’,‘rabbit_resource_monitor_misc’,‘rabbit_restartable_sup’,‘rabbit_router’,‘rabbit_runtime_parameters’,‘rabbit_sasl_report_file_h’,‘rabbit_ssl’,‘rabbit_sup’,‘rabbit_table’,‘rabbit_trace’,‘rabbit_upgrade’,‘rabbit_upgrade_functions’,‘rabbit_variable_queue’,‘rabbit_version’,‘rabbit_vhost’,‘rabbit_vm’,‘supervised_lifecycle’,‘tcp_listener’,‘tcp_listener_sup’,‘truncate’,‘vm_memory_monitor’,‘worker_pool’,‘worker_pool_sup’,‘worker_pool_worker’]},
{registered, [rabbit_amqqueue_sup,
rabbit_log,
rabbit_node_monitor,
rabbit_router,
rabbit_sup,
rabbit_direct_client_sup]},
{applications, [kernel, stdlib, sasl, mnesia, rabbit_common, ranch, os_mon, xmerl]},
%% we also depend on crypto, public_key and ssl but they shouldn’t be
%% in here as we don’t actually want to start it
{mod, {rabbit, []}},
{env, [{tcp_listeners, [5672]},
{num_tcp_acceptors, 10},
{ssl_listeners, []},
{num_ssl_acceptors, 1},
{ssl_options, []},
{vm_memory_high_watermark, 0.4},
{vm_memory_high_watermark_paging_ratio, 0.5},
{memory_monitor_interval, 2500},
{disk_free_limit, 50000000}, %% 50MB
{msg_store_index_module, rabbit_msg_store_ets_index},
{backing_queue_module, rabbit_variable_queue},
%% 0 (“no limit”) would make a better default, but that
%% breaks the QPid Java client
{frame_max, 131072},
{channel_max, 0},
{heartbeat, 60},
{msg_store_file_size_limit, 16777216},
{fhc_write_buffering, true},
{fhc_read_buffering, false},
{queue_index_max_journal_entries, 32768},
{queue_index_embed_msgs_below, 4096},
{default_user, <<“guest”>>},
{default_pass, <<“guest”>>},
{default_user_tags, [administrator]},
{default_vhost, <<“/”>>},
{default_permissions, [<<“.“>>, <<”.”>>, <<“.*”>>]},
{loopback_users, []},
{password_hashing_module, rabbit_password_hashing_sha256},
{cluster_nodes, {[], disc}},
{server_properties, []},
{collect_statistics, none},
{collect_statistics_interval, 5000},
{mnesia_table_loading_timeout, 30000},
{auth_mechanisms, [‘PLAIN’, ‘AMQPLAIN’]},
{auth_backends, [rabbit_auth_backend_internal]},
{delegate_count, 16},
{trace_vhosts, []},
{log_levels, [{connection, info}]},
{ssl_cert_login_from, distinguished_name},
{ssl_handshake_timeout, 5000},
{ssl_allow_poodle_attack, false},
{handshake_timeout, 10000},
{reverse_dns_lookups, false},
{cluster_partition_handling, ignore},
{cluster_keepalive_interval, 10000},
{tcp_listen_options, [{backlog, 128},
{nodelay, true},
{linger, {true, 0}},
{exit_on_close, false}]},
{halt_on_upgrade_failure, true},
{hipe_compile, false},
%% see bug 24513 for how this list was created
{hipe_modules,
[rabbit_reader, rabbit_channel, gen_server2, rabbit_exchange,
rabbit_command_assembler, rabbit_framing_amqp_0_9_1, rabbit_basic,
rabbit_event, lists, queue, priority_queue, rabbit_router,
rabbit_trace, rabbit_misc, rabbit_binary_parser,
rabbit_exchange_type_direct, rabbit_guid, rabbit_net,
rabbit_amqqueue_process, rabbit_variable_queue,
rabbit_binary_generator, rabbit_writer, delegate, gb_sets, lqueue,
sets, orddict, rabbit_amqqueue, rabbit_limiter, gb_trees,
rabbit_queue_index, rabbit_exchange_decorator, gen, dict, ordsets,
file_handle_cache, rabbit_msg_store, array,
rabbit_msg_store_ets_index, rabbit_msg_file,
rabbit_exchange_type_fanout, rabbit_exchange_type_topic, mnesia,
mnesia_lib, rpc, mnesia_tm, qlc, sofs, proplists, credit_flow,
pmon, ssl_connection, tls_connection, ssl_record, tls_record,
gen_fsm, ssl]},
{ssl_apps, [asn1, crypto, public_key, ssl]},
%% see rabbitmq-server#114
{mirroring_flow_control, true},
{mirroring_sync_batch_size, 4096},
%% see rabbitmq-server#227 and related tickets.
%% msg_store_credit_disc_bound only takes effect when
%% messages are persisted to the message store. If messages
%% are embedded on the queue index, then modifying this
%% setting has no effect because credit_flow is not used when
%% writing to the queue index. See the setting
%% queue_index_embed_msgs_below above.
{msg_store_credit_disc_bound, {2000, 500}},
自我介绍一下，小编13年上海交大毕业，曾经在小公司待过，也去过华为、OPPO等大厂，18年进入阿里一直到现在。
深知大多数Linux运维工程师，想要提升技能，往往是自己摸索成长或者是报班学习，但对于培训机构动则几千的学费，着实压力不小。自己不成体系的自学效果低效又漫长，而且极易碰到天花板技术停滞不前！
因此收集整理了一份《2024年Linux运维全套学习资料》，初衷也很简单，就是希望能够帮助到想自学提升又不知道该从何学起的朋友，同时减轻大家的负担。
既有适合小白学习的零基础资料，也有适合3年以上经验的小伙伴深入学习提升的进阶课程，基本涵盖了95%以上Linux运维知识点，真正体系化！
由于文件比较大，这里只是将部分目录大纲截图出来，每个节点里面都包含大厂面经、学习笔记、源码讲义、实战项目、讲解视频，并且后续会持续更新
如果你觉得这些内容对你有帮助，可以添加VX：vip1024b （备注Linux运维获取）
一个人可以走的很快，但一群人才能走的更远。如果你从事以下工作或对以下感兴趣，欢迎戳这里加入程序员的圈子，让我们一起学习成长！
AI人工智能、Android移动开发、AIGC大模型、C C#、Go语言、Java、Linux运维、云计算、MySQL、PMP、网络安全、Python爬虫、UE5、UI设计、Unity3D、Web前端开发、产品经理、车载开发、大数据、鸿蒙、计算机网络、嵌入式物联网、软件测试、数据结构与算法、音视频开发、Flutter、IOS开发、PHP开发、.NET、安卓逆向、云计算文章来源地址https://www.toymoban.com/news/detail-851200.html
orums/4304bb5a486d4c3ab8389e65ecb71ac0)文章来源：https://www.toymoban.com/news/detail-851200.html
AI人工智能、Android移动开发、AIGC大模型、C C#、Go语言、Java、Linux运维、云计算、MySQL、PMP、网络安全、Python爬虫、UE5、UI设计、Unity3D、Web前端开发、产品经理、车载开发、大数据、鸿蒙、计算机网络、嵌入式物联网、软件测试、数据结构与算法、音视频开发、Flutter、IOS开发、PHP开发、.NET、安卓逆向、云计算
到了这里，关于分布式消息队列RabbitMQ-Linux下服务搭建，面试完腾讯我才发现这些知识点竟然没掌握全的文章就介绍完了。如果您还想了解更多内容，请在右上角搜索TOY模板网以前的文章或继续浏览下面的相关文章，希望大家以后多多支持TOY模板网！
