MacOS host file editor

  1. Gas Mask (Mac):
    • Gas Mask is a simple hosts file manager for macOS with a graphical interface.
    • It allows you to edit, update, enable, or disable hosts entries easily.
    • You can download it from: Gas Mask
  2. Hosts (Mac):
    • Hosts is another hosts file manager for macOS that provides a clean and minimalistic interface.
    • It allows you to toggle between different hosts files easily.
    • You can download it from: Hosts
  3. Hosts File Editor (Windows, Mac, Linux):
    • Hosts File Editor is a cross-platform tool that allows you to easily manage your hosts file.
    • It provides a simple GUI for editing, adding, and removing entries.
    • You can download it from: Hosts File Editor
  4. Text Editors (Any Platform):
    • You can use any text editor with elevated privileges to manually edit the hosts file.
    • For Mac, you can use the Terminal and a text editor like nano or vim with sudo to edit the hosts file directly.

SAN Brocade Firmware commit failed – Firmwarecommit failed. (0x1a)

Workaround 1:

Run command supportsave -R.

The -R option removes all cores files on the Control Processor (CP) and Blade Processor (BP). This option cannot be used with any other options.

Note: On director switches run this command on each CP.

Workaround 2:

Run cleanup utility.

Note: This utility will check for any obsoleted files that are in the file system that do not belong to any package, and will then remove them. These files may be resulted from firmwareCommit command. The list of directories it checks is in /etc/cleanup.conf. This utility can only be run from root account. Be aware the tool will remove all unauthorized code under following directories on BOTH partitions:        

/bin
/lib
/fabos
/root
/usr
/core_files

 

  1. Validate space by running df -kh  as root
  2. Run du -h /mnt/xx/xx to verify space usage of a directory.

Example:

Brocade:root>du -h /mnt/var/log/mstatdir/*

423M   /mnt/var/log/mstatdir/memorystatus

  1. If  a directory has a huge space (for example:/mnt/var/log/mstatdir/memorystatus):
    1. Run supportsave -R command
    2. Run  cleanup command
    3. Check again  /mnt/var/log/mstatdir to see if the memorystatus file(s) are still there.

Note: It should have been several memorystatus files, each generated on a daily basis. If it is only 1 huge memorystatus file, again that will confirm the out of space issue seen on FOS as a result of the log rotation mechanism not working (Brocade Defect DEFECT000543727)

  1. If the issue persists, perform the following:
  •  Delete memorystatus file from /mnt/var/log/mstatdir on the second partition

Example:

Brocade:root>rm /mnt/var/log/mstatdir/memorystatus

  •  Check with df /mnt command to see if space has been regained.
  1. If space is not regained, it would mean that there is a process that has memorystatus file open and the process needs to close the file
  • Run fuser /mnt/var/log/mstatdir command to find out if a process has the file open.