Nothing but silence on this subject.

Is this working for everybody?

On 6/8/2015 23:01, mourik jan heupink wrote:
> Hi,
>
> I removed all samba traces, reinstalled the backports version, created a
> domain/realm with different a name.
>
> So I'm seeing different directories under /chroots, and again: the
> testjoin succeeds, but authentication fails:
>
>> root@pf:~# /usr/bin/sudo /usr/sbin/chroot /chroots/new /usr/bin/ntlm_auth 
>> --username=my-user
>> Password:
>> could not obtain winbind separator!
>> Reading winbind reply failed! (0x01)
>> :  (0x0)
>> root@pf:~#
>
> But more fundamental I think, in /chroot/new/var/log/sambanew/log.winbindd:
>
>> [2015/06/08 22:55:04.473913,  0] 
>> ../lib/util/util.c:216(directory_create_or_exist)
>>    mkdir failed on directory /var/run/samba/winbindd: No such file or 
>> directory
>> [2015/06/08 22:55:04.474091,  0] ../lib/util/become_daemon.c:124(exit_daemon)
>>    STATUS=daemon failed to start: Winbindd failed to setup listeners, error 
>> code 32
>
> And winbindd is not running:
>> root@pf:~# ps aux | grep winb
>> root      4780  0.0  0.0   7836   880 pts/1    S+   22:56   0:00 grep winb
>> root@pf:~#
>
> Any ideas?
>
> Note: this all worked fine in 5.0.x, when we manually had to configure
> radius/AD integration. For us, 5.10 has not been a real improvement so
> far. (though we like the statistics graphs in /admin)
>
> And something else: Is there an overview (docs?) somewhere, about the
> new directories /chroots, /AD and /ad? I feel they are not always
> removed when they are not needed anymore, plus I wonder what precisely
> they are for. (many mounts exist, since 5.10)
>
> MJ
>
>
> On 06/06/2015 12:47 PM, mourik jan heupink wrote:
>> Some more info:
>>
>> ./pfcmd service winbindd status
>> service|shouldBeStarted|pid
>> winbindd-INTECH.conf|1|0
>> root@pf:/usr/local/pf/bin#
>>
>> So, pfcmd does not detect winbindd as started, however:
>>
>>> root@pf:/chroots# ps aux | grep winbind
>>> root     19514  0.0  0.0 229788  3684 ?        Ss   10:26   0:00 
>>> /usr/sbin/winbindd -D -s /etc/samba/OUR-WKGR.conf -l /var/log/sambaOUR-WKGR
>>> root     19515  0.0  0.1 239032  6236 ?        S    10:26   0:00 
>>> /usr/sbin/winbindd -D -s /etc/samba/OUR-WKGR.conf -l /var/log/sambaOUR-WKGR
>>> root     21559  0.0  0.0   7840   880 pts/1    S+   12:35   0:00 grep 
>>> winbind
>>> root@pf:/chroots# cd /etc/samba/
>>
>> So winbindd seems to be actually running, only not DETECTED by pfcmd.
>>
>> Service watch then tries to restart it every five minutes, and obviously
>> that fails as well:
>>
>>   ERROR: winbindd is already running. File
>> /usr/local/pf/var/run/winbindd.pid exists and process id 19514 is running.
>>
>> GUI: status, services also reports winbindd as 'stopped'.
>>
>> Hope this gives some clues...?
>>
>> MJ
>>
>
>
> ------------------------------------------------------------------------------
>


------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to