is it possible that they are operating in SATA PCIe?
Doubtful. I have no problem with two different mini pcie devices.
is it possible that they are operating in SATA PCIe?
Doubtful. I have no problem with two different mini pcie devices.
Run the fix6to7upgrade script. Many threads about it on the forum.
wikijs in the examples now.
I would have thought wikijs would fit with users of swag as there is a subdomain proxy conf for wikijs. The xwiki image is large at 1.15GB for the web container, plus 431MB for the postgres container. The linuxserverio container images are usually pretty light in comparison, only circa 400MB for the wikijs sqlite version which is node.js based and it can run as a non-root user.
ok, I will add it.
Patience....
I don't see any signs of hacks in that attached file. But if you were hacked, it is because you are running a severly out of date, EOL system. I would not expose ftp to the internet if you are. And make sure you are using long, complicated passwords.
Why, after successfully cloning a disk and clicking the close button, does the system write: Do I want to discard the changes? However, there is no window for saving changes.
Because you changed settings on the form and then the plugin is navigating away from the form which will lose those changes. I will look at it but it can safely be ignored.
They are all identical. this is what I have. Not yet works higher quality but I’ve used them before without issue. And it’s hard to believe that 6 out of 8 would be bad.
I wasn't saying any of them are bad. I am wondering if the cm3588 board only "sees" one when they are identical.
Was there any particular reason for picking xwiki over wikijs
I can add both to the examples. I didn't really pick one over the other. I had never heard of xwiki before and used the source github repo and compose file. And when I tried the xwiki compose, it worked. Is there a reason to prefer the linuxserver compose/image?
what is the problem I'm seeing when I run docker-compose up ?
No idea. I have never used xwiki before and don't know what your compose file looks like. I don't like java apps either. I just found a compose on the xwiki github page and it worked when I tried it. So, I added it to the example list for the compose plugin. We can possibly help with something wrong in the compose file but unlikely to be able to help with an xwiki problem.
No link needed. In the compose plugin on the Files tab, use the Add example option from the add menu. It will be listed under xwiki. Read this - https://wiki.omv-extras.org/do…v7_plugins:docker_compose
I just added an xwiki example compose to the compose plugin. It works without making any changes.
This happens when you create the user before samba is enabled. Otherwise, omv will do the sync.
Are all of your nvme drives identical? I'm curious if two different nvme drives would work. I still haven't had a chance to try yet.
OK. I guess it would only be an issue if people run snapraid from the terminal like me. People running it from the web interface should have no issue. And for me it's not an issue until I would make a change to the array.
Why not change your command line commands to use -c and the path to the new config file?
Is there anything in dmesg? Anything in logs in /var/log? What about sudo grep -E "@weekly|@monthly|@yearly|@daily" /etc/cron.d/*
I see weekly compose tasks running at midnight but they wouldn't touch your parity drive.
But it looks like the starting character is preventing the message from being processed correctly later on.
The 'span' element in the UI where the text should be is left empty:
Interesting. Probably another issue for that.
sudo apt-get update also completed successfully.
I wanted the output. Can't help without it.
Those are individual log messages. I'd like to see logs per run, all the messages of a single run grouped together, with some form of colour or icon for each to quickly see if that run passed or failed.
Access to logs per run from where the tasks are defined I mean. Either as a window on that page or a link to a global log viewer that automatically applies a filter for a specific task definition.
File an issue then. That would be a big change since all runs are stored in one log file and there is no component in OMV currently that would do the colorizing. Even things like Splunk show individual messages and don't show colorized log files. You can get the log of each run in email now though.
I also noticed lots of empty log entries in the existing log viewer after a task run:
rsync is being told to log to that file. Either rsync is logging a blank line OR the log line doesn't conform the viewer's regex (which is very open - https://github.com/openmediava…nc/90logfilespec.inc#L235).
A task run log would be highly appreciated. To be able to see when a task has run and if it ran correctly. At the moment, there is no way of knowing if all went well for automated tasks, nor what the issues were when things didn't go as planned.
rsync runs are logged to /var/log/rsync.log and you can view that in the log viewer (Diagnostics -> System Logs -> Logs). You could always have it email you as well.
For the second point, a global log viewer could be introduced to include other automated task logs as well. I do would like to be able to access/filter the logs of a specific task from its definition though.
Something other than Diagnostics -> System Logs -> Logs?
known hosts handling is a bit cumbersome. When you run a task for the first time, it is likely to fail with a "Host key verification failed" error because the key of the system you connect to is not known yet. The same issue will occur when e.g. the IP address of a known host has changed. The only way to add new keys to the list of known host is to either add it manually to `/root/.ssh/known_hosts` or make an ssh connection through ssh manually. Either way, it can not be done through the web UI.
Please file an issue here - https://github.com/openmediavault/openmediavault/issues
Can somebody share some light on this behaviour? In my opinion it needs to be addressed.
How do you know it is something OMV controlled? It would almost certainly have to be something kicked off by cron. What is the output of:
sudo find /etc/cron* -type f -exec awk '$1 == 0 && $2 == 0 { print $0 }' {} \;
sudo find /etc/cron* -type f -exec awk '$1 == 0 && $2 == "*" { print $0 }' {} \;
sudo find /etc/cron* -type f -exec awk '$1 == "*" && $2 == 0 { print $0 }' {} \;
sudo grep '0 0' /etc/crontab /etc/cron.d/* /var/spool/cron/crontabs/*
Do you have any rsync jobs or scheduled jobs?