atmosphere creating thousands of files in erpt_reports even when no crashes are happening

[NekoNoor]

What's the issue you encountered?

when booted into atmosphere a lot of files are created in the erpt_reports folder even when i am not doing anything

How can the issue be reproduced?

launch atmosphere and wait for a couple minutes and check the sd card erpt_reports folder, there will be a lot of files causing it to hit the FAT limit of 16383 files in that folder and making the switch completely unusable (games load noticably slow and homebrew works extremely badly)

Crash Report

N/A

System Firmware Version

15.0.1

Environment?

• hekate (launching atmosphere using fusee.bin)
• Official release version 1.4.0
• Do you have additional kips or sysmodules you're loading: N/A
• Homebrew software installed: N/A
• SysNAND

Additional context?

N/A

[SciresM]

So, to be explicit:

I do not want to add a mechanism that a user can toggle that allows disabling error reporting. I am flatly not willing to do this.

The inevitable result of doing this will be that people who make "packs"/distribute atmosphere alongside homebrew will disable error logging, and then people will reach out for support, and they won't have logs. That's clearly unacceptable to me.

Also, to be clear, consoles should not be logging thousands of errors, and I would also like to note that if atmosphere was not writing to them to the SD card, the official nintendo software would be writing them to the internal emmc, which seems even worse from a wear/tear perspective to me?

I would maybe be willing to consider not saving further reports if the user has a stupidly large amount present. Maybe...5000? I could see an argument for not writing reports to the SD card if there are a stupidly large number already present. This would, I guess, require the automatic cleanup stuff to be off to work.

[SciresM]

I didn't say remove them from Atmosphere I said let the user disable them via config. If a user has no intention of reporting errors to GitHub or is using atmosphere in a way that is unsupported this feature is useless to them and only causes unnecessary wear and tear on their SD card.

I would also like to note: "If a user has no intention of reporting errors to GitHub or is using atmosphere in a way that is unsupported"...if they are doing something unsupported, why would I provide support to them? And if they're behaving in a way that's supported but aren't willing to share error logs, why would I provide explicit support for users who are not willing to help me make atmosphere better?

[DraconicNEO]

I do not want to add a mechanism that a user can toggle that allows disabling error reporting. I am flatly not willing to do this.

The inevitable result of doing this will be that people who make "packs"/distribute atmosphere alongside homebrew will disable error logging, and then people will reach out for support, and they won't have logs. That's clearly unacceptable to me.

Not like they can't do it anyway, atmosphere is open source after all, I think there are a few that do it (no I won't link them here).

Also, to be clear, consoles should not be logging thousands of errors, and I would also like to note that if atmosphere was not writing to them to the SD card, the official nintendo software would be writing them to the internal emmc, which seems even worse from a wear/tear perspective to me?

I know it does, that's why I suggested something like destroying them entirely i.e. /dev/null (or a similar equivalent) approach where they aren't saved anywhere and are wiped from existence upon creation.

I would maybe be willing to consider not saving further reports if the user has a stupidly large amount present. Maybe...5000? I could see an argument for not writing reports to the SD card if there are a stupidly large number already present. This would, I guess, require the automatic cleanup stuff to be off to work.

That's a fair compromise if you don't want to disable it entirely. I mean the cleanup script doesn't really work if people don't reboot their consoles before hitting the driver limit most people keep their switches asleep and powered on because it's just more convenient with the tethered nature of the RCM exploit.

[SciresM]

Not like they can't do it anyway, atmosphere is open source after all, I think there are a few that do it (no I won't link them here).

Well, yes, part of being open source is that people can do whatever they want. That is their prerogative and I support people's right to do whatever they want. But if someone is using a pack, I can tell them "I don't provide support if you're using that", in a way that I can't if it's native to Atmosphere.

I mean the cleanup script doesn't really work if people don't reboot their consoles before hitting the driver limit most people keep their switches asleep and powered on because it's just more convenient with the tethered nature of the RCM exploit.

I would like to reiterate one more time that I think this whole problem is complete nonsense. But, yes, not writing if there are already thousands of files, or if we've written 1000 files since the last reboot, or some other insanity metric seems not unreasonable to me.

[SuperSpe]

Not like they can't do it anyway, atmosphere is open source after all, I think there are a few that do it (no I won't link them here).

Well, yes, part of being open source is that people can do whatever they want. That is their prerogative and I support people's right to do whatever they want. But if someone is using a pack, I can tell them "I don't provide support if you're using that", in a way that I can't if it's native to Atmosphere.

I mean the cleanup script doesn't really work if people don't reboot their consoles before hitting the driver limit most people keep their switches asleep and powered on because it's just more convenient with the tethered nature of the RCM exploit.

I would like to reiterate one more time that I think this whole problem is complete nonsense. But, yes, not writing if there are already thousands of files, or if we've written 1000 files since the last reboot, or some other insanity metric seems not unreasonable to me.

I have at least 16k files inside that folder and on the boot the switch becomes very slow. I want to know in my case why these reports are made and correct the errors. How can I view them? They are not plain text...

[DraconicNEO]

Not like they can't do it anyway, atmosphere is open source after all, I think there are a few that do it (no I won't link them here).

Well, yes, part of being open source is that people can do whatever they want. That is their prerogative and I support people's right to do whatever they want. But if someone is using a pack, I can tell them "I don't provide support if you're using that", in a way that I can't if it's native to Atmosphere.

I mean the cleanup script doesn't really work if people don't reboot their consoles before hitting the driver limit most people keep their switches asleep and powered on because it's just more convenient with the tethered nature of the RCM exploit.

I would like to reiterate one more time that I think this whole problem is complete nonsense. But, yes, not writing if there are already thousands of files, or if we've written 1000 files since the last reboot, or some other insanity metric seems not unreasonable to me.

I have at least 16k files inside that folder and on the boot the switch becomes very slow. I want to know in my case why these reports are made and correct the errors. How can I view them? They are not plain text...

Erpt reports are indeed plaintext and you can view them in a text viewer, that's how I figured out that they're all the same error related to Nintendo network.

[SuperSpe]

I have at least 16k files inside that folder and on the boot the switch becomes very slow. I want to know in my case why these reports are made and correct the errors. How can I view them? They are not plain text...

Erpt reports are indeed plaintext and you can view them in a text viewer, that's how I figured out that they're all the same error related to Nintendo network.

strange. I search for the errore inside the zip and did not find any of this errors on single file. what I am missing?

[DraconicNEO]

I have at least 16k files inside that folder and on the boot the switch becomes very slow. I want to know in my case why these reports are made and correct the errors. How can I view them? They are not plain text...

Erpt reports are indeed plaintext and you can view them in a text viewer, that's how I figured out that they're all the same error related to Nintendo network.

strange. I search for the errore inside the zip and did not find any of this errors on single file. what I am missing?

If you open one of the report files it'll have the error code in it somewhere in the text as a four digit number with a dash followed by another four digit number (xxxx-xxxx) i.e. 2155-8007 which is when Nintendo servers cannot be contacted, (happens usually when people block the servers).

[SuperSpe]

I've searched inside files with vscode...no matches

[ehx-v1]

When I took a look at the errors in the ZIP above (since I deleted the reports that were on my own SD card), I saw a lot of binary symbols mixed into the file. Maybe the encoding is misrecognized?

[SciresM]

Error report files are messagepack format.

anyway, can we please not spam this issue with comments? I will lock it if this continues. This isn't the right place for questions about how to decode report files.

[filipegorges]

@SciresM could something kinda like a circular list be put in place, as in fill in up to 5k files and then overwrite from first position? maybe create the files ahead of time and use some modulus op to redirect the errors, thinking them being out of order can be sorted by writing some script to put them together and sort them when actually investigating the logs, just thinking out loud, I didn't read the code to see how this is working there now.

I get your frustration with people writing up crappy error reports, maybe the issue template could be updated to state that unless the user uploads a zip of the logs, the issue will be ignored or something

[jamjazz]

If I can give my modest experience to you.. I have the same problem too. I believe it started when I re-linked my user accounts with linkalho. Maybe that's the problem... If I unlink accounts, everything is back to normal.

[SuperSpe]

If I can give my modest experience to you.. I have the same problem too. I believe it started when I re-linked my user accounts with linkalho. Maybe that's the problem... If I unlink accounts, everything is back to normal.

I also had a suspicion it was really link halo, now I have the confirmation

[ehx-v1]

So we're back to "Atmosphère is not responsible for this issue". I'd suggest reporting the problem to Linkhalo and then calling it a day.

[NekoNoor]

it's also reproducible if you had an account linked without linkalho, so it isn't necessarily an issue with linkalho but an issue with having an account linked

[jamjazz]

Yep.. same problem with Tinfoil fake-linked account pass.

[Ammako]

some game require having an nnid linked, how would i play those if i cant have one linked (becouse it would fill the sd card with errors)

sys-tweak can override this linked account requirement in theory, but in practice it's unclear if there are any games this would work for. Like Bloodstained RotN for instance has a seemingly unnecessary linked account requirement to run (even the physical cartridge!), but overriding the nacp to allow running the game without a linked account, it hangs early on in the initial loading screen and eventually crashes back to the home menu. Maybe the games you have which require a linked account could work perfectly fine with this, or maybe not. It might be worth a try.

[Ammako]

some game require having an nnid linked, how would i play those if i cant have one linked (becouse it would fill the sd card with errors)

sys-tweak can override this linked account requirement in theory, but in practice it's unclear if there are any games this would work for. Like Bloodstained RotN for instance has a seemingly unnecessary linked account requirement to run (even the physical cartridge!), but overriding the nacp to allow running the game without a linked account, it hangs early on in the initial loading screen and eventually crashes back to the home menu. Maybe the games you have which require a linked account could work perfectly fine with this, or maybe not. It might be worth a try.

Oh hey, what do you know, I was just doing it wrong. You don't set startup_user_account=0, you set startup_user_account=1. Now Bloodstained runs fine without crashing, with no linked Nintendo account.

So I suggest: get sys-tweak, make a folder in atmosphere/contents for each of your games that require a linked account to run, and make a config.ini like this in it:

[override_nacp]
startup_user_account=1

See if this works and if you're able to run all of your games with Nintendo account unlinked. This should hopefully avoid the issue of too many erpt reports being created, while still being able to play your games.

[NonaSuomy]

Had this issue as well when I linked the accounts with linkhalo It fiercely generated 10K erpt_reports in 1 night causing the system to slow to a crawl. Atmosphere should toss up a warning when this folder becomes polluted or fix why having a linked account causes this issue. Ideally, it doesn't seem like I needed a linked account for anything after unlinking them. It stopped generating the reports and everything worked fine again after purging the folder. The only reason I did it was I had a corrupted DLC that was tossing up Nintendo account-required message after reinstalling again without the DLC that message stopped as well.

[ehx-v1]

fix why having a linked account causes this issue

That's the whole Nintendo Network problem, seems like it tries to look up the linked account and fails.

a corrupted DLC that was tossing up Nintendo account-required message

That kind of stuff can be forced to shut up with sys-tweak as described above, seems the much better option to me compared to setting up a linked account literally nothing for Singleplayer has any business needing.

[springroll-xx]

Had this issue as well when I linked the accounts with linkhalo It fiercely generated 10K erpt_reports in 1 night causing the system to slow to a crawl. Atmosphere should toss up a warning when this folder becomes polluted or fix why having a linked account causes this issue. Ideally, it doesn't seem like I needed a linked account for anything after unlinking them. It stopped generating the reports and everything worked fine again after purging the folder. The only reason I did it was I had a corrupted DLC that was tossing up Nintendo account-required message after reinstalling again without the DLC that message stopped as well.

How does one know which DLC is corrupted that would toss up account-required message?

[NonaSuomy]

That kind of stuff can be forced to shut up with sys-tweak as described above, seems the much better option to me compared to setting up a linked account literally nothing for Singleplayer has any business needing.

So I just found one thing that now doesn't work without linked accounts is the online official emulators. After removing all the linked accounts they no longer work for me (They were working fine before but I linked the accounts I think with tinfoil). Do you know of a way to get these working without linked accounts? As when I try to link accounts in tinfoil now it tosses up an error and then crashes the system.

[NonaSuomy]

Had this issue as well when I linked the accounts with linkhalo It fiercely generated 10K erpt_reports in 1 night causing the system to slow to a crawl. Atmosphere should toss up a warning when this folder becomes polluted or fix why having a linked account causes this issue. Ideally, it doesn't seem like I needed a linked account for anything after unlinking them. It stopped generating the reports and everything worked fine again after purging the folder. The only reason I did it was I had a corrupted DLC that was tossing up Nintendo account-required message after reinstalling again without the DLC that message stopped as well.

How does one know which DLC is corrupted that would toss up account-required message?

It only tosses up that error when you open that game so I would say delete each update/dlc with tinfoil update remove options until the error goes away then download fresh/working ones then add them back and see what happens.

[lucasvm01]

Hello, I apologize if I should not ask about it here, and if not, please tell me where to. I'm currently using FW 17.0.1 and AMS 1.6.2.

I was trying to play the Nintendo Switch Online games, which require a link to a Nintendo account, so I used Tinfoil to fake link an account and soon got this flood of errors on my atmosphere/content/erpt_reports folder. I tried the sugestion from @Ammako:

So I suggest: get sys-tweak, make a folder in atmosphere/contents for each of your games that require a linked account to run, and make a config.ini like this in it:

[override_nacp]
startup_user_account=1

See if this works and if you're able to run all of your games with Nintendo account unlinked. This should hopefully avoid the issue of too many erpt reports being created, while still being able to play your games.

And it did not work on the Nintendo Switch Online games (all of them), so I tried it on the game they previously tried, Bloodstained: Ritual of the Night, and it did work. So I'm guessing it doesn't work on the Nintendo Switch Online games specifically.

I would like to ask if anyone has found a solution for playing those games, without fake linking an account or downloading Retroarch or another third party emulator.

[Ammako]

You're better off playing the NSO emulators on OFW. If you don't actually have NSO or you're banned, this means you're pirating the NSO apps, which isn't supported here.

I don't know why some single-player games require a linked Nintendo account even for the physical copies, but sys-tweak can bypass that and let those games run at least. For digital copies of games, you can't do that, because HOS needs the account that purchased the game to be linked, or it will not launch the game. It might be possible to patch out that account check, which would allow you to unlink your account without breaking your games, but nobody's done that yet.

The alternative for digital games would require replacing the personalized ticket with an illegitimate common ticket, which would require signature patches to run, which is explicitly unsupported by Atmosphere (piracy.)