Read the statement by Michael Teeuw here.
MMM-Buttons to activate MMM-Assistantmk2 (v3)
-
see below
[15:09:19.817] [LOG] [AMK2] QUERY: { type: 'MIC', profile: { profileFile: 'default.json', lang: 'en-US' }, key: null, lang: null, useScreenOutput: true, useAudioOutput: true, session: 1579273759810, status: 'standby', secretMode: false, sayMode: false } [15:09:19.985] [LOG] [AMK2:AS] MIC:RECORDING START. mmap() failed: Cannot allocate memory Failed to create permanent mapping for memfd region with ID = 2467795728 Ignoring received block reference with non-registered memfd ID = 2467795728 [15:09:20.546] [LOG] [AMK2:AS] CONVERSATION:RESPONSE [15:09:22.659] [LOG] [AMK2:AS] CONVERSATION:TRANSCRIPTION { transcription: 'test', done: false } [15:09:22.792] [LOG] [AMK2:AS] CONVERSATION:TRANSCRIPTION { transcription: 'testing', done: false } [15:09:23.520] [LOG] [AMK2:AS] CONVERSATION:TRANSCRIPTION { transcription: 'testing', done: false } [15:09:23.548] [LOG] [AMK2:AS] CONVERSATION:END_OF_UTTERANCE [15:09:23.551] [LOG] [AMK2:AS] MIC:RECORDING_END [15:09:23.585] [LOG] [AMK2:AS] Recorder Error: arecord has exited with error code 1. Enable debugging with the environment variable DEBUG=record. [15:09:23.599] [LOG] [AMK2:AS] CONVERSATION:TRANSCRIPTION { transcription: 'testing', done: true } [15:09:23.906] [LOG] [AMK2:AS] CONVERSATION:SCREEN object [15:09:23.915] [LOG] [AMK2:AS] CONVERSATION:ACTION { requestId: '5e215c36-0000-2e45-8016-089e0826d0a0' } [15:09:23.918] [LOG] [AMK2:AS] CONVERSATION:RESPONSE [15:09:23.929] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.931] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.933] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.937] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.938] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.940] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.941] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.943] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.944] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.945] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.947] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.949] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.950] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.951] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.953] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.955] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.959] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.962] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.966] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.968] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.970] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.972] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.975] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.979] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.982] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.984] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.986] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.987] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.989] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.990] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.992] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.993] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.995] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.997] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:23.999] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.000] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.002] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.004] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.006] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.008] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.010] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.012] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.015] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.017] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.019] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.022] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.027] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.031] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.034] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.036] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.039] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.041] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.043] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.046] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.051] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.056] [LOG] [AMK2:AS] CONVERSATION:AUDIO 1600 [15:09:24.058] [LOG] [AMK2:AS] CONVERSATION:AUDIO 14 [15:09:24.065] [LOG] [AMK2:AS] CONVERSATION_ALL_RESPONSES_RECEIVED [15:09:24.066] [LOG] [AMK2:AS] CONVERSATION_END:COMPLETED [15:09:24.067] [LOG] [AMK2:AS] CONVERSATION_PP:RESPONSE_AUDIO_MAKING [15:09:24.097] [LOG] [AMK2:BW] RESPONSE_WAV_FILE_CREATED [15:09:24.099] [LOG] [AMK2:AS] CONVERSATION_PP:RESPONSE_AUDIO_CREATED tmp/lastResponse.wav [15:09:24.228] [LOG] [AMK2] { session: 1579273759810, error: null, action: { requestId: '5e215c36-0000-2e45-8016-089e0826d0a0' }, text: null, screen: { help: [ 'What can you do?' ], trysay: 'Try saying…', links: [], text: 'You\'re coming in loud and clear 👌', photos: [], path: '/home/pi/MagicMirror/modules/MMM-AssistantMk2/tmp/lastScreenOutput.html', uri: 'tmp/lastScreenOutput.html' }, audio: { path: '/home/pi/MagicMirror/modules/MMM-AssistantMk2/tmp/lastResponse.wav', uri: 'tmp/lastResponse.wav' }, transcription: { transcription: 'testing', done: true }, continue: false, lastQuery: { type: 'MIC', profile: { profileFile: 'default.json', lang: 'en-US' }, key: null, lang: null, useScreenOutput: true, useAudioOutput: true, session: 1579273759810, status: 'standby', secretMode: false, sayMode: false } } mmap() failed: Cannot allocate memory Failed to create permanent mapping for memfd region with ID = 3652511026 Ignoring received block reference with non-registered memfd ID = 3652511026
-
@Apartment_Moose
Well, the module itself is working as log says. But themmap() failed
means, you have not enough memory. (I don’t know why)mmap()
issue could happen with various reasons, so hard to point out exactly.
I think it is not related to my module directly because there was no same issue report but I cannot declare definitely. -
@Sean
ok thanks for taking a look.
dont know what the mmap() issue is but i will look into it@sdetweil
do you potentially know what could cause this ? -
@Apartment_Moose said in MMM-Buttons to activate MMM-Assistantmk2 (v3):
do you potentially know what could cause this ?
mmap is memory mapped file
here is a site with a pretty decent dewscription of what to look for and what to change
https://mroonga.org/docs/faq/mmap_cannot_allocate_memory.html -
@sdetweil
Thanks for getting back to me on this. I will check it out over the weekend when I next am free (probably sunday). I will report back on if this fixed it. Thanks again for the support as I couldnt find anything on google. -
@Apartment_Moose i just did a search on google for “mmap Cannot allocate memory”
-
Hi @sdetweil
thanks for the help so far, I have edited the vm map count as per the link you linked (with the 16gb used in the example)
i am still getting the same log error however
mmap() failed: Cannot allocate memory Failed to create permanent mapping for memfd region with ID = 738611435 Ignoring received block reference with non-registered memfd ID = 738611435
any ideas as i am stumped…
-
I seem to have fixed the issue by switching everything to my raspberry 4.
didn’t look like the 3 b+ could handle it for some reason and now it is all working.
thank you for your help, it was greatly appreciated!@Sean
quick one for you if you don’t, (after upgrading to 3.0.1) When i speak a command and it responds, the google wheel continues to spin as per the picture. (log file doesn’t do anything unless i press the button to activate again)
is this normal? or should it return to the floating bubbles?
also, log files show after any open questions such as “hello google” its status goes to standby after responding with the log showing the continue line on set to “false”.if i press the button and dont say anything, then it resets due to the timer setting.
-
@Apartment_Moose
We found some issues under specific condition about memory shortage. so we are trying another approach to use smaller memory. wait a while. sorry. -
@Sean
thanks for the response :) i will close this as solve for now.
thank you