Adding a Active Directory (AD) Domain Account to /etc/sudo is fairly easy on Centrify Express for CentOS 6. Suppose you have an AD Group called “Sys_Admin”, just add it to the
## Allow root to run any commands anywhere
root ALL=(ALL) ALL
%System_Admin ALL=(ALL) ALL
If it is an individual user, just get the userid from Active Directory
As of 07/28/2014 Bug https://ask.openstack.org/en/question/35705/attempt-of-rdo-aio-install-icehouse-on-centos-7/ is still pending and workaround suggested above should be applied during two node RDO packstack installation.
Successful implementation of Neutron ML2&&OVS&&VXLAN multi node setup requires correct version of plugin.ini -> /etc/neutron/plugins/ml2/ml2_conf.ini which appears to be generated with errors by packstack.
Many environments make use of sudo to delegate access to administrative or application user accounts. This can make ssh X forwarding tricky because your environment changes as you sudo to another user. This is a workaround that will allow you to continue your ssh X forwarding session while running sudo as another user. How to […]
The post X Forwarding Sudo SSH Session appeared first on Backdrift.
This is a very nice project I have been working on. The hardware at hand – two servers, with a shared SAS bus containing several SAS disks. Since it’s a shared bus, no RAID solution would cut it, and as I don’t want to waste disks with ASM (“normal” redundancy meaning half the size…), I went to ZFS storage.
ZFS is a wonderful technology, with many advantages, but with some dangerous pitfalls. As I prefer Linux, I did not bother with any Sloaris solutions, and went directly to Centos 6. I will describe my cluster setup below.
If you come across this error while attempting to mount an NFS filesystem it means that the statd process is not running. # mount -a -t nfs mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount […]
The post Fixing rpc.statd is not running but is required for remote locking appeared first on Backdrift.
Step 1: Enable Debugging for Centrify
# /usr/share/centrifydc/bin/addebug on
/var/log/centrify_client.log does not exist. Creating now.
Send HUP signal to rsyslogd
Configure log level in /etc/centrifydc/centrifydc.conf
Centrify DirectControl debug logging is on
Step 2: Collect support information via adinfo_extra.sh
Pointer 1: To install specific version of packages do
# pip install 'numpy==1.5.1'
Pointer 2: To show what files was installed
# pip show --files numpy
Pointer 3: Uninstall a package
The problem: protocol daemon is not running While attempting to commit a change on a new vyatta router install I ran into this error: vyatta@host# commit [[interfaces bonding bond0]] failed [ interfaces ethernet eth1 ] % Protocol daemon is not running [[interfaces ethernet eth1]] failed [ interfaces ethernet eth0 ] % Protocol daemon […]
The post How to fix vyatta protocol daemon is not running appeared first on Backdrift.