[BETA] ModSyslogUI v1.1.0 - CLOSED

[saison2023]

FYI, when I ran "modsyslogui" in SSH, it brings me to the same menu if I ran "amtm" and selected "ms"

amtm and ms:

Spoiler: amtm and ms

"modsyslogui" directly after connecting to SSH:

Spoiler: modsyslogui only

So base on your answer, I think I did update the right way (using your script UPDATE function).

Again, no argue, only goal is to be sure we are aligned and ease next step(s) and test(s)

 

[kstamand]

Ok, so just to be clear and do right next time(s), you mean to only run the below comment (from your first post):

/usr/sbin/curl --retry 3 "https://raw.githubusercontent.com/kstamand/modsyslogui/beta/modsyslogui" -o "/tmp/modsyslogui" && chmod +x /tmp/modsyslogui && sh /tmp/modsyslogui install

Because, when you said "BETA is not managed under AMTM for updates", for me it means not able to do "u" command under amtm, which seems totally normal when testing a beta.
But, as I wrote, I was inside your addon menu and selected option "4" to update. Doing this, I thought I was using your addon update feature, which should be behaving like you described (not erase customized preset).
I am not arguing, I just want to be sure everything is clear and to do things right next time(s).

Thanks

I don't take it as arguing at all. In fact, I very much appreciate level setting details like this to ensure we are on the same page.

You did exactly as I was trying to describe. Am I correct in understanding the issue you described by following that process, because in the various tests I have tried using the latest update, the /jffs/addons/modsyslogui/presets.conf (contains any and all presets you may have saved) was not removed or erased?

If that is what is occurring for you, with the latest update installed, can you do the following:
1. SAVE a couple of presets and the capture the corresponding syslog lines and reply back here with the copy (they should look like the following and if they don't, we will need to dig further)

Feb 26 10:30:49 custom_script: Running /jffs/scripts/service-event (args: modsyslogui)
Feb 26 10:30:49 ModSyslogUI: Manager triggered. Extraction phase...
Feb 26 10:30:49 ModSyslogUI: Action: setdefault
Feb 26 10:30:49 ModSyslogUI: Set My addons as new global default.
Feb 26 10:30:49 ModSyslogUI: Process complete.

Feb 26 10:31:21 rc_service: httpd 7181:notify_rc modsyslogui
Feb 26 10:31:21 custom_script: Running /jffs/scripts/service-event (args: modsyslogui)
Feb 26 10:31:21 ModSyslogUI: Manager triggered. Extraction phase...
Feb 26 10:31:21 ModSyslogUI: Action: save
Feb 26 10:31:21 ModSyslogUI: Updated DivSky in presets.
Feb 26 10:31:21 ModSyslogUI: Process complete.

2. Issue the following command and post the results back in your response

 ls -l /jffs/addons/modsyslogui

3. Run the Shell update command, then rerun the

 ls -l /jffs/addons/modsyslogui

and post back the results

 

[kstamand]

FYI, when I ran "modsyslogui" in SSH, it brings me to the same menu if I ran "amtm" and selected "ms"

amtm and ms:

Spoiler: amtm and ms

View attachment 70512

"modsyslogui" directly after connecting to SSH:

Spoiler: modsyslogui only

View attachment 70513

So base on your answer, I think I did update the right way (using your script UPDATE function).

Again, no argue, only goal is to be sure we are aligned and ease next step(s) and test(s)

Well now, I did not realize AMTM Update would utilize the BETA update functionality. I learn something new everyday and with regards to AMTM, am really impressed with the work @thelonelycoder has done with AMTM

Thank you for providing that additional information!!!

 

[saison2023]

Am I correct in understanding the issue you described by following that process, because in the various tests I have tried using the latest update, the /jffs/addons/modsyslogui/presets.conf (contains any and all presets you may have saved) was not removed or erased?

To be very clear: I had edited "My addons" default preset to happen "AdGuardHome" at the end of the list.
Each time I did update, "My addons" default preset reverted back to default (without "AdGuardHome" at the end of the list).
I think this is the same situation described by @JB_1366 (he will confirm).

 

[saison2023]

SAVE a couple of presets and the capture the corresponding syslog lines and reply back here with the copy (they should look like the following and if they don't, we will need to dig further)

Since the last (or past 2 updates), I confirm I can see these lines in the log when I am updating "My addons" default preset to add the keyword I want.
I think the problem is not we can't reconfigure the preset(s) (like it happened to me and I had to uninstall and reinstall the addon), it is more we would like to not have to reconfigure the preset after each update.

 

[kstamand]

Since the last (or past 2 updates), I confirm I can see these lines in the log when I am updating "My addons" default preset to add the keyword I want.
I think the problem is not we can't reconfigure the preset(s) (like it happened to me and I had to uninstall and reinstall the addon), it is more we would like to not have to reconfigure the preset after each update.

I fear I am misunderstanding the process you are following and the problem you are encountering.

Can you reply back with the exact steps, plus screenshots of the issue? If if the problem is arising from the SSH Update (not the UI Save/Edit option), I really need the output of those

 ls -l /jffs/addons/modsyslogui

commands, before and after update, to know where to look for the issue.

And I thank you for your continued input and patience while I try to get this right for you and everyone

 

[saison2023]

Issue: "My addons" preset is reverted back to default after an update

BEFORE THE UPDATE
Below is the screenshot before the update ("AdGuardHome" is the word I am adding each time after an update)

ls -l /jffs/addons/modsyslogui

UPDATE

 

[saison2023]

(Message continues because limitations in attachments)
AFTER THE UPDATE

And this time, My addons keeps the settings.................................................

 

[saison2023]

And to be even more frustrating and irritating, even after running full installation command line, "My addons" preset keeps my custom addition

/usr/sbin/curl --retry 3 "https://raw.githubusercontent.com/kstamand/modsyslogui/beta/modsyslogui" -o "/tmp/modsyslogui" && chmod +x /tmp/modsyslogui && sh /tmp/modsyslogui install

I can't reproduce the problem anymore, let`s consider it closed.

 

[kstamand]

And to be even more frustrating and irritating, even after running full installation command line, "My addons" preset keeps my custom addition

/usr/sbin/curl --retry 3 "https://raw.githubusercontent.com/kstamand/modsyslogui/beta/modsyslogui" -o "/tmp/modsyslogui" && chmod +x /tmp/modsyslogui && sh /tmp/modsyslogui install

I can't reproduce the problem anymore, let`s consider it closed.

Glad to hear it's working as expected. I pushed 2 updates this morning, one for the updated help information and the other to no longer include a default set of presets / overwrite existing personalized presets. My guess is you may have caught the first update and not the second when you were having issues earlier.

Thank you for persisting and taking the time to provide troubleshooting information!!!

 

[kstamand]

@saison2023 and @JB_1366 before I go to the wider snbforums add-on users for others feedback, what are your thoughts if I provided a one line curl script (e.g. curl -LSs https://raw.githubusercontent.com/kstamand/ModSyslogUI/xxx/debug.sh | sh) that would download a script that automatically collects information related to my add-on and then uploads to a site like ix.io for my debugging purposes (it would only run when you initiate it) - would you NOT want this type of automated troubleshooting information collection or would you prefer to only provide what I request as needed and you posting it in the associated snbforums thread?

Background
My thoughts are, instead of me asking you to issue certain commands, which may be different depending on the issue, I have a single script that automatically collects ALL relevant and dependent information for my addon. Additionally, I would have a "scrubber" function to remove any potential sensitive information related to your environment (MAC address or Public IP Address), even though my collection script would not gather any of that info.

Reference
For reference purposes, here' is what the script would collect into a single upload file:
- ls -l /jffs/addons/modsyslogui (this directory contains everything related to my add one)
- ls -l /www/user/modsyslogui (this directory contains a symlink to your personalized presets file)
- cat /jffs/addons/modsysloguit/modsyslogui (this captures the version of my addon that is currently running on your router)
- cat /jfss/addons/modsyslogui/preset.conf (this captures what the list of your personalize presets you may have saved)
- cat /jffs/addons/modsyslogui/Main_LogStatus_Content.asp (this file contains all the logic of what is presented on the "System Log Page" UI, including my addons "filtering" customization of your router and how it calls the backend "handlers" in the lines above
- cat /jffs/scripts/ service-event (this contains the command line inserted by my addon to process whatever addon changes you request)
- cat /jffs/scripts/services-start (this contains the line to automatically ruin my addon everything the router reboots, to add in the customized filtering options on the "System Log" page UI
**That combination of information will let me known what version of my addon script is running, if it was successfully inserted into the default "System Log Page" for the router, and whether the automiation pieces were added correctly (e.g., when router reboots or whenever an install/update runs)

 

[CaptainLockness]

Since the beta is has been updated a few times, wouldn't it be better to update a new version number? from 1.1.0, to 1.1.1 beta, etc.?

This addon is awesome, its useful filtering out the messages that you can safely ignore and focus on troubleshooting issues. The beta is helped improve it a ton, especially updating the list on the UI instead of going by SSH. Having both SSH/UI options is helpful for new users and experienced users of the add on.

 

[saison2023]

@saison2023 and @JB_1366 before I go to the wider snbforums add-on users for others feedback, what are your thoughts if I provided a one line curl script (e.g. curl -LSs https://raw.githubusercontent.com/kstamand/ModSyslogUI/xxx/debug.sh | sh) that would download a script that automatically collects information related to my add-on and then uploads to a site like ix.io for my debugging purposes (it would only run when you initiate it) - would you NOT want this type of automated troubleshooting information collection or would you prefer to only provide what I request as needed and you posting it in the associated snbforums thread?

Background
My thoughts are, instead of me asking you to issue certain commands, which may be different depending on the issue, I have a single script that automatically collects ALL relevant and dependent information for my addon. Additionally, I would have a "scrubber" function to remove any potential sensitive information related to your environment (MAC address or Public IP Address), even though my collection script would not gather any of that info.

Reference
For reference purposes, here' is what the script would collect into a single upload file:
- ls -l /jffs/addons/modsyslogui (this directory contains everything related to my add one)
- ls -l /www/user/modsyslogui (this directory contains a symlink to your personalized presets file)
- cat /jffs/addons/modsysloguit/modsyslogui (this captures the version of my addon that is currently running on your router)
- cat /jfss/addons/modsyslogui/preset.conf (this captures what the list of your personalize presets you may have saved)
- cat /jffs/addons/modsyslogui/Main_LogStatus_Content.asp (this file contains all the logic of what is presented on the "System Log Page" UI, including my addons "filtering" customization of your router and how it calls the backend "handlers" in the lines above
- cat /jffs/scripts/ service-event (this contains the command line inserted by my addon to process whatever addon changes you request)
- cat /jffs/scripts/services-start (this contains the line to automatically ruin my addon everything the router reboots, to add in the customized filtering options on the "System Log" page UI
**That combination of information will let me known what version of my addon script is running, if it was successfully inserted into the default "System Log Page" for the router, and whether the automiation pieces were added correctly (e.g., when router reboots or whenever an install/update runs)

I personally think it is a great idea and I would make this available through your addons GUI, same place where we can edit, update, disable, uninstall,....
The action could be to always download latest version of your debug script, run it, create an archive, upload and delete after (or keep it but it could lead to space consumption and create side effect).
Be sure to well document all the steps you described, because without being paranoiac, we all want to know what is happening when we run a script.