Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to write to hcidump.pklg - :enospc #69

Open
philipgiuliani opened this issue Sep 17, 2021 · 1 comment
Open

Failed to write to hcidump.pklg - :enospc #69

philipgiuliani opened this issue Sep 17, 2021 · 1 comment

Comments

@philipgiuliani
Copy link

philipgiuliani commented Sep 17, 2021

I have created a clean nerves project which is running the example of #57 . After around 4 hours of execution I got the following logs spammed in my console:

10:51:22.592 [info]  Plant #1 - moisture: 30
10:51:32.577 [info]  Plant #1 - fertility: 168
10:51:42.607 [info]  Plant #1 - temperature: 25.1
10:51:53.588 [info]  Plant #1 - lux: 249
10:52:02.579 [info]  Plant #1 - moisture: 30
10:52:12.592 [info]  Plant #1 - fertility: 165
10:52:22.600 [info]  Plant #1 - temperature: 25.1
10:52:32.619 [info]  Plant #1 - lux: 249
10:52:42.585 [info]  Plant #1 - moisture: 30
10:52:45.081 [warn]  Failed to write to hcidump.pklg - :enospc
10:52:45.083 [debug] HCI Packet in <<0x3E, 0xC, 0x2, 0x1, 0x4, 0x1, 0x38, 0xE3, 0x57, 0x3B, 0x5D, 0x65, 0x0, 0xB0>>
10:52:45.135 [warn]  Failed to write to hcidump.pklg - :enospc
10:52:45.137 [debug] HCI Packet in <<0x3E, 0x2B, 0x2, 0x1, 0x2, 0x1, 0x4C, 0x7F, 0x0, 0x5A, 0x38, 0x53, 0x1F, 0x1E, 0xFF, 0x4C, 0x0, 0x7, 0x19, 0x1, 0xE, 0x20, 0x2B, 0x77, 0x8F, 0x1, 0x0, 0x5, 0x64, 0xCC, 0x48, 0x3A, 0x55, 0x3D, 0x4C, 0x7C, 0x65, 0x93, 0xCE, 0xAA, 0x22, 0x55, 0x92, 0xAB, 0xBE>>
10:52:45.146 [warn]  Failed to write to hcidump.pklg - :enospc
10:52:45.149 [debug] HCI Packet in <<0x3E, 0x2B, 0x2, 0x1, 0x3, 0x1, 0xCB, 0x6B, 0xA7, 0xAC, 0x9B, 0x25, 0x1F, 0x1E, 0xFF, 0x6, 0x0, 0x1, 0x9, 0x20, 0x2, 0x1, 0x16, 0x59, 0xFD, 0xCE, 0x70, 0xC7, 0xF3, 0x8E, 0x12, 0x5, 0xD7, 0x9C, 0xF2, 0xED, 0xC2, 0xA7, 0xA5, 0xEB, 0xBA, 0x8, 0x57, 0x19, 0xBB>>
10:52:45.169 [warn]  Failed to write to hcidump.pklg - :enospc
10:52:45.172 [debug] HCI Packet in <<0x3E, 0x2A, 0x2, 0x1, 0x0, 0x1, 0xE0, 0x39, 0x93, 0x4D, 0x45, 0x41, 0x1E, 0x2, 0x1, 0x2, 0x13, 0xFF, 0xFF, 0xFF, 0x32, 0x35, 0x61, 0x66, 0x61, 0x37, 0x38, 0x61, 0x66, 0x35, 0x38, 0x32, 0x63, 0x35, 0x33, 0x34, 0x2, 0xA, 0xF1, 0x3, 0x3, 0x56, 0x34, 0xD5>>
10:52:45.200 [warn]  Failed to write to hcidump.pklg - :enospc
10:52:45.203 [debug] HCI Packet in <<0x3E, 0x14, 0x2, 0x1, 0x4, 0x1, 0xE0, 0x39, 0x93, 0x4D, 0x45, 0x41, 0x8, 0x7, 0x9, 0x53, 0x48, 0x49, 0x45, 0x4C, 0x44, 0xD5>>
10:52:45.235 [warn]  Failed to write to hcidump.pklg - :enospc
10:52:45.238 [debug] HCI Packet in <<0x3E, 0x2B, 0x2, 0x1, 0x3, 0x1, 0xFB, 0x16, 0xC3, 0xC1, 0x46, 0x40, 0x1F, 0x1E, 0xFF, 0x6, 0x0, 0x1, 0x9, 0x20, 0x2, 0xAF, 0xB4, 0x68, 0x75, 0xB, 0xD, 0x98, 0x7B, 0x5A, 0xF3, 0x1A, 0x3F, 0x75, 0x52, 0x4A, 0x6, 0x31, 0xEE, 0xF8, 0x5E, 0x48, 0xF5, 0xB9, 0xBA>>
10:52:45.254 [warn]  Failed to write to hcidump.pklg - :enospc
10:52:45.257 [debug] HCI Packet in <<0x3E, 0x1A, 0x2, 0x1, 0x0, 0x1, 0x7A, 0x8C, 0xD8, 0x4B, 0x2A, 0x63, 0xE, 0x2, 0x1, 0x6, 0xA, 0xFF, 0x4C, 0x0, 0x10, 0x5, 0x1, 0x1C, 0x19, 0x2D, 0x52, 0xBB>>
10:52:45.274 [warn]  Failed to write to hcidump.pklg - :enospc
10:52:45.277 [debug] HCI Packet in <<0x3E, 0x1D, 0x2, 0x1, 0x0, 0x1, 0x5D, 0x15, 0xDD, 0xE9, 0x8, 0x45, 0x11, 0x2, 0x1, 0x1A, 0x2, 0xA, 0x18, 0xA, 0xFF, 0x4C, 0x0, 0x10, 0x5, 0xD, 0x98, 0x88, 0xBE, 0xFE, 0xB6>>
10:52:45.297 [warn]  Failed to write to hcidump.pklg - :enospc
10:52:45.299 [debug] HCI Packet in <<0x3E, 0x2B, 0x2, 0x1, 0x3, 0x1, 0x35, 0x90, 0x8F, 0x5D, 0x17, 0x30, 0x1F, 0x1E, 0xFF, 0x6, 0x0, 0x1, 0x9, 0x20, 0x2, 0xED, 0xAB, 0xCC, 0xE, 0xFD, 0x3A, 0x93, 0xD3, 0x30, 0x31, 0x6E, 0x31, 0x94, 0x25, 0x31, 0xB2, 0x78, 0x13, 0x6B, 0xCD, 0x10, 0x91, 0x19, 0xBB>>
... logs go on forever

What could the reason for this be? My df -h output looks like this:

Filesystem                Size      Used Available Use% Mounted on
/dev/root                27.4M     27.4M         0 100% /
devtmpfs                  1.0M         0      1.0M   0% /dev
tmpfs                    30.9M      8.0K     30.9M   0% /tmp
tmpfs                    15.5M      4.0K     15.5M   0% /run
/dev/mmcblk0p1           18.7M      5.9M     12.8M  32% /boot
/dev/mmcblk0p3           56.7G    148.0K     53.8G   0% /root
tmpfs                     1.0M         0      1.0M   0% /sys/fs/cgroup
@philipgiuliani
Copy link
Author

Ok I found it, seems that blue_heron is logging a hci_dump file by default:

      with true <- Application.get_env(:blue_heron, :log_hci_dump_file, true),
           :ok <- File.write("/tmp/hcidump.pklg", encoded, [:append]) do

I think this should be false by default since it could produce some huge files after running for a while - and if you are not aware it could crash a production environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant