Skip to content

Dev 0.2.40 Targeted as latest master/stable release#54

Merged
ExtremeFiretop merged 21 commits intomainfrom
dev
Dec 24, 2023
Merged

Dev 0.2.40 Targeted as latest master/stable release#54
ExtremeFiretop merged 21 commits intomainfrom
dev

Conversation

@ExtremeFiretop
Copy link
Owner

Dev 0.2.40 Targeted as latest master/stable release

Martinski4GitHub and others added 20 commits December 22, 2023 01:08
- Added new method to log messages into a file during the F/W Update process. This replaces the previous method that was causing some issues when trying to unmount the USB-attached drive just before the F/W was updated.
- Added code to show the F/W Update notification date on the menu.
- Moved a few functions to the top.
Update MerlinAU.sh Logging Solution to Stop Duplicating Mount Points
Just a couple of changes to double-check that the LOG directory actually exists.
Version increment.
Version increment.
Set the wait times for the "curl" command to return and then for the reboot (if necessary) to 3 minutes each.
Updated version.
Code changes WRT the blinking LEDs. Rather than stopping the blinking LEDs while waiting for a reboot, we restart them with a slower blinking rate to show users some activity is still going on but not the same as before when the curl cmd was being executed.
Added last LED reset *before* the reboot call.
Added/modified code to output some trace log messages when the "_DoCleanUp_" & "_Reset_LEDs_" functions are called after the F/W Update process is completed. This should leave a trace indicating IF/WHEN the "cleanup" is done as expected, especially if the router reboots itself.

This trace log is only temporary. We can switch it off later on once we have determined whether the "trap" mechanism is working after the F/W Update.
@ExtremeFiretop ExtremeFiretop merged commit 7f7658b into main Dec 24, 2023
@ExtremeFiretop
Copy link
Owner Author

@Martinski4GitHub

Merged all our improvements and hard work and troubleshooting into master/production.

Merry Christmas!! Happy Holidays!!

@Martinski4GitHub
Copy link
Collaborator

@Martinski4GitHub

Merged all our improvements and hard work and troubleshooting into master/production.

Merry Christmas!! Happy Holidays!!

Let's open the champagne early & start toasting!! :>)

@ExtremeFiretop
Copy link
Owner Author

@Martinski4GitHub
Merged all our improvements and hard work and troubleshooting into master/production.
Merry Christmas!! Happy Holidays!!

Let's open the champagne early & start toasting!! :>)

I never really went to sleep last night. I got a couple hours of zzz's
I've been toasting since Friday ;) Haha!

@ExtremeFiretop
Copy link
Owner Author

ExtremeFiretop commented Dec 26, 2023

@Martinski4GitHub

Just realized for me the script doesn't seem to run as a Cron job anymore :(
I don't know when that started happening.

If I run other scripts in the jffs/scripts folder as crons they work normally.
And our script works if I manually run this command: sh /./jffs/scripts/MerlinAU.sh run_now

But that command as a cron job seems to do nothing for me. I adjusted the cron to be every 1 minute and I have an update available and it still is doing nothing, while the other script I have to ping google every mintue is working fine on the same cron schedule.

Will troubleshoot some more tomorrow.

@Martinski4GitHub
Copy link
Collaborator

@Martinski4GitHub

Just realized for me the script doesn't seem to run as a Cron job anymore :( I don't know when that started happening.

If I run other scripts in the jffs/scripts folder as crons they work normally. And our script works if I manually run this command: sh /./jffs/scripts/MerlinAU.sh run_now

But that command as a cron job seems to do nothing for me. I adjusted the cron to be every 1 minute and I have an update available and it still is doing nothing, while the other script I have to ping google every mintue is working fine on the same cron schedule.

That's a very odd behavior. Just to clarify: the cron job "hook" is indeed found in the "/jffs/scripts/services-start" file, and the cron job entry does exist under crontab BUT when the job actually runs via cron nothing happens. However, running the same command manually via CLI "sh /jffs/scripts/MerlinAU.sh run_now" works fine, so something in the cron mechanism appears to fail when calling the script.

Is my understanding correct?
ATM, I don't see what could be causing that. If all the pieces are in place and "all the ducks are in a row" (so to speak) the call to the script should work unless there's a syntax error somewhere.

@Martinski4GitHub
Copy link
Collaborator

@Martinski4GitHub

Just realized for me the script doesn't seem to run as a Cron job anymore :( I don't know when that started happening.

If I run other scripts in the jffs/scripts folder as crons they work normally. And our script works if I manually run this command: sh /./jffs/scripts/MerlinAU.sh run_now

But that command as a cron job seems to do nothing for me. I adjusted the cron to be every 1 minute and I have an update available and it still is doing nothing, while the other script I have to ping google every mintue is working fine on the same cron schedule.

OK, on a hunch I put a log message before and after the code that prevents running the script multiple times simultaneously, and that's where it fails because it gets 2 processes running when called from crontab. So I know what the problem is and I'm working on a fix. Good catch, buddy!!!

@ExtremeFiretop
Copy link
Owner Author

ExtremeFiretop commented Dec 26, 2023

@Martinski4GitHub
Just realized for me the script doesn't seem to run as a Cron job anymore :( I don't know when that started happening.
If I run other scripts in the jffs/scripts folder as crons they work normally. And our script works if I manually run this command: sh /./jffs/scripts/MerlinAU.sh run_now
But that command as a cron job seems to do nothing for me. I adjusted the cron to be every 1 minute and I have an update available and it still is doing nothing, while the other script I have to ping google every mintue is working fine on the same cron schedule.

OK, on a hunch I put a log message before and after the code that prevents running the script multiple times simultaneously, and that's where it fails because it gets 2 processes running when called from crontab. So I know what the problem is and I'm working on a fix. Good catch, buddy!!!

No, whats a good catch is how you just freaking knew that on a whim/hunch!!! Like wth?!?! No testing? No troubleshooting?
I was chasing a syntax error for probably an hour last night before bed, (I assumed the same thing you initially did) until I said "it's christmas, it's late, I'm off to bed and will troubleshoot more tomorrow"

No need! Martins on the case! Hahaha.
I just woke up and that was nuts! Looked to me like you just took that out of the air. Great catch Martin!

@Martinski4GitHub
Copy link
Collaborator

No, whats a good catch is how you just freaking knew that on a whim/hunch!!! Like wth?!?! No testing? No troubleshooting? I was chasing a syntax error for probably an hour last night before bed, (I assumed the same thing you initially did) until I said "it's christmas, it's late, I'm off to bed and will troubleshoot more tomorrow"

No need! Martins on the case! Hahaha. I just woke up and that was nuts! Looked to me like you just took that out of the air. Great catch Martin!

Sometimes, your intuition (based on accummulated knowledge/experience) points you in the right direction and you just get lucky!! :>)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants