Hi,
I am trying to debug a problem, then under certain load postfix, which is
configured to use ldap lookups, throughs warning: dict_ldap_lookup: Search
error -5: Timed out messages. In dirsrv slapd access logs I can see a lot
of ABANDON messages and that is all I can find in logs related to
Thanks. that makes sense.
On Fri, Jul 5, 2013 at 3:47 PM, Ludwig Krispenz lkris...@redhat.com wrote:
Hi,
error -5 is not an LDAP timeout error, it must be logged by the client
application, and the fact that you see ABANDON messages looks like the
client waits for some time for a search
Alberto Viana wrote:
Hello,
DS base: 1.3.0.4
DS admin: 1.3.1.31
I´m trying to setup a new version of 389 DS multi master replication
with active directory(win 2008) and I´m getting the following erros:
[04/Jul/2013:16:57:32 -0300] NSMMReplicationPlugin - agmt=cn=AD-HMG1
(hmg1:636): binddn
Noriko,
In my 389 DS:
root@hmg2:~# certutil -L -d /opt/dirsrv/etc/dirsrv/slapd-RNP/
Certificate Nickname Trust
Attributes
SSL,S/MIME,JAR/XPI
homolog-HMG1-CA CT,,
Here is my CA details:
Data:
Alberto Viana wrote:
I already imported my certificates into 389 ds and windows 2008. I use
win2008 as CA. Just to remeber that the same enviroment was
working fine with my previous 389DS version.
You upgraded 389-ds-base from 1.2.10.12 to 1.3.0.4 using in-place
upgrade? What is your
Norkio,
No, it's a new machine. I just rebuild everything.
I'm using Ubuntu 12.04.2 LTS.
Alberto Viana
On Fri, Jul 5, 2013 at 2:50 PM, Noriko Hosoi nho...@redhat.com wrote:
Alberto Viana wrote:
I already imported my certificates into 389 ds and windows 2008. I use
win2008 as CA. Just to
Alberto Viana wrote:
Norkio,
No, it's a new machine. I just rebuild everything.
When you switched to the new machine, you reuse the old server cert from
the previous DS or renewed it?
Subject: CN=hmg2.homolog.rnp,OU=GTI,O=Rede Nacional de Ensino
e Pesquisa,L=Rio de Janeiro,C=BR
And
No. It's a new server cert (it's the same name, but i prefered to revoke it
and generate a new one).
Yes, for sure. I will try to rebuild everything on this branch (and make
new certs just to ensure there is nothing related with it), and if the
error persist, I will try this other branch and let
Just installed F19, fully updated. Was using F15, successfully.
Now I can't start stunnel. I'm using the stunnel config from my F15 system.
See output below. Any clues will be much appreciated. I really don't get
the fingerprint error, I don't have a fingerprint reader.
Clients allowed=500
On Thu, Jul 04, 2013 at 03:04:43PM -0400, D. Hugh Redelmeier wrote:
Do you use tracker? Can you give examples of how you've used it
and if you find it useful?
Tracker is one of the better desktop search utilities. I tried it for
sometime several years back, however I stopped because I do not
El 2013-07-04 23:52, g escribió:
hello juan,
On 07/04/2013 04:49 AM, Juan Orti Alcaine wrote:
Another good option if everything else fails (and you have configured
previously kernel.sysrq=1 with sysctl) is:
Alt+SysRq+ {R, E, I, S, U, B}
See:
El 2013-07-05 05:47, Tim escribió:
Allegedly, on or about 04 July 2013, Juan Orti Alcaine sent:
Another good option if everything else fails (and you have configured
previously kernel.sysrq=1 with sysctl) is:
Alt+SysRq+ {R, E, I, S, U, B}
See: https://en.wikipedia.org/wiki/Magic_SysRq_key#Uses
hello
I installed fedora 19 on 3 systems now and all have the same problem.
when X11 start , it show the traditional fedora logo in the center of the
screen , but then nothing else, no login screen, gdm or whatever gnome-shell
should take over after:-(
Xorg.0.log doesn't seem to show any pb ,
Try starting with fips = no in the config file. I'm guessing you don't
really need fips.
Damon
On Fri, Jul 5, 2013 at 2:04 AM, John Wendel jwende...@comcast.net wrote:
Just installed F19, fully updated. Was using F15, successfully.
Now I can't start stunnel. I'm using the stunnel config
Can anyone explain what is going on here? Error message:
This kernel requires an x86-64 CPU, but only detects an i686 CPU.
[bobg@box7 ~]$ uname -a
Linux box7 3.9.8-300.fc19.x86_64 #1 SMP Thu Jun 27 19:24:23 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
Processor Information
Socket
On 5 July 2013 09:50, Bob Goodwin - Zuni, Virginia, USA
bobgood...@wildblue.net wrote:
Can anyone explain what is going on here? Error message:
This kernel requires an x86-64 CPU, but only detects an i686 CPU.
[bobg@box7 ~]$ uname -a
Linux box7 3.9.8-300.fc19.x86_64 #1 SMP Thu Jun 27
On 07/05/2013 08:50 AM, Bob Goodwin - Zuni, Virginia, USA wrote:
Can anyone explain what is going on here? Error message:
This kernel requires an x86-64 CPU, but only detects an i686 CPU.
[bobg@box7 ~]$ uname -a
Linux box7 3.9.8-300.fc19.x86_64 #1 SMP Thu Jun 27 19:24:23 UTC 2013
x86_64
Am 03.07.2013 23:00, schrieb Mateusz Marzantowicz:
On 03.07.2013 22:32, Reindl Harald wrote:
Am 03.07.2013 22:19, schrieb Mateusz Marzantowicz:
On 03.07.2013 20:30, Richard Vickery wrote:
Is there a way to reboot the computer while its stuck on Starting GNOME
Desktop Manager?
Yes, press
Am 04.07.2013 00:58, schrieb Roger:
I successfully fresh installed Fedora19 , works a treat, very good very fast
operating system.
Updated everything and installed rvm rails 4 and postgresql.
Tryng to get into postgres with psql postgres postgres and I get could not
connect to server:
Am 04.07.2013 00:33, schrieb Tom Horsley:
When I was running f19 beta, I mostly ignored this, but I've
done a distro-sync now and the update I just did once again
got a slew of deltas do not match errors:
Finishing delta rebuilds of 118 package(s) (222 M)
delta does not match installed
if you type gnome tracker in google it leads you
to https://wiki.gnome.org/Tracker
besides my question why people do not use search
engines: nobody *needs* all this indexing crap
for his daily workload
Am 04.07.2013 21:04, schrieb D. Hugh Redelmeier:
Do you use tracker? Can you give examples
Am 05.07.2013 05:47, schrieb Tim:
Allegedly, on or about 04 July 2013, Juan Orti Alcaine sent:
Another good option if everything else fails (and you have configured
previously kernel.sysrq=1 with sysctl) is:
Alt+SysRq+ {R, E, I, S, U, B}
See:
Am 05.07.2013 15:50, schrieb Bob Goodwin - Zuni:
Can anyone explain what is going on here? Error message:
This kernel requires an x86-64 CPU, but only detects an i686 CPU.
this is a well known problem
you need VT-x enabled in the BIOS and after change this
you need a *hard* power cycle,
Hello,
I see that from time to time I get in fedora 18 this traffic:
SSDP - Simple Service Discovery Protocol
every 2-3 minutes a couple of frames for address: 239.255.255.255.
I tried to disable bluetooth with no help.
google shows that this might be some upnp client, but I don't know how
to
Can anyone recommend a PCI 4 or 8 port serial card with in-kernel
drivers, that works out of the box with Fedora?
- Mike
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines:
I just installed Fedora 19 anew from the live cd and I'm having a few
issues.
One is that I'm trying to install a java application that requires the
jar command, but jar can't be found:
jar xf myApp.jar
bash: jar: command not found...
I have this:
rpm -qa | grep -i java
On 5 July 2013 12:34, Amadeus W.M. amadeu...@verizon.net wrote:
I just installed Fedora 19 anew from the live cd and I'm having a few
issues.
One is that I'm trying to install a java application that requires the
jar command, but jar can't be found:
jar xf myApp.jar
bash: jar: command not
On 05/07/13 09:57, Reindl Harald wrote:
this is a well known problem
you need VT-x enabled in the BIOS and after change this
you need a *hard* power cycle, means complete power off
and power on again - a reboot is not enough
without hardware virtualization you can not run x86_64 guests
Ok,
On Fri, Jul 5, 2013 at 1:34 PM, Amadeus W.M. amadeu...@verizon.net wrote:
jar xf myApp.jar
that's not the right command to launch a java app, you surely mean
java -jar yourappname.jar
FC
--
During times of Universal Deceit, telling the truth becomes a revolutionary
act
Durante épocas
On Thu, 2013-07-04 at 00:55 +0200, Reindl Harald wrote:
14 out of 118 - who cares?
so there was some invalid delta-files - that's why yum is designed
to fall back to the ordinary full RPM in such cases
snip
Should I file a bugzilla against yum (or something else)?
clearly: NO
The
can you say what you changed? I've had a fc18 sys with qemu/KVM guest
running fc18 that started hanging after the .200 kernel. it would hang both
guest and host. filing a bug didn't go very far...
On Jul 4, 2013 2:30 AM, Mateusz Marzantowicz mmarzantow...@osdf.com.pl
wrote:
On 04.07.2013 11:17,
On Fri, 05 Jul 2013 13:50:36 -0300, Fernando Cassia wrote:
On Fri, Jul 5, 2013 at 1:34 PM, Amadeus W.M. amadeu...@verizon.net
wrote:
jar xf myApp.jar
that's not the right command to launch a java app, you surely mean java
-jar yourappname.jar
FC
I tried that, but I don't
On Fri, 05 Jul 2013 12:42:13 -0400, Carlos \casep\ Sepulveda wrote:
On 5 July 2013 12:34, Amadeus W.M. amadeu...@verizon.net wrote:
I just installed Fedora 19 anew from the live cd and I'm having a few
issues.
One is that I'm trying to install a java application that requires the
jar
Once upon a time, Amadeus W.M. amadeu...@verizon.net said:
Incidentally, I went to file manager and clicked on myApp.jar, opened it
with archive manager, selected the files I needed and it extracted them,
so I gues that can handle java archives too.
I'm pretty sure that jar files just use
You'd think those two things would be unrelated: one manages color
rendering profiles, the other builds a bootable USB stick from a .iso
file.
When I was running livecd-iso-to-disk.sh, SELinux popped up a warning.
The source process: /usr/libexec/colord
Attempted this access: read,search
On 05.07.2013 19:04, Gary Artim wrote:
can you say what you changed? I've had a fc18 sys with qemu/KVM guest
running fc18 that started hanging after the .200 kernel. it would hang
both guest and host. filing a bug didn't go very far...
I think this bug is identified and being fixed. This [1]
On 05.07.2013 20:35, Mateusz Marzantowicz wrote:
On 05.07.2013 19:04, Gary Artim wrote:
can you say what you changed? I've had a fc18 sys with qemu/KVM guest
running fc18 that started hanging after the .200 kernel. it would hang
both guest and host. filing a bug didn't go very far...
I
Ranjan Maitra wrote:
How do I fix these messages:
/usr/bin/curl: /lib64/libcrypto.so.10: no version information available
(required
by /usr/lib64/libssh2.so.1) /usr/bin/curl: /lib64/libcrypto.so.10: no
version information available (required
by /usr/lib64/libssl.so.10) /usr/bin/curl: relocation
Hi
On Thu, Jul 4, 2013 at 1:24 PM, Joe Zeff j...@zeff.us wrote:
On 07/04/2013 05:55 AM, Tom Horsley wrote:
Yea, I might as well. At least I might get a reason why it isn't
a bug when they close it :-).
Judging by my own recent experience, the next time you hear anything about
it is when
Temlakos wrote:
If your system is clean, the upgrade will succeed.
It didn't take quite as long to use the fedora-upgrade script that uses
yum directly. But that other method (F17-F18) didn't seem to leave
things as clean as I would have liked. This did--so far.
What exactly do you mean by
On 07/05/2013 04:12 PM, Timothy Murphy wrote:
Temlakos wrote:
If your system is clean, the upgrade will succeed.
It didn't take quite as long to use the fedora-upgrade script that uses
yum directly. But that other method (F17-F18) didn't seem to leave
things as clean as I would have liked.
On 07/05/2013 01:07 PM, Rahul Sundaram wrote:
No need to be negative. Generally speaking, there are hundreds of bugs
fixed via updates every release.
Funny thing, though, I keep reporting crashes but I almost never get any
feedback except for a bot reporting that they're closing the bug at
On 07/05/2013 01:14 PM, Temlakos wrote:
Clean to me means all version numbers consistent.
You do know, don't you, that there isn't a mass rebuilding of rpms that
haven't changed just to get the new version number? It's quite possible
to be completely up-to-date and still have packages from
On Fri, 05 Jul 2013 13:15:37 -0700
Joe Zeff j...@zeff.us wrote:
...snip...
When was the last time you got a reply from anybody that fast on the
Fedora Bugzilla?
I've had a number of cases of people replying to bugs within a day.
For my part I try and always reply on bugs filed on my
On 07/05/2013 04:31 PM, Joe Zeff wrote:
On 07/05/2013 01:14 PM, Temlakos wrote:
Clean to me means all version numbers consistent.
You do know, don't you, that there isn't a mass rebuilding of rpms
that haven't changed just to get the new version number? It's quite
possible to be
On 07/05/2013 06:34 PM, Amadeus W.M. wrote:
rpm -qa | grep -i java
java-1.7.0-openjdk-1.7.0.25-2.3.10.3.fc19.x86_64
javapackages-tools-0.14.1-2.fc19.noarch
tzdata-java-2013c-1.fc19.noarch
Install
java-1.7.0-openjdk-devel-1.7.0.25-2.3.10.4.fc18.x86_64
Lars
--
Lars E. Pettersson l...@homer.se
On 07/05/2013 01:35 PM, Kevin Fenzi wrote:
As far as ABRT reports, it's a pretty sad record, as I always reply to
them and ask the reporter what they were doing and if they can
duplicate the crash. I'd say something like 95% of them never reply. :(
I guess, then, that I've never had an issue
thanks, I had to run the kernel before 200 to keep my fc 18 virt mach from
hanging.
On Jul 5, 2013 11:35 AM, Mateusz Marzantowicz mmarzantow...@osdf.com.pl
wrote:
On 05.07.2013 19:04, Gary Artim wrote:
can you say what you changed? I've had a fc18 sys with qemu/KVM guest
running fc18 that
On 07/05/2013 12:50 PM, Fernando Cassia wrote:
On Fri, Jul 5, 2013 at 1:34 PM, Amadeus W.M. amadeu...@verizon.net
mailto:amadeu...@verizon.net wrote:
jar xf myApp.jar
that's not the right command to launch a java app, you surely mean
java -jar yourappname.jar
No. jar is
On Fri, Jul 5, 2013 at 5:28 PM, Kevin J. Cummings
cummi...@kjchome.homeip.net wrote:
No. jar is similar to tar, bar, etc
its stands for Java ARchive, and it works very much like tar does, right
down to a similar set of command line arguments.
What he is trying to do above is to extract
Mateusz Marzantowicz wrote
Check CD/DVD media or better use USB. I had similar situation on broken
CD several years ago.
The media matches the SHA256 checksum.
But, I appear to be the only one reporting this problem. Anybody have any
other ideas?
Paul Allen
--
View this message in
On 07/06/13 09:02, walksalot wrote:
Mateusz Marzantowicz wrote
Check CD/DVD media or better use USB. I had similar situation on broken
CD several years ago.
The media matches the SHA256 checksum.
But, I appear to be the only one reporting this problem. Anybody have any
other ideas?
Shot
I just now used Fedup to update Fedora 18 to 19. It did it's thing
quickly and efficiently and awaited a reboot.
I have both Ubuntu and Fedora on the hard drive. It boots to the Ubuntu
grub from which I select the Fedora install.
I selected Fedora spherical cow from the Ubuntu grub.
It booted
On 07/05/2013 10:26 PM, Roger wrote:
I just now used Fedup to update Fedora 18 to 19. It did it's thing
quickly and efficiently and awaited a reboot.
I have both Ubuntu and Fedora on the hard drive. It boots to the Ubuntu
grub from which I select the Fedora install.
I selected Fedora
On Jul 3, 2013 5:04 PM, T.C. Hollingsworth tchollingswo...@gmail.com
wrote:
On Jul 3, 2013 1:12 PM, Richard Vickery richard.vicker...@gmail.com
wrote:
Is there a way to reboot the computer while its stuck on Starting
GNOME Desktop Manager?
Usually by this point in the boot process you can
Am 05.07.2013 23:28, schrieb Kevin J. Cummings:
On 07/05/2013 12:50 PM, Fernando Cassia wrote:
On Fri, Jul 5, 2013 at 1:34 PM, Amadeus W.M. amadeu...@verizon.net
mailto:amadeu...@verizon.net wrote:
jar xf myApp.jar
that's not the right command to launch a java app, you surely mean
On 07/06/2013 01:19 PM, Kevin J. Cummings wrote:
On 07/05/2013 10:26 PM, Roger wrote:
I just now used Fedup to update Fedora 18 to 19. It did it's thing
quickly and efficiently and awaited a reboot.
I have both Ubuntu and Fedora on the hard drive. It boots to the Ubuntu
grub from which I select
57 matches
Mail list logo
