kollmos

Hi, actually don't wanted to argue anymore about this but have to leave some comment. I fully understand the feedback from Werner and actually many thanks to do the patch! Unfortunatly I don't have the capability to do all the tests with all the different setups (otherwise I would really like to do). What I can provide is the clear view about the root cause of the issue (acutally I have some strong Linux background and I just wanted to share this here because I really appreciate the job you guys doing). Hope this helps with merging the patch from Werner. 1. The issue depends on the shell used via symlink /bin/sh. In all my systems (even non armbian) this seams to be nowerdays dash instead of bash. 2. the change raising the issue (aka root cause) is the change done in /etc/default/armbian-ramlog using arrays (commit https://github.com/armbian/build/commit/2606d17ec7e8cc28c298bbac31549f3597253121#diff-2d82f72c778209a339df3f1d9b3b300c795161a8572719b7ee9e589ef5724dc9) introduced Jun 12 2021 so it's more a regression then the issue reported is a bug. 3. the change introduce leads to the general failure that running /usr/lib/armbian/armbian-truncate-logs with /bin/sh (so actuall dash) will always fail when trying to source the configuration file /etc/default/armbian-ramlog because dash cannot handle the arrays 4. Solution to this is (you can choose) revert the change done from above (not using arrays in configuration) -> I assume there is a good reason not to revert so I was not proposing this. change the link /bin/sh in general to /bin/bash -> seams to be not compatible with all the different debian/ubuntu releases so even bigger risk, so also not a good proposal just change #!/bin/sh in armbian-truncate-logs -> should not have any other negative impact -> therefor the proposal I guess anyway (even if this costs time): if you run the armbian-truncate-logs on any of your system, this will fail as well if you did not change either the /bin/sh link or you still use older /etc/default/armbian-ramlog from before Jun 12th. On the other hand the change should not break anything because bash should be installed on every debian/ubuntu. If you try to uninstall it, you will get a big fat warning and there are related dependencies. Last thing again: I really have to thank you to do the work on armbian and can totally understand the problem with all the different bugs and the work behind and the reason asking for logs. Maybe the explanation above is sufficient to merge the patch from Werner and I believe everybody can be happy You don't have to spend a lot of time reading error logs (I'm quite sure you will not find a problem in there) any many still upcoming problem reports will be solved already (the number will increase as soon as the change above will spread over all the different systems). Cheers

Hi Werner, Understood. Unfortunatly the bug reporting is asking a lot of questions and I need to provide the armbianmonitor ourput which is not required at all. Please take the solution given as a hint to fix https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-truncate-logs I will mark this as solved because my solution given above works for me (and maybe others). Cheers

After upgrading to Focal on hc1 I countinously receive cron mails with the following content: /usr/lib/armbian/armbian-truncate-logs: 19: /etc/default/armbian-ramlog: Syntax error: "(" unexpected Similar problem is reported here: https://forum.yunohost.org/t/continuously-receiving-email-about-armbian-log/16549 After checking the code, the problem seams to be, that nowerdays /etc/default/armbian-ramlog contains something like # If USE_RSYNC is true, additional options may be specified for the rsync # commands used to synchronize logs to disk from RAM (XTRA_RSYNC_TO) or from # disk to RAM (XTRA_RSYNC_FROM). These are bash arrays to make specifying # multiple arguments easy even in the presence of whitespace. XTRA_RSYNC_TO=( ## If you use log rotation programs that datestamp their logs (e.g., runit's ## svlogd or daemontools' multilog), deleting log files while synchronizing is ## likely a good idea. # --delete ) When now /usr/lib/armbian/armbian-truncate-logs sources this file, this will always fail because the script is using `#!/bin/sh` which is actually (at least on my system) a link to dash. To fix the problem, in armbian-truncate-logs the first line should be replaced with `#!/bin/bash` and the error disappears. Would be great if this could be fixed. Cheers