flash memory plugin and nginx restart on clean install

jata1 · Jan 8th 2025

I am trying to repurpose a macmini for omv (mainly for testing/learning). Have made good progress but have a couple of issues that I need a bit of help with.

1. The omv iso installer creates a linux swap partition on the install disk (a usb flash drive). After a bit of work I have managed to remove the swap and clean up system (update-initramfs). Is there a way to run the standard install without creating a swap partition? Should I start with a debian netinstall then install OMV?

2. After dealing with 1 above, i have installed the flash memory plugin. On restart the system comes up fine but I see that nginx does not start normally and monit restarts it. Any thoughts on why this is happening? The macmini is old (2012) so I thought it might have something to do with the RAM?

Any advice appreciated.

thanks.

jata1 · Jan 8th 2025

I have found some logs relating to nginx that might be helpful.

But the file does exist (/var/log/nginx/error.log) but I think it is created when the service restarts...

Code

root@macmini:~#  journalctl -u nginx -b
Jan 09 07:55:36 macmini systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server...
Jan 09 07:55:37 macmini nginx[784]: 2025/01/09 07:55:36 [emerg] 784#784: open() "/var/log/nginx/error.log" failed (2: No such file or directory)
Jan 09 07:55:37 macmini nginx[784]: nginx: configuration file /etc/nginx/nginx.conf test failed
Jan 09 07:55:37 macmini systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Jan 09 07:55:37 macmini systemd[1]: nginx.service: Failed with result 'exit-code'.
Jan 09 07:55:37 macmini systemd[1]: Failed to start nginx.service - A high performance web server and a reverse proxy server.
Jan 09 07:56:04 macmini systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server...
Jan 09 07:56:04 macmini systemd[1]: Started nginx.service - A high performance web server and a reverse proxy server.

jata1 · Jan 8th 2025

Tried to redeploy nginx using omv-salt deploy run nginx

It did make a few updates/changes but I still have the same issue on restart. Strange thing is that when monit attempts to restart nginx it is all fine.

Code

root@macmini:~# omv-salt deploy run nginx
debian:
----------
          ID: cleanup_monit_conf_dir
    Function: module.run
      Result: True
     Comment: file.find: ['/etc/monit/conf.d/openmediavault-engined.conf', '/etc/monit/conf.d/openmediavault-filesystem.conf', '/etc/monit/conf.d/openmediavault-nginx.conf', '/etc/monit/conf.d/openmediavault-phpfpm.conf', '/etc/monit/conf.d/openmediavault-system.conf']
     Started: 08:50:01.610345
    Duration: 3.94 ms
     Changes:
              ----------
              file.find:
                  - /etc/monit/conf.d/openmediavault-engined.conf
                  - /etc/monit/conf.d/openmediavault-filesystem.conf
                  - /etc/monit/conf.d/openmediavault-nginx.conf
                  - /etc/monit/conf.d/openmediavault-phpfpm.conf
                  - /etc/monit/conf.d/openmediavault-system.conf
----------
          ID: remove_monit_delay_file
    Function: file.absent
        Name: /etc/monit/monit_delay
      Result: True
     Comment: File /etc/monit/monit_delay is not present
     Started: 08:50:01.616580
    Duration: 0.634 ms
     Changes:
----------
          ID: divert_monit_delay_file
    Function: omv_dpkg.divert_add
        Name: /etc/monit/monit_delay
      Result: True
     Comment: Leaving 'local diversion of /etc/monit/monit_delay to /tmp/_etc_monit_monit_delay'
     Started: 08:50:01.617780
    Duration: 21.725 ms
     Changes:
----------
          ID: configure_default_monit
    Function: file.managed
        Name: /etc/default/monit
      Result: True
     Comment: File /etc/default/monit is in the correct state
     Started: 08:50:01.639696
    Duration: 52.533 ms
     Changes:
----------
          ID: divert_default_monit
    Function: omv_dpkg.divert_add
        Name: /etc/default/monit
      Result: True
     Comment: Leaving 'local diversion of /etc/default/monit to /tmp/_etc_default_monit'
     Started: 08:50:01.692371
    Duration: 12.567 ms
     Changes:
----------
          ID: configure_monit_monitrc
    Function: file.managed
        Name: /etc/monit/monitrc
      Result: True
     Comment: File /etc/monit/monitrc is in the correct state
     Started: 08:50:01.705110
    Duration: 151.198 ms
     Changes:
----------
          ID: divert_monit_monitrc
    Function: omv_dpkg.divert_add
        Name: /etc/monit/monitrc
      Result: True
     Comment: Leaving 'local diversion of /etc/monit/monitrc to /tmp/_etc_monit_monitrc'
     Started: 08:50:01.856455
    Duration: 12.51 ms
     Changes:
----------
          ID: configure_monit_filesystem_service
    Function: file.managed
        Name: /etc/monit/conf.d/openmediavault-filesystem.conf
      Result: True
     Comment: File /etc/monit/conf.d/openmediavault-filesystem.conf updated
     Started: 08:50:01.869172
    Duration: 139.268 ms
     Changes:
              ----------
              diff:
                  New file
              mode:
                  0644
----------
          ID: configure_monit_nginx_service
    Function: file.managed
        Name: /etc/monit/conf.d/openmediavault-nginx.conf
      Result: True
     Comment: File /etc/monit/conf.d/openmediavault-nginx.conf updated
     Started: 08:50:02.008583
    Duration: 133.825 ms
     Changes:
              ----------
              diff:
                  New file
              mode:
                  0644
----------
          ID: configure_monit_omv-engined_service
    Function: file.managed
        Name: /etc/monit/conf.d/openmediavault-engined.conf
      Result: True
     Comment: File /etc/monit/conf.d/openmediavault-engined.conf updated
     Started: 08:50:02.142538
    Duration: 142.516 ms
     Changes:
              ----------
              diff:
                  New file
              mode:
                  0644
----------
          ID: configure_monit_php-fpm_service
    Function: file.managed
        Name: /etc/monit/conf.d/openmediavault-phpfpm.conf
      Result: True
     Comment: File /etc/monit/conf.d/openmediavault-phpfpm.conf updated
     Started: 08:50:02.285187
    Duration: 135.117 ms
     Changes:
              ----------
              diff:
                  New file
              mode:
                  0644
----------
          ID: configure_monit_system_service
    Function: file.managed
        Name: /etc/monit/conf.d/openmediavault-system.conf
      Result: True
     Comment: File /etc/monit/conf.d/openmediavault-system.conf updated
     Started: 08:50:02.420432
    Duration: 138.717 ms
     Changes:
              ----------
              diff:
                  New file
              mode:
                  0644
----------
          ID: test_monit_config
    Function: cmd.run
        Name: monit -t
      Result: True
     Comment: Command "monit -t" run
     Started: 08:50:02.559930
    Duration: 13.841 ms
     Changes:
              ----------
              pid:
                  2713
              retcode:
                  0
              stderr:
              stdout:
                  Control file syntax OK
----------
          ID: reload_monit_service
    Function: service.running
        Name: monit
      Result: True
     Comment: Service reloaded
     Started: 08:50:03.513026
    Duration: 91.785 ms
     Changes:
              ----------
              monit:
                  True
----------
          ID: configure_nginx_site_webgui
    Function: file.managed
        Name: /etc/nginx/sites-available/openmediavault-webgui
      Result: True
     Comment: File /etc/nginx/sites-available/openmediavault-webgui is in the correct state
     Started: 08:50:03.605043
    Duration: 180.27 ms
     Changes:
----------
          ID: configure_nginx_security
    Function: file.managed
        Name: /etc/nginx/openmediavault-webgui.d/security.conf
      Result: True
     Comment: File /etc/nginx/openmediavault-webgui.d/security.conf is in the correct state
     Started: 08:50:03.785444
    Duration: 139.925 ms
     Changes:
----------
          ID: execute_nginx_ensite
    Function: cmd.run
        Name: nginx_ensite openmediavault-webgui
      Result: True
     Comment: Command "nginx_ensite openmediavault-webgui" run
     Started: 08:50:03.925498
    Duration: 9.096 ms
     Changes:
              ----------
              pid:
                  2733
              retcode:
                  0
              stderr:
              stdout:
                  Site configuration file 'openmediavault-webgui' is already enabled.
----------
          ID: test_nginx_service_config
    Function: cmd.run
        Name: nginx -t
      Result: True
     Comment: Command "nginx -t" run
     Started: 08:50:03.934742
    Duration: 9.009 ms
     Changes:
              ----------
              pid:
                  2734
              retcode:
                  0
              stderr:
                  nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
                  nginx: configuration file /etc/nginx/nginx.conf test is successful
              stdout:
----------
          ID: restart_nginx_service
    Function: service.running
        Name: nginx
      Result: True
     Comment: The service nginx is already running
     Started: 08:50:03.944464
    Duration: 39.033 ms
     Changes:
----------
          ID: monitor_nginx_service
    Function: module.run
      Result: True
     Comment: monit.monitor: True
     Started: 08:50:03.984205
    Duration: 12.717 ms
     Changes:
              ----------
              monit.monitor:
                  True

Summary for debian
-------------
Succeeded: 20 (changed=11)
Failed:     0
-------------
Total states run:     20
Total run time:    1.440 s

Display More

ryecoaaron · Jan 8th 2025

Quote from jata1

Is there a way to run the standard install without creating a swap partition?

Nope

Quote from jata1

Should I start with a debian netinstall then install OMV?

Yes. you end up with basically the same results either way. That is what the install script was written for.

Quote from jata1

After dealing with 1 above, i have installed the flash memory plugin. On restart the system comes up fine but I see that nginx does not start normally and monit restarts it. Any thoughts on why this is happening? The macmini is old (2012) so I thought it might have something to do with the RAM?

Slow storage? Has nothing to do with the ram. If you shutdown improperly, the folder2ram sync is probably bad. If you fix the issue, I would manually run the sync in the flashmemory plugin.

jata1 · Jan 8th 2025

Thanks ryecoaaron.

System boots fine with no issue with nginx when I uninstall the flash memory plugin. If I reinstall the plugin then the issue returns. I have tried to sync the flashmemory plugin but it doesn't fix the issue. It's a relatively new usb 3.2 sandisk flash drive so hope it is fast enough

jata1 · Jan 8th 2025

In relation to Q1 above. Can you confirm that if I use the debian netinstall I can customise the disk config to not include a swap partition? Then run the script to install OMV?

Soma · Jan 8th 2025

Quote from jata1

In relation to Q1 above. Can you confirm that if I use the debian netinstall I can customise the disk config to not include a swap partition? Then run the script to install OMV?

Fire up a VM and select manual partitioning.

See if it is possible.

I might do that tomorrow just for fun.

jata1 · Jan 8th 2025

Quote from Soma

Fire up a VM and select manual partitioning.

Doing a new install on another usb flash drive using the debian netinstall. I can confirm that you can use manual and guided partitioning and remove the swap partition as part of the process.

Will continue to install OMV using the script and see if I can resolve this flash memory / nginx issue...

jata1 · Jan 9th 2025

Lost patience with installing OMV on usb flash drives... I already have 3 OMV servers on my network so I guess that is enough. LOL.

So just installed Proxmox VE directly on the SSD on the mac. Working great. Will only switch it on to play/test stuff from time to time. Bit of a waste of a good bit of kit but better than dumping it in the garage.

Thanks all

chente · Jan 9th 2025

Quote from jata1

So just installed Proxmox VE directly on the SSD on the mac.

If you have an amd64 OMV server you don't need to do that. Just install the kvm plugin on OMV and make an OMV vm on it.

ryecoaaron · Jan 9th 2025

I have run omv on a 2012 mac mini but the OS was on an SSD. I run the flashmemory plugin on all of my systems. So, I don't know why you are having this issue. Something is starting or syncing slow.

I have been running the new flashmemory plugin that uses zram instead of folder2ram on all of my systems. No issues that I have noticed. Since this is a test system, maybe you could try that? test new version of flashmemory plugin using zram

It doesn't do a sync at startup since it is using overlayfs instead.

jata1 · Jan 9th 2025

ryecoaaron. Ok. Will do a clean install on and test both plugins.

ryecoaaron · Jan 9th 2025

Quote from jata1

test both plugins.

While I don't mind the testing where you start with the folder2ram version and upgrade, I would avoid it.

jata1 · Jan 10th 2025

Quote from ryecoaaron

While I don't mind the testing where you start with the folder2ram version and upgrade, I would avoid it.

I have a clean omv installed from omv iso with omv extras installed on brand new USB flash drive. This setup includes the default swap partition as it is based on the omv 7 iso. I have used clonezilla to clone this baseline setup before installing any plugins.

These are my test scenarios/process so far...

1. baseline omv setup (working good - clean log)

2. baseline with original folder2ram plugin (tested and working correctly)

3. remove swap partition with folder2ram plugin running (tested and working without nginx restarting.)

4. uninstall folder2ram and reboot (tested and working. no swap + nginx starting correctly)

I did not expect test 3 to work like this. In previous tests nginx needed to be restarted by monit after a reboot. I am using a brand new sandisk USB flash (same type/capacity as the one I have been having trouble with - but it is shiny new from amazon today).

Will now revert to my baseline using the image i created earlier and run same tests using the new flash plugin

jata1 · Jan 10th 2025

So another set of tests using the new flash memory plugin after restoring the original baseline using clonezilla.

1. baseline omv setup (working good - clean log)

2. baseline with new flash memory plugin (tested and working correctly)

3. remove swap partition with flash memory plugin running (failed - issue running update-initramfs -u - complains about lack of space)

So I am guessing test 3 is failing due to how the new flash memory is handling the update-initramfs command?

Or it could be something different with baseline image that I restored.

Code

root@macmini:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-6.1.0-28-amd64
cpio: write error: No space left on device
E: mkinitramfs failure cpio 2
update-initramfs: failed for /boot/initrd.img-6.1.0-28-amd64 with 1.
root@macmini:~#

ryecoaaron · Jan 10th 2025

Quote from jata1

So I am guessing test 3 is failing due to how the new flash memory is handling the update-initramfs command?

Not exactly. The sizes of filesystems created by zram-config might be too small. I actually had to increase /var/tmp for an rpi upgrade. Not sure which filesystem filled on your system. What does your /etc/ztab look like?

jata1 · Jan 10th 2025

Here is ztab file contents after setting up the new flash memory plugin

Also tried running update-initramfs -u and I do get the same error as I posted earlier.

Code

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
# swap  alg      mem_limit  disk_size  swap_priority  page-cluster  swappiness
swap    lzo-rle  250M            750M       75             0             150
# dir  alg      mem_limit  disk_size  target_dir                   bind_dir
dir    lzo-rle  150M       300M       /var/tmp                     /opt/zram/vartmp.bind
dir    lzo-rle  50M        150M       /var/lib/openmediavault/rrd  /opt/zram/rrd.bind
dir    lzo-rle  50M        150M       /var/spool                   /opt/zram/spool.bind
dir    lzo-rle  50M        150M       /var/lib/rrdcached/          /opt/zram/rrdcached.bind
dir    lzo-rle  50M        150M       /var/lib/monit               /opt/zram/monit.bind
dir    lzo-rle  50M        150M       /var/cache/samba             /opt/zram/samba.bind
# log     alg      mem_limit  disk_size  target_dir                   bind_dir                  oldlog_dir
log    lzo-rle  50M        150M       /var/log                     /opt/zram/log.bind        /opt/zram/oldlog

Display More

jata1 · Jan 10th 2025

Another update from my testing is that when using folder2ram version of flash memory plugin I have reproduced the nginx not starting properly issue.

I uninstalled the folder2ram flash memory plugin and installed the new version and I no longer have an issue with nginx not starting.

Overall the new flash memory plugin is working well. I see it creates a 750mb swap. I guess it is doing this because I do not have a swap partition/file on this test system?

ryecoaaron · Jan 11th 2025

Quote from jata1

I do get the same error as I posted earlier.

you still have the /var/spool mount in that ztab. The saltstack cache needed to be cleared. Uninstalling the plugin seems to have worked though.

Quote from jata1

Overall the new flash memory plugin is working well. I see it creates a 750mb swap. I guess it is doing this because I do not have a swap partition/file on this test system?

The plugin doesn't check to see if there is swap already configured on the system. I need to add a checkbox for the plugin to disable/enable zram swap. I also want to make the filesystem sizes configurable. Just need to think who to do that.

jata1 · Jan 11th 2025

The improvements / features you are thinking about sound good.

I just ran all the apt package updates on this test system - there are a load of updates as a new kernel etc has been released. The update has updated all the packages but failed to execute the update-initramfs - same reason as reported above.

So I uninstalled the flash memory plugin and this process forced the system to complete the update correctly.

Can you explain what and how I can configure the new flash memory plugin to increase the size of the relevant temp ram fs?

flash memory plugin and nginx restart on clean install

jata1 Jan 9th 2025

Participate now!