sudo apt update: terminate called after throwing an instance of 'std::runtime_error'
Clash Royale CLAN TAG#URR8PPP up vote
4
down vote
favorite
I am randomly seeing the following error on my Ubuntu 18.04 server.
sudo apt update
[sudo] password for david:
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [83.2 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
0% [1 InRelease gpgv 242 kB] [4 InRelease 2,281 B/74.6 kB 3%]terminate called after throwing an instance of 'std::runtime_error'
what(): random_device::__x86_rdrand(void)
Aborted
Sometimes a reboot solves the issue, sometimes not. Currently not. At one point it seemed to be related to urbackup, but stopping the service doesn't fix the problem today.
apt updates
asked Jun 11 at 10:57
m-dw
261
add a comment |Â
up vote
4
down vote
favorite
I am randomly seeing the following error on my Ubuntu 18.04 server.
sudo apt update
[sudo] password for david:
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [83.2 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
0% [1 InRelease gpgv 242 kB] [4 InRelease 2,281 B/74.6 kB 3%]terminate called after throwing an instance of 'std::runtime_error'
what(): random_device::__x86_rdrand(void)
Aborted
Sometimes a reboot solves the issue, sometimes not. Currently not. At one point it seemed to be related to urbackup, but stopping the service doesn't fix the problem today.
apt updates
asked Jun 11 at 10:57
m-dw
261
1
That's interesting. I have disabled the "Execute Disable Bit" in the server BIOS and it works. Don't know if this is a permanent or temporary solution.
– m-dw
Jun 11 at 11:56
You should post that an an answer instead of a comment before your question gets closed...
– Fabby
Jun 21 at 20:46
add a comment |Â
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I am randomly seeing the following error on my Ubuntu 18.04 server.
sudo apt update
[sudo] password for david:
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [83.2 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
0% [1 InRelease gpgv 242 kB] [4 InRelease 2,281 B/74.6 kB 3%]terminate called after throwing an instance of 'std::runtime_error'
what(): random_device::__x86_rdrand(void)
Aborted
Sometimes a reboot solves the issue, sometimes not. Currently not. At one point it seemed to be related to urbackup, but stopping the service doesn't fix the problem today.
apt updates
asked Jun 11 at 10:57
m-dw
261
I am randomly seeing the following error on my Ubuntu 18.04 server.
sudo apt update
[sudo] password for david:
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [83.2 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
0% [1 InRelease gpgv 242 kB] [4 InRelease 2,281 B/74.6 kB 3%]terminate called after throwing an instance of 'std::runtime_error'
what(): random_device::__x86_rdrand(void)
Aborted
Sometimes a reboot solves the issue, sometimes not. Currently not. At one point it seemed to be related to urbackup, but stopping the service doesn't fix the problem today.
apt updates
asked Jun 11 at 10:57
m-dw
261
asked Jun 11 at 10:57
m-dw
261
asked Jun 11 at 10:57
m-dw
261
asked Jun 11 at 10:57
m-dw
261
261
1
That's interesting. I have disabled the "Execute Disable Bit" in the server BIOS and it works. Don't know if this is a permanent or temporary solution.
– m-dw
Jun 11 at 11:56
You should post that an an answer instead of a comment before your question gets closed...
– Fabby
Jun 21 at 20:46
add a comment |Â
1
That's interesting. I have disabled the "Execute Disable Bit" in the server BIOS and it works. Don't know if this is a permanent or temporary solution.
– m-dw
Jun 11 at 11:56
You should post that an an answer instead of a comment before your question gets closed...
– Fabby
Jun 21 at 20:46
1
1
That's interesting. I have disabled the "Execute Disable Bit" in the server BIOS and it works. Don't know if this is a permanent or temporary solution.
– m-dw
Jun 11 at 11:56
That's interesting. I have disabled the "Execute Disable Bit" in the server BIOS and it works. Don't know if this is a permanent or temporary solution.
– m-dw
Jun 11 at 11:56
You should post that an an answer instead of a comment before your question gets closed...
– Fabby
Jun 21 at 20:46
You should post that an an answer instead of a comment before your question gets closed...
– Fabby
Jun 21 at 20:46
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1045582%2fsudo-apt-update-terminate-called-after-throwing-an-instance-of-stdruntime-er%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
1
That's interesting. I have disabled the "Execute Disable Bit" in the server BIOS and it works. Don't know if this is a permanent or temporary solution.
– m-dw
Jun 11 at 11:56
You should post that an an answer instead of a comment before your question gets closed...
– Fabby
Jun 21 at 20:46