>When performing an upgrade of Red Hat 2.1 AS to Red Hat 3 ES Samba fail tostart>due of missing libssl.so.2 and libcrypt.so.2 libraries that has beendeleted>during upgrade process. We restored files from backup but winbind stillfail>to starting.Radu, First, it's very scary that you're using RedHat 3. That could be a source of many problems. ;) Anyway, what error(s) is winbind giving you when it fails to start? Anything in the syslog? Matthew
On Fri, 2004-06-04 at 12:03, mconnor@reisonline.com wrote:> >When performing an upgrade of Red Hat 2.1 AS to Red Hat 3 ES Samba fail to > start > >due of missing libssl.so.2 and libcrypt.so.2 libraries that has been > deleted > >during upgrade process. We restored files from backup but winbind still > fail > >to starting. > > Radu, > > First, it's very scary that you're using RedHat 3. That could be a > source of many problems. ;) Anyway, what error(s) is winbind giving you when > it fails to start? Anything in the syslog?Ummm, that is Enterprise Server v3.0 of RedHat. Which is the current version. -- greg@gregfolkert.net REMEMBER ED CURRY! http://www.iwethey.org/ed_curry Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20040604/d5428d72/attachment.bin
On Fri, 2004-06-04 at 09:03, mconnor@reisonline.com wrote:> >When performing an upgrade of Red Hat 2.1 AS to Red Hat 3 ES Samba fail to > start > >due of missing libssl.so.2 and libcrypt.so.2 libraries that has been > deleted > >during upgrade process. We restored files from backup but winbind still > fail > >to starting. > > Radu, > > First, it's very scary that you're using RedHat 3. That could be a > source of many problems. ;) Anyway, what error(s) is winbind giving you when > it fails to start? Anything in the syslog?---- just for the record - I have had virtually no problems with several RHEL AS 3 systems. For the solution, it would seem that the thing to do is to either remove your samba installation on RHEL 3 and reinstall, either from source or from their up2date/rpm mechanism... rpm -qa|grep samba samba-3.0.2-6.3E redhat-config-samba-1.0.16-1 samba-common-3.0.2-6.3E samba-client-3.0.2-6.3E Craig