similar to: Standalone Update 4.8.5 -> 4.9.2 smb fails to start ERROR: failed to setup guest info.

Charles, All, I just updated the kernel on my Arch box (the one we have been working on nut with on this list). Now upsd fails to start. (upsdrvctl is fine). I've posted working then -- Reboot -- the failing log information below. The 'Reboot' was for the kernel upgrade: Dec 14 14:02:00 phoinix systemd[1]: Starting Network UPS Tools - power devices information server... Dec 14

On 12/16/2013 09:23 PM, Charles Lepple wrote: > Not sure - I didn't write the getaddrinfo() code in upsd, but it seemed to > follow all of the recommendations on how to use that function. So if there is > a way to fix it in the NUT code, I am not aware of it (and would appreciate > any updates if that turns out to be the case). > > The odd part is that it looks like you went

All, Looking at logs for 4.1.3 on my standalone server (Archlinux w/systemd), I get an error launching samba with 'systemctl start samba.service' telling me I should start all individual daemons instead (nmbd/smbd/winbindd) of using samba.service: Jan 07 22:25:07 phoinix systemd[1]: Starting Samba AD Daemon... Jan 07 22:25:07 phoinix samba[29948]: [2014/01/07 22:25:07.734014, 0]

All, I've run samba in standalone mode since the 2.0.7 days and have been though a few breakages due to version updates along the way. It seems we have hit one again in the 4.4 to 4.5 update. Specifically, the update was samba-4.4.5 => samba-4.5.0 There were no changes made to smb.conf, but the following attempted mount failed using: mount.cifs //phoinix/samba /mnt/phx -o

All, I have built and installed nut from git on Archlinux. It uses the usbhid driver. Beginning a couple of years ago, nut begin failing to run on Archlinux without 'tweaking' or 'fudging' the install. There are two primary problems: (1) upsdrvctl cannot be launched normally i.e. (/usr/sbin/upsdrvctl start) without failing to connect: Dec 14 02:24:39 phoinix systemd[1]:

All, If the post "Samba 3.6 -> 4.1 change that prevent sharing / - mount error(13)" makes it to the list, I apologize, but it has been over a day and I have no indication that the post ever made it to the list. The issue is that in versions prior to 4.x, I was able to create a root share in samba, but now, something prevents it from being mounted. The relevant smb.conf is:

On 12/17/2013 10:43 AM, David C. Rankin wrote: > Huh? Why the : in Servname? So I just hardwired it passing the port "Servname" > as "3493" (could have just used "nut" from /etc/services): Sheepishly looking for a place to hide.... Yes there was a ':' there all right. Seems I was hit by a vi error: [12:04 phoinix:/etc/ups] # grep 3493 *.conf

On 12/16/2013 08:01 PM, Charles Lepple wrote: > On Dec 16, 2013, at 4:19 PM, David C. Rankin wrote: > >> > Dec 16 14:05:16 phoinix upsd[369]: getaddrinfo: Servname not supported for >> > ai_socktype > [...] >> > The kernel update was from linux (3.12.1-3 -> 3.12.5-1), I don't see what >> > could have changed. How do I attempt to further

Hello, I've been using samba for a few years but I use it only occasionally. Today, I've found out that since the upgrade to 4.9.2, smbd wouldn't start. I use Arch Linux. The command that starts samba on the systemd service is this: /usr/bin/smbd --foreground --no-process-group These are my configuration file's [global] parameters: bind interfaces only = Yes domain master =

On Dec 16, 2013, at 4:19 PM, David C. Rankin wrote: > Dec 16 14:05:16 phoinix upsd[369]: getaddrinfo: Servname not supported for > ai_socktype [...] > The kernel update was from linux (3.12.1-3 -> 3.12.5-1), I don't see what > could have changed. How do I attempt to further debug/fix this? getaddrinfo(3) is a libc function - is it possible that libc was updated as well? I am

On 16/09/2020 19:38, Rommel Rodriguez Toirac via samba wrote: > Hello all; > > I am installing samba4 (version 4.9.5) on Debian 10.5 to use it as a member of a samba4 AD DC domain (version 4.11.4). I am following the guide https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member but I am having problems starting samba. > > So far I have installed the necessary packages

On Dec 16, 2013, at 10:11 PM, David C. Rankin wrote: > On 12/16/2013 08:01 PM, Charles Lepple wrote: >> On Dec 16, 2013, at 4:19 PM, David C. Rankin wrote: >> >>>> Dec 16 14:05:16 phoinix upsd[369]: getaddrinfo: Servname not supported for >>>> ai_socktype >> [...] >>>> The kernel update was from linux (3.12.1-3 -> 3.12.5-1), I don't

The below Globals section is reporting some testparm failures that don't make sense to me. Perhaps someone could shine a light for me? This is a new installation - from 3.6.23 to 4.10.6-1. Necessitated by a Windows Server 2016 DC being installed. The testparm command, when run, reports the following error(s): # testparm Load smb config files from /etc/samba/smb.conf Loaded

Now hold on there... you said the problem started when you updated kernels - not when you changed the config file - did you change the config file or was it wrong before and the old kernel accepted it anyway? ted On 12/17/2013 10:08 AM, David C. Rankin wrote: > On 12/17/2013 10:43 AM, David C. Rankin wrote: >> Huh? Why the : in Servname? So I just hardwired it passing the port

On Dec 17, 2013, at 1:08 PM, David C. Rankin wrote: > On 12/17/2013 10:43 AM, David C. Rankin wrote: >> Huh? Why the : in Servname? So I just hardwired it passing the port "Servname" >> as "3493" (could have just used "nut" from /etc/services): > > Sheepishly looking for a place to hide.... > > Yes there was a ':' there all

Hai, I see: create_local_token failed: NT_STATUS_INVALID_PARAMETER_MIX So i suggest, remove these 3 first. That's my first bet to change. > > ??????? client ntlmv2 auth = yes > > ??????? ntlm auth = mschapv2-and-ntlmv2-only > > ??????? restrict anonymous = 2 Try again, when smbd starts, only add: ntlm auth = mschapv2-and-ntlmv2-only Greetz, Louis >

On 05/10/2019 14:10, Rowland penny via samba wrote: > On 05/10/2019 13:41, lejeczek via samba wrote: >> hi everyone, >> >> I believe a resolution is there - >> https://access.redhat.com/solutions/4367771 > Which is behind a paywall ;-) >> >> But what I'm hoping for is an expert would comment how >> would this apply >> to Samba with LDAP

Hello all; I am installing samba4 (version 4.9.5) on Debian 10.5 to use it as a member of a samba4 AD DC domain (version 4.11.4). I am following the guide https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member but I am having problems starting samba. So far I have installed the necessary packages listed here

Hello, i have a fresh installed/compiled from source samba 4.11.2 on ubuntu 18.04. But samba wont start. Syslog output: Nov? 6 12:15:19 dms systemd[1]: Starting Samba4 smbd... Nov? 6 12:15:19 dms systemd[1]: Started Samba4 smbd. Nov? 6 12:15:19 dms smbd[1557]: [2019/11/06 12:15:19.594448,? 0] ../../source3/auth/auth_util.c:1385(make_new_session_info_guest) Nov? 6 12:15:19 dms smbd[1557]:??

Jerry, Everybody: 3.0.25c compiled from source on a mandriva 2005le server in my no (AD, LDAP, Kerbose) environment. A full day of production and nothing more that a whimper out of the system. So, at least in my case 3.0.25c looks good.