Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - spott

Pages: [1] 2
1
I think now 6.2 or newer - but not 7.

2
Hi

I get rid of that after update

3
EDIT:
I updated to the latest Zentyal 6.1 - lets see, does it help or not.

4
I still have the same problem.
Any help or hints - what to look?
Now one user can't copy or add files to any shared folder any more. Other user - can.

5
I can't change the owner of that directory:
chown SERVER-DOMAIN/administrator share_name/
chown: invalid user: 'SERVER_DOMAIN/administrator'

Even when I try to change it from MC - the same. There I can see the list of users - but it doesn't change.

EDIT:
I look the ACL permissions also for this problematic share - is this normal:
Code: [Select]
getfacl SHARE_WITH_PROBLEMS
# file: SHARE_WITH_PROBLEMS
# owner: root
# group: adm
user::rwx
user:root:rwx
group::rwx
group:adm:rwx
group:SERVER_DOMAIN\134domain\040admins:rwx
group:SERVER_DOMAIN\134tootearendus_i:rwx
group:SERVER_DOMAIN\134tootearendus_i_piiratud:r-x
mask::rwx
other::---
default:user::rwx
default:user:root:rwx
default:group::rwx
default:group:adm:rwx
default:group:SERVER_DOMAIN\134domain\040admins:rwx
default:group:SERVER_DOMAIN\134tootearendus_i:rwx
default:group:SERVER_DOMAIN\134tootearendus_i_piiratud:r-x
default:mask::rwx
default:other::---

More information. I looked also ACL information inside this share:
Code: [Select]
# file: Tootmine_/
# owner: SERVER_DOMAIN\134otherusername
# group: SERVER_DOMAIN\134domain\040users
# flags: ss-
user::rwx
user:root:rwx
user:SERVER_DOMAIN\134administrator:rwx
user:SERVER_DOMAIN\134username:rwx
group::rwx
group:adm:rwx
group:SERVER_DOMAIN\134domain\040admins:rwx
group:SERVER_DOMAIN\134tootearendus_i:rwx
group:SERVER_DOMAIN\134tootearendus_i_piiratud:r-x
group:SERVER_DOMAIN\134tootearendus\040mets:rwx
mask::rwx
other::rwx
default:user::rwx
default:user:root:rwx
default:user:SERVER_DOMAIN\134administrator:rwx
default:user:SERVER_DOMAIN\134username:rwx
default:group::rwx
default:group:adm:rwx
default:group:SERVER_DOMAIN\134domain\040admins:rwx
default:group:SERVER_DOMAIN\134tootearendus_i:rwx
default:group:SERVER_DOMAIN\134tootearendus_i_piiratud:r-x
default:group:SERVER_DOMAIN\134tootearendus\040mets:rwx
default:mask::rwx
default:other::---
But here is one output from other folder - inside other share.
Code: [Select]
# file: Kataloogid/
# owner: root
# group: 1901
user::rwx
user:SERVER_DOMAIN\134administrator:rwx
group::rwx
group:adm:rwx
group:SERVER_DOMAIN\134domain\040admins:rwx
group:SERVER_DOMAIN\134tootearendus_iii:rwx
group:SERVER_DOMAIN\134tootearendus_iii_piiratud:r-x
group:SERVER_DOMAIN\134juhtkond\040company:rwx
mask::rwx
other::r-x
default:user::rwx
default:user:SERVER_DOMAIN\134administrator:rwx
default:group::rwx
default:group:adm:rwx
default:group:SERVER_DOMAIN\134domain\040admins:rwx
default:group:SERVER_DOMAIN\134tootearendus_iii:rwx
default:group:SERVER_DOMAIN\134tootearendus_iii_piiratud:r-x
default:group:SERVER_DOMAIN\134juhtkond\040company:rwx
default:mask::rwx
default:other::---

Where we have problems - there are # flags: ss-  - what it mean? Can it be the problem?

EDIT: More information.
There is some samba ACL reset problems - as default:group:SERVER_DOMAIN\134tootearendus\040mets:rwx - this is removed from this share access list. But why it still shows it? So the samba doesn't reset ACL-s.

6
But any idea - why this Apply ACLs recursively is missing from admin now? Is this normal or some bug?
I will look these wikis and try it tomorrow - there are right now some network service works - so I can't access to the server.

7
Hi

Suddenly - after moving some big folders from one share to another (I made it over terminal) and reseting ownership of files as usual - chown -R username . - we have now big problems with that share. Users can't overwrite files or folders - windows giving disk is full error. They can add new files and folders to this share and delete existing ones - but they can't overwrite files/folders as it gives disk is full error (but we have more than 2TB free space). I gave inside this folder 777 permissions to all files and folders - nothing. I restarted several times server - still nothing.
What I discover. I am running Zentyal 5.0.14 - and under Shares - I don't see "Apply ACLs recursively" part any more in Zentyal admin. This is completely missing.
When I am checking folder permissions under /home/samba/shares, then I see fallowing situation:
Code: [Select]
drwxrwx---+ 11 SERVER-DOMAIN\administrator adm                        4096 Feb 28 15:50 SHARE_1
drwxrwx---+  4 root                        adm                        4096 Mar  3 13:07 SHARE_WITH_PROBLEMS
drwxrwx---+ 30 SERVER-DOMAIN\administrator adm                        4096 Mar 30  2018 SHARE_3
drwxrwx---+  8 SERVER-DOMAIN\administrator adm                        4096 Mar  3 14:09 SHARE_4
this share has other owner - not SERVER_DOMAIN - but root.
When I am making new share - then also - owner is root and group adm.

So my questions:
1) Why this Apply ACLs recursively - is missing now from admin
2) How I can fix permissions inside this share - usually samba restart rewrites all ACL permissions. But not now. Why?
Any other help and tips - what to look.

8
pcready.cl - does you have virtualized servers? Mainly have her problems when Zentyal is running in VPS - at least my server is virtualized.

9
I am running more than 20 days now with GNU/Linux 3.19.0-43-generic x86_64 kernel.
Read this topic here are good step by step guide.
Install manualy the older kernel and then modify Grub to load only this kernel. Or choose in boot manually that kernel. When You are doing that - down down time is only minut or so for restart.

10
Change kernel to older one

11
I am running now 12 days already GNU/Linux 3.19.0-43-generic x86_64 kernel without that issue.

12
Problem starts after upgrading to 4.2 and we using some older kernel in 4.2 branch. I am testing right now with 3.19.0.43 kernel.

13
No - we using older kernel
Samba update doesn't fix it right now.

14
When You have it installed - You can try to load that older kernel. But I think its from Zentyal 4.1 and Zentyal 4.2 brings 3.19 kernels.

15
3.19.0-47
But with that was in first day big crash - so I updated again and get 51. Now I installed 43 kernel - right now its fine - but with 51 kernel it was also two days fine and then was one cores fully loaded.

Pages: [1] 2