{"id":704,"date":"2020-04-07T23:10:05","date_gmt":"2020-04-07T22:10:05","guid":{"rendered":"https:\/\/notiz.comanet.xyz\/?p=704"},"modified":"2022-05-22T15:09:05","modified_gmt":"2022-05-22T14:09:05","slug":"linux-log2ram","status":"publish","type":"post","link":"https:\/\/notiz.comanet.xyz\/?p=704","title":{"rendered":"Linux Log2Ram"},"content":{"rendered":"\n

Treba povecati log size<\/strong><\/p>\n\n\n\n

# Size for the ram folder, it defines the size the log folder will reserve into the RAM.
# If it’s not enough, log2ram will not be able to use ram. Check you \/var\/log size folder.
# The default is 40M and is basically enough for a lot of applications.
# You will need to increase it if you have a server and a lot of log for example.
SIZE=400M <\/p>\n\n\n\n

\n\n\n\n

milan@RavaRadio:~ $ systemctl status log2ram
\u25cf log2ram.service – Log2Ram
Loaded: loaded (\/etc\/systemd\/system\/log2ram.service; enabled; vendor prese>
Active: failed (Result: exit-code) since Sun 2022-05-22 15:44:32 CEST; 7mi>
Process: 376 ExecStart=\/usr\/local\/bin\/log2ram start (code=exited, status=1\/>
Main PID: 376 (code=exited, status=1\/FAILURE)
CPU: 152ms<\/p>\n\n\n\n

May 22 15:44:32 RavaRadio log2ram[273]: ERROR: RAM disk for “\/var\/hdd.log\/” too>
May 22 15:44:32 RavaRadio log2ram[362]: \/usr\/local\/bin\/log2ram: 45: mail: not f>
May 22 15:44:32 RavaRadio log2ram[376]: ERROR: RAM disk for “\/var\/hdd.log\/” too>
May 22 15:44:32 RavaRadio log2ram[397]: \/usr\/local\/bin\/log2ram: 45: mail: not f>
May 22 15:44:32 RavaRadio systemd[1]: log2ram.service: Main process exited, cod>
May 22 15:44:32 RavaRadio systemd[1]: log2ram.service: Failed with result ‘exit>
May 22 15:44:32 RavaRadio systemd[1]: Failed to start Log2Ram.
lines 1-14\/14 (END)\u2026skipping\u2026
\u25cf log2ram.service – Log2Ram
Loaded: loaded (\/etc\/systemd\/system\/log2ram.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2022-05-22 15:44:32 CEST; 7min ago
Process: 376 ExecStart=\/usr\/local\/bin\/log2ram start (code=exited, status=1\/FAILURE)
Main PID: 376 (code=exited, status=1\/FAILURE)
CPU: 152ms<\/p>\n\n\n\n

May 22 15:44:32 RavaRadio log2ram[273]: ERROR: RAM disk for “\/var\/hdd.log\/” too small. Can’t sync.
May 22 15:44:32 RavaRadio log2ram[362]: \/usr\/local\/bin\/log2ram: 45: mail: not found
May 22 15:44:32 RavaRadio log2ram[376]: ERROR: RAM disk for “\/var\/hdd.log\/” too small. Can’t sync.
May 22 15:44:32 RavaRadio log2ram[397]: \/usr\/local\/bin\/log2ram: 45: mail: not found
May 22 15:44:32 RavaRadio systemd[1]: log2ram.service: Main process exited, code=exited, status=1\/FAILURE
May 22 15:44:32 RavaRadio systemd[1]: log2ram.service: Failed with result ‘exit-code’.
May 22 15:44:32 RavaRadio systemd[1]: Failed to start Log2Ram.
~<\/p>\n\n\n\n

Like ramlog for systemd (on debian 8 jessie for example).<\/p>\n\n\n\n

Usefull for RaspberryPi<\/strong> for not writing on the SD card all the time. You need it because your SD card doesn’t want to suffer anymore!<\/p>\n\n\n\n

Explanations: The script creates a \/var\/log<\/code> mount point in RAM. So any writing of the log to the \/var\/log<\/code>\n folder will not actually be written to disk (in this case to the sd \ncard for a raspberry card) but directly to RAM. By default, every days, \nthe CRON will launch a synchronization of the RAM to the folder located \non the physical disk. The script will also make this copy of RAM to disk\n in case of machine shutdown (but cannot do it in case of power \nfailure). This way you avoid excessive writing on the SD card.<\/p>\n\n\n\n

The script log2ram<\/a> can work on every linux system. So you can use it with your own daemon manager if you don’t have systemd.<\/p>\n\n\n\n

Log2Ram is based on transient log for Systemd here : A transient \/var\/log<\/a><\/p>\n\n\n\n

\n\n\n\n

<\/a><\/h2>\n\n\n\n

Menu<\/h2>\n\n\n\n
  1. Install<\/a><\/li>
  2. Upgrade<\/a><\/li>
  3. Customize<\/a><\/li>
  4. It is working ?<\/a><\/li>
  5. Uninstall<\/a><\/li><\/ol>\n\n\n\n

    <\/a><\/h2>\n\n\n\n

    Install<\/h2>\n\n\n\n

    <\/a><\/h3>\n\n\n\n

    With APT (recommended)<\/h3>\n\n\n\n
    echo \"deb http:\/\/packages.azlux.fr\/debian\/ buster main\" | sudo tee \/etc\/apt\/sources.list.d\/azlux.list\nwget -qO - https:\/\/azlux.fr\/repo.gpg.key | sudo apt-key add -\napt update\napt install log2ram\n<\/code><\/pre>\n\n\n\n
    <\/a><\/h3>\n\n\n\n
    Manually<\/h3>\n\n\n\n
    curl -Lo log2ram.tar.gz https:\/\/github.com\/azlux\/log2ram\/archive\/master.tar.gz\ntar xf log2ram.tar.gz\ncd log2ram-master\nchmod +x install.sh && sudo .\/install.sh\ncd ..\nrm -r log2ram-master\n<\/code><\/pre>\n\n\n\n
    REBOOT<\/strong> before installing anything else (for example apache2)<\/p>\n\n\n\n
    <\/a><\/h2>\n\n\n\n
    Upgrade<\/h2>\n\n\n\n
    You need to stop log2ram (service log2ram stop<\/code>) and start the install<\/a>.<\/p>\n\n\n\n
    <\/a><\/h2>\n\n\n\n
    Customize<\/h2>\n\n\n\n
    <\/a><\/h4>\n\n\n\n
    variables :<\/h4>\n\n\n\n
    In the file \/etc\/log2ram.conf<\/code>, there are three variables:<\/p>\n\n\n\n