What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

MerlinAU MerlinAU v1.5.6 - The Ultimate Firmware Auto-Updater (WEBUI + GNUTON SUPPORT!)

Just tried to run the update again, making sure this time to avoid spdMerlin's schedule, and it completed successfully in about 5 minutes. I'm now on 3004.388.10.2. FYI, the logs don't show any lines containing rc_service: start_upgrade. Are you sure that's part of an upgrade?

Seems to us that the most likely explanation is that your settings for the system log are preventing some entries from showing up in the log.
You most likely have set the option "Log only messages more urgent than" to "notice" level or perhaps higher, which is causing our ability to see what happened to be limited in scope unfortunately.

I've merged in a change from Martinski that enhances our control of the USB unmount so we will be doing extensive testing to try and recreate the issue and validate the changes ASAP.
Thanks for holding tight, anyone that updates to the current dev build, be aware we are calling it experimental and in testing at this time.
 
Last edited:
Seems to us that the most likely explanation is that your settings for the system log are preventing some entries from showing up in the log.
You most likely have set the option "Log only messages more urgent than" to "notice" level or perhaps higher, which is causing our ability to see what happened to be limited in scope unfortunately.
1762885021371.png

I have it set to info. I thought this would mean the only messages hidden are the debug level. Am I mistaken? I'm not sure how the "Default message log level" affects this, but I don't remember changing anything here from defaults. I guess this does mean that if the rc_service: start_upgrade is a kernel message, it wouldn't be shown.
 
Last edited:
View attachment 68869
I have it set to info. I thought this would mean the only messages hidden are the debug level. Am I mistaken? I'm not sure how the "Default message log level" affects this, but I don't remember changing anything here from defaults. I guess this does mean that if the rc_service: start_upgrade is a kernel message, it wouldn't be shown.

I believe this is usually the default we see/deal with:

The option for "Default message log level" is set to: "notice"
And the option for "log only messages more urgent than" is set to: "debug"

(I've never changed mine)

1762951543692.png


Other posts found below that confirm this:

 
Last edited:
View attachment 68869
I have it set to info. I thought this would mean the only messages hidden are the debug level. Am I mistaken? I'm not sure how the "Default message log level" affects this, but I don't remember changing anything here from defaults. I guess this does mean that if the rc_service: start_upgrade is a kernel message, it wouldn't be shown.

Can I ask you to share a screenshot of your spdMerlin configuration? For example, which binary are you using? built-in or external? etc
May help us recreate your situation better. Thank you.
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Back
Top