I deleted the existing installation and re-ran wget -O - www. napp-it.org/nappit | perl - same results. It is putting the entries in the sudoers file and presenting the same issues.
I'm not sure if this is an 18.04 only issue or not, but this was definitely the issue causing my sudo access problems. It also prevented Napp-It from running with this change as well.
I think I isolated the reason, but not the cause.
This was added to the sudoers file, but I don't know from where:
## supress Console messages from sudo
Defaults logfile=/dev/null
Defaults !syslog
##
I commented those out and everything started to work again. This link Sudo hangs after...
FWIW, I rolled back my installation back to the pre-Napp-It and Docker installs. This time I updated Docker and Docker compose via apt and the problem does not appear (at least in overnight testing).
I'm using 18.04 Server.
With my original install everything works fine until Napp-It is fired...
Found something interesting, but nothing that gives me a solution:
I have installed docker-ce on Ubuntu 18.02 and after I run the Napp-It GUI the problems start where I can no longer sudo. This time I started a new VM and only installed items required to run Napp-It.
Installed docker-ce...
Nothing on this problem. I just simply ran the installer and tried to start napp-it when this all happened. I should have tested sudo before starting so I'm going to roll back this snapshot and try again. Hopefully Gea will pop in later and give a suggestion.
I'm working on a Linux install with Napp-It and twice on an Ubuntu 18.04 VM on ESX I've run into problems where after the install script has run I can't use sudo any longer. If I try to run a sudo command after entering the password the screen just echoes back and it never executes my command...
We are looking at a second rack in our datacenter and right now we use a single 4036 switch for our IB NFS traffic. I'm trying to locate the steps for stacking/bridging 2 switches together and the best I could come up with so far was to disable SM on one switch and just run a cable between the...
Looks like we will have to stick on our current versions of OmniOS as well. We just added ConnectX-2 cards due to the cost and speed . We'll be ok with not upgrading for a while as I ran into APD issues with the current OmniOS. It's still a bummer to hear this though.
I've been doing some cursory research on ZFS tiering and it seems to come down to ARC and log cache on top of slower drives. It started me thinking about our current environment and what would be the best approach to our storage.
We were looking at moving our databases to SSD arrays with the...
Well, this is a bummer. We decided to pull the cables today and reboot everything to try to get the larger MTU and we were finally able to get ESX to let us set the vSwitch to 4092. The problem is once we pulled the cables from the switch we didn't get any lights after plugging them back in...
I finally found the updated firmware files as these are HP cards. It's been a pain trying to follow any Google links to HP right now.
For the life of me I cannot get the MTU set to 4092 on my ESX servers. I've rebooted both of them, set the mtu_4k flags, made sure to restart the SM on my...
It looks like my next logical step will be as follows (feel free to yell stop at any point)
1. Update the partitions.conf on my Voltaire 4036 to read:
Default=0x7fff , ipoib , mtu=5:ALL=full;
2. Update the MTU of my vSwitch on ESX to 4092
3. Leave OmniOS alone since it's showing an MTU of...
Even though that article discusses Windows Server 2012 will it have an impact on ESX? It doesn't look like there's a lot of new stuff for ConnectX-2 and ESX but I haven't fully combed over the Mellanox forums.
I'm not running an NVME drive just 10 Sandisk Extreme Pro 960GB SSDs in RAID-Z3.
Here's the stats on our server hardware:
2U 24 Bay 2 5 Supermicro Tyan S7012 Storage Server 2X Xeon L5640 6 Core HW RAID | eBay
We upgraded to 72GB of RAM and an M1015 driving the array. One dual port Mellanox...
I think I figured out the eui mapping information that was throwing me for a loop earlier.
First, I looked at Napp-It:
root@NAPPIT:~# stmfadm list-target -v
Target: eui.0002C903000FC8BC
Operational Status: Online
Provider Name : srpt
Alias : -
Protocol...
How do you find the eui WWNN of the ESX server? That's what's been tripping me up so far. I'm sure it's simple, but I just can't locate the right command. It's also been a long week so I'm not quite on my A game right now.
I ran 2 quick tests with the I/O Analyze fling (I/O Analyzer – VMware...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.