Posts by jata1

Thanks to you both. I had the same issue and this fix has resolved it.

gabrielwhite quick question - how did you find that the armbian script was failing? which log? I did not have any errors in my syslog

do all of the commands work? i.e. have you tried each command in a terminal/command/shell window?

I suggest the following:

1. check each command works in a terminal window

2. Once you have all commands working then you can create a shell script (filename.sh) and execute it with the command sh /path/filename.sh from the terminal. Again test that it is working.

3. final step is to create a scheduled job in the OMV GUI that runs the script - i.e. code to execute = sh /path/filename.sh

A further update on my investigation is that the OMV cron.d jobs from the rsync GUI/page are working fine.

It seems that the scheduled jobs in the GUI/page are not running - but they are enabled.

Can anyone verify that scheduled jobs are working fine with latest OMV 5 (5.5.8-1) linux version 5.7 on their system?

Have been doing more testing and setup a new scheduled job. This does not work either.

Running the script via ssh / cmd / shell works fine.

So I'm wondering if this is a bug with OMV and scheduled jobs and latest linux kernel?

Hi all - yesterday I updated to linux kernel 5.7 on my rock64 with OMV5. Everything fine but I noticed that my cron job/script that checks and updates my Dynamic DNS config was not running - I have it set to log to the syslog when it runs as part of the script. The job/script is scheduled through the OMV GUI as a scheduled job.

If I open/run the job manually through the OMV GUI it works fine. I tried changing the frequency and saving/applying but this hasn't helped.

Any ideas or things I can look into to troubleshoot?

I don't use email notifications but you might need to have OMV notifications enabled and working in the GUI config before this will work as OMV will need to send the email via a mail server.

Awesome. thanks for your help with this.

Understood. I have no idea what else could be triggering ambian-ramlog but something is and, therefore, the issue will persist for armbian builds.

I'm just a noob with enough knowledge to be dangerous but happy to help if I can. Sorry if I am not being helpful.

I already had this cron file commented out but it still ran armbian-ramlog

The only thing that I have found to stop it is to change the enabled flag in the default files below...

changed the enabled flag to false in etc/default/armbian-ramlog

changed the enabled flag to false in etc/default/armbian-zram-config

have you made all the changes outlined in the previous post and restarted?

Quote from ryecoaaron

Disabling the service means the value in the default files doesn't matter.

I changed the values back to enabled in the default files and rebooted. After reboot the services do not start (as expected) but the armbian-ramlog does execute logrotate and this prevents OMV logrotate from working.

Changed the enabled setting back to disabled and rebooted. Now everything fine again. So long story short is that you do need to do all of the following to fully disable armbian-ramlog

systemctl disable armbian-ramlog

systemctl disable armbian-zram-config

changed the enabled flag to false in etc/default/armbian-ramlog

changed the enabled flag to false in etc/default/armbian-zram-config

commented out all lines in etc/cron.daily/armbian-ram-logging

Thanks. The issue is that the FTP service starts on reboot even when disabled using systemctl disable and also disabled in the GUI.

I think there could be a bug in the logic the controls the service. If I enable the FTP service in GUI and restart, then proftpd is disabled.

all good. thanks for the help.

Any chance you can help with my last outstanding issue? see thread below

RE: FTP service running when disabled after reboot

Strange that the service does run on my clean install(s) of Armbian rock64 with OMV script. I am using latest Buster 5.4 image from the armbian website.

Have you done a install using latest build?

It is all fine now as I have disabled manually but it could affect others so I thought I would report it here.

I have tried but the command does not stop the service - see below.

Thanks for the help. Much appreciated.

Yes it is running when I check status using systemctl status proftpd - but according to the configuration it should not be running as it was off and disabled prior to the reboot.

If I enable and disable the service using the GUI, proftpd is correctly sopped and disabled

when I do a restart, I am back to the same situation so I really would like to find and resolve the root issue.

Happy Easter everyone.

I reported this issue a while ago but I still have the same issue.

FTP service (proftpd) starts on boot even when disabled

If I disable FTP service and reboot then I get a red light on the running indicator for the FTP service.

If I enable FTP and restart then I get green light on running indicator but enabled is grey.

So I think there might be a bug in the code/logic that enables/disables the FTP service.

I'm happy to investigate but I need some help to get started

screen shot of status after reboot with FTP service disabled/off

ryecoaaron I use the install script and I don't think it is disabling armbian-ramlog. On rock64 buster with kernel 5.4 it is not disabling and I have done around 5 clean installs over the last month or so. I'm using the script below.

https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash

I noticed this issue and after a bit of investigating, I have disabled armbian-ramlog manually and logrotate is working fine now.

forgot to say that I used this thread to work out how to disable ramlog

https://forum.armbian.com/topi…an-ram-logging-correctly/

In summary, I did the following and then did a reboot

systemctl disable armbian-ramlog

systemctl disable armbian-zram-config

changed the enabled flag to false in etc/default/armbian-ramlog

changed the enabled flag to false in etc/default/armbian-zram-config

commented out all lines in etc/cron.daily/armbian-ram-logging

I am currently looking into ram logging on my rock64 running Armbian 5.4 Buster.

Armbian uses armbian-ramlog that I think uses log2ram

The OMV config I use has the folder2ram plugin enabled. I'm not sure both are needed and I have issues with logrotate at the moment.

I have disabled armbian-ramlog and will see how things work over the next couple of days and report back.

Is your NanoPi running armbian?

Understood. Maybe having a GUI page for Advance/Custom settings that allows people to modify/add some of these settings to make it easier for less technical users (feature request) .

I think editing the announcement name for SMB Ito use just the hostname (without - SMB etc at the end) would be quite a good example and I am sure there are others.

Very happy with OMV5 so great work and thanks.