similar to: Iptables config removed with 7.1 update

I updated to CentOS 4.5 yesterday and now I am finding the snmpd daemon is logging reams and reams of these messages: May 20 10:40:03 mx01 snmpd[2572]: Connection from - 127.0.0.1 May 20 10:40:03 mx01 snmpd[2572]: transport socket = 12 Is there a way to turn off this useless logging? I am getting these every 5 minutes (every time MRTG updates my MailScanner statistics). So far what I tried

so, Just chroot to mountpoint: http://www.cyberciti.biz/faq/unix-linux-chroot-command-examples-usage-syntax/ chroot /mounted/path /bin/bash and then .. mkinitrd (see man page for documentation) 2016-10-30 22:57 GMT+02:00 Eero Volotinen <eero.volotinen at iki.fi>: > A bit hard to say. Try chrooting into environment and rebuilding initrd? > > -- > Eero > > 2016-10-30

On Thu, 02 Apr 2015 22:42:02 -0600 Paul R. Ganci wrote: > Literally the /etc/sysconfig/iptables is gone and > the /etc/sysconfig/iptables-config is the blank template that comes with > the distribution. This seems to me to be a serious bug with the upgrade. Do you have a .rpmsave file in that directory? If so, that's your old configuration and the new version has different

I have something very strange that occurred. After updating the kernel on my host CentOS 7 Dell 2950iii I have found that one of my CentOS 7 guest VMs will no longer boot... it just stops at the grub prompt (a second VM functions just fine). I have no idea why this problem occurred and have been unable to fix it. On google I have found several suggestions as to how to repair grub but so far

On 12/22/19 12:07 PM, Rowland penny via samba wrote: >> >> Are there any suggestions to to fix the problem? >> > Cached record somewhere ? > > You seem to have done everything correctly. > Okay I discovered that any changes to my DNS are not being seeing by bind.? So exploring the Wiki

On 05/28/2016 01:35 PM, Alexander Dalloz wrote: > Am 28.05.2016 um 21:03 schrieb Paul R. Ganci: >> Starting httpd: Syntax error on line 31 of >> /etc/httpd/conf.d/olddomain.conf: >> RewriteCond: bad argument line '%{REQUEST_URI}!^/test/ > > You missed a whitespace between the server variable %{REUQEST_URI} and > the value you test against. In both cases you did.

Hi All, A while ago I replaced a Samba AD on old hardware with a another AD on newer hardware. Everything went smoothly including the demotion of the old AD. However after I did some cleanup DNS records and turned off the old hardware I noticed that there still was a NS record associated with the old AD. So I went to the wiki page https://wiki.samba.org/index.php/DNS_Administration and

I have a system with two CentOS 7.1 guests. When I created the VMs I did not have enough storage space in the default location /var/lib/libvirt/images so I moved the default location to a directory /home/vmimages. While this configuration is functional I regret creating a new storage pool in /home. I would like to create a separate partition to place the VM images removing them from their

On 10/30/2016 12:26 PM, Paul R. Ganci wrote: > <snip>I am thinking of putting the CentOS iso out and then booting the > VM into it just to poke around the file system. Otherwise my other > option is to just clone a twin VM on another server and then just > change the networking IPs/hostname. Anybody have any other ideas as to > how to debug this problem? So I booted off

> > Some more information. RSAT on the windows 10 client shows all the > proper UNIX attributes. The uidNumber is the correct 3001108. So I > removed the idmap.ldb entry for my wife's sid and restarted the AD. > The new idmap entry was created and I noticed that getent returned the > xidNumber from the new entry. It appears that the AD is ignoring the > UNIX

Can somebody tell me what this error means (server, domain etc. changed to protect the innocent)? ldapsearch -H ldap://ldapserv-1.example.com:389 -ZZ -W -D cn=Boss,dc=example,dc=com -b dc=example,dc=com uid=testuser homeDirectory ldap_start_tls: Connect error (-11) additional info: TLS error -8023:A PKCS #11 module returned CKR_DEVICE_ERROR, indicating that a problem has occurred with the

I have a strange problem that I have not been able to resolve. On October 25, 2019 I took a laptop off my domain for 10 days while traveling. When I arrived back home and placed the laptop back on the domain I ran into the problem where domain logins hang at the spinning wheel. So to work around the problem I re-imaged to a date prior to leaving for 10 days. Once I did that domain logins

On 10/09/2016 12:14 PM, Rowland Penny via samba wrote: > I would like to take you to task over 'winbindd which is adequate for > my purposes'. Anything that sssd can do, winbind can do, in fact sssd > uses some of the code from winbind. I should say one more thing. If you have a URL of a good, recent guide I will give it a try again. I want to move to hardware running CentOS 7.

On Wed, 18 May 2016 09:30:54 +0100 James Hogarth wrote: > And of course as will be pointed out by many the only right answer is yum > update anyway given cherry picking updates is not supported. The objective is not to cherry pick updates, but rather to install a second system with packages that match the first system. After fine-tuning the installed packages and stripping out the

I have some hardware running CentOS 7 and Sernet Samba 4.7 that started out as a member server that I would like to make into a 2nd DC. However I am having trouble converting it because it seems I am not removing all the remnants of the client setup. What I thought I would have to do is this: 1.) net ads leave -U administrator 2.) Remove the machine entry on the 1st DC 3.) mv /var/lib/samba

I just did a fresh minimal install of centos 7 on new hardware. While playing around with window systems I removed X windows like so: >yum remove "X Window system" and then tried to re install >yum group install "X Window system" which gives this error: Maybe run: yum groups mark install (see man yum) No packages in any requested group available to install or

I would like to move a Samba AD from one server to another. I am finding the documentation on the web somewhat lacking. Can somebody point me to documentation that might help step me through an acceptable migration path? Will the command > samba-tool drs clone-dc-database <dnsdomain> --server=SERVER -targetdir=TARGETDIR essentially do what I want? Basically clone the AD on another

On 04/12/2018 08:51 AM, Kay Diederichs wrote: >> I tried running: >>> yum groups mark install "X Window system" >> and get the same message. I tried different permutations removing the >> "s" on groups. Nothing seems to bring back the yum "X Window system" >> group. Can anyone help me resolve this issue and tell me what I did wrong?

Well I may have been over zealous and upgraded my Samba AD server to CentOS 7.5. After doing so the named service will not start. The error message I get is: May 12 00:50:55 nureyev named[11351]: Loading 'AD DNS Zone' using driver dlopen May 12 00:50:55 nureyev named[11351]: dlz_dlopen of 'AD DNS Zone' failed May 12 00:50:55 nureyev named[11351]: SDLZ driver failed to load. May

There was an update to opendkim 2.10.1 which I applied and now I am seeing this: warning: connect to Milter service inet:127.0.0.1:8891: Connection refused I tried to yum history rollback to 2.9.1 but that package has disappeared so I am evidently constrained to resolve this. Does anyone have any idea what has happened and why I might be getting that message? -- *** E-Mail is NOT a