Can't Install Openvas on Kali
I've can't solve this problem. Trying to install Openvas on Kali. I'm surprised by the amount of problems I'm facing to install a program on this OS.
I've used
apt-get install openvas
Done. Then I used
openvas-check-setup
Getting this error:
ERROR: redis-server is not running or not listening on socket: /tmp/redis.sock
FIX: You should start the redis-server or configure it to listen on socket: /tmp/redis.sock
I don't have a redis.sock on tmp folder. I tried to fix it by everything I found online.
kali-linux redis
asked Dec 23 '17 at 4:40
Hansol BoloHansol Bolo
112
add a comment |
I've can't solve this problem. Trying to install Openvas on Kali. I'm surprised by the amount of problems I'm facing to install a program on this OS.
I've used
apt-get install openvas
Done. Then I used
openvas-check-setup
Getting this error:
ERROR: redis-server is not running or not listening on socket: /tmp/redis.sock
FIX: You should start the redis-server or configure it to listen on socket: /tmp/redis.sock
I don't have a redis.sock on tmp folder. I tried to fix it by everything I found online.
kali-linux redis
asked Dec 23 '17 at 4:40
Hansol BoloHansol Bolo
112
add a comment |
I've can't solve this problem. Trying to install Openvas on Kali. I'm surprised by the amount of problems I'm facing to install a program on this OS.
I've used
apt-get install openvas
Done. Then I used
openvas-check-setup
Getting this error:
ERROR: redis-server is not running or not listening on socket: /tmp/redis.sock
FIX: You should start the redis-server or configure it to listen on socket: /tmp/redis.sock
I don't have a redis.sock on tmp folder. I tried to fix it by everything I found online.
kali-linux redis
asked Dec 23 '17 at 4:40
Hansol BoloHansol Bolo
112
I've can't solve this problem. Trying to install Openvas on Kali. I'm surprised by the amount of problems I'm facing to install a program on this OS.
I've used
apt-get install openvas
Done. Then I used
openvas-check-setup
Getting this error:
ERROR: redis-server is not running or not listening on socket: /tmp/redis.sock
FIX: You should start the redis-server or configure it to listen on socket: /tmp/redis.sock
I don't have a redis.sock on tmp folder. I tried to fix it by everything I found online.
kali-linux redis
kali-linux redis
asked Dec 23 '17 at 4:40
Hansol BoloHansol Bolo
112
asked Dec 23 '17 at 4:40
Hansol BoloHansol Bolo
112
asked Dec 23 '17 at 4:40
Hansol BoloHansol Bolo
112
asked Dec 23 '17 at 4:40
Hansol BoloHansol Bolo
112
asked Dec 23 '17 at 4:40
Hansol BoloHansol Bolo
112
112
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I encountered the same issue. The problem is that OpenVas is looking for Redis Socket in /tmp
We need to change this location in OpenVas by editing the file /etc/openvas/openvassd.conf
The problem that in Kali Linux, OpenVas does not have file: /etc/openvas/openvassd.conf by default.
So I created this file and entered below content to overwrite the default value for Redis Server.
kb_location=/var/run/redis/redis.sock
This fixed my issue.
I have wrote complete tutorial on this site:
https://waqasahmedkhan.com/openvas-bug-in-kali-linux-2017-3-5/
answered Jan 2 '18 at 5:33
yurmukiyurmuki
111
It doesn't work. Also your link to the tutorial is dead.
– Nik-Lz
Apr 9 '18 at 10:55
I have fixed the url. After migration to new server the url stopped working.
– yurmuki
Apr 16 '18 at 11:51
add a comment |
comment out “Type=forking” then reinstall openvas
/usr/lib/systemd/system/redis-server.service
[Service]
Type=forking
it works for me
why comment out
If set to forking, it is expected that the process configured with ExecStart= will call fork() as part of its start-up. The parent process is expected to exit when start-up is complete and all communication channels are set up. The child continues to run as the main daemon process. This is the behavior of traditional UNIX daemons. If this setting is used, it is recommended to also use the PIDFile= option, so that systemd can identify the main process of the daemon. systemd will proceed with starting follow-up units as soon as the parent process exits.
answered Dec 28 '18 at 8:46
jeckxiejeckxie
1
Can you be a little more explicit on how and where to implement your solution? Thanks.
– fixer1234
Dec 28 '18 at 9:36
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
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%2fsuperuser.com%2fquestions%2f1279518%2fcant-install-openvas-on-kali%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I encountered the same issue. The problem is that OpenVas is looking for Redis Socket in /tmp
We need to change this location in OpenVas by editing the file /etc/openvas/openvassd.conf
The problem that in Kali Linux, OpenVas does not have file: /etc/openvas/openvassd.conf by default.
So I created this file and entered below content to overwrite the default value for Redis Server.
kb_location=/var/run/redis/redis.sock
This fixed my issue.
I have wrote complete tutorial on this site:
https://waqasahmedkhan.com/openvas-bug-in-kali-linux-2017-3-5/
answered Jan 2 '18 at 5:33
yurmukiyurmuki
111
It doesn't work. Also your link to the tutorial is dead.
– Nik-Lz
Apr 9 '18 at 10:55
I have fixed the url. After migration to new server the url stopped working.
– yurmuki
Apr 16 '18 at 11:51
add a comment |
I encountered the same issue. The problem is that OpenVas is looking for Redis Socket in /tmp
We need to change this location in OpenVas by editing the file /etc/openvas/openvassd.conf
The problem that in Kali Linux, OpenVas does not have file: /etc/openvas/openvassd.conf by default.
So I created this file and entered below content to overwrite the default value for Redis Server.
kb_location=/var/run/redis/redis.sock
This fixed my issue.
I have wrote complete tutorial on this site:
https://waqasahmedkhan.com/openvas-bug-in-kali-linux-2017-3-5/
answered Jan 2 '18 at 5:33
yurmukiyurmuki
111
It doesn't work. Also your link to the tutorial is dead.
– Nik-Lz
Apr 9 '18 at 10:55
I have fixed the url. After migration to new server the url stopped working.
– yurmuki
Apr 16 '18 at 11:51
add a comment |
I encountered the same issue. The problem is that OpenVas is looking for Redis Socket in /tmp
We need to change this location in OpenVas by editing the file /etc/openvas/openvassd.conf
The problem that in Kali Linux, OpenVas does not have file: /etc/openvas/openvassd.conf by default.
So I created this file and entered below content to overwrite the default value for Redis Server.
kb_location=/var/run/redis/redis.sock
This fixed my issue.
I have wrote complete tutorial on this site:
https://waqasahmedkhan.com/openvas-bug-in-kali-linux-2017-3-5/
answered Jan 2 '18 at 5:33
yurmukiyurmuki
111
I encountered the same issue. The problem is that OpenVas is looking for Redis Socket in /tmp
We need to change this location in OpenVas by editing the file /etc/openvas/openvassd.conf
The problem that in Kali Linux, OpenVas does not have file: /etc/openvas/openvassd.conf by default.
So I created this file and entered below content to overwrite the default value for Redis Server.
kb_location=/var/run/redis/redis.sock
This fixed my issue.
I have wrote complete tutorial on this site:
https://waqasahmedkhan.com/openvas-bug-in-kali-linux-2017-3-5/
answered Jan 2 '18 at 5:33
yurmukiyurmuki
111
answered Jan 2 '18 at 5:33
yurmukiyurmuki
111
answered Jan 2 '18 at 5:33
yurmukiyurmuki
111
answered Jan 2 '18 at 5:33
yurmukiyurmuki
111
111
It doesn't work. Also your link to the tutorial is dead.
– Nik-Lz
Apr 9 '18 at 10:55
I have fixed the url. After migration to new server the url stopped working.
– yurmuki
Apr 16 '18 at 11:51
add a comment |
It doesn't work. Also your link to the tutorial is dead.
– Nik-Lz
Apr 9 '18 at 10:55
I have fixed the url. After migration to new server the url stopped working.
– yurmuki
Apr 16 '18 at 11:51
It doesn't work. Also your link to the tutorial is dead.
– Nik-Lz
Apr 9 '18 at 10:55
It doesn't work. Also your link to the tutorial is dead.
– Nik-Lz
Apr 9 '18 at 10:55
I have fixed the url. After migration to new server the url stopped working.
– yurmuki
Apr 16 '18 at 11:51
I have fixed the url. After migration to new server the url stopped working.
– yurmuki
Apr 16 '18 at 11:51
add a comment |
comment out “Type=forking” then reinstall openvas
/usr/lib/systemd/system/redis-server.service
[Service]
Type=forking
it works for me
why comment out
If set to forking, it is expected that the process configured with ExecStart= will call fork() as part of its start-up. The parent process is expected to exit when start-up is complete and all communication channels are set up. The child continues to run as the main daemon process. This is the behavior of traditional UNIX daemons. If this setting is used, it is recommended to also use the PIDFile= option, so that systemd can identify the main process of the daemon. systemd will proceed with starting follow-up units as soon as the parent process exits.
answered Dec 28 '18 at 8:46
jeckxiejeckxie
1
Can you be a little more explicit on how and where to implement your solution? Thanks.
– fixer1234
Dec 28 '18 at 9:36
add a comment |
comment out “Type=forking” then reinstall openvas
/usr/lib/systemd/system/redis-server.service
[Service]
Type=forking
it works for me
why comment out
If set to forking, it is expected that the process configured with ExecStart= will call fork() as part of its start-up. The parent process is expected to exit when start-up is complete and all communication channels are set up. The child continues to run as the main daemon process. This is the behavior of traditional UNIX daemons. If this setting is used, it is recommended to also use the PIDFile= option, so that systemd can identify the main process of the daemon. systemd will proceed with starting follow-up units as soon as the parent process exits.
answered Dec 28 '18 at 8:46
jeckxiejeckxie
1
Can you be a little more explicit on how and where to implement your solution? Thanks.
– fixer1234
Dec 28 '18 at 9:36
add a comment |
comment out “Type=forking” then reinstall openvas
/usr/lib/systemd/system/redis-server.service
[Service]
Type=forking
it works for me
why comment out
If set to forking, it is expected that the process configured with ExecStart= will call fork() as part of its start-up. The parent process is expected to exit when start-up is complete and all communication channels are set up. The child continues to run as the main daemon process. This is the behavior of traditional UNIX daemons. If this setting is used, it is recommended to also use the PIDFile= option, so that systemd can identify the main process of the daemon. systemd will proceed with starting follow-up units as soon as the parent process exits.
answered Dec 28 '18 at 8:46
jeckxiejeckxie
1
comment out “Type=forking” then reinstall openvas
/usr/lib/systemd/system/redis-server.service
[Service]
Type=forking
it works for me
why comment out
If set to forking, it is expected that the process configured with ExecStart= will call fork() as part of its start-up. The parent process is expected to exit when start-up is complete and all communication channels are set up. The child continues to run as the main daemon process. This is the behavior of traditional UNIX daemons. If this setting is used, it is recommended to also use the PIDFile= option, so that systemd can identify the main process of the daemon. systemd will proceed with starting follow-up units as soon as the parent process exits.
answered Dec 28 '18 at 8:46
jeckxiejeckxie
1
answered Dec 28 '18 at 8:46
jeckxiejeckxie
1
answered Dec 28 '18 at 8:46
jeckxiejeckxie
1
answered Dec 28 '18 at 8:46
jeckxiejeckxie
1
1
Can you be a little more explicit on how and where to implement your solution? Thanks.
– fixer1234
Dec 28 '18 at 9:36
add a comment |
Can you be a little more explicit on how and where to implement your solution? Thanks.
– fixer1234
Dec 28 '18 at 9:36
Can you be a little more explicit on how and where to implement your solution? Thanks.
– fixer1234
Dec 28 '18 at 9:36
Can you be a little more explicit on how and where to implement your solution? Thanks.
– fixer1234
Dec 28 '18 at 9:36
add a comment |
Thanks for contributing an answer to Super User!
- 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.
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%2fsuperuser.com%2fquestions%2f1279518%2fcant-install-openvas-on-kali%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
