django redis with django showing ulimit error
1
Im trying to use redis on my django project and when i try to run thr server using 'redis-server' on the terminal i get the following errors
2280:C 23 Nov 15:19:57.938 # oO0OoO0OoO0Oo Redis is starting
oO0OoO0OoO0Oo
2280:C 23 Nov 15:19:57.938 # Redis version=4.0.9, bits=64,
commit=00000000, modified=0, pid=2280, just started
2280:C 23 Nov 15:19:57.938 # Warning: no config file specified, using
the default config. In order to specify a config file use redis-server
/path/to/redis.conf
2280:M 23 Nov 15:19:57.939 # You requested maxclients of 10000
requiring at least 10032 max file descriptors.
2280:M 23 Nov 15:19:57.939 # Server can't set maximum open files to
10032 because of OS error: Operation not permitted.
2280:M 23 Nov 15:19:57.939 # Current maximum open files is 4096.
maxclients has been reduced to 4064 to compensate for low ulimit. If
you need higher maxclients increase 'ulimit -n'.
2280:M 23 Nov 15:19:57.939 # Creating Server TCP listening socket
*:6379: bind: Address already in use
I have tried all solutions including setting the file max size etc ,still error persists.Im using ubuntu 18.04 .Any other solutions?
python django redis
asked Nov 23 '18 at 9:56
Mohit Harshan
1249
add a comment |
1
Im trying to use redis on my django project and when i try to run thr server using 'redis-server' on the terminal i get the following errors
2280:C 23 Nov 15:19:57.938 # oO0OoO0OoO0Oo Redis is starting
oO0OoO0OoO0Oo
2280:C 23 Nov 15:19:57.938 # Redis version=4.0.9, bits=64,
commit=00000000, modified=0, pid=2280, just started
2280:C 23 Nov 15:19:57.938 # Warning: no config file specified, using
the default config. In order to specify a config file use redis-server
/path/to/redis.conf
2280:M 23 Nov 15:19:57.939 # You requested maxclients of 10000
requiring at least 10032 max file descriptors.
2280:M 23 Nov 15:19:57.939 # Server can't set maximum open files to
10032 because of OS error: Operation not permitted.
2280:M 23 Nov 15:19:57.939 # Current maximum open files is 4096.
maxclients has been reduced to 4064 to compensate for low ulimit. If
you need higher maxclients increase 'ulimit -n'.
2280:M 23 Nov 15:19:57.939 # Creating Server TCP listening socket
*:6379: bind: Address already in use
I have tried all solutions including setting the file max size etc ,still error persists.Im using ubuntu 18.04 .Any other solutions?
python django redis
asked Nov 23 '18 at 9:56
Mohit Harshan
1249
Not a programming problem. Most likely just an other process listening on port 6379 or Redis is still running.
– Klaus D.
Nov 23 '18 at 10:02
how to kill it? @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:04
This was when trying to start for the first time,the server was never run successfully before @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:23
solved it @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:26
add a comment |
1
1
1
Im trying to use redis on my django project and when i try to run thr server using 'redis-server' on the terminal i get the following errors
2280:C 23 Nov 15:19:57.938 # oO0OoO0OoO0Oo Redis is starting
oO0OoO0OoO0Oo
2280:C 23 Nov 15:19:57.938 # Redis version=4.0.9, bits=64,
commit=00000000, modified=0, pid=2280, just started
2280:C 23 Nov 15:19:57.938 # Warning: no config file specified, using
the default config. In order to specify a config file use redis-server
/path/to/redis.conf
2280:M 23 Nov 15:19:57.939 # You requested maxclients of 10000
requiring at least 10032 max file descriptors.
2280:M 23 Nov 15:19:57.939 # Server can't set maximum open files to
10032 because of OS error: Operation not permitted.
2280:M 23 Nov 15:19:57.939 # Current maximum open files is 4096.
maxclients has been reduced to 4064 to compensate for low ulimit. If
you need higher maxclients increase 'ulimit -n'.
2280:M 23 Nov 15:19:57.939 # Creating Server TCP listening socket
*:6379: bind: Address already in use
I have tried all solutions including setting the file max size etc ,still error persists.Im using ubuntu 18.04 .Any other solutions?
python django redis
asked Nov 23 '18 at 9:56
Mohit Harshan
1249
Im trying to use redis on my django project and when i try to run thr server using 'redis-server' on the terminal i get the following errors
2280:C 23 Nov 15:19:57.938 # oO0OoO0OoO0Oo Redis is starting
oO0OoO0OoO0Oo
2280:C 23 Nov 15:19:57.938 # Redis version=4.0.9, bits=64,
commit=00000000, modified=0, pid=2280, just started
2280:C 23 Nov 15:19:57.938 # Warning: no config file specified, using
the default config. In order to specify a config file use redis-server
/path/to/redis.conf
2280:M 23 Nov 15:19:57.939 # You requested maxclients of 10000
requiring at least 10032 max file descriptors.
2280:M 23 Nov 15:19:57.939 # Server can't set maximum open files to
10032 because of OS error: Operation not permitted.
2280:M 23 Nov 15:19:57.939 # Current maximum open files is 4096.
maxclients has been reduced to 4064 to compensate for low ulimit. If
you need higher maxclients increase 'ulimit -n'.
2280:M 23 Nov 15:19:57.939 # Creating Server TCP listening socket
*:6379: bind: Address already in use
I have tried all solutions including setting the file max size etc ,still error persists.Im using ubuntu 18.04 .Any other solutions?
python django redis
python django redis
asked Nov 23 '18 at 9:56
Mohit Harshan
1249
asked Nov 23 '18 at 9:56
Mohit Harshan
1249
asked Nov 23 '18 at 9:56
Mohit Harshan
1249
asked Nov 23 '18 at 9:56
Mohit Harshan
1249
asked Nov 23 '18 at 9:56
Mohit Harshan
1249
1249
Not a programming problem. Most likely just an other process listening on port 6379 or Redis is still running.
– Klaus D.
Nov 23 '18 at 10:02
how to kill it? @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:04
This was when trying to start for the first time,the server was never run successfully before @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:23
solved it @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:26
add a comment |
Not a programming problem. Most likely just an other process listening on port 6379 or Redis is still running.
– Klaus D.
Nov 23 '18 at 10:02
how to kill it? @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:04
This was when trying to start for the first time,the server was never run successfully before @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:23
solved it @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:26
Not a programming problem. Most likely just an other process listening on port 6379 or Redis is still running.
– Klaus D.
Nov 23 '18 at 10:02
Not a programming problem. Most likely just an other process listening on port 6379 or Redis is still running.
– Klaus D.
Nov 23 '18 at 10:02
how to kill it? @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:04
how to kill it? @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:04
This was when trying to start for the first time,the server was never run successfully before @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:23
This was when trying to start for the first time,the server was never run successfully before @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:23
solved it @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:26
solved it @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:26
add a comment |
1 Answer
1
active
oldest
votes
0
An instance of redis was already running! Killed it using :
$ /etc/init.d/redis-server stop
answered Nov 23 '18 at 10:27
Mohit Harshan
1249
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53444359%2fdjango-redis-with-django-showing-ulimit-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
An instance of redis was already running! Killed it using :
$ /etc/init.d/redis-server stop
answered Nov 23 '18 at 10:27
Mohit Harshan
1249
add a comment |
0
An instance of redis was already running! Killed it using :
$ /etc/init.d/redis-server stop
answered Nov 23 '18 at 10:27
Mohit Harshan
1249
add a comment |
0
0
0
An instance of redis was already running! Killed it using :
$ /etc/init.d/redis-server stop
answered Nov 23 '18 at 10:27
Mohit Harshan
1249
An instance of redis was already running! Killed it using :
$ /etc/init.d/redis-server stop
answered Nov 23 '18 at 10:27
Mohit Harshan
1249
answered Nov 23 '18 at 10:27
Mohit Harshan
1249
answered Nov 23 '18 at 10:27
Mohit Harshan
1249
answered Nov 23 '18 at 10:27
Mohit Harshan
1249
1249
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53444359%2fdjango-redis-with-django-showing-ulimit-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Not a programming problem. Most likely just an other process listening on port 6379 or Redis is still running.
– Klaus D.
Nov 23 '18 at 10:02
how to kill it? @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:04
This was when trying to start for the first time,the server was never run successfully before @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:23
solved it @KlausD.
– Mohit Harshan
Nov 23 '18 at 10:26