This discussion looks similar:
http://stackoverflow.com/questions/5362512/unable-to-run-java-gui-programs-with-ubuntu
They suggest it is the specific version of Java being used.
Topic: MultiBit - page 50. (Read 336309 times)
That 'HeadlessException' at the bottom is caused by when MultiBit wants to create a graphical interface, ie a window, on a non graphical machine.
I get it on our integration machine which has no display if I try to create a window with content in it.
Do you have any MultiBit shortcuts generated in your menu and do they fail in the same way ?
I think (not sure) it might be related to having X windows installed/available or not.
I get it on our integration machine which has no display if I try to create a window with content in it.
Do you have any MultiBit shortcuts generated in your menu and do they fail in the same way ?
I think (not sure) it might be related to having X windows installed/available or not.
I'm getting serious errors and cannot run multibit.
I've installed it on this same machine in the past with Ubuntu 12.04 and it worked fine. But recently I gave my computer a fresh install of Ubuntu and cleaned things up. In my attempt to reinstall MultiBit I am having difficulties I never had before.
My first one came with needing to install java. No problem. I hadn't yet done that with my fresh install.
Here is everything that happened during my console installation. My apologies for not putting it in a scroll window. I just spent 10 minutes trying to figure out how to do that. I've never known. Somebody please tell me!
seth@oldbox:~/Downloads$ ls
multibit-0.4.12-linux.jar wireless_driver
seth@oldbox:~/Downloads$ chmod +x multibit-0.4.12-linux.jar
seth@oldbox:~/Downloads$ java -jar multibit-0.4.12-linux.jar
The program 'java' can be found in the following packages:
* default-jre
* gcj-4.6-jre-headless
* openjdk-6-jre-headless
* gcj-4.5-jre-headless
* openjdk-7-jre-headless
Try: sudo apt-get install
seth@oldbox:~/Downloads$ sudo apt-get install openjdk-7-jre-headless
[sudo] password for seth:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
linux-headers-3.2.0-29 linux-headers-3.2.0-29-generic-pae
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
ca-certificates-java icedtea-7-jre-jamvm java-common openjdk-7-jre-lib
tzdata-java
Suggested packages:
default-jre equivs sun-java6-fonts ttf-dejavu-extra fonts-ipafont-gothic
fonts-ipafont-mincho ttf-telugu-fonts ttf-oriya-fonts ttf-kannada-fonts
ttf-bengali-fonts
The following NEW packages will be installed:
ca-certificates-java icedtea-7-jre-jamvm java-common openjdk-7-jre-headless
openjdk-7-jre-lib tzdata-java
0 upgraded, 6 newly installed, 0 to remove and 1 not upgraded.
Need to get 44.1 MB of archives.
After this operation, 63.4 MB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get:1 http://us.archive.ubuntu.com/ubuntu/ precise-updates/universe openjdk-7-jre-lib all 7u7-2.3.2a-0ubuntu0.12.04.1 [5,536 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ precise/main ca-certificates-java all 20110912ubuntu6 [8,186 B]
Get:3 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main tzdata-java all 2012e-0ubuntu0.12.04.1 [140 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu/ precise/main java-common all 0.43ubuntu2 [61.7 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu/ precise-updates/universe openjdk-7-jre-headless i386 7u7-2.3.2a-0ubuntu0.12.04.1 [37.8 MB]
Get:6 http://us.archive.ubuntu.com/ubuntu/ precise-updates/universe icedtea-7-jre-jamvm i386 7u7-2.3.2a-0ubuntu0.12.04.1 [538 kB]
Fetched 44.1 MB in 2min 46s (265 kB/s)
Selecting previously unselected package openjdk-7-jre-lib.
(Reading database ... 170742 files and directories currently installed.)
Unpacking openjdk-7-jre-lib (from .../openjdk-7-jre-lib_7u7-2.3.2a-0ubuntu0.12.04.1_all.deb) ...
Selecting previously unselected package ca-certificates-java.
Unpacking ca-certificates-java (from .../ca-certificates-java_20110912ubuntu6_all.deb) ...
Selecting previously unselected package tzdata-java.
Unpacking tzdata-java (from .../tzdata-java_2012e-0ubuntu0.12.04.1_all.deb) ...
Selecting previously unselected package java-common.
Unpacking java-common (from .../java-common_0.43ubuntu2_all.deb) ...
Selecting previously unselected package openjdk-7-jre-headless.
Unpacking openjdk-7-jre-headless (from .../openjdk-7-jre-headless_7u7-2.3.2a-0ubuntu0.12.04.1_i386.deb) ...
Selecting previously unselected package icedtea-7-jre-jamvm.
Unpacking icedtea-7-jre-jamvm (from .../icedtea-7-jre-jamvm_7u7-2.3.2a-0ubuntu0.12.04.1_i386.deb) ...
Processing triggers for doc-base ...
Processing 2 added doc-base files...
Processing triggers for man-db ...
Setting up tzdata-java (2012e-0ubuntu0.12.04.1) ...
Setting up java-common (0.43ubuntu2) ...
Setting up openjdk-7-jre-headless (7u7-2.3.2a-0ubuntu0.12.04.1) ...
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/java to provide /usr/bin/java (java) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/keytool to provide /usr/bin/keytool (keytool) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/pack200 to provide /usr/bin/pack200 (pack200) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/rmid to provide /usr/bin/rmid (rmid) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/rmiregistry to provide /usr/bin/rmiregistry (rmiregistry) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/unpack200 to provide /usr/bin/unpack200 (unpack200) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/orbd to provide /usr/bin/orbd (orbd) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/servertool to provide /usr/bin/servertool (servertool) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/tnameserv to provide /usr/bin/tnameserv (tnameserv) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/lib/jexec to provide /usr/bin/jexec (jexec) in auto mode.
Setting up ca-certificates-java (20110912ubuntu6) ...
Adding debian:CNNIC_ROOT.pem
Adding debian:TC_TrustCenter__Germany__Class_3_CA.pem
Adding debian:GlobalSign_Root_CA.pem
Adding debian:Secure_Global_CA.pem
Adding debian:VeriSign_Universal_Root_Certification_Authority.pem
Adding debian:Entrust_Root_Certification_Authority.pem
Adding debian:Starfield_Root_Certificate_Authority_-_G2.pem
Adding debian:TURKTRUST_Certificate_Services_Provider_Root_2.pem
Adding debian:RSA_Security_2048_v3.pem
Adding debian:Certplus_Class_2_Primary_CA.pem
Adding debian:SwissSign_Gold_CA_-_G2.pem
Adding debian:QuoVadis_Root_CA_2.pem
Adding debian:TC_TrustCenter__Germany__Class_2_CA.pem
Adding debian:GlobalSign_Root_CA_-_R2.pem
Adding debian:Certinomis_-_Autorité_Racine.pem
Adding debian:TDC_Internet_Root_CA.pem
Adding debian:ssl-cert-snakeoil.pem
Adding debian:GeoTrust_Universal_CA.pem
Adding debian:Staat_der_Nederlanden_Root_CA.pem
Adding debian:COMODO_Certification_Authority.pem
Adding debian:Swisscom_Root_CA_1.pem
Adding debian:Izenpe.com.pem
Adding debian:thawte_Primary_Root_CA_-_G2.pem
Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G4.pem
Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority.pem
Adding debian:Comodo_Secure_Services_root.pem
Adding debian:America_Online_Root_Certification_Authority_1.pem
Adding debian:Taiwan_GRCA.pem
Adding debian:ValiCert_Class_2_VA.pem
Adding debian:NetLock_Arany_=Class_Gold=_Főtanúsítvány.pem
Adding debian:ACEDICOM_Root.pem
Adding debian:Camerfirma_Global_Chambersign_Root.pem
Adding debian:NetLock_Express_=Class_C=_Root.pem
Adding debian:Starfield_Services_Root_Certificate_Authority_-_G2.pem
Adding debian:Deutsche_Telekom_Root_CA_2.pem
Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
Adding debian:AffirmTrust_Networking.pem
Adding debian:TC_TrustCenter_Universal_CA_I.pem
Adding debian:DST_Root_CA_X3.pem
Adding debian:GeoTrust_Global_CA_2.pem
Adding debian:AddTrust_Public_Services_Root.pem
Adding debian:Digital_Signature_Trust_Co._Global_CA_1.pem
Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority_-_G2.pem
Adding debian:Staat_der_Nederlanden_Root_CA_-_G2.pem
Adding debian:Thawte_Premium_Server_CA.pem
Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem
Adding debian:AffirmTrust_Premium_ECC.pem
Adding debian:Sonera_Class_2_Root_CA.pem
Adding debian:NetLock_Business_=Class_B=_Root.pem
Adding debian:GeoTrust_Primary_Certification_Authority.pem
Adding debian:Buypass_Class_2_CA_1.pem
Adding debian:E-Guven_Kok_Elektronik_Sertifika_Hizmet_Saglayicisi.pem
Adding debian:Certum_Trusted_Network_CA.pem
Adding debian:TWCA_Root_Certification_Authority.pem
Adding debian:GeoTrust_Universal_CA_2.pem
Adding debian:Starfield_Class_2_CA.pem
Adding debian:UTN_USERFirst_Hardware_Root_CA.pem
Adding debian:DigiCert_Assured_ID_Root_CA.pem
Adding debian:Hongkong_Post_Root_CA_1.pem
Adding debian:Sonera_Class_1_Root_CA.pem
Adding debian:DigiCert_High_Assurance_EV_Root_CA.pem
Adding debian:COMODO_ECC_Certification_Authority.pem
Adding debian:UTN_DATACorp_SGC_Root_CA.pem
Adding debian:AffirmTrust_Commercial.pem
Adding debian:GeoTrust_Primary_Certification_Authority_-_G2.pem
Adding debian:WellsSecure_Public_Root_Certificate_Authority.pem
Adding debian:GTE_CyberTrust_Global_Root.pem
Adding debian:IGC_A.pem
Adding debian:DigiCert_Global_Root_CA.pem
Adding debian:Certigna.pem
Adding debian:Equifax_Secure_eBusiness_CA_1.pem
Adding debian:Go_Daddy_Class_2_CA.pem
Adding debian:A-Trust-nQual-03.pem
Adding debian:Comodo_Trusted_Services_root.pem
Adding debian:Network_Solutions_Certificate_Authority.pem
Adding debian:ca.pem
Adding debian:AddTrust_Qualified_Certificates_Root.pem
Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority.pem
Adding debian:CA_Disig.pem
Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority_-_G2.pem
Adding debian:Equifax_Secure_Global_eBusiness_CA.pem
Adding debian:Thawte_Server_CA.pem
Adding debian:NetLock_Qualified_=Class_QA=_Root.pem
Adding debian:TC_TrustCenter_Universal_CA_III.pem
Adding debian:Microsec_e-Szigno_Root_CA.pem
Adding debian:America_Online_Root_Certification_Authority_2.pem
Adding debian:Entrust.net_Premium_2048_Secure_Server_CA.pem
Adding debian:Cybertrust_Global_Root.pem
Adding debian:NetLock_Notary_=Class_A=_Root.pem
Adding debian:TC_TrustCenter_Class_2_CA_II.pem
Adding debian:Equifax_Secure_eBusiness_CA_2.pem
Adding debian:AC_Raíz_Certicámara_S.A..pem
Adding debian:TDC_OCES_Root_CA.pem
Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem
Adding debian:Entrust.net_Secure_Server_CA.pem
Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority.pem
Adding debian:Comodo_AAA_Services_root.pem
Adding debian:Equifax_Secure_CA.pem
Adding debian:UbuntuOne-Go_Daddy_Class_2_CA.pem
Adding debian:Verisign_Class_4_Public_Primary_Certification_Authority_-_G3.pem
Adding debian:Firmaprofesional_Root_CA.pem
Adding debian:Security_Communication_Root_CA.pem
Adding debian:AddTrust_External_Root.pem
Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority_-_G3.pem
Adding debian:Global_Chambersign_Root_-_2008.pem
Adding debian:cacert.org.pem
Adding debian:RSA_Root_Certificate_1.pem
Adding debian:Buypass_Class_3_CA_1.pem
Adding debian:Go_Daddy_Root_Certificate_Authority_-_G2.pem
Adding debian:thawte_Primary_Root_CA.pem
Adding debian:Wells_Fargo_Root_CA.pem
Adding debian:ValiCert_Class_1_VA.pem
Adding debian:StartCom_Certification_Authority.pem
Adding debian:Microsec_e-Szigno_Root_CA_2009.pem
Adding debian:EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem
Adding debian:Visa_eCommerce_Root.pem
Adding debian:Baltimore_CyberTrust_Root.pem
Adding debian:ePKI_Root_Certification_Authority.pem
Adding debian:UTN_USERFirst_Email_Root_CA.pem
Adding debian:TÜBİTAK_UEKAE_Kök_Sertifika_Hizmet_Sağlayıcısı_-_Sürüm_3.pem
Adding debian:ApplicationCA_-_Japanese_Government.pem
Adding debian:thawte_Primary_Root_CA_-_G3.pem
Adding debian:Digital_Signature_Trust_Co._Global_CA_3.pem
Adding debian:GeoTrust_Primary_Certification_Authority_-_G3.pem
Adding debian:S-TRUST_Authentication_and_Encryption_Root_CA_2005_PN.pem
Adding debian:TURKTRUST_Certificate_Services_Provider_Root_1.pem
Adding debian:spi-cacert-2008.pem
Adding debian:AffirmTrust_Premium.pem
Adding debian:Certum_Root_CA.pem
Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G3.pem
Adding debian:DST_ACES_CA_X6.pem
Adding debian:AddTrust_Low-Value_Services_Root.pem
Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.pem
Adding debian:SecureTrust_CA.pem
Adding debian:spi-ca-2003.pem
Adding debian:Chambers_of_Commerce_Root_-_2008.pem
Adding debian:SecureSign_RootCA11.pem
Adding debian:XRamp_Global_CA_Root.pem
Adding debian:GeoTrust_Global_CA.pem
Adding debian:Juur-SK.pem
Adding debian:OISTE_WISeKey_Global_Root_GA_CA.pem
Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G2.pem
Adding debian:QuoVadis_Root_CA_3.pem
Adding debian:Security_Communication_EV_RootCA1.pem
Adding debian:Root_CA_Generalitat_Valenciana.pem
Adding debian:SwissSign_Platinum_CA_-_G2.pem
Adding debian:certSIGN_ROOT_CA.pem
Adding debian:ComSign_Secured_CA.pem
Adding debian:TC_TrustCenter_Class_3_CA_II.pem
Adding debian:GlobalSign_Root_CA_-_R3.pem
Adding debian:Verisign_Class_4_Public_Primary_Certification_Authority_-_G2.pem
Adding debian:QuoVadis_Root_CA.pem
Adding debian:ComSign_CA.pem
Adding debian:UbuntuOne-Go_Daddy_CA.pem
Adding debian:SwissSign_Silver_CA_-_G2.pem
done.
Setting up icedtea-7-jre-jamvm (7u7-2.3.2a-0ubuntu0.12.04.1) ...
Setting up openjdk-7-jre-lib (7u7-2.3.2a-0ubuntu0.12.04.1) ...
seth@oldbox:~/Downloads$ java -jar multibit-0.4.12-linux.jar
Welcome to the installation of MultiBit 0.4.12!
The homepage is at: http://multibit.org/
press 1 to continue, 2 to quit, 3 to redisplay
1
Copyright (c) 2012 MultiBit Developers
Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom
the Software is furnished to do so, subject to the following
conditions:
The above copyright notice and this permission notice shall
be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE
OR OTHER DEALINGS IN THE SOFTWARE.
press 1 to accept, 2 to reject, 3 to redisplay
1
Select target path [/home/seth/Downloads]
press 1 to continue, 2 to quit, 3 to redisplay
1
[ Starting to unpack ]
[ Processing package: MultiBit (1/1) ]
[ Unpacking finished ]
Install was successful
application installed on /home/seth/Downloads
[ Console installation done ]
seth@oldbox:~/Downloads$ java -jar multibit-exe.jar
23:36:13.524 [main] INFO o.m.ApplicationDataDirectoryLocator - Application data directory.1 = '/home/seth/MultiBit'
23:36:13.553 [main] INFO o.m.ApplicationDataDirectoryLocator - Application data directory.1 - Log files are '/home/seth/MultiBit/multibit_console.log' and '/home/seth/MultiBit/multibit_debug.log'.
seth@oldbox:~/Downloads$ cd /home/seth/MultiBit
seth@oldbox:~/MultiBit$ java -jar multibit-exe.jar
Error: Unable to access jarfile multibit-exe.jar
seth@oldbox:~/MultiBit$ cd /home/seth/Downloads
seth@oldbox:~/Downloads$ java -jar multibit-exe.jar
23:40:26.624 [main] INFO o.m.ApplicationDataDirectoryLocator - Application data directory.1 = '/home/seth/MultiBit'
23:40:26.668 [main] INFO o.m.ApplicationDataDirectoryLocator - Application data directory.1 - Log files are '/home/seth/MultiBit/multibit_console.log' and '/home/seth/MultiBit/multibit_debug.log'.
seth@oldbox:~/Downloads$ less /home/seth/MultiBit/multibit_debug.log
/home/seth/MultiBit/multibit_debug.log: No such file or directory
seth@oldbox:~/Downloads$ cd /home/seth/MultiBit
seth@oldbox:~/MultiBit$ ls
log multibit.properties
seth@oldbox:~/MultiBit$ cd ./log
seth@oldbox:~/MultiBit/log$ ls
multibit_console.log multibit_debug.log
seth@oldbox:~/MultiBit/log$ less multibit_debug.log
seth@oldbox:~/MultiBit/log$
And here is the tail end of my debug log:
23:40:26.788 [main] DEBUG o.m.ApplicationInstanceManager - Listening for application instances on socket 8331
23:40:26.790 [main] DEBUG org.multibit.MultiBit - userLanguageCode = en
23:40:26.797 [main] DEBUG org.multibit.MultiBit - Creating model
23:40:26.829 [main] DEBUG org.multibit.model.MultiBitModel - Initial view from properties file is '17'
23:40:26.830 [main] DEBUG org.multibit.MultiBit - Setting look and feel
23:40:27.237 [main] DEBUG org.multibit.MultiBit - Creating views
23:40:27.374 [main] ERROR org.multibit.MultiBit - An unexpected error caused MultiBit to quit.
23:40:27.375 [main] ERROR org.multibit.MultiBit - The error was 'java.awt.HeadlessException null'
23:40:27.375 [main] ERROR org.multibit.MultiBit - Please read http://multibit.org/help_troubleshooting.html for help on troubleshooting.
23:40:27.441 [main] DEBUG o.m.v.swing.action.ExitAction - Saving user preferences ...
23:40:27.441 [main] DEBUG org.multibit.file.FileHandler - When writing wallets, there were 0
23:40:27.470 [main] DEBUG o.m.v.swing.action.ExitAction - Shutting down Bitcoin URI checker ...
23:40:27.471 [main] DEBUG o.m.ApplicationInstanceManager - Making request to shut down socket ...
I've installed it on this same machine in the past with Ubuntu 12.04 and it worked fine. But recently I gave my computer a fresh install of Ubuntu and cleaned things up. In my attempt to reinstall MultiBit I am having difficulties I never had before.
My first one came with needing to install java. No problem. I hadn't yet done that with my fresh install.
Here is everything that happened during my console installation. My apologies for not putting it in a scroll window. I just spent 10 minutes trying to figure out how to do that. I've never known. Somebody please tell me!
seth@oldbox:~/Downloads$ ls
multibit-0.4.12-linux.jar wireless_driver
seth@oldbox:~/Downloads$ chmod +x multibit-0.4.12-linux.jar
seth@oldbox:~/Downloads$ java -jar multibit-0.4.12-linux.jar
The program 'java' can be found in the following packages:
* default-jre
* gcj-4.6-jre-headless
* openjdk-6-jre-headless
* gcj-4.5-jre-headless
* openjdk-7-jre-headless
Try: sudo apt-get install
seth@oldbox:~/Downloads$ sudo apt-get install openjdk-7-jre-headless
[sudo] password for seth:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
linux-headers-3.2.0-29 linux-headers-3.2.0-29-generic-pae
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
ca-certificates-java icedtea-7-jre-jamvm java-common openjdk-7-jre-lib
tzdata-java
Suggested packages:
default-jre equivs sun-java6-fonts ttf-dejavu-extra fonts-ipafont-gothic
fonts-ipafont-mincho ttf-telugu-fonts ttf-oriya-fonts ttf-kannada-fonts
ttf-bengali-fonts
The following NEW packages will be installed:
ca-certificates-java icedtea-7-jre-jamvm java-common openjdk-7-jre-headless
openjdk-7-jre-lib tzdata-java
0 upgraded, 6 newly installed, 0 to remove and 1 not upgraded.
Need to get 44.1 MB of archives.
After this operation, 63.4 MB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get:1 http://us.archive.ubuntu.com/ubuntu/ precise-updates/universe openjdk-7-jre-lib all 7u7-2.3.2a-0ubuntu0.12.04.1 [5,536 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ precise/main ca-certificates-java all 20110912ubuntu6 [8,186 B]
Get:3 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main tzdata-java all 2012e-0ubuntu0.12.04.1 [140 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu/ precise/main java-common all 0.43ubuntu2 [61.7 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu/ precise-updates/universe openjdk-7-jre-headless i386 7u7-2.3.2a-0ubuntu0.12.04.1 [37.8 MB]
Get:6 http://us.archive.ubuntu.com/ubuntu/ precise-updates/universe icedtea-7-jre-jamvm i386 7u7-2.3.2a-0ubuntu0.12.04.1 [538 kB]
Fetched 44.1 MB in 2min 46s (265 kB/s)
Selecting previously unselected package openjdk-7-jre-lib.
(Reading database ... 170742 files and directories currently installed.)
Unpacking openjdk-7-jre-lib (from .../openjdk-7-jre-lib_7u7-2.3.2a-0ubuntu0.12.04.1_all.deb) ...
Selecting previously unselected package ca-certificates-java.
Unpacking ca-certificates-java (from .../ca-certificates-java_20110912ubuntu6_all.deb) ...
Selecting previously unselected package tzdata-java.
Unpacking tzdata-java (from .../tzdata-java_2012e-0ubuntu0.12.04.1_all.deb) ...
Selecting previously unselected package java-common.
Unpacking java-common (from .../java-common_0.43ubuntu2_all.deb) ...
Selecting previously unselected package openjdk-7-jre-headless.
Unpacking openjdk-7-jre-headless (from .../openjdk-7-jre-headless_7u7-2.3.2a-0ubuntu0.12.04.1_i386.deb) ...
Selecting previously unselected package icedtea-7-jre-jamvm.
Unpacking icedtea-7-jre-jamvm (from .../icedtea-7-jre-jamvm_7u7-2.3.2a-0ubuntu0.12.04.1_i386.deb) ...
Processing triggers for doc-base ...
Processing 2 added doc-base files...
Processing triggers for man-db ...
Setting up tzdata-java (2012e-0ubuntu0.12.04.1) ...
Setting up java-common (0.43ubuntu2) ...
Setting up openjdk-7-jre-headless (7u7-2.3.2a-0ubuntu0.12.04.1) ...
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/java to provide /usr/bin/java (java) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/keytool to provide /usr/bin/keytool (keytool) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/pack200 to provide /usr/bin/pack200 (pack200) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/rmid to provide /usr/bin/rmid (rmid) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/rmiregistry to provide /usr/bin/rmiregistry (rmiregistry) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/unpack200 to provide /usr/bin/unpack200 (unpack200) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/orbd to provide /usr/bin/orbd (orbd) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/servertool to provide /usr/bin/servertool (servertool) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/bin/tnameserv to provide /usr/bin/tnameserv (tnameserv) in auto mode.
update-alternatives: using /usr/lib/jvm/java-7-openjdk-i386/jre/lib/jexec to provide /usr/bin/jexec (jexec) in auto mode.
Setting up ca-certificates-java (20110912ubuntu6) ...
Adding debian:CNNIC_ROOT.pem
Adding debian:TC_TrustCenter__Germany__Class_3_CA.pem
Adding debian:GlobalSign_Root_CA.pem
Adding debian:Secure_Global_CA.pem
Adding debian:VeriSign_Universal_Root_Certification_Authority.pem
Adding debian:Entrust_Root_Certification_Authority.pem
Adding debian:Starfield_Root_Certificate_Authority_-_G2.pem
Adding debian:TURKTRUST_Certificate_Services_Provider_Root_2.pem
Adding debian:RSA_Security_2048_v3.pem
Adding debian:Certplus_Class_2_Primary_CA.pem
Adding debian:SwissSign_Gold_CA_-_G2.pem
Adding debian:QuoVadis_Root_CA_2.pem
Adding debian:TC_TrustCenter__Germany__Class_2_CA.pem
Adding debian:GlobalSign_Root_CA_-_R2.pem
Adding debian:Certinomis_-_Autorité_Racine.pem
Adding debian:TDC_Internet_Root_CA.pem
Adding debian:ssl-cert-snakeoil.pem
Adding debian:GeoTrust_Universal_CA.pem
Adding debian:Staat_der_Nederlanden_Root_CA.pem
Adding debian:COMODO_Certification_Authority.pem
Adding debian:Swisscom_Root_CA_1.pem
Adding debian:Izenpe.com.pem
Adding debian:thawte_Primary_Root_CA_-_G2.pem
Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G4.pem
Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority.pem
Adding debian:Comodo_Secure_Services_root.pem
Adding debian:America_Online_Root_Certification_Authority_1.pem
Adding debian:Taiwan_GRCA.pem
Adding debian:ValiCert_Class_2_VA.pem
Adding debian:NetLock_Arany_=Class_Gold=_Főtanúsítvány.pem
Adding debian:ACEDICOM_Root.pem
Adding debian:Camerfirma_Global_Chambersign_Root.pem
Adding debian:NetLock_Express_=Class_C=_Root.pem
Adding debian:Starfield_Services_Root_Certificate_Authority_-_G2.pem
Adding debian:Deutsche_Telekom_Root_CA_2.pem
Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
Adding debian:AffirmTrust_Networking.pem
Adding debian:TC_TrustCenter_Universal_CA_I.pem
Adding debian:DST_Root_CA_X3.pem
Adding debian:GeoTrust_Global_CA_2.pem
Adding debian:AddTrust_Public_Services_Root.pem
Adding debian:Digital_Signature_Trust_Co._Global_CA_1.pem
Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority_-_G2.pem
Adding debian:Staat_der_Nederlanden_Root_CA_-_G2.pem
Adding debian:Thawte_Premium_Server_CA.pem
Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem
Adding debian:AffirmTrust_Premium_ECC.pem
Adding debian:Sonera_Class_2_Root_CA.pem
Adding debian:NetLock_Business_=Class_B=_Root.pem
Adding debian:GeoTrust_Primary_Certification_Authority.pem
Adding debian:Buypass_Class_2_CA_1.pem
Adding debian:E-Guven_Kok_Elektronik_Sertifika_Hizmet_Saglayicisi.pem
Adding debian:Certum_Trusted_Network_CA.pem
Adding debian:TWCA_Root_Certification_Authority.pem
Adding debian:GeoTrust_Universal_CA_2.pem
Adding debian:Starfield_Class_2_CA.pem
Adding debian:UTN_USERFirst_Hardware_Root_CA.pem
Adding debian:DigiCert_Assured_ID_Root_CA.pem
Adding debian:Hongkong_Post_Root_CA_1.pem
Adding debian:Sonera_Class_1_Root_CA.pem
Adding debian:DigiCert_High_Assurance_EV_Root_CA.pem
Adding debian:COMODO_ECC_Certification_Authority.pem
Adding debian:UTN_DATACorp_SGC_Root_CA.pem
Adding debian:AffirmTrust_Commercial.pem
Adding debian:GeoTrust_Primary_Certification_Authority_-_G2.pem
Adding debian:WellsSecure_Public_Root_Certificate_Authority.pem
Adding debian:GTE_CyberTrust_Global_Root.pem
Adding debian:IGC_A.pem
Adding debian:DigiCert_Global_Root_CA.pem
Adding debian:Certigna.pem
Adding debian:Equifax_Secure_eBusiness_CA_1.pem
Adding debian:Go_Daddy_Class_2_CA.pem
Adding debian:A-Trust-nQual-03.pem
Adding debian:Comodo_Trusted_Services_root.pem
Adding debian:Network_Solutions_Certificate_Authority.pem
Adding debian:ca.pem
Adding debian:AddTrust_Qualified_Certificates_Root.pem
Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority.pem
Adding debian:CA_Disig.pem
Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority_-_G2.pem
Adding debian:Equifax_Secure_Global_eBusiness_CA.pem
Adding debian:Thawte_Server_CA.pem
Adding debian:NetLock_Qualified_=Class_QA=_Root.pem
Adding debian:TC_TrustCenter_Universal_CA_III.pem
Adding debian:Microsec_e-Szigno_Root_CA.pem
Adding debian:America_Online_Root_Certification_Authority_2.pem
Adding debian:Entrust.net_Premium_2048_Secure_Server_CA.pem
Adding debian:Cybertrust_Global_Root.pem
Adding debian:NetLock_Notary_=Class_A=_Root.pem
Adding debian:TC_TrustCenter_Class_2_CA_II.pem
Adding debian:Equifax_Secure_eBusiness_CA_2.pem
Adding debian:AC_Raíz_Certicámara_S.A..pem
Adding debian:TDC_OCES_Root_CA.pem
Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem
Adding debian:Entrust.net_Secure_Server_CA.pem
Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority.pem
Adding debian:Comodo_AAA_Services_root.pem
Adding debian:Equifax_Secure_CA.pem
Adding debian:UbuntuOne-Go_Daddy_Class_2_CA.pem
Adding debian:Verisign_Class_4_Public_Primary_Certification_Authority_-_G3.pem
Adding debian:Firmaprofesional_Root_CA.pem
Adding debian:Security_Communication_Root_CA.pem
Adding debian:AddTrust_External_Root.pem
Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority_-_G3.pem
Adding debian:Global_Chambersign_Root_-_2008.pem
Adding debian:cacert.org.pem
Adding debian:RSA_Root_Certificate_1.pem
Adding debian:Buypass_Class_3_CA_1.pem
Adding debian:Go_Daddy_Root_Certificate_Authority_-_G2.pem
Adding debian:thawte_Primary_Root_CA.pem
Adding debian:Wells_Fargo_Root_CA.pem
Adding debian:ValiCert_Class_1_VA.pem
Adding debian:StartCom_Certification_Authority.pem
Adding debian:Microsec_e-Szigno_Root_CA_2009.pem
Adding debian:EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem
Adding debian:Visa_eCommerce_Root.pem
Adding debian:Baltimore_CyberTrust_Root.pem
Adding debian:ePKI_Root_Certification_Authority.pem
Adding debian:UTN_USERFirst_Email_Root_CA.pem
Adding debian:TÜBİTAK_UEKAE_Kök_Sertifika_Hizmet_Sağlayıcısı_-_Sürüm_3.pem
Adding debian:ApplicationCA_-_Japanese_Government.pem
Adding debian:thawte_Primary_Root_CA_-_G3.pem
Adding debian:Digital_Signature_Trust_Co._Global_CA_3.pem
Adding debian:GeoTrust_Primary_Certification_Authority_-_G3.pem
Adding debian:S-TRUST_Authentication_and_Encryption_Root_CA_2005_PN.pem
Adding debian:TURKTRUST_Certificate_Services_Provider_Root_1.pem
Adding debian:spi-cacert-2008.pem
Adding debian:AffirmTrust_Premium.pem
Adding debian:Certum_Root_CA.pem
Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G3.pem
Adding debian:DST_ACES_CA_X6.pem
Adding debian:AddTrust_Low-Value_Services_Root.pem
Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.pem
Adding debian:SecureTrust_CA.pem
Adding debian:spi-ca-2003.pem
Adding debian:Chambers_of_Commerce_Root_-_2008.pem
Adding debian:SecureSign_RootCA11.pem
Adding debian:XRamp_Global_CA_Root.pem
Adding debian:GeoTrust_Global_CA.pem
Adding debian:Juur-SK.pem
Adding debian:OISTE_WISeKey_Global_Root_GA_CA.pem
Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G2.pem
Adding debian:QuoVadis_Root_CA_3.pem
Adding debian:Security_Communication_EV_RootCA1.pem
Adding debian:Root_CA_Generalitat_Valenciana.pem
Adding debian:SwissSign_Platinum_CA_-_G2.pem
Adding debian:certSIGN_ROOT_CA.pem
Adding debian:ComSign_Secured_CA.pem
Adding debian:TC_TrustCenter_Class_3_CA_II.pem
Adding debian:GlobalSign_Root_CA_-_R3.pem
Adding debian:Verisign_Class_4_Public_Primary_Certification_Authority_-_G2.pem
Adding debian:QuoVadis_Root_CA.pem
Adding debian:ComSign_CA.pem
Adding debian:UbuntuOne-Go_Daddy_CA.pem
Adding debian:SwissSign_Silver_CA_-_G2.pem
done.
Setting up icedtea-7-jre-jamvm (7u7-2.3.2a-0ubuntu0.12.04.1) ...
Setting up openjdk-7-jre-lib (7u7-2.3.2a-0ubuntu0.12.04.1) ...
seth@oldbox:~/Downloads$ java -jar multibit-0.4.12-linux.jar
Welcome to the installation of MultiBit 0.4.12!
The homepage is at: http://multibit.org/
press 1 to continue, 2 to quit, 3 to redisplay
1
Copyright (c) 2012 MultiBit Developers
Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom
the Software is furnished to do so, subject to the following
conditions:
The above copyright notice and this permission notice shall
be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE
OR OTHER DEALINGS IN THE SOFTWARE.
press 1 to accept, 2 to reject, 3 to redisplay
1
Select target path [/home/seth/Downloads]
press 1 to continue, 2 to quit, 3 to redisplay
1
[ Starting to unpack ]
[ Processing package: MultiBit (1/1) ]
[ Unpacking finished ]
Install was successful
application installed on /home/seth/Downloads
[ Console installation done ]
seth@oldbox:~/Downloads$ java -jar multibit-exe.jar
23:36:13.524 [main] INFO o.m.ApplicationDataDirectoryLocator - Application data directory.1 = '/home/seth/MultiBit'
23:36:13.553 [main] INFO o.m.ApplicationDataDirectoryLocator - Application data directory.1 - Log files are '/home/seth/MultiBit/multibit_console.log' and '/home/seth/MultiBit/multibit_debug.log'.
seth@oldbox:~/Downloads$ cd /home/seth/MultiBit
seth@oldbox:~/MultiBit$ java -jar multibit-exe.jar
Error: Unable to access jarfile multibit-exe.jar
seth@oldbox:~/MultiBit$ cd /home/seth/Downloads
seth@oldbox:~/Downloads$ java -jar multibit-exe.jar
23:40:26.624 [main] INFO o.m.ApplicationDataDirectoryLocator - Application data directory.1 = '/home/seth/MultiBit'
23:40:26.668 [main] INFO o.m.ApplicationDataDirectoryLocator - Application data directory.1 - Log files are '/home/seth/MultiBit/multibit_console.log' and '/home/seth/MultiBit/multibit_debug.log'.
seth@oldbox:~/Downloads$ less /home/seth/MultiBit/multibit_debug.log
/home/seth/MultiBit/multibit_debug.log: No such file or directory
seth@oldbox:~/Downloads$ cd /home/seth/MultiBit
seth@oldbox:~/MultiBit$ ls
log multibit.properties
seth@oldbox:~/MultiBit$ cd ./log
seth@oldbox:~/MultiBit/log$ ls
multibit_console.log multibit_debug.log
seth@oldbox:~/MultiBit/log$ less multibit_debug.log
seth@oldbox:~/MultiBit/log$
And here is the tail end of my debug log:
23:40:26.788 [main] DEBUG o.m.ApplicationInstanceManager - Listening for application instances on socket 8331
23:40:26.790 [main] DEBUG org.multibit.MultiBit - userLanguageCode = en
23:40:26.797 [main] DEBUG org.multibit.MultiBit - Creating model
23:40:26.829 [main] DEBUG org.multibit.model.MultiBitModel - Initial view from properties file is '17'
23:40:26.830 [main] DEBUG org.multibit.MultiBit - Setting look and feel
23:40:27.237 [main] DEBUG org.multibit.MultiBit - Creating views
23:40:27.374 [main] ERROR org.multibit.MultiBit - An unexpected error caused MultiBit to quit.
23:40:27.375 [main] ERROR org.multibit.MultiBit - The error was 'java.awt.HeadlessException null'
23:40:27.375 [main] ERROR org.multibit.MultiBit - Please read http://multibit.org/help_troubleshooting.html for help on troubleshooting.
23:40:27.441 [main] DEBUG o.m.v.swing.action.ExitAction - Saving user preferences ...
23:40:27.441 [main] DEBUG org.multibit.file.FileHandler - When writing wallets, there were 0
23:40:27.470 [main] DEBUG o.m.v.swing.action.ExitAction - Shutting down Bitcoin URI checker ...
23:40:27.471 [main] DEBUG o.m.ApplicationInstanceManager - Making request to shut down socket ...
Hi damnek,
Thanks for your feedback.
Yes I must admit my Satoshi client is never up to date now - hopefully the work Pieter+Mike are doing will improve things.
Re: your suggestions:
Scrolling -I don't know if there is much I can do as that would be in the hardware/OS code but I will have a look.
Using googlefu I have set what I believe is the right setting to adjust the mouse scroll speed. (As I have a trackpad I cannot tell so let me know after the next release if it fixes it).
QR code on by default. Yes I will change this I think otherwise people miss the functionality.
Graphs - this bug is fixed so they should appear properly in the next release.
If you start storing non-trivial amounts on MultiBit please, please, please make sure you backup your private keys and/ or wallets. (I normally export the private keys to an encrypted file and then copy all of the wallet/info/key files onto a couple of USB drives. The private keys are the crucial information).
Thanks for your feedback.
Yes I must admit my Satoshi client is never up to date now - hopefully the work Pieter+Mike are doing will improve things.
Re: your suggestions:
Scrolling -
Using googlefu I have set what I believe is the right setting to adjust the mouse scroll speed. (As I have a trackpad I cannot tell so let me know after the next release if it fixes it).
QR code on by default. Yes I will change this I think otherwise people miss the functionality.
Graphs - this bug is fixed so they should appear properly in the next release.
If you start storing non-trivial amounts on MultiBit please, please, please make sure you backup your private keys and/ or wallets. (I normally export the private keys to an encrypted file and then copy all of the wallet/info/key files onto a couple of USB drives. The private keys are the crucial information).
Hi Jim,
I'm considering using multibit as my main bitcoin client now, as the satoshi client is simply becoming too slow for me.
I have two small suggestions:
- scrolling up and down using my mouse wheel in the settings panel goes very slow
- show the QR codes by default and allow the user to hide them (I didn't understand the green + and there is enough room anyway)
Also, the graphs don't work on my computer. The menu becomes a bit unresponsive when I click on the option.
Thanks for all your work on mutltibit!
I'm considering using multibit as my main bitcoin client now, as the satoshi client is simply becoming too slow for me.
I have two small suggestions:
- scrolling up and down using my mouse wheel in the settings panel goes very slow
- show the QR codes by default and allow the user to hide them (I didn't understand the green + and there is enough room anyway)
Also, the graphs don't work on my computer. The menu becomes a bit unresponsive when I click on the option.
Thanks for all your work on mutltibit!
Whilst working on the 'Send Confirm' dialog, I have tweaked it so that the 'Send' button is only enabled once MultiBit has a connected peer.
Screenshot:
When the first peer connects the button is enabled and the text disappears.
Previously MultiBit would queue the send of the transaction until a peer appeared, but this creates a bit of "Send Anxiety". If you are not online it looks like it sent it but actually it is queued for send.
It seemed clearer just to wait until there was definitely a connection available.
Screenshot:
When the first peer connects the button is enabled and the text disappears.
Previously MultiBit would queue the send of the transaction until a peer appeared, but this creates a bit of "Send Anxiety". If you are not online it looks like it sent it but actually it is queued for send.
It seemed clearer just to wait until there was definitely a connection available.
I have added the peer propagation icon (and some descriptive text) onto the 'Send Confirm Dialog' as follows:
When you do a send, MultiBit sends the transaction to one peer, and then listens on all the other peers it is connected to for it to be transmitted back (as the transaction propagates through the network). The icon and text change as more peers see it.
When you do a send, MultiBit sends the transaction to one peer, and then listens on all the other peers it is connected to for it to be transmitted back (as the transaction propagates through the network). The icon and text change as more peers see it.
Playing around with MultiBit tonight I spotted a bug in the 'Charts' page.
The chart and tab headers go blank, here is a screen shot:
http://multibit.org/postImages/xchart.png
I do have a stack trace of the error so have asked Tim Molter (the XChart library author) to have a look.
If you click on one of the other tab headings the screen goes back to normal so it is recoverable.
I didn't see it at all in testing this morning so I don't know exactly what the cause of it is yet.
edit: This is caused by the vertically rotated text for the Y axis heading. I have removed it and the charts appear ok.
The chart and tab headers go blank, here is a screen shot:
http://multibit.org/postImages/xchart.png
I do have a stack trace of the error so have asked Tim Molter (the XChart library author) to have a look.
If you click on one of the other tab headings the screen goes back to normal so it is recoverable.
I didn't see it at all in testing this morning so I don't know exactly what the cause of it is yet.
edit: This is caused by the vertically rotated text for the Y axis heading. I have removed it and the charts appear ok.
Hi ErebusBat,
Good to know that you found the root cause. As a side effect there is more logging in MultiBit now for the peer connections so that may very help someone else in the future.
It is quite interesting it being your firewall actually. Because bitcoind aren't authenticated if an attacker controls your network neighbourhood (eg imagine your firewall was malicious) it can completely mess you around.
If anyone has any ideas on detecting this I would be interested to hear them. I can't think of a simple way to tell if I have been sandboxed by an attacker.
At this point it would appear to be only a DOS attack. I guess they could do a MITM attack and keep block from you or feed you 'bad' blocks, but I think that is only a more advanced DOS attack.Good to know that you found the root cause. As a side effect there is more logging in MultiBit now for the peer connections so that may very help someone else in the future.
It is quite interesting it being your firewall actually. Because bitcoind aren't authenticated if an attacker controls your network neighbourhood (eg imagine your firewall was malicious) it can completely mess you around.
If anyone has any ideas on detecting this I would be interested to hear them. I can't think of a simple way to tell if I have been sandboxed by an attacker.
To clarify the problem:
My Laptop: 192.168.1.70
(Old Server): 192.168.1.182
There was a dstnat rule on my router to forward incoming requests on port 8333 to 192.168.1.182. This server has since been moved and off this network.
So I think what is/was happening is I attempted to make a connection to a node which tried to connect back and the connection was accepted by my FW then forwarded into a blackhole. However this is pure speculation because my knowledge of how the NAT detection code in bitcoind works is non-existant.
I would speculate that this works at my house because the other bitcoind accepting the incoming requests is most likely detected (probably by some sort of ID echo) which also triggers the NAT code.
Hi ErebusBat,
Good to know that you found the root cause. As a side effect there is more logging in MultiBit now for the peer connections so that may very help someone else in the future.
It is quite interesting it being your firewall actually. Because bitcoind aren't authenticated if an attacker controls your network neighbourhood (eg imagine your firewall was malicious) it can completely mess you around.
If anyone has any ideas on detecting this I would be interested to hear them. I can't think of a simple way to tell if I have been sandboxed by an attacker.
Good to know that you found the root cause. As a side effect there is more logging in MultiBit now for the peer connections so that may very help someone else in the future.
It is quite interesting it being your firewall actually. Because bitcoind aren't authenticated if an attacker controls your network neighbourhood (eg imagine your firewall was malicious) it can completely mess you around.
If anyone has any ideas on detecting this I would be interested to hear them. I can't think of a simple way to tell if I have been sandboxed by an attacker.
It is a possible workaround rather than a fix but you could try connecting to a specific node.
MultiBit will then not do any peer discovery but just connect to the single node specified.
In you multibit.properties add:
singleNodeConnection=12.34.56.78
Where 12.34.56.78 is the IP address of your favourite Satoshi node.
The singleNodeConnection is case sensitive.
Someone requested it for connecting to their local Satoshi client on their local network but you should be able to connect to anywhere.
I am glad to know this as I keep a fully synced node on my network for this purpose anyway.MultiBit will then not do any peer discovery but just connect to the single node specified.
In you multibit.properties add:
singleNodeConnection=12.34.56.78
Where 12.34.56.78 is the IP address of your favourite Satoshi node.
The singleNodeConnection is case sensitive.
Someone requested it for connecting to their local Satoshi client on their local network but you should be able to connect to anywhere.
HOWEVER... I still get no connection, and attempting to get bitcoind to add it as a node fails as well... this is very very strange as I don't have anything blocking the connection (that I am aware of).
It is obviously an issue on my end, I will take my laptop home tonight and see what it does there.
Jim (& Others):
Found the issue... I had an old firewall rule to forward port 8333 to a server I had setup to run bitcoind. This forward was NOT my internal IP. As soon as I disabled it then BAM MultiBit would connect on startup.
However very oddly at my home where I also have the same rule (although it goes to an active server) it did connect without incident.
Anyway if anyone else complains you may want to have them check for old/invalid firewall rules.
There is a new live release of MultiBit at:
multibit.org
Version 0.4.12
Enhancements:
+ Farsi/ Persian translation 100%
+ "Online/ Connecting..." tooltip now also shows date of last block and number of connected peers.
+ Transaction icon visualises propagation of transaction across peers.
+ Various code hardening/ extra logging.
Scan of release checklist
multibit.org
Version 0.4.12
Enhancements:
+ Farsi/ Persian translation 100%
+ "Online/ Connecting..." tooltip now also shows date of last block and number of connected peers.
+ Transaction icon visualises propagation of transaction across peers.
+ Various code hardening/ extra logging.
Scan of release checklist
I have put some more network information on the tooltip for the 'Online/Connecting..." indicator:
edit: there are also more details in the log file about exactly which peers are being connected to and if it is successful or not (to try to pin down ErebusBat's connectivity problem).
edit: there are also more details in the log file about exactly which peers are being connected to and if it is successful or not (to try to pin down ErebusBat's connectivity problem).
In the latest version of bitcoinj (V0.6) is the ability to track the 'transaction confidence'.
One of the measures available is the number of peers that have seen the transaction.
MultiBit typically connects to four peers. If all four have seen the transaction it has most probably propagated out across the network. If only one has seen it then you cannot be too sure of its provenance.
I have added the ability to visualise the confidence of a transaction by updating the icon in the 'Status' field in the 'Transactions' tab.
Have a look at the screenshot:
The mantra I am using is:
Spikey is dicey. More round is more sound.
The screen updates as the transactions get seen by more peers in real time.
It is a bit of an experiment in visualising this information so am interested in feedback if you think it is useful or not.
The tooltip for the transaction also gives the number of peers e.g.:
This transaction is not yet confirmed
Seen by 3 peers.
It will go in the next live release.
One of the measures available is the number of peers that have seen the transaction.
MultiBit typically connects to four peers. If all four have seen the transaction it has most probably propagated out across the network. If only one has seen it then you cannot be too sure of its provenance.
I have added the ability to visualise the confidence of a transaction by updating the icon in the 'Status' field in the 'Transactions' tab.
Have a look at the screenshot:
The mantra I am using is:
Spikey is dicey. More round is more sound.
The screen updates as the transactions get seen by more peers in real time.
It is a bit of an experiment in visualising this information so am interested in feedback if you think it is useful or not.
The tooltip for the transaction also gives the number of peers e.g.:
This transaction is not yet confirmed
Seen by 3 peers.
It will go in the next live release.
While I use this client from time to time, the biggest issue I have with it is that it sometimes doesn't let me send my money, and I have to reset the blockchain and it just dies on me.
This is all good feedback Mushroomized. Is the 'it sometimes doesn't let me send my money" the thing about unconfirmed change ? If so, then yeah we have a plan for that. If it is something else please give some more detail.
The 'it just dies on me' I would like to know more about. What platform are you running on ? I have seen that very occasionally on the Linux VM I use for testing. It is a difficult one to get to the bottom of so any information you have would be useful.
Although I have had it crash a few times on linux mint 64 bit. It is a possible workaround rather than a fix but you could try connecting to a specific node.
MultiBit will then not do any peer discovery but just connect to the single node specified.
In you multibit.properties add:
singleNodeConnection=12.34.56.78
Where 12.34.56.78 is the IP address of your favourite Satoshi node.
The singleNodeConnection is case sensitive.
Someone requested it for connecting to their local Satoshi client on their local network but you should be able to connect to anywhere.
I am glad to know this as I keep a fully synced node on my network for this purpose anyway.MultiBit will then not do any peer discovery but just connect to the single node specified.
In you multibit.properties add:
singleNodeConnection=12.34.56.78
Where 12.34.56.78 is the IP address of your favourite Satoshi node.
The singleNodeConnection is case sensitive.
Someone requested it for connecting to their local Satoshi client on their local network but you should be able to connect to anywhere.
HOWEVER... I still get no connection, and attempting to get bitcoind to add it as a node fails as well... this is very very strange as I don't have anything blocking the connection (that I am aware of).
It is obviously an issue on my end, I will take my laptop home tonight and see what it does there.
It is a possible workaround rather than a fix but you could try connecting to a specific node.
MultiBit will then not do any peer discovery but just connect to the single node specified.
In you multibit.properties add:
singleNodeConnection=12.34.56.78
Where 12.34.56.78 is the IP address of your favourite Satoshi node.
The singleNodeConnection is case sensitive.
Someone requested it for connecting to their local Satoshi client on their local network but you should be able to connect to anywhere.
MultiBit will then not do any peer discovery but just connect to the single node specified.
In you multibit.properties add:
singleNodeConnection=12.34.56.78
Where 12.34.56.78 is the IP address of your favourite Satoshi node.
The singleNodeConnection is case sensitive.
Someone requested it for connecting to their local Satoshi client on their local network but you should be able to connect to anywhere.
I notice in that log that the HTTP gets that the currency ticker does are also failing.
This can be if the MtGox server is busy (it just drops requests) but it can obviously also be caused by network problems.
Also in the log the number of peers it finds is always 14. Normally in the two seconds it spends looking up network peers I get 80+ and the number varies. My network is a laggy 3G connection.
Can you describe what your network setup is please ?
Fairly standard corporate connection. Here is a traceroute to google:This can be if the MtGox server is busy (it just drops requests) but it can obviously also be caused by network problems.
Also in the log the number of peers it finds is always 14. Normally in the two seconds it spends looking up network peers I get 80+ and the number varies. My network is a laggy 3G connection.
Can you describe what your network setup is please ?
Code:
$ traceroute www.google.com 1 ↵
traceroute: Warning: www.google.com has multiple addresses; using 74.125.239.19
traceroute to www.google.com (74.125.239.19), 64 hops max, 52 byte packets
1 192.168.85.1 (192.168.85.1) 0.571 ms 1.016 ms 0.433 ms
2 cpr-cbc-ws2-rtr.mwtn.net (66.62.70.33) 32.355 ms 23.231 ms 50.089 ms
3 unused.mwtn.net (66.119.55.89) 33.394 ms 37.770 ms 14.982 ms
4 cbc-cbc9-lnk.mwtn.net (66.62.71.73) 54.910 ms 23.515 ms 33.466 ms
5 cbc-gsr.mwtn.net (66.119.48.150) 34.954 ms 28.013 ms 19.874 ms
6 66.62.160.93 (66.62.160.93) 50.172 ms 28.976 ms 25.075 ms
7 den1-core-01-ae1.360.net (66.62.2.193) 29.738 ms 39.243 ms 36.213 ms
8 lax1-core-02-xe-3-0-0.360.net (66.62.2.174) 68.732 ms 59.549 ms 69.827 ms
9 google.com.any2ix.coresite.com (206.223.143.41) 110.151 ms 63.516 ms 64.764 ms
10 64.233.174.31 (64.233.174.31) 65.213 ms 182.785 ms 80.082 ms
11 216.239.43.148 (216.239.43.148) 54.831 ms 78.751 ms 54.192 ms
12 lax04s09-in-f19.1e100.net (74.125.239.19) 60.131 ms 76.823 ms 119.900 ms
Quote
I have recently changed how it looks up the Bitcoin network peers so that it does a DNS lookup of all the seed nodes in parallel (on different threads). I think I will have to adjust the algorithm a bit as I suspect that is what is causing you problems.
If you still have an old copy of multiBit 0.4.10 that would be a good test to see if that connnects ok. I made the peer lookup change in 0.4.11.
I did, and it exhibits the same (broken?) behavior so it doesn't look like it was peer lookup change. The logs looks pretty much the same so I didn't include it.If you still have an old copy of multiBit 0.4.10 that would be a good test to see if that connnects ok. I made the peer lookup change in 0.4.11.
Quote
Sorry that you are an unvolunteered tester.
No worries, I don't mind. Thank you for the support.EDIT: here is what I am getting for DNS results:
Code:
$ dig +short bitseed.xf2.org 130 ↵
212.7.0.70
46.19.139.106
62.75.216.13
69.64.34.118
69.64.46.74
69.164.196.4
87.139.154.234
91.121.66.59
91.121.120.119
177.71.186.54
184.174.133.70
204.9.55.71
207.164.207.29
I notice in that log that the HTTP gets that the currency ticker does are also failing.
This can be if the MtGox server is busy (it just drops requests) but it can obviously also be caused by network problems.
Also in the log the number of peers it finds is always 14. Normally in the two seconds it spends looking up network peers I get 80+ and the number varies. My network is a laggy 3G connection.
Can you describe what your network setup is please ?
I have recently changed how it looks up the Bitcoin network peers so that it does a DNS lookup of all the seed nodes in parallel (on different threads). I think I will have to adjust the algorithm a bit as I suspect that is what is causing you problems.
If you still have an old copy of multiBit 0.4.10 that would be a good test to see if that connnects ok. I made the peer lookup change in 0.4.11.
Sorry that you are an unvolunteered tester.
This can be if the MtGox server is busy (it just drops requests) but it can obviously also be caused by network problems.
Also in the log the number of peers it finds is always 14. Normally in the two seconds it spends looking up network peers I get 80+ and the number varies. My network is a laggy 3G connection.
Can you describe what your network setup is please ?
I have recently changed how it looks up the Bitcoin network peers so that it does a DNS lookup of all the seed nodes in parallel (on different threads). I think I will have to adjust the algorithm a bit as I suspect that is what is causing you problems.
If you still have an old copy of multiBit 0.4.10 that would be a good test to see if that connnects ok. I made the peer lookup change in 0.4.11.
Sorry that you are an unvolunteered tester.
Still not connecting 
Here is a complete log of the session: https://dl.dropbox.com/u/86939820/tmp/multibit_debug.log
Here is a complete log of the session: https://dl.dropbox.com/u/86939820/tmp/multibit_debug.log
Jump to: