[389-users] Replication Manager DN wrong
Following the directions for setting up a supplier dn for replication I created a file with the following: [root@ldap01 slapd-ldap01]# cat /root/supplier.ldif dn: cn=replication manager,cn=config objectClass: inetorgperson objectClass: person objectClass: top cn: replication manager sn: RM userPassword: X passwordExpirationTime: 20380119031407Z nsIdleTimeout: 0 And then I did cat /root/supplier.ldif /etc/dirsrv/slapd-ldap01/dse.ldif and then restarted dirsrv. When I do that I see the following. Shutting down dirsrv: ldap01... [ OK ] Starting dirsrv: ldap01...[22/Aug/2013:10:22:04 -0400] - Entry cn=replication manager,cn=config has unknown object class inetorgperson (remove the trailing space) [22/Aug/2013:10:22:04 -0400] - Entry cn=replication manager,cn=config has unknown object class person (remove the trailing space) [22/Aug/2013:10:22:04 -0400] - Entry cn=replication manager,cn=config has unknown object class top (remove the trailing space) [ OK ] How do I delete the entry or fix the entry? I tried to use ldapdelete to delete it but no luck. ldapdelete -p 389 -h ldap01.us2.example.com -w X -D -D cn=directory manager cn=replication manager,cn=config Thanks, Louis-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Replication Manager DN wrong
On Thu, Aug 22, 2013 at 10:49 AM, Louis Bohm louisb...@gmail.com wrote: Following the directions for setting up a supplier dn for replication I created a file with the following: [root@ldap01 slapd-ldap01]# cat /root/supplier.ldif dn: cn=replication manager,cn=config objectClass: inetorgperson objectClass: person objectClass: top cn: replication manager sn: RM userPassword: X passwordExpirationTime: 20380119031407Z nsIdleTimeout: 0 And then I did cat /root/supplier.ldif /etc/dirsrv/slapd-ldap01/dse.ldif and then restarted dirsrv. When I do that I see the following. Shutting down dirsrv: ldap01... [ OK ] Starting dirsrv: ldap01...[22/Aug/2013:10:22:04 -0400] - Entry cn=replication manager,cn=config has unknown object class inetorgperson (remove the trailing space) [22/Aug/2013:10:22:04 -0400] - Entry cn=replication manager,cn=config has unknown object class person (remove the trailing space) [22/Aug/2013:10:22:04 -0400] - Entry cn=replication manager,cn=config has unknown object class top (remove the trailing space) [ OK ] How do I delete the entry or fix the entry? I tried to use ldapdelete to delete it but no luck. ldapdelete -p 389 -h ldap01.us2.example.com -w X -D -D cn=directory manager cn=replication manager,cn=config Thanks, Louis -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users by chance did you edit the entry to not include the spaces after the object classes? has unknown object class top * (remove the trailing space)* edit (make backup first) the /etc/dirsrv/slapd-instancename/dse.ldif and see if the spaces are there. -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Replication Manager DN wrong
The file did have the spaces. Took me a bit but I figured out a ldapmodify command that was able to fix it by removing the spaces…. Louis On Aug 22, 2013, at 12:32 PM, Justin Edmands shockwav...@gmail.com wrote: On Thu, Aug 22, 2013 at 10:49 AM, Louis Bohm louisb...@gmail.com wrote: Following the directions for setting up a supplier dn for replication I created a file with the following: [root@ldap01 slapd-ldap01]# cat /root/supplier.ldif dn: cn=replication manager,cn=config objectClass: inetorgperson objectClass: person objectClass: top cn: replication manager sn: RM userPassword: X passwordExpirationTime: 20380119031407Z nsIdleTimeout: 0 And then I did cat /root/supplier.ldif /etc/dirsrv/slapd-ldap01/dse.ldif and then restarted dirsrv. When I do that I see the following. Shutting down dirsrv: ldap01... [ OK ] Starting dirsrv: ldap01...[22/Aug/2013:10:22:04 -0400] - Entry cn=replication manager,cn=config has unknown object class inetorgperson (remove the trailing space) [22/Aug/2013:10:22:04 -0400] - Entry cn=replication manager,cn=config has unknown object class person (remove the trailing space) [22/Aug/2013:10:22:04 -0400] - Entry cn=replication manager,cn=config has unknown object class top (remove the trailing space) [ OK ] How do I delete the entry or fix the entry? I tried to use ldapdelete to delete it but no luck. ldapdelete -p 389 -h ldap01.us2.example.com -w X -D -D cn=directory manager cn=replication manager,cn=config Thanks, Louis -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users by chance did you edit the entry to not include the spaces after the object classes? has unknown object class top (remove the trailing space) edit (make backup first) the /etc/dirsrv/slapd-instancename/dse.ldif and see if the spaces are there. -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Best way to upgrade DS servers
So if I follow this discussion correctly I should do the following steps. 1. Build my new server with OS and DS package 2. Edit the schema for my custom attributes 3. Setup a replication between my old server and the new server (as MMR) 4. Create a replication agreement between the two new servers (as MMR) 5. Remove the replication agreement between the old and new server 6. Run CLEANALLRUV to remove the old replication agreements Does this sound about right? Chris From: 389-users-boun...@lists.fedoraproject.org [mailto:389-users-boun...@lists.fedoraproject.org] On Behalf Of Rich Megginson Sent: Wednesday, August 21, 2013 3:40 PM To: Michael Lang Cc: General discussion list for the 389 Directory server project. Subject: Re: [389-users] Best way to upgrade DS servers On 08/21/2013 01:36 PM, Michael Lang wrote: Am 21.08.2013 21:31, schrieb Rich Megginson: On 08/21/2013 01:03 PM, Michael Lang wrote: Am 21.08.2013 19:25, schrieb Chris Taylor: I am looking at replacing our two CentOS DS servers which are 5.9 with some on the 6.4 channel. What is the best way to transition all the data over? Should I build them separately and import everything via ldif files, or can I add them as consumers or in our setup as another master in our MMR setup. Chris, what I've been expirencing until now, unless you replace the DS with exactly the same machine (name, ...) Why? you should try an LDIF export first and use a VirtualMachine to import your content to see any possible problems (schema violations,...) Why not install the new servers on the new machines as replication masters and replicate the data to them? you would also need to remove the replication later on (not only in the GUI, the DS keeps a lot of logs and traces for every replication you setup) Yes, that's what CLEANALLRUV is for - http://port389.org/wiki/Howto:CLEANRUV beside, I would also consider the ACL's an other Database related settings which will not be exported by a LDIF dump and will only be copied if you can use the Backup functionality. ? for the consumer setup you would still need to extend the schema first if you customized it ... Yes. regards mIke To add a little complexity I have also added some RADIUS attributes to the schema so I am assuming that, those will need to be added before I setup any replication. Any advice would be great. Thanks, Chris -- 389 users mailing list 389-users@lists.fedoraproject.orgmailto:389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.orgmailto:389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Best way to upgrade DS servers
On 08/22/2013 10:40 AM, Chris Taylor wrote: So if I follow this discussion correctly I should do the following steps. 1.Build my new server with OS and DS package 2.Edit the schema for my custom attributes 3.Setup a replication between my old server and the new server (as MMR) 4.Create a replication agreement between the two new servers (as MMR) 5.Remove the replication agreement between the old and new server 6.Run CLEANALLRUV to remove the old replication agreements CLEANALLRUV doesn't remove replication agreements, it removes the replication meta-data associated with the old servers. Does this sound about right? Yes. Chris *From:*389-users-boun...@lists.fedoraproject.org [mailto:389-users-boun...@lists.fedoraproject.org] *On Behalf Of *Rich Megginson *Sent:* Wednesday, August 21, 2013 3:40 PM *To:* Michael Lang *Cc:* General discussion list for the 389 Directory server project. *Subject:* Re: [389-users] Best way to upgrade DS servers On 08/21/2013 01:36 PM, Michael Lang wrote: Am 21.08.2013 21:31, schrieb Rich Megginson: On 08/21/2013 01:03 PM, Michael Lang wrote: Am 21.08.2013 19:25, schrieb Chris Taylor: I am looking at replacing our two CentOS DS servers which are 5.9 with some on the 6.4 channel. What is the best way to transition all the data over? Should I build them separately and import everything via ldif files, or can I add them as consumers or in our setup as another master in our MMR setup. Chris, what I've been expirencing until now, unless you replace the DS with exactly the same machine (name, ...) Why? you should try an LDIF export first and use a VirtualMachine to import your content to see any possible problems (schema violations,...) Why not install the new servers on the new machines as replication masters and replicate the data to them? you would also need to remove the replication later on (not only in the GUI, the DS keeps a lot of logs and traces for every replication you setup) Yes, that's what CLEANALLRUV is for - http://port389.org/wiki/Howto:CLEANRUV beside, I would also consider the ACL's an other Database related settings which will not be exported by a LDIF dump and will only be copied if you can use the Backup functionality. ? for the consumer setup you would still need to extend the schema first if you customized it ... Yes. regards mIke To add a little complexity I have also added some RADIUS attributes to the schema so I am assuming that, those will need to be added before I setup any replication. Any advice would be great. Thanks, Chris -- 389 users mailing list 389-users@lists.fedoraproject.org mailto:389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org mailto:389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
[389-users] Problems setting up MMR
I have 2 servers running cents 6.4 and the newest version of DS from the repos. Both serves have the same supplier DN. On the second server (ldap02) I go no errors when setting up the replication agreement. However, on the first server (ldap01) I got LDAP error: No such object. Error code: 32. The logs on ldap02 show this: [22/Aug/2013:15:14:17 -0400] conn=48 fd=71 slot=71 connection from 10.74.192.51 to 10.74.192.52 [22/Aug/2013:15:14:17 -0400] conn=48 op=0 BIND dn=cn=replication manager,cn=config method=128 version=3 [22/Aug/2013:15:14:17 -0400] conn=48 op=0 RESULT err=32 tag=97 nentries=0 etime=0 [22/Aug/2013:15:14:17 -0400] conn=48 op=1 UNBIND [22/Aug/2013:15:14:17 -0400] conn=48 op=1 fd=71 closed - U1 I guess the first thing I need to do is prove that supplier DN is really there and is the same. But I have been unable to come up with an ldapsearch that shows it. Or is the only way to see it is to grep the dse.ldif file? Louis -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Problems setting up MMR
Louis, Did you create cn=replication manager? It looks like you did not. Try this to see if it's there: ldapsearch -H ldaps://ldap02 -D cn=directory\ manager -w pass -LLLb cn=replication manager,cn=config objectclass=\* replace ldaps with ldap of course if you have not set up ssl. I believe it's in dse.ldif as well. -morgan On Aug 22, 2013, at 3:17 PM, Louis Bohm wrote: I have 2 servers running cents 6.4 and the newest version of DS from the repos. Both serves have the same supplier DN. On the second server (ldap02) I go no errors when setting up the replication agreement. However, on the first server (ldap01) I got LDAP error: No such object. Error code: 32. The logs on ldap02 show this: [22/Aug/2013:15:14:17 -0400] conn=48 fd=71 slot=71 connection from 10.74.192.51 to 10.74.192.52 [22/Aug/2013:15:14:17 -0400] conn=48 op=0 BIND dn=cn=replication manager,cn=config method=128 version=3 [22/Aug/2013:15:14:17 -0400] conn=48 op=0 RESULT err=32 tag=97 nentries=0 etime=0 [22/Aug/2013:15:14:17 -0400] conn=48 op=1 UNBIND [22/Aug/2013:15:14:17 -0400] conn=48 op=1 fd=71 closed - U1 I guess the first thing I need to do is prove that supplier DN is really there and is the same. But I have been unable to come up with an ldapsearch that shows it. Or is the only way to see it is to grep the dse.ldif file? Louis -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Problems setting up MMR
So on ldap01 its there: [root@ldap02 ~]# ldapsearch -H ldap://ldap01 -D cn=directory\ manager -w -LLLb cn=replication manager,cn=config objectclass=\* dn: cn=replication manager,cn=config objectClass: inetorgperson objectClass: person objectClass: top objectClass: organizationalPerson cn:: cmVwbGljYXRpb24gbWFuYWdlciA= sn:: Uk0g userPassword:: YmJucnVsM3M= But on ldap02 its not. When I look at the dse.ldif file I do see it there. I have restarted ldap on the server a few times so I am not sure why its not pulling it in. Should I do an ldap add and then paste it in Louis On Aug 22, 2013, at 3:25 PM, Morgan Jones mor...@morganjones.org wrote: Louis, Did you create cn=replication manager? It looks like you did not. Try this to see if it's there: ldapsearch -H ldaps://ldap02 -D cn=directory\ manager -w pass -LLLb cn=replication manager,cn=config objectclass=\* replace ldaps with ldap of course if you have not set up ssl. I believe it's in dse.ldif as well. -morgan On Aug 22, 2013, at 3:17 PM, Louis Bohm wrote: I have 2 servers running cents 6.4 and the newest version of DS from the repos. Both serves have the same supplier DN. On the second server (ldap02) I go no errors when setting up the replication agreement. However, on the first server (ldap01) I got LDAP error: No such object. Error code: 32. The logs on ldap02 show this: [22/Aug/2013:15:14:17 -0400] conn=48 fd=71 slot=71 connection from 10.74.192.51 to 10.74.192.52 [22/Aug/2013:15:14:17 -0400] conn=48 op=0 BIND dn=cn=replication manager,cn=config method=128 version=3 [22/Aug/2013:15:14:17 -0400] conn=48 op=0 RESULT err=32 tag=97 nentries=0 etime=0 [22/Aug/2013:15:14:17 -0400] conn=48 op=1 UNBIND [22/Aug/2013:15:14:17 -0400] conn=48 op=1 fd=71 closed - U1 I guess the first thing I need to do is prove that supplier DN is really there and is the same. But I have been unable to come up with an ldapsearch that shows it. Or is the only way to see it is to grep the dse.ldif file? Louis -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Problems setting up MMR
I added it with an ldapadd on host ldap02 and was able to initialize the consumer. So now that I have it working how do I test it and validate it? Louis On Aug 22, 2013, at 3:25 PM, Morgan Jones mor...@morganjones.org wrote: Louis, Did you create cn=replication manager? It looks like you did not. Try this to see if it's there: ldapsearch -H ldaps://ldap02 -D cn=directory\ manager -w pass -LLLb cn=replication manager,cn=config objectclass=\* replace ldaps with ldap of course if you have not set up ssl. I believe it's in dse.ldif as well. -morgan On Aug 22, 2013, at 3:17 PM, Louis Bohm wrote: I have 2 servers running cents 6.4 and the newest version of DS from the repos. Both serves have the same supplier DN. On the second server (ldap02) I go no errors when setting up the replication agreement. However, on the first server (ldap01) I got LDAP error: No such object. Error code: 32. The logs on ldap02 show this: [22/Aug/2013:15:14:17 -0400] conn=48 fd=71 slot=71 connection from 10.74.192.51 to 10.74.192.52 [22/Aug/2013:15:14:17 -0400] conn=48 op=0 BIND dn=cn=replication manager,cn=config method=128 version=3 [22/Aug/2013:15:14:17 -0400] conn=48 op=0 RESULT err=32 tag=97 nentries=0 etime=0 [22/Aug/2013:15:14:17 -0400] conn=48 op=1 UNBIND [22/Aug/2013:15:14:17 -0400] conn=48 op=1 fd=71 closed - U1 I guess the first thing I need to do is prove that supplier DN is really there and is the same. But I have been unable to come up with an ldapsearch that shows it. Or is the only way to see it is to grep the dse.ldif file? Louis -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
[389-users] problems with password policies
Either I'm missing something or password policies just don't work in Redhat (CentOS) directory 8.2.8. I started by creating a subtree policy on the command line: # ./ns-newpwpolicy.pl -D cn=directory\ manager -w pass -h localhost -S ou=students,dc=domain,dc=org adding new entry cn=nsPwPolicyContainer,ou=students,dc=domain,dc=org adding new entry cn=cn=nsPwPolicyEntry\,ou=students\,dc=domain\,dc=org,cn=nsPwPolicyContainer,ou=students,dc=domain,dc=org adding new entry cn=cn=nsPwTemplateEntry\,ou=students\,dc=domain\,dc=org,cn=nsPwPolicyContainer,ou=students,dc=domain,dc=org adding new entry cn=nsPwPolicy_cos,ou=students,dc=domain,dc=org modifying entry cn=config The following were created: dn: cn=nsPwPolicyContainer,ou=students,dc=domain,dc=org objectClass: top objectClass: nsContainer cn: nsPwPolicyContainer dn: cn=cn=nsPwTemplateEntry\2Cou=students\2Cdc=domain\2Cdc=org,cn=nsPwPolicyC ontainer,ou=students,dc=domain,dc=org objectClass: top objectClass: extensibleObject objectClass: costemplate objectClass: ldapsubentry cosPriority: 1 cn: cn=nsPwTemplateEntry,ou=students,dc=domain,dc=org dn: cn=nsPwPolicy_cos,ou=students,dc=domain,dc=org objectClass: top objectClass: LDAPsubentry objectClass: cosSuperDefinition objectClass: cosPointerDefinition costemplatedn: cn=cn=nsPwTemplateEntry\2Cou=students\2Cdc=domain\2Cdc=org,cn= nsPwPolicyContainer,ou=students,dc=domain,dc=org cosAttribute: pwdpolicysubentry default operational-default cn: nsPwPolicy_cos dn: cn=cn=nsPwPolicyEntry\2Cou=students\2Cdc=domain\2Cdc=org,cn=nsPwPolicyCon tainer,ou=students,dc=domain,dc=org objectClass: top objectClass: ldapsubentry objectClass: passwordpolicy cn: cn=nsPwPolicyEntry,ou=students,dc=domain,dc=org I added the policy attributes we're interested in: dn: cn=cn=nsPwPolicyEntry\2Cou=students\2Cdc=domain\2Cdc=org,cn=nsPwPolicyCon tainer,ou=students,dc=domain,dc=org passwordResetFailureCount: 600 passwordMaxFailure: 10 passwordLockout: on passwordMinLength: 6 objectClass: top objectClass: ldapsubentry objectClass: passwordpolicy cn: cn=nsPwPolicyEntry,ou=students,dc=domain,dc=org I then tried 11 ldapsearches as a user under ou=students,dc=domain,dc=org and the account was not locked out. I then checked the console and the settings weren't there. I set them and it added two additional entries: dn: cn=cn\3DnsPwPolicyEntry\2Cou\3Dstudents\2Cdc\3Ddomain\2Cdc\3Dorg,cn=nsPwP olicyContainer,ou=students,dc=domain,dc=org passwordMaxFailure: 10 passwordResetFailureCount: 600 passwordLockout: on passwordStorageScheme: ssha passwordCheckSyntax: on passwordChange: off passwordMinAge: 0 passwordExp: off passwordMustChange: off passwordMinLength: 6 objectClass: ldapsubentry objectClass: passwordpolicy objectClass: top cn: cn=nsPwPolicyEntry,ou=students,dc=domain,dc=org dn: cn=cn\3DnsPwTemplateEntry\2Cou\3Dstudents\2Cdc\3Ddomain\2Cdc\3Dorg,cn=nsP wPolicyContainer,ou=students,dc=domain,dc=org objectClass: extensibleObject objectClass: costemplate objectClass: ldapsubentry objectClass: top cosPriority: 1 cn: cn=nsPwTemplateEntry,ou=students,dc=domain,dc=org However I still can't force a user to be locked out. I did set passwordIsGlobalPolicy to on under cn=config though as far as I can tell that only affects replication of password policies. Am I missing something? thanks, -morgan -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: F19 Kernels 3.10.5, 6, 7 won't boot
On Thu, Aug 22, 2013 at 12:34:59AM -0400, Robert McBroom wrote: Updated to Fedora 19 but none of the kernels will boot. The process begins and something about an error with connecting to DBUS flashes on the screen then the cycle starts over. I can still run with kernel-3.10.4-100.fc18.x86_64 although it complains about a file missing that udev would like to see. [ 14.730648] systemd-udevd[1081]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz Working boot BOOT_IMAGE=/vmlinuz-3.10.4-100.fc18.x86_64 root=UUID=f04657c0-2964-494f-8efa-f194b7ba370a ro rd.md=0 rd.lvm=0 rd.dm=0 vconsole.keymap=us rd.luks=0 LANG=en_US.UTF-8 quiet pci=nomsi noapic irqpoll vconsole.font=latarcyrheb-sun16 3 nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off Looking at the /var/log messages see Aug 18 00:31:57 robert-pc dbus[1066]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Aug 18 00:31:57 robert-pc dbus[1066]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.nm-dispatcher.service' for details. Aug 18 00:31:57 robert-pc NetworkManager[1044]: warn Dispatcher failed: (32) Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.nm-dispatcher.service' for details. Aug 18 00:31:57 robert-pc dbus-daemon[1066]: dbus[1066]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Aug 18 00:31:57 robert-pc dbus-daemon[1066]: dbus[1066]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.nm-dispatcher.service' for details. # systemctl status dbus-org.freedesktop.nm-dispatcher.service dbus-org.freedesktop.nm-dispatcher.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) Any ideas as to what is happening? No idea, but I also see that: ** the icon of the power manager is missing; ** when is returning from sleep it goes back to sleep right away. Only the second time stays awake; ** when this happens, after the second wakeup the ath9k module issues continuously for a couple dozen of seconds or so: kernel: [121459.809116] ath: phy0: PLL4 meaurement not done 3.10.[56] had no apparent shortcoming, though. Mihai -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F19 Kernels 3.10.5, 6, 7 won't boot
On Thu, 22 Aug 2013 00:34:59 -0400 Robert McBroom mcfo...@bellsouth.net wrote: # systemctl status dbus-org.freedesktop.nm-dispatcher.service dbus-org.freedesktop.nm-dispatcher.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) https://bugzilla.redhat.com/show_bug.cgi?id=974811 -- Regards, Frank When in doubt PANIC! I check for new mail app. 20min www.frankly3d.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
non luks encryption, other minds?
Could some one good at crypt look at the link, lmk thoughts re fedora 19. Have the following in /etc/crypttab: # swap UUID=4ea253d9-e5d2-4d7c-b40c-22c44b2affc6 /dev/urandom swap,cipher=aes-cbc-essiv:sha256,size=256 But during bootup am asked for password for swap So Googled: http://unix.stackexchange.com/questions/64693/how-do-i-configure-systemd-to-activate-an-encrypted-swap-file -- Regards, Frank When in doubt PANIC! I check for new mail app. 20min www.frankly3d.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: non luks encryption, other minds?
On Thu, 22 Aug 2013 11:20:10 +0100 Forgot to add I have an 80gb sata as swap drive. -- Regards, Frank When in doubt PANIC! I check for new mail app. 20min www.frankly3d.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Google Calendar client for Fedora
Dear All, Is there some Google Calendar client for Fedora? Thanks in advance, Paul -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Google Calendar client for Fedora
On 2013-08-22 13:49, Paul Smith wrote: Dear All, Is there some Google Calendar client for Fedora? https://wiki.mozilla.org/Calendar:Using_Lightning_with_Google_Calendars -- RMA. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Google Calendar client for Fedora
On Thu, Aug 22, 2013 at 11:55 AM, Mihamina Rakotomandimby miham...@rktmb.org wrote: Is there some Google Calendar client for Fedora? https://wiki.mozilla.org/Calendar:Using_Lightning_with_Google_Calendars Thanks, Mihamina, lightning is a nice Thunderbird extension, which synchronizes with Google Calendar. Paul -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Google Calendar client for Fedora
On Thu, 2013-08-22 at 11:49 +0100, Paul Smith wrote: Dear All, Is there some Google Calendar client for Fedora? Evolution works fine as far as I know. poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Google Calendar client for Fedora
On 08/22/2013 06:49 AM, Paul Smith wrote: Dear All, Is there some Google Calendar client for Fedora? Thanks in advance, Paul KOrganizer with libgcal (via Akonadi) also works well, although there are a couple of minor timezone/daylight savings issues. Install libgcal, and in KOrganizer, go to Configure, General, Calendars, Add... and select Google Calendars and Tasks. Regards, Raman -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
gpg-agent
As I understand it the file gpg-agent-startup.sh should be placed in /etc/kde/env and made executable for the gpg-agent to start att boot time? Agent is also enabled in the ~/.gnupg/gpg.conf Running the file manually it starts the agent, but after having booted, the gpg-agent isn't started, so it seems the directory/file isn't read at boot time? Where should that file be place to be run at startup? /Martin S -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: [389-users] Problems setting up MMR
Modify an entry on the (a) master and see if the change propagates. The master will also complain vociferously in the error log if it can't send updates to a consumer. -morgan On Aug 22, 2013, at 4:12 PM, Louis Bohm wrote: I added it with an ldapadd on host ldap02 and was able to initialize the consumer. So now that I have it working how do I test it and validate it? Louis On Aug 22, 2013, at 3:25 PM, Morgan Jones mor...@morganjones.org wrote: Louis, Did you create cn=replication manager? It looks like you did not. Try this to see if it's there: ldapsearch -H ldaps://ldap02 -D cn=directory\ manager -w pass -LLLb cn=replication manager,cn=config objectclass=\* replace ldaps with ldap of course if you have not set up ssl. I believe it's in dse.ldif as well. -morgan On Aug 22, 2013, at 3:17 PM, Louis Bohm wrote: I have 2 servers running cents 6.4 and the newest version of DS from the repos. Both serves have the same supplier DN. On the second server (ldap02) I go no errors when setting up the replication agreement. However, on the first server (ldap01) I got LDAP error: No such object. Error code: 32. The logs on ldap02 show this: [22/Aug/2013:15:14:17 -0400] conn=48 fd=71 slot=71 connection from 10.74.192.51 to 10.74.192.52 [22/Aug/2013:15:14:17 -0400] conn=48 op=0 BIND dn=cn=replication manager,cn=config method=128 version=3 [22/Aug/2013:15:14:17 -0400] conn=48 op=0 RESULT err=32 tag=97 nentries=0 etime=0 [22/Aug/2013:15:14:17 -0400] conn=48 op=1 UNBIND [22/Aug/2013:15:14:17 -0400] conn=48 op=1 fd=71 closed - U1 I guess the first thing I need to do is prove that supplier DN is really there and is the same. But I have been unable to come up with an ldapsearch that shows it. Or is the only way to see it is to grep the dse.ldif file? Louis -- 389 users mailing list 389-us...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-us...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-us...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-us...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: gpg-agent
On 08/22/2013 01:18 PM, Martin S wrote: Where should that file be place to be run at startup? My guess (and it's only that) is that you should create gpg-agent.service and enable it. Either that, or invoke the script from /etc/rc.local, after making sure that rc.local.service is enabled. Of course, ICBW. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: gpg-agent
On 08/22/2013 04:18 PM, Martin S wrote: As I understand it the file gpg-agent-startup.sh should be placed in /etc/kde/env and made executable for the gpg-agent to start att boot time? Agent is also enabled in the ~/.gnupg/gpg.conf Running the file manually it starts the agent, but after having booted, the gpg-agent isn't started, so it seems the directory/file isn't read at boot time? Where should that file be place to be run at startup? /Martin S I would suggest use of keychain. It will automatically load from /etc/profile.d and will handle your gpg agent as well as other agents like ssh. Regards, Raman -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Yumex problem
fedora 18 / KDE I have problems starting Yumex, something about backend not running. Yum runs normal doing installs or updates $ yumex -d 15:20:52 : INFO - Using config file : /home/jim/.config/yumex/yumex.conf 15:20:52 : INFO - Using config file : /home/jim/.config/yumex/yumex.conf 15:20:52 : DEBUG - Current Yumex Settings: 15:20:52 : DEBUG - autorefresh: True 15:20:52 : DEBUG - branding_title: 'Yum Extender' 15:20:52 : DEBUG - bugzilla_url: 'https://bugzilla.redhat.com/show_bug.cgi?id=' 15:20:52 : DEBUG - color_downgrade: 'goldenrod' 15:20:52 : DEBUG - color_install: 'darkgreen' 15:20:52 : DEBUG - color_normal: 'black' 15:20:52 : DEBUG - color_obsolete: 'blue' 15:20:52 : DEBUG - color_update: 'red' 15:20:52 : DEBUG - debug: True 15:20:52 : DEBUG - disable_netcheck: False 15:20:52 : DEBUG - disable_repo_page: False 15:20:52 : DEBUG - history_limit: 15 15:20:52 : DEBUG - no_gpg_check: False 15:20:52 : DEBUG - plugins: True 15:20:52 : DEBUG - proxy: '' 15:20:52 : DEBUG - recentdays: 14 15:20:52 : DEBUG - remove_requirements: False 15:20:52 : DEBUG - repo_exclude: ['debug', 'source'] 15:20:52 : DEBUG - show_newest_only: True 15:20:52 : DEBUG - skip_broken: False 15:20:52 : DEBUG - typeahead_search: False 15:20:52 : DEBUG - use_sortable_view: False 15:20:52 : DEBUG - use_sudo: False 15:20:52 : DEBUG - win_height: 494 15:20:52 : DEBUG - win_sep: 300 15:20:52 : DEBUG - win_width: 1000 15:20:52 : DEBUG - yum_conf: '/etc/yum.conf' 15:20:52 : DEBUG - yumdebuglevel: 2 15:20:53 : DEBUG - network interface wlan0 (rtl8188eu) is connected 15:20:53 : DEBUG - network interface wlan0 (rtl8188eu) is connected 15:20:54 : INFO - Connected to an network 15:20:54 : DEBUG - Getting package lists - BEGIN yumexgui.populate_package_cache 15:20:54 : DEBUG - network interface wlan0 (rtl8188eu) is connected 15:20:54 : INFO - Starting yum child process 15:20:54 : DEBUG - Initialize yum backend - BEGIN yum_backend.setup 15:20:54 : DEBUG - Setup START yum_backend.setup 15:21:08 : ERROR - ERROR: Fatal Error : backend-not-running 15:21:08 : ERROR - ERROR: Backend not running as expected Yum Extender will terminate -- exit code : None 15:21:08 : DEBUG - Quiting the program !!! yum_backend.quit 15:21:08 : INFO - yum backend process is ended 15:21:08 : DEBUG - Backend reset completed yum_backend.quit 15:21:08 : DEBUG - Quiting the program !!! yum_backend.quit 15:21:08 : INFO - yum backend process is ended 15:21:08 : DEBUG - Backend reset completed yum_backend.quit Program Terminated [jim@localhost ~]$ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: gpg-agent
On Thursday, August 22, 2013 01:55:26 PM Joe Zeff wrote: On 08/22/2013 01:18 PM, Martin S wrote: Where should that file be place to be run at startup? My guess (and it's only that) is that you should create gpg-agent.service and enable it. Either that, or invoke the script from /etc/rc.local, after making sure that rc.local.service is enabled. Of course, ICBW. OK, tried both. There is no gpg-agent.service, so I tried enabling rc.local instead. And got the following. [root@dragon mskjoldebrand]# systemctl enable rc-local.service The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). /Martin S -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: gpg-agent
On Thursday, August 22, 2013 05:16:57 PM Raman Gupta wrote: On 08/22/2013 04:18 PM, Martin S wrote: As I understand it the file gpg-agent-startup.sh should be placed in /etc/kde/env and made executable for the gpg-agent to start att boot time? Agent is also enabled in the ~/.gnupg/gpg.conf Running the file manually it starts the agent, but after having booted, the gpg-agent isn't started, so it seems the directory/file isn't read at boot time? Where should that file be place to be run at startup? /Martin S I would suggest use of keychain. It will automatically load from /etc/profile.d and will handle your gpg agent as well as other agents like ssh. I installed keychain, created a file in profile.d which I tested manually (and it worked) and then rebooted. Then [mskjoldebrand@dragon ~]$ ps aux | grep gpg-agent mskjold+ 1491 0.0 0.0 112644 928 pts/1S+ 05:41 0:00 grep -- color=auto gpg-agent Hmm gpg-agent isn't there ... still I tried creating a new signed message from KMail, and it actually works. Shouldn't gpg-agent show up in ps aux | grep gpg-agent if it's run from profile.d? Or have I worked from outdated gpg-docs, and KMail finds gpg anyway (it didn't before) and wasted everyuones time? =( /Martin S -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: gpg-agent
On 08/22/2013 11:48 PM, Martin S wrote: On Thursday, August 22, 2013 05:16:57 PM Raman Gupta wrote: On 08/22/2013 04:18 PM, Martin S wrote: As I understand it the file gpg-agent-startup.sh should be placed in /etc/kde/env and made executable for the gpg-agent to start att boot time? Agent is also enabled in the ~/.gnupg/gpg.conf Running the file manually it starts the agent, but after having booted, the gpg-agent isn't started, so it seems the directory/file isn't read at boot time? Where should that file be place to be run at startup? /Martin S I would suggest use of keychain. It will automatically load from /etc/profile.d and will handle your gpg agent as well as other agents like ssh. I installed keychain, created a file in profile.d which I tested manually (and it worked) and then rebooted. You shouldn't need to create anything in profile.d manually: # rpm -q --whatprovides /etc/profile.d/keychain.sh keychain-2.6.8-11.fc19.noarch Then [mskjoldebrand@dragon ~]$ ps aux | grep gpg-agent mskjold+ 1491 0.0 0.0 112644 928 pts/1S+ 05:41 0:00 grep -- color=auto gpg-agent Hmm gpg-agent isn't there ... still I tried creating a new signed message from KMail, and it actually works. Shouldn't gpg-agent show up in ps aux | grep gpg-agent if it's run from profile.d? Did you create a .keychainrc file with your gpg key ID as specified here: /usr/share/doc/keychain-2.6.8/README.Fedora After you do that, and login again, what happens when you type keychain at the prompt? This is what I see: $ keychain KeyChain 2.6.8; http://www.gentoo.org/proj/en/keychain/ Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL * Found existing ssh-agent (4386) * Found existing gpg-agent (4651) and those pid's match my running ssh and gpg agents (which were started by keychain at login time). Or have I worked from outdated gpg-docs, and KMail finds gpg anyway (it didn't before) and wasted everyuones time? =( Not sure about this, I don't use kmail. Regards, Raman -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: gpg-agent
On Thursday, August 22, 2013 11:58:29 PM Raman Gupta wrote: On 08/22/2013 11:48 PM, Martin S wrote: On Thursday, August 22, 2013 05:16:57 PM Raman Gupta wrote: On 08/22/2013 04:18 PM, Martin S wrote: As I understand it the file gpg-agent-startup.sh should be placed in /etc/kde/env and made executable for the gpg-agent to start att boot time? Agent is also enabled in the ~/.gnupg/gpg.conf Running the file manually it starts the agent, but after having booted, the gpg-agent isn't started, so it seems the directory/file isn't read at boot time? Where should that file be place to be run at startup? /Martin S I would suggest use of keychain. It will automatically load from /etc/profile.d and will handle your gpg agent as well as other agents like ssh. I installed keychain, created a file in profile.d which I tested manually (and it worked) and then rebooted. You shouldn't need to create anything in profile.d manually: # rpm -q --whatprovides /etc/profile.d/keychain.sh keychain-2.6.8-11.fc19.noarch Then [mskjoldebrand@dragon ~]$ ps aux | grep gpg-agent mskjold+ 1491 0.0 0.0 112644 928 pts/1S+ 05:41 0:00 grep -- color=auto gpg-agent Hmm gpg-agent isn't there ... still I tried creating a new signed message from KMail, and it actually works. Shouldn't gpg-agent show up in ps aux | grep gpg-agent if it's run from profile.d? Did you create a .keychainrc file with your gpg key ID as specified here: /usr/share/doc/keychain-2.6.8/README.Fedora After you do that, and login again, what happens when you type keychain at the prompt? This is what I see: $ keychain KeyChain 2.6.8; http://www.gentoo.org/proj/en/keychain/ Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL * Found existing ssh-agent (4386) * Found existing gpg-agent (4651) I get this too, but one issue remains. Does the value GPGKEYS take 2 keys? I tried seperating the with and , and both fails. As well as having two lines, but it only reads the first. /M . -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: gpg-agent
On 08/23/2013 12:50 AM, Martin S wrote: I get this too, but one issue remains. Does the value GPGKEYS take 2 keys? I tried seperating the with and , and both fails. As well as having two lines, but it only reads the first. According to README.Fedora, you can specify multiple keys, space separated: GPGKEYS defines a single key ID or a space separated list of key IDs. I would quote it e.g.: GPGKEYS=key1 key2 I've never tried multiple gpg keys though. Regards, Raman -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: gpg-agent
On Friday, August 23, 2013 01:00:35 AM Raman Gupta wrote: On 08/23/2013 12:50 AM, Martin S wrote: I get this too, but one issue remains. Does the value GPGKEYS take 2 keys? I tried seperating the with and , and both fails. As well as having two lines, but it only reads the first. According to README.Fedora, you can specify multiple keys, space separated: GPGKEYS defines a single key ID or a space separated list of key IDs. I would quote it e.g.: GPGKEYS=key1 key2 I've never tried multiple gpg keys though. I didn't get that to work ...Or at least it said it didn't load the keys =( Still, the setup is working, KMail is signing messages and I'm happy with that =) Thanks for the input. /M. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F19 Kernels 3.10.5, 6, 7 won't boot [Solved]
On 08/22/2013 12:34 AM, Robert McBroom wrote: Updated to Fedora 19 but none of the kernels will boot. The process begins and something about an error with connecting to DBUS flashes on the screen then the cycle starts over. I can still run with kernel-3.10.4-100.fc18.x86_64 although it complains about a file missing that udev would like to see. [ 14.730648] systemd-udevd[1081]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz Working boot BOOT_IMAGE=/vmlinuz-3.10.4-100.fc18.x86_64 root=UUID=f04657c0-2964-494f-8efa-f194b7ba370a ro rd.md=0 rd.lvm=0 rd.dm=0 vconsole.keymap=us rd.luks=0 LANG=en_US.UTF-8 quiet pci=nomsi noapic irqpoll vconsole.font=latarcyrheb-sun16 3 nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off Looking at the /var/log messages see Some way in the upgrade process in grb2.cfg the kernel command line merged the upgrade parameters with the rest of the initialization. That then propagated to all later kernel installs. linux/vmlinuz-3.10.6-100.fc18.x86_64 root=UUID=f04657c0-2964-494f-8efa-f194b7ba370a ro rd.md=0 rd.lvm=0 rd.dm=0 vconsole.keymap=us rd.luks=0 LANG=en_US.UTF-8 quiet pci=nomsi noapic irqpoll vconsole.font=latarcyrheb-sun16 3 nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off upgrade systemd.unit=system-upgrade.target plymouth.splash=fedup enforcing=0 === linux/vmlinuz-3.10.6-100.fc18.x86_64 root=UUID=f04657c0-2964-494f-8efa-f194b7ba370a ro rd.md=0 rd.lvm=0 rd.dm=0 vconsole.keymap=us rd.luks=0 LANG=en_US.UTF-8 quiet pci=nomsi noapic irqpoll vconsole.font=latarcyrheb-sun16 3 nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off Edit of grub.cfg allows everything to function as it should. Robert McBroom -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
