Bump, any further info I can provide?
Beiträge von antsh
-
-
Hi All,
I am trying to allow remote monitoring of a locally connected UPS, but am having issues with remote clients connecting to the service. I have attached screenshots of the setup in OMV, and a screenshot of what looks like the log saying that it isn't listening on IPv4, but is on IPv6? Is this a bug? Anything I can do to present more data?
-
Getting closer, now just getting a 504 timeout after clicking save. I can see that the tar is being decompressed into the destination, and the wget and tar processes are still running after the timeout.
-
Yup. I have run apt autoremove at some point, so might have nuked a few packages.
-
That package is indeed missing. This is a vanilla omv6 install, that is very recent (within the last month).
-
This is what it returns:
Code
Alles anzeigen# wget -O- https://images.linuxcontainers.org/images/ubuntu/kinetic/amd64/default/20221115_07:43/rootfs.tar.xz | tar xJ -C /srv/dev-disk-by-uuid-76f4ccf2-ad92-4313-ba2e-259476a90313/lxc/ tar (grandchild): xz: Cannot exec: No such file or directory tar (grandchild): Error is not recoverable: exiting now --2022-11-16 08:35:34-- https://images.linuxcontainers.org/images/ubuntu/kinetic/amd64/default/20221115_07:43/rootfs.tar.xz Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 45.45.148.8, 2602:fc62:a:1::8 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|45.45.148.8|:443... connected. HTTP request sent, awaiting response... 302 Moved Temporarily Location: https://us.lxd.images.canonical.com/images/ubuntu/kinetic/amd64/default/20221115_07:43/rootfs.tar.xz [following] --2022-11-16 08:35:34-- https://us.lxd.images.canonical.com/images/ubuntu/kinetic/amd64/default/20221115_07:43/rootfs.tar.xz Resolving us.lxd.images.canonical.com (us.lxd.images.canonical.com)... 91.189.91.123, 91.189.91.124, 2001:67c:1562::25, ... Connecting to us.lxd.images.canonical.com (us.lxd.images.canonical.com)|91.189.91.123|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 107499176 (103M) [application/x-xz] Saving to: ‘STDOUT’ - 0%[ ] 0 --.-KB/s tar: Child died with signal 13 tar: Error is not recoverable: exiting now - 0%[ ] 16.00K --.-KB/s in 0.2s Cannot write to ‘-’ (Broken pipe). -
Please use the bell in the upper right to copy&paste the error message. Your screenshot doesn't show all of the error. But from what I can see, it is failing to download the image from linuxcontainers.org. Make sure your dns is working on your OMV system and make sure your network isn't blocking linuxcontainers.org.
The full error is below. The omv machine does have working DNS and can reach linuxcontainers.org. Thanks for the help!
Code
Alles anzeigenFailed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; wget -qO- https://images.linuxcontainers.org/images/ubuntu/kinetic/amd64/default/20221115_07:43/rootfs.tar.xz | tar xJ -C /srv/dev-disk-by-uuid-76f4ccf2-ad92-4313-ba2e-259476a90313/lxc/' with exit code '2': 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=; wget -qO- https://images.linuxcontainers.org/images/ubuntu/kinetic/amd64/default/20221115_07:43/rootfs.tar.xz | tar xJ -C /srv/dev-disk-by-uuid-76f4ccf2-ad92-4313-ba2e-259476a90313/lxc/' with exit code '2': in /usr/share/php/openmediavault/system/process.inc:217 Stack trace: #0 /usr/share/openmediavault/engined/rpc/kvm.inc(2854): OMV\System\Process->execute(Array, 2) #1 /usr/share/openmediavault/engined/rpc/kvm.inc(1182): OMVRpcServiceKvm->downloadImage('ubuntu;kinetic;...', '/srv/dev-disk-b...') #2 [internal function]: OMVRpcServiceKvm->setVm(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('setVm', Array, Array) #5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Kvm', 'setVm', Array, Array, 1) #6 {main} -
I keep getting the attached error anytime I try to start an LXC container. Any initial troubleshooting I can do?
-
Yup, that works!
Code
Alles anzeigen# smartctl -d nvme,0xffffffff -x /dev/nvme0n1 smartctl 6.6 2017-11-05 r4594 [x86_64-linux-5.10.0-0.bpo.8-amd64] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: SPCC M.2 PCIe SSD Serial Number: 03F1079B084400554756 Firmware Version: ECFM22.6 PCI Vendor/Subsystem ID: 0x1987 IEEE OUI Identifier: 0x6479a7 Total NVM Capacity: 1,024,209,543,168 [1.02 TB] Unallocated NVM Capacity: 0 Controller ID: 1 Number of Namespaces: 1 Namespace 1 Size/Capacity: 1,024,209,543,168 [1.02 TB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 6479a7 29c2573536 Local Time is: Wed Sep 15 11:21:45 2021 PDT Firmware Updates (0x12): 1 Slot, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005d): Comp DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Maximum Data Transfer Size: 512 Pages Warning Comp. Temp. Threshold: 75 Celsius Critical Comp. Temp. Threshold: 80 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 7.13W - - 0 0 0 0 0 0 1 + 5.29W - - 1 1 1 1 0 0 2 + 4.36W - - 2 2 2 2 0 0 3 - 0.0490W - - 3 3 3 3 2000 2000 4 - 0.0018W - - 4 4 4 4 25000 25000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 2 1 - 4096 0 1 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff) Critical Warning: 0x00 Temperature: 27 Celsius Available Spare: 100% Available Spare Threshold: 5% Percentage Used: 2% Data Units Read: 25,189,529 [12.8 TB] Data Units Written: 25,544,247 [13.0 TB] Host Read Commands: 255,652,728 Host Write Commands: 353,189,165 Controller Busy Time: 738 Power Cycles: 853 Power On Hours: 5,595 Unsafe Shutdowns: 109 Media and Data Integrity Errors: 0 Error Information Log Entries: 1,245 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Error Information (NVMe Log 0x01, max 63 entries) Num ErrCount SQId CmdId Status PELoc LBA NSID VS 0 1245 0 0x0011 0x4004 0x004 0 1 - -
-
Can I buy/donate to you to acquire one?
-
Same issue here. I think it's pretty simple. The device in the SMART tab in the UI is listed as /dev/nvme0n1.
If I run 'smartctl -a /dev/nvme0n1' I get the same error returned:
Read NVMe SMART/Health Information failed: NVMe Status 0x2002
If I run 'smartctl -a /dev/nvme0' I get proper smart data back.
-
I just used the .run file from the NVIDIA website. I don't use built in Debian repos for NVIDIA drivers as I have run into the aforementioned problems.
-
I was having the same issues with 5.9 as well. Instead of rolling back I installed the current short lived driver from nvidia (455.45.01) and it works with the 5.9 kernel.
-
I might be not understanding something very simple, but I need a bit of help navigating this "issue".
I have a 6 port ethernet card in my OMV server. Ports 1 and 2 are configured as a bond, all of that is working fine. The rest of the ports on this card are NOT configured at all in OMV.
I took a cable and plugged it into port 6 on the above network card, and plugged the other end into my switch (different VLAN if that matters), and the unconfigured interface on port 6 pulled an IP via DHCP (on the correct VLAN). I would expect since the interface is not configured for anything in OMV, it wouldn't actually pull a DHCP lease when the link went up. I actually don't want it to pull a lease in this case (going to pass it through to some VMs).
I also tried defining the interface in the OMV UI, and setting the IPv4 and IPv6 settings to disabled, but that completely brought the interface down instead of leaving it up but disabling IPv4 and IPv6.
Is this expected behavior? Is there a way to prevent this?
-
I use Time Machine over SMB on OMV5 here. Happy to help out if anyone runs into issues. I have windows and mac clients accessing the server all over SMB, and all is working smoothly.
-
This is due to the force create mask that OMV uses as default for samba shares. You need to change the environment variables.
-
Just experienced this when upgrading to the 5.6 kernel. For anyone that comes across this the answer is to install the
linux-headers-amd64 package. This will automatically install the new headers needed when a new kernel is installed. This way you don't have to manually install the linux headers for your specific kernel every time.
-
Got it thanks. This will default these for all shares for my testing. Am I right in assuming that these settings are not currently adjustable at a per share level?
-
Hi All,
Is there an env variable available to change the file create masks and force create modes for samba shares? Right now they are are set as 0664 which works for most things. Also, this will change the create mask and create modes for every share created. Is there a way to change this at a per share level?
My use case is I am using a share as a mapped drive in windows for a steam library. This mask causes the files that steam creates at installation to be created as non-executable, which of course breaks the launching of games.
I am looking for a way to create a share that allows files to be created as executable. I am thinking modifying the create mask and mode is the way to solve this, unless there is a better way?
Thanks!
and in general, is there a way to lookup all the valid env variables that can be set across OMV?
