Displaying 20 results from an estimated 1000 matches similar to: "Daemon "started" messages"
2024 May 17
1
Daemon "started" messages
On Fri, 17 May 2024 09:34:25 +0200
Andrea Venturoli via samba <samba at lists.samba.org> wrote:
> Hello.
>
> I'm gradually replacing my 4.17 installations with 4.19 (on FreeBSD).
> As soon as I do this, I'm starting to see gobs of messages in the log
> like the followings:
>
> rpcd_lsad[54129]: rpcd_lsad version 4.19.5 started.
> samba-dcerpcd[14381]:
2024 Nov 19
1
Working through the PAM Offline Authentication Wiki page, but...
...the tests for initial online login to my newly joined Linux domain
member the machine through ssh are failing. I ran:
??? terra ~ # ssh HOME\\jgraham at localhost
??? (HOME\jgraham at localhost) Password:
??? (HOME\jgraham at localhost) Password:
??? (HOME\jgraham at localhost) Password:
??? HOME\jgraham at localhost's password:
??? Permission denied, please try again.
???
2024 Jun 13
1
winbind error after startup on Samba member server
Hi folks,
The last log record from journalctl -xeu winbind directly after winbind
startup is:
Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate
failed with exit status 1
For completeness, the log entries for winbind startup is displayed below.
Things seem to work though, but I have never seen it before (I don't
like error messages). When I noticed the message I
2024 Jun 13
1
winbind error after startup on Samba member server
On Thu, 13 Jun 2024 16:26:17 +0200
Peter Milesson via samba <samba at lists.samba.org> wrote:
> Hi folks,
>
> The last log record from journalctl -xeu winbind directly after
> winbind startup is:
>
> Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate
> failed with exit status 1
>
> For completeness, the log entries for winbind startup is
2024 Jun 13
1
winbind error after startup on Samba member server
On 13.06.2024 17:21, Rowland Penny via samba wrote:
> On Thu, 13 Jun 2024 16:26:17 +0200
> Peter Milesson via samba <samba at lists.samba.org> wrote:
>
>> Hi folks,
>>
>> The last log record from journalctl -xeu winbind directly after
>> winbind startup is:
>>
>> Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate
>>
2024 Oct 04
1
Joining a 2022-schema Active Directory
Le Fri, 4 Oct 2024 09:27:12 +0100
Rowland Penny via samba <samba at lists.samba.org> ?crivait:
> >
> > OK, I'll try first the 4.17 version from the backports, and if it's
> > not enough I'll upgrade to 4.20.
>
> I would upgrade to bookworm with Samba from backports, but its your
> domain ;-)
Well I've upgraded up to 4.20, but no dice :( No
2024 Oct 04
3
Joining a 2022-schema Active Directory
On Fri, 4 Oct 2024 10:11:37 +0200
Emmanuel Florac <eflorac at intellique.com> wrote:
> Le Thu, 3 Oct 2024 21:35:04 +0100
> Rowland Penny via samba <samba at lists.samba.org> ?crivait:
>
> > > Yes, I mean Windows 11 or WIndows Server 2022 machines that are
> > > registered into the AD. A Win11 PC which isn't AD-connected (but
> > > in the same
2023 Nov 27
2
missing file in logrotate config
Am 28.03.23 um 10:40 schrieb Rowland Penny via samba:
>
>
> On 28/03/2023 08:40, Arnaud FLORENT via samba wrote:
>> Hello
>>
>>
>> i am running samba 4.16 as AD-DC controller on Ubuntu 20.04 using
>> www.corpit.ru/mjt/packages/samba focal/samba-4.16 repository
>>
>>
>> everything is running fine but i have few log files in /var/log/samba/
2023 Oct 01
3
rpc_pipe_open_ncalrpc: connect(/run/samba/ncalrpc/EPMAPPER) failed: No such file or directory
This question has already been asked in the past, but there was
no answer.
The above message is logged quite often in /var/log/samba/log.samba-dcerpcd.
This is a stand-alone anonymous read-only server.
Is it something to worry about? It smells like samba isn't working
properly.
If yes, how can I fix it?
If no, how can I stop samba from logging un-interesting messages?
What dcerpcd is
2024 Jun 14
1
winbind error after startup on Samba member server
On 13.06.2024 20:33, Peter Milesson via samba wrote:
>
>
> On 13.06.2024 17:21, Rowland Penny via samba wrote:
>> On Thu, 13 Jun 2024 16:26:17 +0200
>> Peter Milesson via samba <samba at lists.samba.org> wrote:
>>
>>> Hi folks,
>>>
>>> The last log record from journalctl -xeu winbind directly after
>>> winbind startup is:
2023 Mar 28
1
missing file in logrotate config
On 28/03/2023 08:40, Arnaud FLORENT via samba wrote:
> Hello
>
>
> i am running samba 4.16 as AD-DC controller on Ubuntu 20.04 using
> www.corpit.ru/mjt/packages/samba focal/samba-4.16 repository
>
>
> everything is running fine but i have few log files in /var/log/samba/
> are not handl by /etc/logrotate.d/samba
>
> log.samba-dcerpcd
>
>
2022 Mar 21
2
[Announce] Samba 4.16.0 Available for Download
Release Announcements
---------------------
This is the first stable release of the Samba 4.16 release series.
Please read the release notes carefully before upgrading.
NEW FEATURES/CHANGES
====================
New samba-dcerpcd binary to provide DCERPC in the member server setup
---------------------------------------------------------------------
In order to make it much easier to break out
2022 Mar 21
2
[Announce] Samba 4.16.0 Available for Download
Release Announcements
---------------------
This is the first stable release of the Samba 4.16 release series.
Please read the release notes carefully before upgrading.
NEW FEATURES/CHANGES
====================
New samba-dcerpcd binary to provide DCERPC in the member server setup
---------------------------------------------------------------------
In order to make it much easier to break out
2023 Mar 28
1
missing file in logrotate config
Hello
i am running samba 4.16 as AD-DC controller on Ubuntu 20.04 using
www.corpit.ru/mjt/packages/samba focal/samba-4.16 repository
everything is running fine but i have few log files in /var/log/samba/
are not handl by /etc/logrotate.d/samba
log.samba-dcerpcd
log.rpcd_classic
log.rpcd_winreg
log.samba-bgqd
log.rpcd_spoolss
i guess those files size will not grow more than max log
2024 Nov 13
1
tdb_expand overflow detected
Hello,
I'm using samba416-4.16.11 on FreeBSD 14.1 (on ZFS, in a jail, with quotas on those filesystems, etc)
I'm seeing these entries in my logs. Is this something which needs action? If not, I'll start ignoring them.
Nov 11 19:00:45 tm samba-dcerpcd[7373]: [2024/11/11 19:00:45.852391, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log)
Nov 11 19:00:45 tm samba-dcerpcd[7373]:
2024 Jul 29
2
share enumeration, samba-dcerpcd, variable %i
hi, samba team and other,
client software calls samba and samba reads /etc/samba/smb.conf where
some parameter contains variable %i (client ip address), but when samba
calls samba-dcerpcd, it again reads /etc/samba/smb.conf where some
parameter contains variable %i and at that moment %i is not client ip
address, it is equal 0.0.0.0
for example I need client ip1 and client ip2 to get
2024 Nov 18
1
tdb_expand overflow detected
On Wed, Nov 13, 2024, at 4:30 PM, Dan Langille via samba wrote:
> Hello,
>
> I'm using samba416-4.16.11 on FreeBSD 14.1 (on ZFS, in a jail, with
> quotas on those filesystems, etc)
>
> I'm seeing these entries in my logs. Is this something which needs
> action? If not, I'll start ignoring them.
>
> Nov 11 19:00:45 tm samba-dcerpcd[7373]: [2024/11/11
2022 Jan 31
1
[Announce] Samba 4.16.0rc2 Available for Download
Release Announcements
=====================
This is the second release candidate of Samba 4.16.? This is *not*
intended for production environments and is designed for testing
purposes only.? Please report any defects via the Samba bug reporting
system at https://bugzilla.samba.org/.
Samba 4.16 will be the next version of the Samba suite.
UPGRADING
=========
NEW FEATURES/CHANGES
2022 Jan 31
1
[Announce] Samba 4.16.0rc2 Available for Download
Release Announcements
=====================
This is the second release candidate of Samba 4.16.? This is *not*
intended for production environments and is designed for testing
purposes only.? Please report any defects via the Samba bug reporting
system at https://bugzilla.samba.org/.
Samba 4.16 will be the next version of the Samba suite.
UPGRADING
=========
NEW FEATURES/CHANGES
2023 Nov 28
1
missing file in logrotate config
Hi
you could try a file /etc/logrotate.d/samba-local with this content
/var/log/samba/log.samba-dcerpcd
/var/log/samba/log.rpcd_classic
/var/log/samba/log.rpcd_winreg
/var/log/samba/log.samba-bgqd
/var/log/samba/log.rpcd_spoolss {
?? ?weekly
?? ?missingok
?? ?rotate 7
?? ?compress
?? ?delaycompress
?? ?notifempty
}
Le 27/11/2023 ? 10:12, Stefan G. Weichinger via samba a ?crit?:
> Am