Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
6377f3e2
Commit
6377f3e2
authored
Dec 04, 2019
by
GitLab Bot
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add latest changes from gitlab-org/gitlab@master
parent
e2334f36
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
16 additions
and
2 deletions
+16
-2
doc/administration/geo/replication/troubleshooting.md
doc/administration/geo/replication/troubleshooting.md
+14
-0
doc/install/aws/index.md
doc/install/aws/index.md
+1
-1
doc/user/admin_area/settings/visibility_and_access_controls.md
...ser/admin_area/settings/visibility_and_access_controls.md
+1
-1
No files found.
doc/administration/geo/replication/troubleshooting.md
View file @
6377f3e2
...
...
@@ -701,3 +701,17 @@ See ["Foreign Data Wrapper (FDW) is not configured" error?](#foreign-data-wrappe
This can be caused by orphaned records in the project registry. You can clear them
[
using a Rake task
](
../../../administration/raketasks/geo.md#remove-orphaned-project-registries
)
.
### Geo Admin Area returns 404 error for a secondary node
Sometimes
`sudo gitlab-rake gitlab:geo:check`
indicates that the
**secondary**
node is
healthy, but a 404 error for the
**secondary**
node is returned in the Geo Admin Area on
the
**primary**
node.
To resolve this issue:
-
Try restarting the
**secondary**
using
`sudo gitlab-ctl restart`
.
-
Check
`/var/log/gitlab/gitlab-rails/geo.log`
to see if the
**secondary**
node is
using IPv6 to send its status to the
**primary**
node. If it is, add an entry to
the
**primary**
node using IPv4 in the
`/etc/hosts`
file. Alternatively, you should
[
enable IPv6 on the primary node
](
https://docs.gitlab.com/omnibus/settings/nginx.html#setting-the-nginx-listen-address-or-addresses
)
.
doc/install/aws/index.md
View file @
6377f3e2
...
...
@@ -362,7 +362,7 @@ Choose the AMI:
You should choose an instance type based on your workload. Consult
[
the hardware requirements
](
../requirements.md#hardware-requirements
)
to choose
one that fits your needs (at least
`c
4
.xlarge`
, which is enough to accommodate 100 users):
one that fits your needs (at least
`c
5
.xlarge`
, which is enough to accommodate 100 users):
1.
Choose the your instance type.
1.
Click
**Next: Configure Instance Details**
.
...
...
doc/user/admin_area/settings/visibility_and_access_controls.md
View file @
6377f3e2
...
...
@@ -38,7 +38,7 @@ To change the default project creation protection:
For more details, see
[
Default project-creation level
](
../../group/index.md#default-project-creation-level
)
.
## Default project deletion protection
## Default project deletion protection
**(PREMIUM ONLY)**
By default, a project can be deleted by anyone with the
**Owner**
role, either at the project or
group level.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment