similar to: fails to start @boot - service-start-limit-hit

hi, free IPA everyone? I wanted to ask if you maybe seen below errors. I'm trying regular: $ ipa-client-install --principal=admin --password="ccnR.Biotec13#diradm" --enable-dns-updates and it fails: ... ?? Valid From:? 2018-01-09 16:51:35 ??? Valid Until: 2038-01-09 16:51:35 Enrolled in IPA realm PRIVATE.CCNR.CEB.PRIVATE.CAM.AC.UK Please make sure the following ports are

I'm setting up for libvirt remote access on a xend host. On the host, xl info | egrep "release|xen_version" release : 5.6.10-24.gde48f93-default xen_version : 4.13.0_12-lp151.700 systemctl --version systemd 234 I've installed rpm -qa libvirt-daemon-xen libvirt-daemon-xen-6.2.0-lp151.890.1.x86_64 libvirtd --version libvirtd (libvirt)

Hi, Can u please explain for what purpose pacemaker cluster used here? Regards, Jiffin On Thursday 07 December 2017 06:59 PM, Tomalak Geret'kal wrote: > > Hi guys > > I'm wondering if anyone here is using the GlusterFS OCF resource > agents with Pacemaker on CentOS 7? > > yum install centos-release-gluster > yum install glusterfs-server

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi guys I'm wondering if anyone here is using the GlusterFS OCF resource agents with Pacemaker on CentOS 7? yum install centos-release-gluster yum install glusterfs-server glusterfs-resource-agents The reason I ask is that there seem to be a few problems with them on 3.10, but these problems are so severe that I'm struggling to believe I'm not just doing something wrong. I created

If you just want active/standby, you can simply use corosync/pacemaker as other already suggest and don?t use Director. I have a dovecot HA server that uses floating IP and pacemaker to managed it, and it works quite well. The only real hard part is having a HA storage. You can simply use a NFS storage shared by both servers (as long as only one has the floating IP, you won?t have issue with the

Hi guys. I have a domain definition with this: ... ? <qemu:commandline> ??? <qemu:arg value='-fw_cfg'/> ??? <qemu:arg value='name=opt/com.coreos/config,file=/00-VMs/oshift1node.ign'/> ? </qemu:commandline> </domain> at the bottom of xml. 'virsh' creates domain a okey but in VM I do not see ignition happened - it's fedora coreos -

hi guys in my qutest I have this: ...     <filesystem type='mount' accessmode='passthrough'>       <source dir='/home'/>       <target dir='/home'/>     </filesystem> ... and on the host /home/* are user home dirs which are automounted off a glusterfs volume. The guest starts okey, I can see dirs under /home but if I go to /home/userA I

hi guys I'm trying a typical, I'd presume, setup: two libvirt hosts with one lxc guest each. boxA: $  ovs-vsctl show 1a6a2e4f-11f3-48df-becd-03b59d00a1fb     Bridge "ovsbr0"         Port nm-team             trunks: [55]             Interface nm-team         Port "vnet12"             trunks: [55]             Interface "vnet12"         Port

Hello everybody, What is the status of the freeipa/sssd and samba conflicts in the repositories? I can not wrap my mind around that two big packages are not getting security updates anymore, because they are conflicting. I will go to FOSDEM in Belgium this year to figure out more, but I am considering moving my centos systems to rockylinux. Kind regards, Jelle de Jong On 12/16/22 16:59,

Yes, but it works for small systems if you set IP source address persistence on LB or even better, if you set priority to be Active/Standby. I couldn't find a good example with dovecot director and backend on the same server, so adding another two machines seems overkill for small setups. If someone has a working example for this please make it public ! Quote from

Hello everybody, Could someone give me an estimate on when the repositories are resolving the right dependencies for the freeipa pacakges in CentOS Stream release 8? I have about +10 systems sending me alerts everyday that dnf-automatic.service is failing because of the freeipa dependency issues. Since freeipa is one of the security elements I would like to give people an estimate on when

Okey, after more extensive R&D and testing I came up with 2 final solutions: 1) external tool: wipchg 2) internal tincd: wait_device(int secs) Both solution works 100% time (tested on Win2003). I publish them here, so interested parties can do they own testing. 1) ftp://borg.uu3.net/home/borg/tmp/wipchg.tgz You need Mingw compiler to build this. 2)

Hello, On Tue, 13 Dec 2016 18:59:15 +0100 Tru Huynh <tru at centos.org> wrote: > On Tue, Dec 13, 2016 at 04:44:06PM +0000, lejeczek wrote: > > does anybody see this: > > > > unning transaction > > Warning: RPMDB altered outside of yum. > > ** Found 8 pre-existing rpmdb problem(s), 'yum check' output > > follows: > >

Hi Folks. I have installed an ipa server on a linux CentOS release 6.4 (Final). It is using outside DNS. I have https console access authenticating admin user through kerberos, and have migrated information on 80+ users and groups to it from a LDAP server. Packages related to ipa installed are: [root ~]# rpm -qa | grep ipa ipa-server-selinux-3.0.0-26.el6_4.2.x86_64

hi guys do you see the same by any chance? .... --> Processing Dependency: ipa-server-common = 4.6.4-10.el7.centos.2 for package: python2-ipaserver-4.6.4-10.el7.centos.2.noarch --> Processing Dependency: ipa-common = 4.6.4-10.el7.centos.2 for package: python2-ipaserver-4.6.4-10.el7.centos.2.noarch --> Finished Dependency Resolution Error: Package:

On Tue, Dec 13, 2016 at 04:44:06PM +0000, lejeczek wrote: > does anybody see this: > > unning transaction > Warning: RPMDB altered outside of yum. > ** Found 8 pre-existing rpmdb problem(s), 'yum check' output > follows: > ipa-admintools-4.4.0-14.el7.centos.noarch has installed conflicts > freeipa-admintools: ipa-admintools-4.4.0-14.el7.centos.noarch >

yum update was killed at an inopportune time, leaving ipa\* and xorg\* in an inconsistent state. yum-complete-transaction looks like it it's going to erase the entire system and then fails. >From the transaction files, the following are in: install 0:ipa-python-2.2.0-17.el6_3.1.x86_64 install 0:ipa-client-2.2.0-17.el6_3.1.x86_64 install

does anybody see this: unning transaction Warning: RPMDB altered outside of yum. ** Found 8 pre-existing rpmdb problem(s), 'yum check' output follows: ipa-admintools-4.4.0-14.el7.centos.noarch has installed conflicts freeipa-admintools: ipa-admintools-4.4.0-14.el7.centos.noarch ipa-client-4.4.0-14.el7.centos.x86_64 has installed conflicts freeipa-client:

CentOS Errata and Bugfix Advisory 2013:0945 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0945.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 83a7529265080304a85b1b5f09e9593dd06c8b3ebcded082a3200e667598b6c7 ipa-admintools-3.0.0-26.el6_4.4.i686.rpm