In CLI you cannot login as admin. You need to login as root or, better, with another user you created in the GUI of OMV and added to the ssh group. If you also add him to the sudo group you can execute commands with elevated privileges.
You may want to read the New User Guide.
DUHHH!!! Thank You!!! its been a long time since i have used the CLI or ssh and i forgot i had to use the user root and not the admin. thank you for reminding me
thanks for the reply but its not the GUI that is looping, i can access the web GUI without issue and logon everytime. i cannot do what is in your article because the admin username/password is not being accepted using SSH either. When i try to logon to the CLI or SSH it wont let me in but i can access the Web GUI
for some reason my password no longer works when i try to log in to my server locally however the admin password works fine on the web GUI? when i try to log on locally it asks for my username, i give it admin, then asks for the password and i give it and it just blinks back to the login prompt. no bad password message at all. if purposefully put in a wrong password it tells me its wrong. i tried a reboot but after reboot i attempted to logon and i can see it accepted my password cause i saw it blink something that looked like a logon but it was so fast and i am back at the login prompt again. i have no issues whatsoever logging on to the web GUI though
Hello,
after watching the latest Technodadlife video about OMV5 i thing i already know my answer but will ask it anyways. is there a way to upgrade OMV 4 to OMV 5 or do you have to do a side by side new build?
just realized i posted this in the wrong section. sorry 
could an admin move it to an appropriate section please?
it appears that it does see the 16gb
Disk /dev/sda: 16 GiB, 17179869184 bytes, 33554432 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf5efde6c
i do agree that if i dont find the problem that this will be a band-aid and not a fix
If there was a way to increase the system drive to the full 16gb I assigned it in the VMware settings that would help a bit but I know it will not solve the issue as 8gb was working fine for a while
Its a VM that I assigned 3 hard drives to. 1 is 16gb in the VM settings but for some reason (I am guessing I messed up something in the install) it is only 8gb in OMV and that is the system drive that keeps filling up. The 2nd and 3rd assigned hard drives are 120gb a piece. One of them has a storage space for handbrake for watch and media folders. The other is where I pointed the docker folder too. I also have a 8TB external hard drive mounted.
I have in plugins, OMV extras, shell-in-the-box, and docker.
I am not to versed in which logs to look in nor do I really know how to read them in CLI. So I have been using another Ubuntu desktop I have and connect to my OMV and mount the state so I can use gedit to read the logs in a gui environment
OMG!!! i feel like an idiot!!! i thought i was in my server using putty and i was actually using my vmware console. sorry about that. so i fired up putty and yes i now see scroll bars. i feel like the idiot in your signature @donh i am still no figuring out where all my space has gone or where to get it back yet but i am still trying to learn. i really hope i dont have to do a rebuild
You can also use putty to ssh to your omv. You can scroll and then paste text here. Easier than posting pictures.
Read threw this https://unix.stackexchange.com…k-space-has-gone-on-linux
i am actually using putty... lol i do not see any way to scroll though and yes i can copy and paste text. i just figured if copy and paste a lot of text here would look messy so i thought a screenshot would be easier
so i did have to install "less" to which i did. i did the command again and could see it worked. i have attached the output of the top of output. the bottom of the output is just like it was in the pic in my previous post
Alles anzeigenShow the output of df -h.
Try apt-get clean all to clean up apt'
See how many older kernels you have. dpkg -l |grep linux-image |grep ii Keep at least one older one.
Coderoot@OMV4:~# dpkg -l |grep linux-image |grep ii ii linux-image-4.19.0-0.bpo.1-amd64-unsigned 4.19.12-1~bpo9+1 amd64 Linux 4.19 for 64-bit PCs ii linux-image-4.19.0-0.bpo.2-amd64 4.19.16-1~bpo9+1 amd64 Linux 4.19 for 64-bit PCs (signed) ii linux-image-amd64 4.19+102~bpo9+1 amd64 Linux for 64-bit PCs (meta-package) root@OMV4:~#To remove old one (line 2) dpkg -r linux-image-4.19.0-0.bpo.1-amd64-unsigned
ok... so i did the df -h command and a whole lot of info scrolled by that i am not sure what it means or how much is actually there since there are no scroll bars to scroll up and look. i have attached a pic of that output to this post.
i then did the apt-get clean all and it didn't do anything, there was no output, just a return to the prompt, but when i looked at my system it was still as full as in my previous post pic.
i then did the command to list the kernels and it listed 3 and they all look very similar so i really am not sure which two are safe to remove. i attached a pic of that as well
Alles anzeigenYou can use ncdu to check the size of each folder.
https://linux.die.net/man/1/ncdu
Install it with sudo apt install ncdu
Then run it with ncdu -x /
With the -x option it will not descend into other filesystem, so it will only analyse your root file system.
Exit ncdu with Ctrl+c
thanks for that tool. i like it. it helps alot, but something just doesnt seem right. i did the command you said to do to get the root file system and the numbers dont match. i attached a pic
Well, one question for you is what is the source of those large log files you have been deleting and what do they say inside of them?
it was a daemon.log that was over 2GB and i did look inside but did not understand anything so i figured it was a log file so it was safe to delete and i admit i just wanted to get my system running and that helped.
the second time the drive filled to the max i went to the logs folder again and this time that log was not large and i deleted another large log file just dont remember which one it was, again it got my system stable again.
today the system drive was full yet again, so i went to the logs folder and there were no extremely large log files today and i looked at the size of the logs folder itself and it was not over the 1GB mark yet my system drive is full. so i am guessing its something else this time. if i was in a windows machine i would install windirstat and find the large folder/files and fix it. Being so new to linux, i do not know what the equivalent of that is
Hello all,
first let me start off by apologizing that i am a linux noob but i am trying to learn. I have had OMV installed and running for quite a few months now. things have been pretty good with a few hiccups here and there. However, the last few days, perhaps a week, my root drive which is 8GB has been filling up to the point where there is no room and has been causing some serious stability issues. so let me try and lay out the specs of my system:
OMV 4 installed in a VM on an ESXi server. I originally gave the system drive 16gb but for some reason after installing OMV it only created an 8GB drive. i didn't realize it till later and users on here said 8GB is plenty and i should be ok
I created two more drives of 120GB each and mounted them in OMV. on one of those 2 drives i moved the docker folder too. When i first installed the docker plugin i installed it to the system drive and it grew to the point of filling up the drive. so i worked with a few users on here and moved it to one of the bigger drives.
things were well after that but as i said in the past few days i have been seeing the system drive fill to the top again, i have been going in and deleting some very large log files, but since i am a linux noob i was hoping someone would be willing to help me figure out what is wrong. other places to look? other commands to try?
please help and i will try and do my best to keep up
Thanks in advance
using Pi-hole as my DHCP server seems to be working for now. lets see how it goes.....
one other (probably dumb) question.... if pihole is working, do i still need adblocker addons on my browser?
Exactly , line for line, as it laid out in the How-To.
The VM switch setting is a virtual networking consideration, of ESXi. (But, since I don't have it, I couldn't tell you the exact reasons why it's needed.)
Don't forget to check that the are no spaces before the slashes "/" in bind points and mounts. While minor, that's a show stopper.
WOOO-HOOO!!!!! i changed the ESXi setting and i followed the guide to the letter, i even included the EV "ServerIP" like in your guide even though the docker says its not needed anymore. and lo and behold the web page finally loads!!!
thanks for everyone's patience with me, it is much appreciated
now just need to figure out how to cinfigure it. it appears my routers DHCP settings are on or off no where do i tell it what DNS server settings to hand out... hmmmm but thats not anyone on here's issue but mine
But, I noticed you're running OMV in VM, in ESXi. Did you see @ryecoaaron 's note about setting your VM's virtual switch to " promiscuous mode"?
If ryecoaaron made a special mention of it, it's safe to say that it's required.
no i did not notice that at all. i just made that change. prior to making that change i again tried building the container and putting the dns servers in as Environment Variables. although i noticed the logs looked different it still did not keep the container up longer than 4 minutes.
now that i made this ESXi change... i wonder which way i should try to install the container???
Even if all is working correctly, it still takes 3 minutes or so, before the the admin page will come up.
Give me a bit to take a look at it.
believe me, i am not being argumentive in any way. i understand it takes a bit for the web page to come up but i can tell you on my system its like clockwork... the container says "starting", then "starting health status" then "starting unhealthy" and then the container restarts itself and the process takes 4 minutes
But what I do to resolve this, once logged in to Pi-Hole, is go to settings, dns, scroll down to Advanced DNS settings, check the Use Conditional Forwarding and enter the IP of my DHCP server and the Local domain name and that resolves IP to name resolution for local hosts.
the web page never opens so i can t do this. i'll look at some of your other suggestions as well
i am hoping someone can help me. Been fighting with this for 3 days now. here is my environment:
OMV 4 is running on a VM inside a VMWare ESXi 6.5
using docker plugin
Pihole is 4.2.2
i have followed the videos from Technodadlife:
and i followed the guide from these forums:
[How To] Install Pi-Hole in Docker: Update 01/18/19 - Adding Unbound, a Recursive DNS Server.
i have followed each guide at least 3 times each some times more. each time i re-start the build, i delete the container, the network i created, and empty the folder contents it creates so i start from scratch each time
everytime i am done and the save the settings i wait for the container to build and each time it never fully startes and gets into a loop where it will be "starting" then go to "unhealthy" and then exit and restart the process.
the admin page will never load and i always see in the logs "DNS Resolution is currently unavailable
according to the 4.2 image EV "ServerIP" is no longer needed HOWEVER, i have tried builds with it and without it and neither works
i have also tried the following extra arguments and none have helped:
-p 53:53/tcp -p 53:53/udp -p 67:67/udp -p 80:80/tcp -p 443:443/tcp
-p 53:53/tcp -p 53:53/udp -p 67:67/udp -p 80:80/tcp -p 443:443/tcp --cap-add=NET_ADMIN --dns=127.0.0.1
-p 53:53/tcp -p 53:53/udp -p 67:67/udp -p 80:80/tcp -p 443:443/tcp --dns=127.0.0.1 --cap-add=NET_ADMIN
i REALLY REALLY have no idea what is wrong or why this wont work. i really hope someone can assist me
thanks in advance
