Re: [CentOS] upgrading 7.5 ==> 7.6

[Fred Smith]

On Fri, Dec 21, 2018 at 01:06:14PM -0800, Alice Wonder wrote:
> On 12/21/18 12:44 PM, Fred Smith wrote:
> >On Fri, Dec 21, 2018 at 06:27:45PM +, Liam O'Toole wrote:
> >>On 2018-12-19, Fred Smith
> >> wrote:
> >>
> >>[...]
> >>
> >>>Result: Boots to GDM just fine, but Mate is a black screen. Switching
> >>>to Gnome, works fine, but I can't stand Gnome.  Not knowing what else
> >>>to try I restored the dd backup.
> >>
> >>This is a known issue, and was mentioned on this list recently. The
> >>problem is that Mate in EPEL needs to be updated to work with CentOS
> >>7.6. Perhaps keep an eye on changes to the EPEL repo before attempting
> >>the upgrade again.
> >
> >Thanks, Liam, for the info.
> >
> >Since it IS working on the netbook I'm hoping that means that whatever
> >needed updating has been updated.
> >
> >So, I compared the versions on my desktop with those on the netbook, and
> >find that mate_dictionary, mate-disk-usage-analyzer, mate-screenshot,
> >mate-search-tool, mate-system-log, mate-system-monitor, mate-utilsk,
> >mate-utils-common all had a minor version bump. Some from 1.16.1-1 to
> >1.16.1-2, one from 1.16.0-1 to 1.16.0-2.
> >
> >I know there are other packages that do not contain "mate" in their names,
> >but I don't know which they are.
> >
> >So, do you (or anyone else) happen to know which Mate packages are/were
> >in need of update?
> >
> >thanks again, in advance.
> >
> 
> Not sure, MATE is working just fine for me, versions range from
> 1.16.0 to 1.16.3
> 
> yum list |grep "mate" |grep -v "@epel" |grep -v "devel"
> mate-menus-preferences-category-menu.x86_64
> classmate.noarch 1.3.1-2.el7 epel
> classmate-javadoc.noarch 1.3.1-2.el7 epel
> f22-backgrounds-mate.noarch  21.91.0-1.el7 epel
> mate-common.noarch   1.16.0-1.el7 epel
> mate-netspeed.x86_64 1.12.0-1.el7 epel
> mate-sensors-applet.x86_64   1.16.1-1.el7 epel
> mate-themes-extras.noarch3.14.7-1.el7 epel
> php-league-climate.noarch3.2.4-1.el7 epel
> workrave-mate.x86_64 1.10.16-1.el7 epel
> xmonad-mate.x86_64   0.11-12.el7 epel
> 
> Some of those obviously are not mate packages, but those are the
> only mate packages I do NOT have installed and it is working, so if
> mate is not working I wonder if the issue is something other than
> the packages.


Good question, Alice. I guess I need to go back to trying the upgrade
again on my new-to-me-but-still-pretty-old laptop, where it failed a week
or so ago. If that works I'll be slightly less paranoid about trying it
on my main desktop box, which I definitely do NOT want to screw up.

Or maybe plug in a 1tb usb drive and install on it and see what happens.

Fred

-- 
---
Under no circumstances will I ever purchase anything offered to me as
the result of an unsolicited e-mail message. Nor will I forward chain
letters, petitions, mass mailings, or virus warnings to large numbers
of others. This is my contribution to the survival of the online
community.
 --Roger Ebert, December, 1996
- The Boulder Pledge -
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] upgrading 7.5 ==> 7.6

[Alice Wonder]

On 12/21/18 12:44 PM, Fred Smith wrote:

On Fri, Dec 21, 2018 at 06:27:45PM +, Liam O'Toole wrote:

On 2018-12-19, Fred Smith
 wrote:

[...]


Result: Boots to GDM just fine, but Mate is a black screen. Switching
to Gnome, works fine, but I can't stand Gnome.  Not knowing what else
to try I restored the dd backup.


This is a known issue, and was mentioned on this list recently. The
problem is that Mate in EPEL needs to be updated to work with CentOS
7.6. Perhaps keep an eye on changes to the EPEL repo before attempting
the upgrade again.


Thanks, Liam, for the info.

Since it IS working on the netbook I'm hoping that means that whatever
needed updating has been updated.

So, I compared the versions on my desktop with those on the netbook, and
find that mate_dictionary, mate-disk-usage-analyzer, mate-screenshot,
mate-search-tool, mate-system-log, mate-system-monitor, mate-utilsk,
mate-utils-common all had a minor version bump. Some from 1.16.1-1 to
1.16.1-2, one from 1.16.0-1 to 1.16.0-2.

I know there are other packages that do not contain "mate" in their names,
but I don't know which they are.

So, do you (or anyone else) happen to know which Mate packages are/were
in need of update?

thanks again, in advance.



Not sure, MATE is working just fine for me, versions range from 1.16.0 
to 1.16.3


yum list |grep "mate" |grep -v "@epel" |grep -v "devel"
mate-menus-preferences-category-menu.x86_64
classmate.noarch 1.3.1-2.el7 
epel
classmate-javadoc.noarch 1.3.1-2.el7 
epel
f22-backgrounds-mate.noarch  21.91.0-1.el7 
epel
mate-common.noarch   1.16.0-1.el7 
epel
mate-netspeed.x86_64 1.12.0-1.el7 
epel
mate-sensors-applet.x86_64   1.16.1-1.el7 
epel
mate-themes-extras.noarch3.14.7-1.el7 
epel
php-league-climate.noarch3.2.4-1.el7 
epel
workrave-mate.x86_64 1.10.16-1.el7 
epel

xmonad-mate.x86_64   0.11-12.el7 epel

Some of those obviously are not mate packages, but those are the only 
mate packages I do NOT have installed and it is working, so if mate is 
not working I wonder if the issue is something other than the packages.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] upgrading 7.5 ==> 7.6

[Fred Smith]

On Fri, Dec 21, 2018 at 06:27:45PM +, Liam O'Toole wrote:
> On 2018-12-19, Fred Smith
>  wrote:
> 
> [...]
> 
> > Result: Boots to GDM just fine, but Mate is a black screen. Switching
> > to Gnome, works fine, but I can't stand Gnome.  Not knowing what else 
> > to try I restored the dd backup.
> 
> This is a known issue, and was mentioned on this list recently. The
> problem is that Mate in EPEL needs to be updated to work with CentOS
> 7.6. Perhaps keep an eye on changes to the EPEL repo before attempting
> the upgrade again.

Thanks, Liam, for the info.

Since it IS working on the netbook I'm hoping that means that whatever
needed updating has been updated.

So, I compared the versions on my desktop with those on the netbook, and
find that mate_dictionary, mate-disk-usage-analyzer, mate-screenshot,
mate-search-tool, mate-system-log, mate-system-monitor, mate-utilsk,
mate-utils-common all had a minor version bump. Some from 1.16.1-1 to
1.16.1-2, one from 1.16.0-1 to 1.16.0-2.

I know there are other packages that do not contain "mate" in their names,
but I don't know which they are.

So, do you (or anyone else) happen to know which Mate packages are/were
in need of update?

thanks again, in advance.

-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
The Lord is like a strong tower. 
 Those who do what is right can run to him for safety.
--- Proverbs 18:10 (niv) -
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap

[Miroslav Geisselreiter]

Thanks for tip, Kenneth.
Please find proper formatted logs here:
https://pastebin.com/eXfNWBLu

Dne 21.12.2018 v 17:18 Kenneth Porter napsal(a):
--On Friday, December 21, 2018 1:37 PM +0100 Miroslav Geisselreiter 
 wrote:



I am sorry logs are bad formatted I am trying again and hope it will be
better. Otherwise lokk at link bellow or tell me how to send logs
correctly.


Copy them to a pastebin and post the link to the pastebin. Pastebin is 
ideal for log files, source code, and other text data that's large or 
needs special formatting.



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] daemon core dump

[Alice Wonder]

I have a daemon I can conistently cause a crash on.

https://iangilham.com/2016/12/08/core-dump-from-centos-7.html

Is that the best way (obviously with debug packages installed) to get 
the core dump or is there a better way?


It is NOT a CentOS/EPEL maintained daemon.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] upgrading 7.5 ==> 7.6

[Liam O'Toole]

On 2018-12-19, Fred Smith
 wrote:

[...]

> Result: Boots to GDM just fine, but Mate is a black screen. Switching
> to Gnome, works fine, but I can't stand Gnome.  Not knowing what else 
> to try I restored the dd backup.

This is a known issue, and was mentioned on this list recently. The
problem is that Mate in EPEL needs to be updated to work with CentOS
7.6. Perhaps keep an eye on changes to the EPEL repo before attempting
the upgrade again.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Gnome-shell memory

[Jerry Geis]

Looks like over time the --replace is not an option.

Is there an repo that has update Gnome-shell and needed files  that I can
try ?

Thanks,

Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap

[Kenneth Porter]

--On Friday, December 21, 2018 1:37 PM +0100 Miroslav Geisselreiter 
 wrote:



I am sorry logs are bad formatted I am trying again and hope it will be
better. Otherwise lokk at link bellow or tell me how to send logs
correctly.


Copy them to a pastebin and post the link to the pastebin. Pastebin is 
ideal for log files, source code, and other text data that's large or needs 
special formatting.



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Fedora Server - as an alternative ?

[Robert Moskowitz]

On 12/21/18 10:25 AM, mark wrote:

Robert Moskowitz wrote:

On 12/20/18 10:33 AM, mark wrote:

lejeczek via CentOS wrote:

I wonder if any Centosian here have done something different than
only contemplated using Fedora Server, actually worked on it in
test/production envs.

If here are some folks who have done it I want to ask if you deem it
to be a viable option to put it on at least portion of servers stack.

Anybody?



I would not run it as a server. In a server and workstation
environment, you do *not* want to have daily multiple updates to
software, you want stability, or you're likely to have your users
seriously aggravated by you, for breaking their jobs far too frequently.

Where do you get that with Fedora server you have to do daily multiple
updates?


I frequently see my manager's fedora box doing updates, multiple times a
week.


Yes, updates come out practically every day.  So?  Microsoft sends out 
updates to its desktops practically every day also.


I turned off auto updates on my Fedora notebook and tend to do them 
Monday mornings to start the new week 'up to date'.  I have NOT turned 
off auto updates on the Win7 systems here, as otherwise I might just 
forget as I use them too infrequently myself.


Tracer is an interesting tool to see, after an update, what you have to 
restart.  Sometimes just an app or a logout and back in. Sometimes a reboot.



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Gnome-shell memory

[Jerry Geis]

> Sounds like a hammer method. Is this issue already communicated to upstream 
> (bugzilla)?

I believe so - Gnome 3.28+  says even more memory fixes... I would
think something like that they would rebase gnome again (hopefully
before 7.7).  But certainly not up to me.


Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Fedora Server - as an alternative ?

[mark]

Robert Moskowitz wrote:
> On 12/20/18 10:33 AM, mark wrote:
>> lejeczek via CentOS wrote:
>>>
>>> I wonder if any Centosian here have done something different than
>>> only contemplated using Fedora Server, actually worked on it in
>>> test/production envs.
>>>
>>> If here are some folks who have done it I want to ask if you deem it
>>> to be a viable option to put it on at least portion of servers stack.
>>>
>>> Anybody?
>>>
>>>
>> I would not run it as a server. In a server and workstation
>> environment, you do *not* want to have daily multiple updates to
>> software, you want stability, or you're likely to have your users
>> seriously aggravated by you, for breaking their jobs far too frequently.
>
> Where do you get that with Fedora server you have to do daily multiple
> updates?
>
I frequently see my manager's fedora box doing updates, multiple times a
week.

   mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Gnome-shell memory

[Leon Fauster via CentOS]

> Am 21.12.2018 um 16:02 schrieb Jerry Geis :
> 
> So after much research it seems the only way to "help" the gnome-shell
> memory leak issue (I still see it on CentOS 7.6) is to do "export
> DISPLAY=:0.0; gnome-shell --replace"  periodically. Perhaps in cron.
> 
> Is that an OK solution for the LONG haul? Seems to knock the memory back
> down and box appears to keep running.


Sounds like a hammer method. Is this issue already communicated to upstream 
(bugzilla)?

--
LF

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Gnome-shell memory

[Jerry Geis]

So after much research it seems the only way to "help" the gnome-shell
memory leak issue (I still see it on CentOS 7.6) is to do "export
DISPLAY=:0.0; gnome-shell --replace"  periodically. Perhaps in cron.

Is that an OK solution for the LONG haul? Seems to knock the memory back
down and box appears to keep running.

Thanks,

Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Fedora Server - as an alternative ?

[Robert Moskowitz]

On 12/20/18 12:19 PM, lejeczek via CentOS wrote:

On 20/12/2018 15:33, mark wrote:

lejeczek via CentOS wrote:

hi guys

I wonder if any Centosian here have done something different than only
contemplated using Fedora Server, actually worked on it in 
test/production

envs.

If here are some folks who have done it I want to ask if you deem it to
be a viable option to put it on at least portion of servers stack.

Anybody?


I would not run it as a server. In a server and workstation environment,
you do *not* want to have daily multiple updates to software, you want
stability, or you're likely to have your users seriously aggravated by
you, for breaking their jobs far too frequently.

Spin up a VM or two, for folks who actually (or think they actually) 
need

newer software and utility stacks, but use something stable as a base.

   mark "I do see how many update's my manager's fedora box gets..."

What I'm really looking forward to - why I thought I'd poke around, 
thus that question - is RDP in Wayland.


When it get's into RHELs I worry be ages and I'd really love to try to 
introduce Linux desktops to those really dumb and unreformable users.


Everything else - frequent updates, etc. These can be as rare as we 
users want them, another extra bit of time to think of it would not 
kill me, personally.


Why are we beating ourselves up about updates.  I have a couple Win7 
systems here and updates are constant.  My daughter is often caught not 
being able to do her homework as the system is applying updates on 
powerup.  Or I wake up to my Win7 system running at the login after I 
had suspended it the prior day, as some non-sleeping task took advantage 
and did a required reboot overnight.


dnf update is now part of the startup and a regular process. Warnings 
about needing to reboot, are really no different than what Win users 
deal with.  Again, my daughter is often clicking on delay autoreboot for 
an hour so she can finish her homework (and the other night she got the 
BSOD for her efforts).




Also, we all know, what is in those Fedoras(maybe more so when it 
comes to "server" variant) is going to end up in our Centoses - why 
not help by using/testing those, I ask myself. Especially now with 29 
which I suspect might be our Centos main new version.


So I'm thinking.. I'll start mixing that Fedora Server in.




___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap

[Miroslav Geisselreiter]

I am sorry logs are bad formatted I am trying again and hope it will be 
better. Otherwise lokk at link bellow or tell me how to send logs correctly.


Mirek

21.12.2018 v 13:19 Miroslav Geisselreiter:

Originally I posted this question at CentOS forum 20.12.2018.
https://www.centos.org/forums/viewtopic.php?f=48=69193

Hi all,

I am not able to mount samba shares after upgrading CentOS 7.5 to 7.6. 
I have been searching and trying to configure samba and winbind but no 
success. I find a lot of manuals and help pages about setting samba 
and winbind for machine acting as AD DC member but almost nothing 
about machine acting as NT4 style DC member and that is my case.


Samba version before upgrade: samba-4.7.1-9.el7_5.x86_64, after 
upgrade: samba-4.8.3-4.el7.x86_64. I noticed that now it is necessary 
to use winbind which I did not use before upgrade.


My network:

Machine with CentOS 6.9 is PDC (NT4 style) configured with ldap and 
kerberos, providing domain logon services to Windows and Samba clients 
of an NT4-like domain. openldap-2.4.40-16.el6.x86_64, 
krb5-server-1.10.3-65.el6.x86_64, samba-3.6.23-51.el6.x86_64.


Machine with CentOS 7.6 is domain member offering network shares to 
windows clients. Before upgrade my samba-4.7 run only smb and nmb 
services and everything were fine. After upgrade samba-4.8.3 runs smb 
nmb and winbind services.

smb.conf:
workgroup = NT4DOMAIN
netbios name = NT4MEMBER
|# wbinfo -m --verbose Domain Name DNS Domain Trust Type Transitive In 
Out BUILTIN Local NT4MEMBER Local NT4DOMAIN INTRANET.XX Workstation 
Yes No Yes # wbinfo --own-domain NT4DOMAIN |


I discovered that winbind is not authenticating users with NT4DOMAIN 
but only with NT4MEMBER. In this case NT4MEMBER users ARE NT4DOMAIN 
users (there is only one user1 in ldap database). It can be seen in 
logs bellow. I set debug level 3 for smbd and winbindd. Windows 
machines have joined NT4DOMAIN but now cannot mount shares from 
NT4MEMBER. Windows mount command net use /user:NT4DOMAIN\user1 
\\NT4MEMBER\share1 is equal to linux command smbclient 
//NT4MEMBER/share1 -U NT4DOMAIN\\user1. From linux machine I can mount 
share by this command: smbclient //NT4MEMBER/share1 -U 
NT4MEMBER\\user1 but from windows machine it is not possible. Normally 
(before upgrade) Windows users mapped shares from startup script with 
this command: net use \\NT4MEMBER\share1.


What is going wrong can be seen from logs:
|# smbclient //NT4MEMBER/share1 -U NT4DOMAIN\\user1 smbd log: 
check_ntlm_password: Checking password for unmapped user 
[NT4DOMAIN]\[user1]@[NT4MEMBER] with the new password interface 
check_ntlm_password: mapped user is: [NT4DOMAIN]\[user1]@[NT4MEMBER] 
check_ntlm_password: Authentication for user [user1] -> [user1] FAILED 
with error NT_STATUS_NO_MEMORY, authoritative=1 Auth: [SMB2,(null)] 
user [NT4DOMAIN]\[user1] at [Wed, 19 Dec 2018 13:56:08.989053 CET] 
with [NTLMv2] status [NT_STATUS_NO_MEMORY] workstation [NT4MEMBER] 
remote host [ipv4:X.X.X.X:40488] mapped to [NT4DOMAIN]\[user1]. local 
host [ipv4:X.X.X.X:445] log_no_json: JSON auth logs not available 
unless compiled with jansson gensec_spnego_server_negTokenTarg_step: 
SPNEGO(ntlmssp) login failed: NT_STATUS_NO_MEMORY 
smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] 
status[NT_STATUS_NO_MEMORY] || at ../source3/smbd/smb2_sesssetup.c:137 
Server exit (NT_STATUS_END_OF_FILE) Terminated winbind log: [ 9232]: 
request interface version (version = 30) [ 9232]: request location of 
privileged pipe [ 9232]: pam auth crap domain: [NT4DOMAIN] user: user1 
set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was 
a DC for domain NT4MEMBER, refusing to initialize [ 9228]: pam auth 
crap domain: NT4DOMAIN user: user1 set_dc_type_and_flags_connect: DC 
for domain NT4DOMAIN claimed it was a DC for domain NT4MEMBER, 
refusing to initialize set_dc_type_and_flags_connect: DC for domain 
NT4DOMAIN claimed it was a DC for domain NT4MEMBER, refusing to 
initialize ldb_wrap open of secrets.ldb rpccli_create_netlogon_creds 
failed for NT4DOMAIN, unable to create NETLOGON credentials: 
NT_STATUS_NO_MEMORY Could not open handle to NETLOGON pipe (error: 
NT_STATUS_NO_MEMORY, attempts: 0) The connection to netlogon failed, 
retrying set_dc_type_and_flags_connect: DC for domain NT4DOMAIN 
claimed it was a DC for domain NT4MEMBER, refusing to initialize 
set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was 
a DC for domain NT4MEMBER, refusing to initialize ldb_wrap open of 
secrets.ldb rpccli_create_netlogon_creds failed for NT4DOMAIN, unable 
to create NETLOGON credentials: NT_STATUS_NO_MEMORY Could not open 
handle to NETLOGON pipe (error: NT_STATUS_NO_MEMORY, attempts: 1) This 
is again a problem for this particular call, forcing the close of this 
connection The connection to netlogon failed, retrying 
set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was 
a DC for domain NT4MEMBER, refusing to initialize 

[CentOS] upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap

[Miroslav Geisselreiter]

Originally I posted this question at CentOS forum 20.12.2018.
https://www.centos.org/forums/viewtopic.php?f=48=69193

Hi all,

I am not able to mount samba shares after upgrading CentOS 7.5 to 7.6. I 
have been searching and trying to configure samba and winbind but no 
success. I find a lot of manuals and help pages about setting samba and 
winbind for machine acting as AD DC member but almost nothing about 
machine acting as NT4 style DC member and that is my case.


Samba version before upgrade: samba-4.7.1-9.el7_5.x86_64, after upgrade: 
samba-4.8.3-4.el7.x86_64. I noticed that now it is necessary to use 
winbind which I did not use before upgrade.


My network:

Machine with CentOS 6.9 is PDC (NT4 style) configured with ldap and 
kerberos, providing domain logon services to Windows and Samba clients 
of an NT4-like domain. openldap-2.4.40-16.el6.x86_64, 
krb5-server-1.10.3-65.el6.x86_64, samba-3.6.23-51.el6.x86_64.


Machine with CentOS 7.6 is domain member offering network shares to 
windows clients. Before upgrade my samba-4.7 run only smb and nmb 
services and everything were fine. After upgrade samba-4.8.3 runs smb 
nmb and winbind services.

smb.conf:
workgroup = NT4DOMAIN
netbios name = NT4MEMBER

|# wbinfo -m --verbose Domain Name DNS Domain Trust Type Transitive In 
Out BUILTIN Local NT4MEMBER Local NT4DOMAIN INTRANET.XX Workstation Yes 
No Yes # wbinfo --own-domain NT4DOMAIN |



I discovered that winbind is not authenticating users with NT4DOMAIN but 
only with NT4MEMBER. In this case NT4MEMBER users ARE NT4DOMAIN users 
(there is only one user1 in ldap database). It can be seen in logs 
bellow. I set debug level 3 for smbd and winbindd. Windows machines have 
joined NT4DOMAIN but now cannot mount shares from NT4MEMBER. Windows 
mount command net use /user:NT4DOMAIN\user1 \\NT4MEMBER\share1 is equal 
to linux command smbclient //NT4MEMBER/share1 -U NT4DOMAIN\\user1. From 
linux machine I can mount share by this command: smbclient 
//NT4MEMBER/share1 -U NT4MEMBER\\user1 but from windows machine it is 
not possible. Normally (before upgrade) Windows users mapped shares from 
startup script with this command: net use \\NT4MEMBER\share1.


What is going wrong can be seen from logs:

|# smbclient //NT4MEMBER/share1 -U NT4DOMAIN\\user1 smbd log: 
check_ntlm_password: Checking password for unmapped user 
[NT4DOMAIN]\[user1]@[NT4MEMBER] with the new password interface 
check_ntlm_password: mapped user is: [NT4DOMAIN]\[user1]@[NT4MEMBER] 
check_ntlm_password: Authentication for user [user1] -> [user1] FAILED 
with error NT_STATUS_NO_MEMORY, authoritative=1 Auth: [SMB2,(null)] user 
[NT4DOMAIN]\[user1] at [Wed, 19 Dec 2018 13:56:08.989053 CET] with 
[NTLMv2] status [NT_STATUS_NO_MEMORY] workstation [NT4MEMBER] remote 
host [ipv4:X.X.X.X:40488] mapped to [NT4DOMAIN]\[user1]. local host 
[ipv4:X.X.X.X:445] log_no_json: JSON auth logs not available unless 
compiled with jansson gensec_spnego_server_negTokenTarg_step: 
SPNEGO(ntlmssp) login failed: NT_STATUS_NO_MEMORY 
smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] 
status[NT_STATUS_NO_MEMORY] || at ../source3/smbd/smb2_sesssetup.c:137 
Server exit (NT_STATUS_END_OF_FILE) Terminated winbind log: [ 9232]: 
request interface version (version = 30) [ 9232]: request location of 
privileged pipe [ 9232]: pam auth crap domain: [NT4DOMAIN] user: user1 
set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a 
DC for domain NT4MEMBER, refusing to initialize [ 9228]: pam auth crap 
domain: NT4DOMAIN user: user1 set_dc_type_and_flags_connect: DC for 
domain NT4DOMAIN claimed it was a DC for domain NT4MEMBER, refusing to 
initialize set_dc_type_and_flags_connect: DC for domain NT4DOMAIN 
claimed it was a DC for domain NT4MEMBER, refusing to initialize 
ldb_wrap open of secrets.ldb rpccli_create_netlogon_creds failed for 
NT4DOMAIN, unable to create NETLOGON credentials: NT_STATUS_NO_MEMORY 
Could not open handle to NETLOGON pipe (error: NT_STATUS_NO_MEMORY, 
attempts: 0) The connection to netlogon failed, retrying 
set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a 
DC for domain NT4MEMBER, refusing to initialize 
set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a 
DC for domain NT4MEMBER, refusing to initialize ldb_wrap open of 
secrets.ldb rpccli_create_netlogon_creds failed for NT4DOMAIN, unable to 
create NETLOGON credentials: NT_STATUS_NO_MEMORY Could not open handle 
to NETLOGON pipe (error: NT_STATUS_NO_MEMORY, attempts: 1) This is again 
a problem for this particular call, forcing the close of this connection 
The connection to netlogon failed, retrying 
set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a 
DC for domain NT4MEMBER, refusing to initialize 
set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a 
DC for domain NT4MEMBER, refusing to initialize ldb_wrap open of 
secrets.ldb rpccli_create_netlogon_creds failed for NT4DOMAIN, unable to 

[CentOS] CentOS-announce Digest, Vol 166, Issue 7

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. Updates in 7.6.1810/os Repository from the CR Announce List
  (Johnny Hughes)


--

Message: 1
Date: Thu, 20 Dec 2018 07:50:09 -0600
From: Johnny Hughes 
To: CentOS-Announce 
Subject: [CentOS-announce] Updates in 7.6.1810/os Repository from the
CR  Announce List
Message-ID: <776565e3-dfea-45ba-a4a6-ef909464c...@centos.org>
Content-Type: text/plain; charset="utf-8"

As part of the CR process (
https://wiki.centos.org/AdditionalResources/Repositories/CR ), the
following updates were done and are included in the CentOS base ( os/ )
repository for CentOS Linux 7.6.1810.

https://lists.centos.org/pipermail/centos-cr-announce/2018-November/thread.html

https://lists.centos.org/pipermail/centos-cr-announce/2018-December/thread.html

There was an issue with the announcement generation scripting that used
the errata API to pull information for the announcements (that is now
fixed), so some of the announcements happened later than the actual
build date and release date of the packages (as an example, the date we
created the man-db announcement was December 19th (
https://lists.centos.org/pipermail/centos-cr-announce/2018-December/005800.html
) .. the actual date of the package build was 30 Oct 2018 08:26:54 PM
UTC .. and it was signed and then released initially into CR on 12 Nov 2018.

We have since generated any missing announcements to the CR announce
list and also any updates to the os/ repo (that live in the udpates/
repo) were announced to this centos-announce list.

Thanks,
Johnny Hughes




-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: 


--

Subject: Digest Footer

___
CentOS-announce mailing list
centos-annou...@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce


--

End of CentOS-announce Digest, Vol 166, Issue 7
***
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Fedora Server - as an alternative ?

[Patrick Bégou]

Le 20/12/2018 à 16:21, Chris Schanzle via CentOS a écrit :
> On 12/20/18 10:07 AM, Patrick Bégou wrote:
>> Le 20/12/2018 à 14:11, lejeczek via CentOS a écrit :
>>> hi guys
>>>
>>> I wonder if any Centosian here have done something different than only
>>> contemplated using Fedora Server, actually worked on it in
>>> test/production envs.
>>>
>>> If here are some folks who have done it I want to ask if you deem it
>>> to be a viable option to put it on at least portion of servers stack.
>>>
>>> Anybody?
>>>
>>> Many thanks, L.
>>>
>>> ___
>>> CentOS mailing list
>>> CentOS@centos.org
>>>
>> Using fedora will lead you to reinstall servers frequently, for almost
>> each new versions I think.
>>
>> Many years ago I was using opensuse as some of my servers were running
>> SLES and migration between versions was  realy difficult without full
>> reinstall every 1,5 to 2 years...
>>
>>
>> Patrick
>
>
> That's just...err, misinformation.  The Fedora team works very hard to
> enable upgrading (without a clean install) from one release to the
> next...often skipping releases is fine (e.g., 27 to 29).
>
> That said, I only have a few Fedora boxes (used like servers -- that
> is, not on people's desks) for my users that need more bleeding edge
> software stacks and additional packages than CentOS + EPEL can
> provide.  Due to the heavy flow of packages updates and kernel
> updates, it takes a special kind of user to cope with updates,
> reboots, and occasional breakage.
>
> Chris


... or just 27 years of migration experience :-D (all OS included). Even
with Fedora laptop, but of course it was many years ago with realy old
versions (4 to 5 to 6...). No doubtthat things have been improved but
between theory and practice

Patrick


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos