Posts by movielover76

So I have a zfs filesystem with open access mode 777 (Just for debugging purposes at the moment)

I made sure that all acls are disabled on te zfs share as well

Sharing via smb works fine with the included openmediavault UI tools

When I try to do the same for zfs, I cannot correctly write to the nfs share (if I try a nano test.txt on a remote linux instance with the nfs share mounted, I get an error trying to write stale file handle) I gave up on the default openmediavault tools and tried to share the dataset directly from the zfs pool (removing the openmediavault share)

I ran zfs set sharenfs='rw' and now I can write to the share from the remote host, but everything is set as the user:group nobody:nogroup

I would like to set it to always be the same user and group like the nfs parameter anonuid=john anongid=users but no version of that seems to work in the zfs set command

does anyone know what zfs set command I should be using

excuse my ingnorance, I'm new to zfs and even nfs (to some degree)

nevermind, I resolved the issue by deleting the readonly datasets in the pool and adjusting the fstab

I didn't need those anyway

So I have a zfs pool which I created in truenas, it's nothing special just a 12 disk raidz2. I was using truenas, but found it too restrictive so I went back to openmediavault installed the zfs plugin and imported all zfs pools and I thought everything was working, only later did I realise that the filesystem is readonly

these are the entries the omv-plugin put in my /etc/fstab

/Store/archive/ /export/archive none bind,nofail,_netdev 0 0
/Store/proxmox/ /export/proxmox none bind,nofail,_netdev 0 0
/Store/emulation/ /export/emulation none bind,nofail,_netdev 0 0

I checked the readonly status and there is only a couple that should be readonly

zfs get all | grep readonly
Store readonly off local
Store/archive readonly off inherited from Store
Store/backups readonly off inherited from Store
Store/backups/SSD_Backup readonly on local
Store/backups/SSD_Backup/config readonly on inherited from Store/backups/SSD_Backup
Store/data readonly off inherited from Store
Store/emulation readonly off inherited from Store
Store/proxmox readonly off inherited from Store

How do I fix this mount so I can read/write to the zfs pool

when I do a zpool status it says it's online with no errors, so I don't think the problem is with the pool itself

I really need to fix this without wiping out the pool and recreating it as it's got over 40TB of data and I don't have anywhere to store it temporarily

Thanks in advance

Quote from ryecoaaron

yep.

thanks, it worked great, I just didn't want to break OMV, it can be kinda picky when you mess with things that are controlled by the UI in the shell

I'm wondering if it's possible to create the zfs equilant of raid10

2 mirroed vdevs

From the UI it seems that only single vdev arrays are supported.

Can I alternatively create the zpool via command line and import it?

thanks

Quote from Soma

omv-env set OMV_RSNAPSHOT_STARTING_HOUR="4"

Thanks for the help

Quote from macom

When done run

Code

omv-salt stage run prepare
omv-salt deploy run rsnapshot

Thanks, you've been a big help

Quote from macom

You can just change the starting hour with

OMV_RSNAPSHOT_STARTING_HOUR="4"

Excuse my ignorance but how and where would I put that environment variable?

Quote from macom

You can set the environmental variable

OMV_RSNAPSHOT_DISABLE_CRON="1"

then you can create or edit the cron job

/etc/cron.d/openmediavault-rsnapshot

and it will not be changed by the plugin

Display More

Excuse my ignorance but how and where would I put that environment variable?

I've got a reasonable amount of linux skills but I'm not an expert

thanks,

Quote from ryecoaaron

Why not just run the script with the Pre-Exec and Post-exec commands. This is exactly why it is there.

If you set hourly to 0, it will only run at the cron job times (early morning) -

https://github.com/OpenMediaVa…in/omv-rsnapshot-conf#L56

https://github.com/OpenMediaVa…in/omv-rsnapshot-conf#L32

Ok so if I understand it correctly daily, weekly, monthly and yearly run around 1 - 2 am?

That's not ideal as I have a few night owls who watch my plex server, I'd prefer 4 - 6am

I would like to use the Rsnapshot plugin to backup my docker container config folders, obviously to do this I have to shut down the containers.

I've created a script to run before and after the Rnsapshot job but I don't see any way to schedule it.

Can I schedule it manually? or if it runs automatically when does it run?

I would like to do weekly backups but as I use many of these services I only want it to run during off hours

Thank you

Quote from KM0201

The general idea is "When it's finished"... This has been the case with every release since the 1.0

Understood, sorry to be a pain in the as*

Quote from macom

If you search the forum you will find that OMV6 is already quite stable. Also a lot of plugins are already available, but not all of them

omv-extras plugins - porting progress to OMV 6.x

Thank you that's helpful, last time I tried it, it still had some big issues.

I love OMV and it's great software. I apologize in advance but I'm just wondering how long it will be for a stable OMV 6.

I know developers hate that question but I'm not looking for anything specific, maybe like a quarter or general idea.

Thank you for all your hard work, I really appreciate it

I've got this issue that from my windows machine I cannot login to the webui via Brave (my default browser)

I don't get an error, I hit submit and it just refreshes to the blank login page

It works fine in Linux and the two brave instances even share the same configuration as they are sync'd and extensions.

No strange extensions bitwarden, Grammarly, screenshoter, messages for web, the camelizer

Any ideas what could be going on?

It works from firefox on the same windows machine (my current workaround)

thanks,

John

I've got the latest openmediavault 5.x installed, all current updates are installed.

I've configured the notification settings and I've tried the test email button and the configuration works. I get the test email.

However, I'm not getting any system notifications.

This is particularly an issue for my cronjobs. I have omv-backup running weekly and snapraid diff running daily.

I have selected send results via email. but the emails are not going out.

I noticed something different recently it says it will email to the user it's running as which is root

I checked mail logged in via SSH for root and it's not in root's inbox either.

Any ideas what could be wrong?

thanks

I had a similar problem installing fail2ban.

The webui component should be visible even though it didn't fully install. Go to the webui and fill in the last box action with one of the calling values. I used action_mwl. Then login via ssh and do a sudo apt-get upgrade and the package should complete it's installation

I've managed to get the ssh and webui-omv filters to work by disabling everything else.

I left everything pretty much at the default and it seems some of the filters I have enabled were causing the service to fail to run.

sshd-ddos which I would like to have enabled failed with the error in fail2ban.log

2020-08-30 16:05:13,337 fail2ban.transmitter [5092]: ERROR Jail 'ssh-ddos' skipped, because of wrong configuration: Unable to read the filter 'sshd-ddos'

I still need help with this filter

Do you know if the apache or ngix filters are needed, I'm not running any of my own sites

But I think the webui uses nginx, right?

Quote from gderf

From where are you trying to ssh in?

Look in the fail2ban configuration file to see if you have any applicable ignoreip settings.

I'm trying to login from a machine on my local network IP address 192.168.1.235

I left the ignoreip setting at the default value 127.0.0.1

I can see the invalid login attempts in the log file configured in fail2ban

Aug 30 15:06:42 Rapier sshd[6078]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.235 user=root

Aug 30 15:06:44 Rapier sshd[6078]: Failed password for root from 192.168.1.235 port 50570 ssh2

Aug 30 15:06:49 Rapier sshd[6078]: Failed password for root from 192.168.1.235 port 50570 ssh2

Aug 30 15:06:55 Rapier sshd[6078]: Failed password for root from 192.168.1.235 port 50570 ssh2

Aug 30 15:06:57 Rapier sshd[6078]: Connection closed by authenticating user root 192.168.1.235 port 50570 [preauth]

Aug 30 15:06:57 Rapier sshd[6078]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.235 user=root

Aug 30 15:07:01 Rapier sshd[6166]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.235 user=root

Aug 30 15:07:03 Rapier sshd[6166]: Failed password for root from 192.168.1.235 port 50572 ssh2

Aug 30 15:07:08 Rapier sshd[6166]: Failed password for root from 192.168.1.235 port 50572 ssh2

Aug 30 15:07:11 Rapier sshd[6166]: Failed password for root from 192.168.1.235 port 50572 ssh2

Aug 30 15:07:13 Rapier sshd[6166]: Connection closed by authenticating user root 192.168.1.235 port 50572 [preauth]

Aug 30 15:07:13 Rapier sshd[6166]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.235 user=root

Aug 30 15:07:17 Rapier sshd[6236]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.235 user=root

Aug 30 15:07:19 Rapier sshd[6236]: Failed password for root from 192.168.1.235 port 50574 ssh2

Aug 30 15:07:25 Rapier sshd[6236]: Failed password for root from 192.168.1.235 port 50574 ssh2

Aug 30 15:07:30 Rapier sshd[6236]: Failed password for root from 192.168.1.235 port 50574 ssh2

Aug 30 15:07:31 Rapier sshd[6236]: Connection closed by authenticating user root 192.168.1.235 port 50574 [preauth]

Aug 30 15:07:31 Rapier sshd[6236]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.235 user=root

Aug 30 15:07:35 Rapier sshd[6332]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.235 user=root

Aug 30 15:07:37 Rapier sshd[6332]: Failed password for root from 192.168.1.235 port 50576 ssh2

Aug 30 15:07:46 Rapier sshd[6332]: Connection closed by authenticating user root 192.168.1.235 port 50576 [preauth]

Aug 30 15:08:43 Rapier sshd[6580]: Accepted password for root from 192.168.1.235 port 50578 ssh2

Aug 30 15:08:43 Rapier sshd[6580]: pam_unix(sshd:session): session opened for user root by (uid=0)

It looks like the Fail2ban service is failing to load

docker.service loaded active running Docker Application Container Engine

● fail2ban.service loaded failed failed Fail2Ban Service

folder2ram_startup.service loaded active exited folder2ram systemd service

Thanks for the reploy

I've installed and configured fail2ban

I enabled ssh, ssh-ddos, omv-webui, ngix-404 and both apache jails.

I started off trying to test it with ssh (the most important to me)

But sshing into the server lets me try 3 times and then disconnects me and I can immediately try the command again

I've done it like 5 times in a row and the ban never takes effect.

I even tried manually restarting the fail2ban service via the command line.

Any ideas what could be wrong?