Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VIO Rabbitmq not starting could not write file (76392)

Last Updated: 6/8/2020Categories: TroubleshootingTotal Views: 11781Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Trying to start services and rabbitmq fails

In the rabbitmq log, you see entries similar to:

root@photon-machine [ ~ ]# oslog rabbitmq1-rabbitmq-0
+ exec /docker-entrypoint.sh rabbitmq-server
2019-11-28 19:20:18.957 [info] <0.33.0> Application lager started on node
[email-masked]'
2019-11-28 19:20:18.983 [error] <0.5.0>
Error description:
init:do_boot/3
init:start_em/1
rabbit:start_it/1 line 478
rabbit:'-boot/0-fun-0-'/0 line 329
rabbit_node_monitor:prepare_cluster_status_files/0 line 129
rabbit_node_monitor:write_cluster_status/1 line 148
throw:{error,{could_not_write_file,"/var/lib/rabbitmq/mnesia/[email-masked]/cluster_nodes.config",
enospc}}
Log file(s) (may contain more information):
<stdout>

BOOT FAILED
===========

Error description:
init:do_boot/3
init:start_em/1
rabbit:start_it/1 line 478
rabbit:'-boot/0-fun-0-'/0 line 329
rabbit_node_monitor:prepare_cluster_status_files/0 line 129
rabbit_node_monitor:write_cluster_status/1 line 148
throw:{error,{could_not_write_file,"/var/lib/rabbitmq/mnesia/[email-masked]/cluster_nodes.config",
enospc}}
Log file(s) (may contain more information):
<stdout>

{"init terminating in
do_boot",{error,{could_not_write_file,"/var/lib/rabbitmq/mnesia/[email-masked]/cluster_nodes.config",enospc}}}
init terminating in do_boot
({error,{could_not_write_file,/var/lib/rabbitmq/mnesia/[email-masked]/cluster_nodes.config,enospc}})

Note:  The preceding log excerpts are only examples.  Date, time and environmental variables may vary depending on your environment.

Cause

The root cause is the 20GB space allocated for rabbitmq has run out. Most of the space is used under

~/mnesia/[email-masked]/msg_stores/vhosts/[xxxxxxxxx]/queues/[yyyyyyyy]/*.idx

Resolution

This is a known issue affecting VMware Integrated Openstack 6.0.

Workaround

Check disk usage of the rabbitmq pod:

osctl exec rabbitmq1-rabbitmq-0 df

Note: Pay attention to Use% of the following line:

/dev/sdc 20511312 50440 20444488 1% /var/lib/rabbitmq

Open interactive TTY to the rabbitmq pod

osctl exec -it rabbitmq1-rabbitmq-0 /bin/bash

Set rabbitmq TTL run the following commands:

for vhost in nova glance keystone neutron heat barbican cinder;do rabbitmqctl set_policy --vhost ${vhost} --priority 0 --apply-to all ha_ttl_${vhost} '(notifications)\.' '{"ha-mode":"all","ha-sync-mode":"automatic","message-ttl":70000}' ; done

rabbitmqctl set_policy TTL ".*" '{"message-ttl":70000}' --apply-to queues

If the /dev/sdc partition is still full we need to clear out the *.idx files

rabbitmqctl list_queues
rabbitmqctl purge queue name=<name of queue>

Restart rabbitmq if stopped

rabbitmqctl force_boot

Related Information

If you cannot get into the rabbitmq pod before it restarts, follow these instructions:

osctl edit statefulset rabbitmq1-rabbitmq

change command to: (add 'sleep 3600')

containers:
- command:
- bash
- -c
- |
sleep 3600
rabbitmqctl force_boot
/tmp/rabbitmq-start.sh

change livenessProbe to: (change initialDelaySeconds from 30 to 300)

livenessProbe:
exec:
command:
- /tmp/rabbitmq-liveness.sh
failureThreshold: 3
initialDelaySeconds: 300
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 10

Save your changes

osctl delete po rabbitmq1-rabbitmq-2

After new rabbitmq1-rabbitmq-2 pod comes up,

osctl exec -ti rabbitmq1-rabbitmq-2 bash
rm -rf /var/lib/rabbitmq/mnesia/[email-masked]/msg_stores/vhosts
exit

Now use 'osctl edit statefulset rabbitmq1-rabbitmq' to revert the changes above.

osctl delete po rabbitmq1-rabbitmq-2

Now the new rabbitmq1-rabbitmq-2 pod should come up and become 1/1 Running.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
ジェネラル サポートの終了：VMware NSX for vSphere 6.3.x (76761)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
Workspace ONE SDK Cordova Plugin 1.5.1 for iOS/Android リリースのお知らせ (76703)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Integrated OpenStack

Related Versions:

VMware Integrated Openstack 7.x

VMware Integrated OpenStack 6.x

Take Our Survey

Support Assistant