similar to: Re: Dovecot died due to some SSL related error

Hi, Dovecot (pre-compiled version of Fedora Core 1, configured for Maildir) is running fine for me since a few days. It happened now twice to me that dovecot died with the following error message in /var/log/maillog: Feb 4 11:18:27 hundehuette imap-login: RAND_bytes() failed: error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded Feb 4 11:18:27 hundehuette dovecot: Login

Hi, with current test releases SSL doesn't work anymore for me on AIX 4.3 with dovecot-0.99.10-test14. It worked with 0.99.9.1. dovecot: Jun 23 19:42:23 Info: Dovecot starting up imap-login: Jun 23 19:42:25 Fatal: RAND_bytes() failed: error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded imap-login: Jun 23 19:42:25 Fatal: RAND_bytes() failed: error:24064064:random number

I've been seeing the Dovecot/SSL/Fedora 1 problem. I have a dovecot server which tends to die at least once a day, with messages like these :- May 24 13:44:44 mail pop3-login: RAND_bytes() failed: error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded May 24 13:44:44 mail dovecot: Login process died too early - shutting down I noticed Timo's email about this at:

I woke up this morning and my dovecot server had died with the following in the dovecot.log file: pop3-login: Jan 23 10:23:08 Fatal: RAND_bytes() failed: error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded dovecot: Jan 23 10:23:08 Error: Login process died too early - shutting down dovecot: Jan 23 10:23:08 Error: child 16321 (login) returned error 89 How can I find out

Dovecot died twice today. This was in the maillog: Apr 9 17:50:27 ciscy pop3-login: RAND_bytes() failed: error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded Apr 9 17:50:27 ciscy dovecot: Login process died too early - shutting down I think I can cause it to happen reliably and I'm asking for other to test this scenario: Open several terminal windows. In each, type

This morning dovecot died with the following messages in the errorlog. Any solution to this problem? I am using Fedora Core 1 on a SMP i686 box. imap-login: Mar 30 08:08:00 Fatal: RAND_bytes() failed: error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded dovecot: Mar 30 08:08:00 Error: Login process died too

Hello! I'm having a problem with Samba 3.0.3 on a HP-UX 11.00 server. In Samba, I'm having a printer which allows me to create PDF files. For this, I added the following lines to smb.conf: [global] load printers = No printcap name = /etc/opt/samba/printcap [printers] comment = Defaults for all printers path = /var/opt/samba/spool read only = Yes

My UPS died two nights ago. From the symptoms, including the fact that the event took the motherboard of my main machine with it and the unreasonable amount of heat the UPS was generating immediately after, I believe this was a genuine fried-brains failure of the control electronics, not a mere battery death. The old UPS (a Belkin FVC1200) has been packed off to a recycler, and the motherboard

On 5.10.2010, at 2.10, Marco Smiatek wrote: > #0 0x00584829 in maildir_sync_set_new_msgs_count () from > /usr/lib/dovecot/libdovecot-storage.so.0 Thanks. http://hg.dovecot.org/dovecot-2.0/rev/e2f9baa436f2 should fix this.

> On Mon, Feb 8, 2010 at 2:20 AM, Olle E. Johansson <oej at edvina.net > wrote: >> >> 7 feb 2010 kl. 15.09 skrev Per Jessen: >> >>> Thomas Winter wrote: >>> >>>> Hi, >>>> >>>> my Asterisk on debian lenny died after 80 days. >>>> >>>> server kernel: [7572666.186852] asterisk[3673]:

Hello all; While configuring a new VM on Xen today, we managed to tickle some sort of bug that caused xenstored to die, resulting in loads of Bad File Descriptor. Is this is a known issue, and if so, would attempting to reproduce it help? Cheers, Edward _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello All, "safe_asterisk" just sent me an email saying "Asterisk on bill exited on signal 11. Might want to take a peek.". Looking at the /var/log/asterisk/message doesn't show me anything... This is a fresh installed Asterisk 1.6.2.6 on Ubuntu 9.10 (64-bit) and it is routing calls from Nextone MSW Softswitch to VPS Softswitch... Any reason why Asterisk died?

This is completely inexplicable to me. I has been using Wine in Fedora Core 6 for some time without a hitch, but then I rebooted into Windows for approximately 2 weeks. At this point I decided to give Fedora another try, so I booted into it. However, Wine basically just died. Essentially, any executable that I run (ones that DEFINITLEY worked before) only shows part of the GUI, or none of it.

One of my W2K3R2 domains just stopped working, and the ''qemu-dm'' process is in the ''defunct'' state, which means it has seg faulted or something... Of course this happens after it has been running perfectly for a week and we think all of these problems are behind us! There wasn''t time to attach the debugger to the process unfortunately... is there any

On Mon, Nov 10, 2014 at 04:12:35PM +0100, Nicolas Ecarnot wrote: > Hi, > > In a oVirt 3.4.4 environnement, and using a > virt-p2v-0.9.1-2.20130730.1.el6.centos, I'm trying to convert a > windows 2003 server 32 bits into an oVirt KVM image. > > I already succeed doing that many times, but now, this is failing : > - All the usual process sounds good : > PXE ->

On Mon, Nov 10, 2014 at 08:28:53PM +0100, Nicolas Ecarnot wrote: > Le 10/11/2014 20:09, Richard W.M. Jones a écrit : > >>>Matt - any ideas? > >>> > >>>There is also the new version of p2v/v2v available, although it > >>>requires recent Fedora or RHEL/Centos 7.0. > >> > >>This is the last thing it does before unwinding: >

On Mon, Nov 17, 2014 at 07:45:12PM +0100, Nicolas Ecarnot wrote: > But I would be enthusiastic to install a dedicated P2V server, on > RH7, with the very last libguestfs, if that helps me to insure our > future P2V will succeed. > But according to what I understood so far, I'm not sure one can > install such a P2V server, independent of any oVirt setup. > > As a matter of

On Tue, Nov 18, 2014 at 03:06:44PM +0100, Nicolas Ecarnot wrote: [...] > Then I PXE-boot my source physical machine (well, at present, at > test time, another VM but whatever), when getting the graphical > prompt to connect to the conversion server, I get > "Failed to start virt-v2v-server on remote server". > though I witness the SSH connection is OK on the conversion

On Wed, Nov 19, 2014 at 09:08:36AM +0100, Nicolas Ecarnot wrote: > I tried to use the virt-p2v-make-disk, but it failed to connect to a > libvirt socket (obviously, there is none running in this VM.) To avoid libvirt problems, do: export LIBGUESTFS_BACKEND=direct Why don't you use the ISO? Burn it onto a CD and boot it. Rich. -- Richard Jones, Virtualization Group, Red Hat

On 11/19/2014 04:47 AM, Richard W.M. Jones wrote: > On Wed, Nov 19, 2014 at 09:08:36AM +0100, Nicolas Ecarnot wrote: >> I tried to use the virt-p2v-make-disk, but it failed to connect to a >> libvirt socket (obviously, there is none running in this VM.) > To avoid libvirt problems, do: > > export LIBGUESTFS_BACKEND=direct > > Why don't you use the ISO? Burn it