Apparmor was mentioned.
Some info:
http://en.wikipedia.org/wiki/AppArmorhttp://manpages.ubuntu.com/manpages/precise/en/man7/apparmor.7.htmlI'm unfamiliar with apparmor, but I think these suggestions might make sense:
If you have root access, try disable or remove apparmor entirely. If block and wallet-notifications now triggers correctly, this was the culprint, and you might decide to have it uninstalled, or you might decide to have it installed but alter it's configuration to suit your needs. From what I understand from the docs, it gives access permissions on application level, rather than user level.
As for how to complete these steps, it's an exercise for you. Good luck.
Thanks for your suggestion.
Apparmor's profiles are supposed to be in the following directory. A profile does not exist for bitcoind:
$ ls /etc/apparmor.d/
abstractions disable local tunables usr.sbin.ntpd usr.sbin.tcpdump
cache force-complain sbin.dhclient usr.sbin.mysqld usr.sbin.rsyslogd
Nevertheless, I tried stopping apparmor. As per
http://www.techytalk.info/disable-and-remove-apparmor-on-ubuntu-based-linux-distributions/ , I did the following:
$ sudo /etc/init.d/apparmor stop
* Clearing AppArmor profiles cache
...done.
All profile caches have been cleared, but no profiles have been unloaded.
Unloading profiles will leave already running processes permanently
unconfined, which can lead to unexpected situations.
To set a process to complain mode, use the command line tool
'aa-complain'. To really tear down all profiles, run the init script
with the 'teardown' option."
But it didn't seem to stop when I checked the status:
$ sudo /etc/init.d/apparmor status
apparmor module is loaded.
6 profiles are loaded.
6 profiles are in enforce mode.
/sbin/dhclient
/usr/lib/NetworkManager/nm-dhcp-client.action
/usr/lib/connman/scripts/dhclient-script
/usr/sbin/mysqld
/usr/sbin/ntpd
/usr/sbin/tcpdump
0 profiles are in complain mode.
2 processes have profiles defined.
2 processes are in enforce mode.
/usr/sbin/mysqld (837)
/usr/sbin/ntpd (1604)
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
So, as per
https://help.ubuntu.com/lts/serverguide/apparmor.html , I tried the following to stop AppArmor:
$ sudo service apparmor stop
* Clearing AppArmor profiles cache
...done.
All profile caches have been cleared, but no profiles have been unloaded.
Unloading profiles will leave already running processes permanently
unconfined, which can lead to unexpected situations.
To set a process to complain mode, use the command line tool
'aa-complain'. To really tear down all profiles, run the init script
with the 'teardown' option."
$ sudo update-rc.d -f apparmor remove
Removing any system startup links for /etc/init.d/apparmor ...
/etc/rcS.d/S37apparmor
When I checked apparmor status, I got the same as before.
I tried to set bitcoind to complain mode, but it didn't work:
$ sudo aa-complain /usr/local/bin/bitcoind
sudo: aa-complain: command not found
$
As per
https://help.ubuntu.com/community/AppArmor , I did the following to disable AppArmor:
$ sudo invoke-rc.d apparmor stop
[sudo] password for stockbet:
* Clearing AppArmor profiles cache
...done.
All profile caches have been cleared, but no profiles have been unloaded.
Unloading profiles will leave already running processes permanently
unconfined, which can lead to unexpected situations.
To set a process to complain mode, use the command line tool
'aa-complain'. To really tear down all profiles, run the init script
with the 'teardown' option."
$ sudo update-rc.d -f apparmor remove
Removing any system startup links for /etc/init.d/apparmor ...
When I checked apparmor status, I got the same as before.
I stopped and started bitcoind:
$ bitcoind stop
Bitcoin server stopping
$ bitcoind -daemon
Bitcoin server starting
$
…but I still got the runCommand error in .bitcoin/debug.log:
2015-03-15 01:18:12 runCommand error: system(/bin/true) returned -1
I have bitcoind 0.9.0. Do I need upgrade it? I read that version 0.10.0 causes frozen blocks.