similar to: Samba4 Compile Error

Andrew, thank you for your help! Could a "Bus error" be related to a hardware problem? Never seen it before. Anyways, here is the output of my debugging session (I hope I did everything correctly): [root at server bin]# gdb --args python /usr/local/samba/bin/samba-tool dbcheck GNU gdb (GDB) Red Hat Enterprise Linux (7.2-75.el6) Copyright (C) 2010 Free Software Foundation, Inc.

Hello, This is my first time posting to the list adn I've run into a problem trying to install python-2.6.6-51.el6.i686 on my x86_64 bit system, which I updated to CentOS 6.5 this evening. I receive the following error: error: Failed dependencies: libpython2.6.so.1.0 is needed by python-2.6.6-51.el6.i686 python-libs(x86-32) = 2.6.6-51.el6 is needed by python-2.6.6-51.el6.i686

I tried to upgrade one user's system, a Dell Optiplex GX620, and yum got a GPF. After *much* grief, I finally gave up, and rebuilt the system. Or, rather, I'm trying to. First problem: I did a minimal install from the graphical installer - I don't know if that's relevant - but when it boots, it does *not* install the NIC driver, tg3, on boot. I've got eth0 defined in

For a few days now my primary DC has some issues. I can create users without a problem. But when I try to alter the group membership of users, one of my samba processes crashes (the one listening to the LDAP related ports: 389, 636, 3268, 3269). Also, when I start my backup DC, a few seconds later another process crashes on the primary DC (the RPC related listening to 135 and 1024). I

Hi, We are having problems with sysvol AD shared folder in a Samba 4.9.13 AD. Has been running smoothly until recently, and we don't know how to fix it. We detected the problem trying to create a new AD GPO, it fails with the message (sorry, we have windows in Spanish, it's not literal translation): "this security identifier cannot be assigned as object owner". If we execute

Hi How would i upgrade python to python2.6.4 using a yum repository ( on all my servers ) and cause manual configuration is time consuming, i am using cent OS 5.4 32 bit Is there an already available repository to do this.? ------------------------------------------------------------------------------ I had tried to install it using contemporary method ( ./configure ; make ;make install) ..

Hi,I am working with a custom built (LFS-based) Linux distro and am attempting to compile Samba4. Samba3 has always compiled without issue. The system has its Python installed in /opt/python2. There are symlinks to put "python" in /usr/local/bin and the "python2.7" lib folder in /usr/include. The configure command used was simply ./configure --enable-fhs --with-quotas The

Applied policy update. Now I see these occasionally. But by the time I try and see what the matter is the file is gone: /var/log/maillog . . . Dec 9 15:12:08 inet08 postfix/smtp[3670]: fatal: shared lock active/0A7EC60D8A: Resource temporarily unavailable . . . Dec 9 15:12:08 inet08 postfix/smtp[3758]: fatal: shared lock active/8DD5060F81: Resource temporarily unavailable . . . Dec 9 15:12:09

Hello llvm-dev, I'm working on some out-of-process reflection support for Swift and I'd like to switch over some of my memory management to context-based with a bump-pointer allocator. I hit a linker error that `grow_pod` was missing. Eventually, some of this code will get linked into the Swift runtime and we are trying to avoid directly linking LLVM into the runtime to keep the size

I do have the 4.3.3 sources. The only configure flag i set was --enable-debug. I can execute that install, however the issue of unwanted libs still lingers. I'm confused, is it or is it not an issue that i have libtld, libtalloc and pytalloc libs in /usr/lib? And if it is an issue whats the best path forward to resolve it? JS On Mar 3, 2016 2:59 PM, "Marc Muehlfeld"

Ha! That should be libtdb: /usr/lib/x86_64-linux-gnu/libtdb.so.1 /usr/lib/x86_64-linux-gnu/libtdb.so.1.3.5 /usr/lib/x86_64-linux-gnu/samba/libtdb-wrap.so.0 /usr/lib/x86_64-linux-gnu/samba/libtdb_compat.so.0 /usr/local/samba/lib/private/libtdb-wrap-samba4.so /usr/local/samba/lib/private/libtdb.so.1 /usr/local/samba/lib/private/libtdb.so.1.3.7 Sorry for the typo, I compose most of my replies on

Thanks Rowland, They've been there all along and the thing ran for a month so my gut said they weren't problematic. JS On Mar 3, 2016 4:30 PM, "Rowland penny" <rpenny at samba.org> wrote: > On 03/03/16 21:24, IT Admin wrote: > >> >> Ha! That should be libtdb: >> >> /usr/lib/x86_64-linux-gnu/libtdb.so.1 >>

pytalloc: /usr/lib/x86_64-linux-gnu/libpytalloc-util.so.2 /usr/lib/x86_64-linux-gnu/libpytalloc-util.so.2.1.2 /usr/local/samba/include/pytalloc.h /usr/local/samba/lib/private/libpytalloc-util.so.2 /usr/local/samba/lib/private/libpytalloc-util.so.2.1.3 libtalloc: /usr/lib/x86_64-linux-gnu/libtalloc.so.2 /usr/lib/x86_64-linux-gnu/libtalloc.so.2.1.2

Could I get some input regarding restoring ACLs? There's nothing in the Samba wiki about what to do with the ACL archive. I've finished all of the other steps already, what do I need to do to restore this archive? JS On Mar 3, 2016 4:02 PM, "Rowland penny" <rpenny at samba.org> wrote: > On 03/03/16 20:33, IT Admin wrote: > >> I do have the 4.3.3 sources.

Apt and to think those packages aren't installed: sudo apt-get remove libtdb-dev libtalloc-dev python-talloc-dev Reading package lists... Done Building dependency tree Reading state information... Done Package 'libtalloc-dev' is not installed, so not removed Package 'libtdb-dev' is not installed, so not removed Package 'python-talloc-dev' is not installed, so not

I have an Ubuntu system and went into Synaptic and checked asterisk for installation. Once installed, I started it with /usr/sbin/asterisk -vvvgc and got the following output with several errors and notices. Do I need to do more or are these ok? I expected to have some conf files in /etc/asterisk but there is nothing there. Thanks! Created by Mark Spencer <markster@digium.com>

On 03/03/16 21:24, IT Admin wrote: > > Ha! That should be libtdb: > > /usr/lib/x86_64-linux-gnu/libtdb.so.1 > /usr/lib/x86_64-linux-gnu/libtdb.so.1.3.5 > /usr/lib/x86_64-linux-gnu/samba/libtdb-wrap.so.0 > /usr/lib/x86_64-linux-gnu/samba/libtdb_compat.so.0 > /usr/local/samba/lib/private/libtdb-wrap-samba4.so > /usr/local/samba/lib/private/libtdb.so.1 >

On 05/17/12 11:15, prabu.murugan at emc.com wrote: > > Hi, > > As a security concern we are upgrading samba to 3.4.17. > > I tried all possible option to compile samba 3.4.17 on Solaris 10_U10. > But it is not going through. > > > > User requirement is to compile samba 3.4.17 to support their > application. 3.4.17 is working on Solaris 9 and Solaris 10_U5. But

I'd remove the distro packages providing those libs in /usr/lib, as they could possibly cause problems. One more I forgot, which might possibly be responsible for corrupting your ldb database if the wrong one is loaded by samba at runtime, is libldb. >From the log, I'm guessing your database is corrupt if it can't read the schema, but someone else might have more insight. On

I have been following this and I am going to add my two cents . . . had a computer awhile back that did strange things after a few weeks. Re-install the OS and try again. Did this twice too many times. Some how, quite by accident I discovered that there was a bad sata cable. Replaced the cable and the computer is still running today, about two years later. We forget that we are dealing with