• ryecoaaron


    Is it recommend to do this if running a helio4 from a omv4to5 upgrade:


    # disable armbian log services if found

    for service in log2ram armbian-ramlog armbian-zram-config; do

    if systemctl list-units --full -all | grep ${service}; then

    systemctl stop ${service}

    systemctl disable ${service}

    fi

    done

    rm -f /etc/cron.daily/armbian-ram-logging

    if [ -f "/etc/default/armbian-ramlog" ]; then

    sed -i "s/ENABLED=.*/ENABLED=false/g" /etc/default/armbian-ramlog

    fi

    if [ -f "/etc/default/armbian-zram-config" ]; then

    sed -i "s/ENABLED=.*/ENABLED=false/g" /etc/default/armbian-zram-config

    fi

    if [ -f "/etc/systemd/system/logrotate.service" ]; then

    rm -f /etc/systemd/system/logrotate.service

    systemctl daemon-reload

    fi


    I did this manually and onced my /var/log folder2ram sized increased from 100MB to 1000MB.


    Thanks

  • I did this manually and onced my /var/log folder2ram sized increased from 100MB to 1000MB.

    You don't have to. Just means your logs won't be compressed. I would be more concerned why you have a gig worth of log files.

    omv 5.5.12 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • No.. Because the install script will remove it based because this a helios4. I did and upgrade from omv4 to 5 so i was wondering how logs are rotated.


    i first noticed logrotate was not working then came upon this thread and read the install script which i believe is in the armbian-config utility, But, I did an upgrade not a fresh install based on this thread:


    https://forum.armbian.com/topi…-helios4-support/page/22/


    I am now trying to figure out random reboots i am having.


    https://forum.armbian.com/topi…-helios4-support/page/23/


    I just disabled the watchdog service. I then listed all the services and noticed the logrotate service not working correctly then found what the install script does.


    So now i wondering how logs will rotate so it will not fill up.




    # disable armbian log services if found

    for service in log2ram armbian-ramlog armbian-zram-config; do

    if systemctl list-units --full -all | grep ${service}; then

    systemctl stop ${service}

    systemctl disable ${service}

    fi

    done

    rm -f /etc/cron.daily/armbian-ram-logging

    if [ -f "/etc/default/armbian-ramlog" ]; then

    sed -i "s/ENABLED=.*/ENABLED=false/g" /etc/default/armbian-ramlog

    fi

    if [ -f "/etc/default/armbian-zram-config" ]; then

    sed -i "s/ENABLED=.*/ENABLED=false/g" /etc/default/armbian-zram-config

    fi

    if [ -f "/etc/systemd/system/logrotate.service" ]; then

    rm -f /etc/systemd/system/logrotate.service

    systemctl daemon-reload

    fi


    Thanks

  • Because the install script will remove it based because this a helios4

    Remove what? Removing the logrotate systemd unit file doesn't stop log rotation. As long as you have the /etc/cron.daily/logrotate file, your system should still be rotating logs.

    omv 5.5.12 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Yes. I was just wondering if this unit file (logrotate systemd) is removed if it will still do log rotation. I did notice the logrotate cron job in cron.daily but I noticed this in the logrotate script:


    if [ -d /run/systemd/system ]; then

    exit 0

    fi



    i have this directory so i am wondering if it will just exit and never do any log rotation.


    Thanks

  • i copied the logrotate.service file back for systemctl and logrotate is now working.


    I was getting this error before i went down this path of disabling /dev/zram and converting to folder2ram:


    error: /etc/logrotate.conf:18 duplicate log entry for /var/log/wtmp

    error: /etc/logrotate.conf:25 duplicate log entry for /var/log/btmp


    This was caused by have wtmp and btmp in the /etc/logrotate.d folder and in the logrotate.conf so i commented out the btmp and wtmp statements in the logrotate.conf


    I am just trying to fix issues i have been noticing since this latest release:


    cron jobs failing after 5.5.8-1 update - armbian-check-first-login.sh


    Thanks

  • i copied the logrotate.service file back for systemctl and logrotate is now working.

    I guess there used to be a systemd timer that ran logrotate as well. Maybe something changed. armbian is a moving target. I will fix the cron.daily job.



    error: /etc/logrotate.conf:18 duplicate log entry for /var/log/wtmp

    error: /etc/logrotate.conf:25 duplicate log entry for /var/log/btmp


    This was caused by have wtmp and btmp in the /etc/logrotate.d folder and in the logrotate.conf so i commented out the btmp and wtmp statements in the logrotate.conf

    This isn't caused the by install or upgrade script. Maybe the upgrade script doesn't fix the problem but it isn't meant to a be super-do everything script. I don't see this problem on a fresh install

    am just trying to fix issues i have been noticing since this latest release:


    cron jobs failing after 5.5.8-1 update - armbian-check-first-login.sh

    A cron job failing because of an armbian script issue is hard for me to fix. This should be an armbian bug report. I don't want to start having to fix or remove their scripts.

    omv 5.5.12 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Thanks for the reply. Yes, I understand.


    These were things i just noticed. my omv-backup cron job stopped working and the cron job wasn't finding the correct path /usr/sbin. I am justing to pin point what happened.


    It was around the Aug 28 timeframe.


    One thing i noticed is that if i create a cron job for omv-backup, it will not run unless i give it a certain time not @daily.


    0 0 * * * root /var/lib/openmediavault/cron.d/userdefined-137e4193-ba57-4674-a99a-24f55b8e9a7e >/dev/null 2>&1



    Do you like the helios64?


    I think i am going to wait for the next batch with ddr memory.


    Thanks

  • Do you like the helios64?

    I just have a dev board with no case right now. But it is a very nice board. My regular board with case will be here in a couple of weeks. I am getting a 2.5GBe switch tomorrow to test the faster ethernet but so far, it does everything I want.

    omv 5.5.12 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!