Beiträge von bigboo3000

Thank you guys!

It's perfect now, I have clean and quick backups!

I think that the compose plug-in should only backup the appdata folder by default, and add an option to backup other volumes. It would be the best default setting for the vast majority of users.

It doesn't make much sense to add # SKIP_BACKUP to all volumes lines to all my compose files.

HI

with the last compose plug-in you added this new capability:

- Support backup for paths using environment variables

I saw in the wiki here that we can exclude volumes for backup:


https://wiki.omv-extras.org/doku.php?id=omv7:omv7_plugins:docker_compose#schedule_updates_and_backups


If I respect exemple of the image in the wiki each config folder is backuped twice (one in "0" folder and one in "1" volume).


Maybe you should update the image in the wiki (./config volume should also have # SKIP_BACKUP

Hi

I updated the script with just zstd instead of gzip:

It's almost 4x faster on my machine (j4105) and the archive is smaller

gzip:

40021000192 bytes (40 GB, 37 GiB) copied, 665.096 s, 60.2 MB/s

final file size: 1,32 Gb

zstd:

40021000192 bytes (40 GB, 37 GiB) copied, 181.178 s, 221 MB/s

final file size: 1,16 Gb

replace gzip with zstd by bigboo3000 · Pull Request #51 · OpenMediaVault-Plugin-Developers/openmediavault-backup

Hi I updated the script with just zstd instead of gzip: It's almost 4x faster on my machine (j4105) and the archive is smaller gzip: 40021000192 bytes (40 GB,…

github.com

HI,

I have random hard reboots since november on my server (Asrock J4105-ITX with a WD 14TB HDD and a Samsung 850 pro 512GB SDD) . I couldn't find the cause until yesterday:

When I enable SMART monitoring in OMV UI the system randomly hard reboot every few hours/days without anything in logs.

If then I disable SMART monitoring in OMV UI the problem (random reboots) stays until I completely power-off/power-on the server.

I suspect this commit trigger a bug with the samsung SDD 850 pro firmware and the bug stays until a complete power-off.

For now I disabled SMART monitoring and my system is stable again.

What can I do to help fix the problem?

Sorry to hijack your thread but maybe it can help you I finally found the cause of my random hard reboots: it's an issue with a Samsung 850 pro SSD and SMART monitoring since OMV update 6.9.6 in november. I'll make a new thread for this problem.

It's a hard reboot for sure.

I switched motherboard (with same ASMedia ASM1061), RAM and power supply so they can't be the cause.

Only remaining things are:

integrated ASMedia ASM1061 on the motherboard

the 3 disks I use (1HDD an 2 SDDs, all SATA)

the 3 SATA cables

for my last test I plugged the SSD1 boot disk with OMV with a SATA>USB cable, I used his previous SATA cable for the second SSD and I disabled ASM1061 in the bios,

So now I have boot SSD1 with USB

HDD and SSD2 on native intel SATA ports.

For now no more reboots since 4 days.

That's why I strongly suspect a kernel bug with ASM1061.

Nothing in the log, that's the problem, it seems everything is fine then the next line is a new boot.

Hi

I have exactly the same problem on my server (Asrock J4105-itx motherboard) since approximately 2 months.

I even switched motherboard (Asrock Q1900dc-itx), RAM and PSU and the problem persisted with random reboots.

One thing in common with these boards is integrated ASMedia ASM1061 for 2 additional SATA ports (and Realtek Lan).

I suspect there is an issue with ASM1061 and a recent linux kernel update, but I'm still not 100% sure.

Now I'm using the Asrock J4105 again.

I disabled AS1061 in BIOS, and I disabled SMART monitoring in OMV.

No more reboot in 48h, but sometimes I had reboot every 5 days so I'm not sure it's completely fixed.

seems great but I don't see 7.0.2 in updates

I think an option here could be useful for non-experts and it make sense with the update function.

Thanks for your suggestion!

Oh sorry I didn't understand it restarted containers after update.

But then could you add a "prune old images" to automatically clean them in the Schedule tab ?

HI,

I have several dockers on my OMV setup and it's quite boring to do that for each container:

• Go to Services > Compose > Containers and select the container you want to update.
• Press the Pull button. This will download the latest available image from that container.
• Now go to Services > Compose > Files and select the file where that container is defined.
• Click Up. The containers defined in the yaml file will start with the latest available image downloaded. Your container is already updated.
• Press Prune and then press Image. Old images will be deleted.

There is Watchtower but it seems it is a security problem (access to /var/run/docker.sock ) so I'm not sure it's a good idea to install it.

The update mecanism in compose plugin only downloads new images without automatically restarting them and pruning old ones, could you add 2 new tick box in this window after the 'backup' and 'update' ones ?

One named "restart containers after update" to automatically up containers after pull

One named "prune old images" to automatically delete old images.

If something bad happens you can restore old images from backup.

Thank you

With portainer you can remove outdated images when you pull a newer one for a container.

It is possible to add this option to the compose plugin?

And also an option to automatically remove outdated images?

Hi

I updated OMV today and followed upgrade procedure here

omv6:omv6_plugins:docker_compose [omv-extras.org]

But when I click on "up" I have the following error message:

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/compose//portainer/portainer.yml' --env-file '/compose//portainer/portainer.env' up -d 2>&1': The Compose file '/compose//portainer/portainer.yml' is invalid because:
volumes.portainer-data value Additional properties are not allowed ('name' was unexpected)

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/compose//portainer/portainer.yml' --env-file '/compose//portainer/portainer.env' up -d 2>&1': The Compose file '/compose//portainer/portainer.yml' is invalid because:
volumes.portainer-data value Additional properties are not allowed ('name' was unexpected) in /usr/share/openmediavault/engined/rpc/compose.inc:420
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMVRpcServiceCompose->{closure}('/tmp/bgstatusi4...', '/tmp/bgoutputYm...')
#1 /usr/share/openmediavault/engined/rpc/compose.inc(423): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#2 [internal function]: OMVRpcServiceCompose->doCommand(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('doCommand', Array, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'doCommand', Array, Array, 1)
#6 {main}

How can I fix this?

I removed old portainer so I can no longer access it, all my other containers are still working fine.

EDIT: I clicked "Reinstall Docker" in the plugin, now it's working!

Hi
I just installed omv 3.0.83 latest image and upgraded it to 3.0.88.
I installed vdr plugin and firmware updates.
I have searched DVB-T channel and all worked correctly (I'm in France).
I then tried to install vnsi plugin to connect to a remote kodi client.
I choosed the latest 1.5.2 and clicked on "build"and it says the following (same with 1.5.1, i didn't tried other versions):

https://pastebin.com/nsaAiK3q

I use a X64 PC and a DVB-T if9135 usb tuner.

Can you help me to build this plugin?

Thanks