On Apr 15, 2013, at 13:57, Joan Moreau <j...@grosjo.net> wrote: > Le 15/04/2013 10:24, Charles Marcus a écrit : > >>> On 2013-04-14 6:30 PM, Joan Moreau <j...@grosjo.net> wrote: >>> Le 14/04/2013 22:24, Viktor Dukhovni a écrit : On Sun, Apr 14, 2013 at >>> 10:21:58PM +0000, Joan Moreau wrote: However, how can postfix NOT use the >>> only openssl library ? or fail to have SHA2 when loading the .so ? Find a >>> less broken operating system. This works on every system I've ever used, >>> and finding out what's wrong with yours is not a good use of your time or >>> mine. >> >>> Well, this server has worked since ever, supporting plenty of web >>> operations (so I can not really 'delete and re-install' and broke only >>> after updating the kernel. Any other clue ? >> >> Roll back to the previous kernel. >> >> Seriously. If you updated the kernel but didn't keep the last known >> good/working one, then hopefully you have learned why doing this is such >> a good idea and will do so in the future. > > Reverted to 3.7.10. Recompiled openssl + cyrus + posfix . Same errors. Where > does the inconsistency reside ?
Probably in library versions you updated along the way, changes in the way you compile things, and so on. Besides, aren't the odd kernel versions such as 3.5.x, 3.7.x etc. development kernels? I really don't get why you are experimenting with development level software on what you claim is a production system. I suggest you stop wasting everyone's time, including your own, and roll back to the supported production kernel for your distribution, supported library versions, and so on. If you need custom Postfix packages for some reason, compile packages against the supported libraries. And if you do want to experiment with development level software, do so on a system that you can wipe and reinstall, or a virtual machine that you can roll back to a previous snapshot. Also, own your decision to live on the cutting edge. Fixing it is YOUR problem when you do, don't outsource it to others. Cya, Jona
