Don't enable them to public (webui or calibre) use a socks proxy with ssh tunneling or an openvpn server with certificates.
I would like to do that - but I have no idea how to use the tunneling or VPN with my Kindle
Don't enable them to public (webui or calibre) use a socks proxy with ssh tunneling or an openvpn server with certificates.
I would like to do that - but I have no idea how to use the tunneling or VPN with my Kindle
I have done a clean install of OMV. Never had plex installed
Only had 3 things open to WAN:
SSH
Calibre
WebGUI login using https
Now only have SSH open, using public / private keys
Have also installed the fail2ban plugin and enabled it for SSH. Next thing to do is enable it for calibre and webgui but I still need to figure out how to do that exactly.
I used to - Now have wan port closed and private / public key auth enabled.
To use ssh from Windows you need a Windows ssh client. Try PuTTY:
Thank you - I figured out where I was going wrong. Forgot to add the Private key to PuTTY
I think I am being an idiot, but how do I do this bit from a Windows 8 machine?
ZitatAlles anzeigenNow in the same linux desktop we can type in terminal
ssh ssh-user-access@IP_OF_NAS -i .ssh/privatekey
If the private key is pass phrase protected it will ask to provide it.
If we must perform root operations we type su in the console and type the root password.
Now it is happening almost every second day.
It doesn't seem to be related to any sort of OMV updates.
I'm now going to go through each of my installed plugins and kill them to see if it is perhaps one of them.
I am having this rather weird and very frustrating issue with OMV 2.1.17 (Linux 3.16.0-0.bpo.4-amd64 kernel)
My entire home network and internet connection times out every few minutes, at the same time as the CPU and Network spikes in OMV. A reinstall of OMV fixes this problem for anywhere between a few days and a few weeks, then it starts happening again.
Intel i7-4770 CPU
Asus Z87I-PRO Motherboard
16GB RAM
Corsair 750 watt PSU
2 port SATA card
6 x 4TB HDD in a software RAID 5
2 x SSD (One for OMV, one for Virtual Machine)
OMV-Extras.org 2.7
openmediavault-calibre 1.1
openmediavault-mysql 2.1
openmediavault-extplorer 1.1
openmediavault-nut 2.0
openmediavault-virtualbox 1.3
OMV is configured to receive an IP via DHCP, as is the Windows 7 VirtualMachine.
I Don't think it is the NIC as this issue still happens when I use the onboard wireless card instead of the hard wire network
Please could someone help me get to the bottom of this issue?
Did you try resetting your graphs with that post I had here before????
So my old post fixed it for you??? I had a post here that would have fixed it but someone hid it....
Yes, the old post fixed it, thank you! I missed your post here - didnt see it before it got hidden
Where are you looking for the nut graphs.???? They are in different area in the web gui. You know this, yes???
Check Diagnostic/Services and look for the TAB for nut there.
That is where I am going, and it shows the sad face bar graph images. Then I click on the refresh image, and get that error I posted above
EDIT: This thread had the answer openmediavault-nut 1.02 - Failed to execute command 'omv-mkgraph 2>&1': ERROR: No DS called 'value' in '/var/lib/rrdcached/db//localhost/nut-ups/percent-charge.rrd'
I missed it on my first google as I gave my UPS a custom name so google returned no results
I've recently upgraded my OMV (from 0.5 to 1 then to 2), and reinstalled NUT
Now I'm getting this error when trying to view the graphs (such as charge or load)
Error #4000:
exception 'OMVException' with message 'Failed to execute command 'export LANG=C; omv-mkgraph 2>&1': ERROR: No DS called 'value' in '/var/lib/rrdcached/db//localhost/nut-AtheneumUPS/percent-charge.rrd'' in /usr/share/openmediavault/engined/rpc/rrd.inc:65
Stack trace:
#0 [internal function]: OMVRpcServiceRrd->generate(NULL, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('generate', NULL, Array)
#3 /usr/sbin/omv-engined(500): OMVRpc::exec('Rrd', 'generate', NULL, Array, 1)
#4 {main}
Nut Version is openmediavault-nut 2.0
OMV is 2.1 (Stone Burner) with Linux 3.2.0-4-amd64 kernel
OMV Extras version is 1.29
Please could someone assist me in trying to sort out this error?
Zitat von "Timbo66"The links to omv-plugins.org report 403 and 502 errors
Marcel.Beck, I'm getting this error now
I've made a few adjustments and added a picture of what the repos must look like after you edit them for the second time.
I hope it's useful!
It was pointed out here (http://forums.openmediavault.o…=9&t=2201&start=30#p14158) by ryecoaaron that I was using the wrong kernels, so bakc to the drawing board. After much googling, reading, and even more Clonezilla, this is what I came up with:
Starting with a disk image with working LAN on the 2.6 kernel (got it from Nay001 - we have the same setups) - Because the LAN drivers had to be built and injected, some tools are already on the system, that are necessary to the build. When I have more time, I will try from scratch and figure out everything that one needs to do.
NB: VirtualBox has not been installed yet!
First edited DNS settings (otherwise OMV doesn't see the repos):
then modified my sources list to look like:
#
# deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official Snapshot amd64 LIVE/INSTALL Binary 20130618-19:29]/ squeeze main non-free
#deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official Snapshot amd64 LIVE/INSTALL Binary 20130618-19:29]/ squeeze main non-free
#deb http://debian.mirror.ac.za/debian/ squeeze main
#deb-src http://debian.mirror.ac.za/debian/ squeeze main
deb http://debian.mirror.ac.za/debian/ testing main
deb-src http://debian.mirror.ac.za/debian/ testing main
#deb http://security.debian.org/ squeeze/updates main non-free
#deb-src http://security.debian.org/ squeeze/updates main non-free
deb http://security.debian.org/ testing/updates main non-free
deb-src http://security.debian.org/ testing/updates main non-free
# squeeze-updates, previously known as 'volatile'
deb http://debian.mirror.ac.za/debian/ squeeze-updates main non-free
deb-src http://debian.mirror.ac.za/debian/ squeeze-updates main non-free
Alles anzeigen
Add the VirtualBox repository and key:
echo "deb http://download.virtualbox.org/virtualbox/debian squeeze contrib non-free" >> /etc/apt/sources.list
wget -q http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc -O- | sudo apt-key add -
Then, to update kernel & header:
apt-get clean
apt-get update
apt-cache search linux-image
apt-get install linux-image-3.9-1-amd64
apt-get install linux-headers-3.9-1-amd64
apt-get install mdadm //this is so you can build RAID arrays in OMV - the previous mdadm version does not like the new kernel.
apt-get install parted //this is so big disks can be used
apt-get install build-essential linux-headers-3.9-1-amd64 //update the build essentials too (needed for later)
Reboot time!
Edit the repositories again (testing was only for the kernel, don't want the rest of the testing stuff, it makes OMV break as I found out).
Remove the #s from in front of the lines with 'squeeze' and add #s to the lines that have 'testing' (you want it to look like the picture below)
Then to just refresh our original sources
(The upgrade command has the benefit of upgrading the components of OMV that are listed under the web interface upgrade manager)
Then access the Web Interface and install the VirtualBox Plugin (for me, the makepasswd all 1.10-5 [12.2 kB] takes for ever.)
It will fail (@ Recompiling VirtualBox kernel modules), but no worries, SSH in again and do the following to install the latest version over the version we installed from the web interface:
wget -c download.virtualbox.org/virtualbox/4.2.16/virtualbox-4.2_4.2.16-86992~Debian~squeeze_amd64.deb
dpkg -i virtualbox-4.2_4.2.16-86992~Debian~squeeze_amd64.deb
And now I have a working OMV install with the 3.9.8 kernel and a working VirtualBox!
After a lot of playing around, I figured out that the headers weren't being installed when I did the kernel update because they required an updated libc6
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
linux-headers-3.10.1-031001-generic : Depends: libc6 (>= 2.14) but 2.11.3-4 is installed
E: Unmet dependencies. Try using -f.
Using apt-get -f install then removes linux-headers-3.10.1-031001-generic
So I have tried updating libc6, but got told I have the latest version
Then I added the testing repositories, tried updating it, but got told it cannot update due to the 2.11.3-4 version having dependencies.
root@OMV-ROCK:~# apt-get install libc6
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
libc-dev-bin : Depends: libc6 (< 2.12) but 2.17-7 is to be installed
libc6 : Breaks: locales (< 2.17)
libc6-dev : Depends: libc6 (= 2.11.3-4) but 2.17-7 is to be installed
locales : Depends: glibc-2.11-1
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
Alles anzeigen
What should I do now?
Please could someone help me with this:
I am running OpenMediaVault 0.4.35 with kernel 3.9.10/3.10.1 (have tried with both) and I am trying to install virtual box.
This is as far as I get with the Command line install (the webUI install fails at a point with a communication error)
root@OMV-ROCK:~# uname -a
Linux OMV-ROCK 3.9.10-030910-generic #201307131608 SMP Sat Jul 13 20:08:47 UTC 2013 x86_64 GNU/Linux
root@OMV-ROCK:~# dpkg --configure -a
root@OMV-ROCK:~# apt-get install linux-headers-`uname -r`
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-headers-3.9.10-030910-generic is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'linux-headers-3.9.10-030910-generic' has no installation candidate
Alles anzeigen
Where/how can I get the Linux headers for the 3.9.10 or 3.10.1 kernels?