Bitcoin Forum
May 22, 2019, 12:11:03 PM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: « 1 ... 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 [1710] 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 ... 2038 »
  Print  
Author Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency  (Read 4560118 times)
CryptShark
Full Member
***
Offline Offline

Activity: 150
Merit: 100


View Profile
March 02, 2017, 05:45:35 PM
 #34181

I did export and re-import, all looks good but i get :

2017-Mar-02 BLOCK ADDED AS ALTERNATIVE ON HEIGH......

Is this normal? I dont re-call seeing this before

Thanks,
1558527063
Hero Member
*
Offline Offline

Posts: 1558527063

View Profile Personal Message (Offline)

Ignore
1558527063
Reply with quote  #2

1558527063
Report to moderator
1558527063
Hero Member
*
Offline Offline

Posts: 1558527063

View Profile Personal Message (Offline)

Ignore
1558527063
Reply with quote  #2

1558527063
Report to moderator
START MINING BTC NOW WITH NEW GENERATION S17 ANTMINER! BTC/BCH/LTC/ZCASH/DASH/ETH/DCR MINING PLAN AVAILABLE Highly Reduced Electricity Fee $0.067/T/DAY!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1558527063
Hero Member
*
Offline Offline

Posts: 1558527063

View Profile Personal Message (Offline)

Ignore
1558527063
Reply with quote  #2

1558527063
Report to moderator
1558527063
Hero Member
*
Offline Offline

Posts: 1558527063

View Profile Personal Message (Offline)

Ignore
1558527063
Reply with quote  #2

1558527063
Report to moderator
1558527063
Hero Member
*
Offline Offline

Posts: 1558527063

View Profile Personal Message (Offline)

Ignore
1558527063
Reply with quote  #2

1558527063
Report to moderator
phytosaw22
Member
**
Offline Offline

Activity: 84
Merit: 10


View Profile
March 02, 2017, 05:49:38 PM
 #34182

Much better than Dash. This coin will go up soon, mark me words!

SHIFT - Decentralize the web
luigi1111
Legendary
*
Offline Offline

Activity: 1113
Merit: 1000



View Profile
March 02, 2017, 11:37:37 PM
 #34183

I did export and re-import, all looks good but i get :

2017-Mar-02 BLOCK ADDED AS ALTERNATIVE ON HEIGH......

Is this normal? I dont re-call seeing this before

Thanks,

This is normal. It occurs when two miners find a solution for the next block at the ~same time; both get published, and the remaining hash power will accept and start building on one or the other. When a new block is found, the "fork" will resolve and all nodes should switch to the longer chain (if they were not on it).
B8888
Newbie
*
Offline Offline

Activity: 59
Merit: 0


View Profile
March 02, 2017, 11:38:50 PM
 #34184

When comparing XMR to DASH. Lets say XMR gets mass adoption wouldnt you say it is much easier to secure XMR network for general person? - no 1000 coin requirement, no wallet requirement - ( yes you could run a dash full node with wallet open just as easy as monerod) but I think the fact that monero seperates the wallet from monerod is a great option. People who just want to secure the network and make xmr stronger can run this monerod on  as many pc as possible and secure the network. Am I on the right track here?

Some say there is no incentive to run full node on XMR. But if your business revolves around privacy then running some full nodes on different PC is a good thing to do and will help the cause. XMR could one day have more full nodes than active DASH masternodes correct? - that could happen very quick from what I understand, therefore making XMR much more decentralized and secure.
c789
Hero Member
*****
Offline Offline

Activity: 848
Merit: 1000



View Profile
March 03, 2017, 12:21:57 AM
 #34185

When comparing XMR to DASH. Lets say XMR gets mass adoption wouldnt you say it is much easier to secure XMR network for general person? - no 1000 coin requirement, no wallet requirement - ( yes you could run a dash full node with wallet open just as easy as monerod) but I think the fact that monero seperates the wallet from monerod is a great option. People who just want to secure the network and make xmr stronger can run this monerod on  as many pc as possible and secure the network. Am I on the right track here?
Spot on.

Some say there is no incentive to run full node on XMR. But if your business revolves around privacy then running some full nodes on different PC is a good thing to do and will help the cause. XMR could one day have more full nodes than active DASH masternodes correct? - that could happen very quick from what I understand, therefore making XMR much more decentralized and secure.
Again, spot on. And running a full node is easy. At home I run one full-time, another one part-time, and I have a website that runs a node full-time. Aside from the initial sync it takes up very little resources.

Here's a fun link: https://monerohash.com/nodes-distribution.html

Comparison of Privacy-Centric Coins: https://moneroforcash.com/monero-vs-dash-vs-zcash-vs-bitcoinmixers.php also includes Verge and Pivx
mrtrodonet
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
March 03, 2017, 04:26:23 AM
 #34186

Fellow monero miners, please help!

I'm building a 6 x MSI rx480 4gb(stock bios) mining rig. Using Biostar TB85 Mobo with windows 7x64.
I installed the latest updates and AMD drivers, but I have an issue where only 4 of 6 vide cards are recognized by the system.
The other two report error 43 device manager.

I have tried moving the cables around, always the same 2 cards in the device manager. Card 3 and card 5. This makes me believe that cards and risers are not an issue, but it is either os/driver or the mobo.
I have the same mobo running 6 GTX1070 with no issues...
 
Any insight would be very appreciated.
If you don't know what my issue is, but know what motherboard works, please let me know.

make sure you set your PCIE lanes in the bios to x1. Thats all thats needed for mining and i found any higher setting like x16 stopped me from using all cards.

I found a setting that allows me to select 1gen/2gen for regular pci-e ports and gen1-gen3 for pci-e x16. Is that an equivalent?
I booted removed all GPUS and re-discovered them in device manager but 2 of them still report error 43 Sad
Bobo81
Sr. Member
****
Offline Offline

Activity: 448
Merit: 250



View Profile
March 03, 2017, 05:44:21 AM
 #34187

Much better than Dash. This coin will go up soon, mark me words!

Or not...  Sad

  Develop Custom Decentralized Blockchain Applications in JavaScript with LISK!
  Website | Blog | BTT Thread | Chat - Be part of the decentralized application movement!
Dodnastes
Newbie
*
Offline Offline

Activity: 58
Merit: 0


View Profile
March 03, 2017, 08:31:06 AM
 #34188

Fellow monero miners, please help!

I'm building a 6 x MSI rx480 4gb(stock bios) mining rig. Using Biostar TB85 Mobo with windows 7x64.
I installed the latest updates and AMD drivers, but I have an issue where only 4 of 6 vide cards are recognized by the system.
The other two report error 43 device manager.

I have tried moving the cables around, always the same 2 cards in the device manager. Card 3 and card 5. This makes me believe that cards and risers are not an issue, but it is either os/driver or the mobo.
I have the same mobo running 6 GTX1070 with no issues...
 
Any insight would be very appreciated.
If you don't know what my issue is, but know what motherboard works, please let me know.

make sure you set your PCIE lanes in the bios to x1. Thats all thats needed for mining and i found any higher setting like x16 stopped me from using all cards.

I found a setting that allows me to select 1gen/2gen for regular pci-e ports and gen1-gen3 for pci-e x16. Is that an equivalent?
I booted removed all GPUS and re-discovered them in device manager but 2 of them still report error 43 Sad


You need to use 6+GPU mod to make all the GPU recognized in Windows.
visdude
Legendary
*
Offline Offline

Activity: 1060
Merit: 1001


View Profile
March 03, 2017, 09:36:30 AM
 #34189


I'm having issues with 0.10.2.1 that I never got with 0.10.1.0. Firstly, though it runs and syncs as expected, why am I getting a "FATAL" warning of some sort each time I start this latest version of the daemon (2nd line)?

Code:
2017-03-02 19:41:49.527 4776    INFO    global  contrib/epee/src/mlog.cpp:145
New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,global:INFO,verify:FATAL,s
tacktrace:INFO
2017-03-02 19:41:49.528 4776    INFO    global  src/daemon/main.cpp:282 Monero '
Wolfram Warptangent' (v0.10.2.1-release)
2017-03-02 19:41:49.528 4776    INFO    global  src/daemon/protocol.h:55
Initializing cryptonote protocol...
2017-03-02 19:41:49.528 4776    INFO    global  src/daemon/protocol.h:60
Cryptonote protocol initialized OK
2017-03-02 19:41:49.529 4776    INFO    global  src/daemon/p2p.h:63     Initiali
zing p2p server...
2017-03-02 19:41:57.490 4776    INFO    global  src/daemon/p2p.h:68     P2p serv
er initialized OK
2017-03-02 19:42:04.435 4776    INFO    global  src/daemon/rpc.h:58     Initiali
zing core rpc server...
2017-03-02 19:42:04.437 4776    INFO    global  contrib/epee/include/net/http_se
rver_impl_base.h:70     Binding on 127.0.0.1:18081
2017-03-02 19:42:04.443 4776    INFO    global  src/daemon/rpc.h:63     Core rpc
 server initialized OK on port: 18081
2017-03-02 19:42:04.443 4776    INFO    global  src/daemon/core.h:73    Initiali
zing core...
2017-03-02 19:42:04.469 4776    INFO    global  src/cryptonote_core/cryptonote_c
ore.cpp:316     Loading blockchain from folder C:\ProgramData\bitmonero\lmdb ...

Secondly, it doesn't like it when I introduce the arg, "--rpc-bind-ip 0.0.0.0 --restricted-rpc" and craps out as soon as it starts to initialize the p2p server. Right about here:

Code:
2017-03-02 19:41:49.527 4776    INFO    global  contrib/epee/src/mlog.cpp:145
New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,global:INFO,verify:FATAL,s
tacktrace:INFO
2017-03-02 19:41:49.528 4776    INFO    global  src/daemon/main.cpp:282 Monero '
Wolfram Warptangent' (v0.10.2.1-release)
2017-03-02 19:41:49.528 4776    INFO    global  src/daemon/protocol.h:55
Initializing cryptonote protocol...
2017-03-02 19:41:49.528 4776    INFO    global  src/daemon/protocol.h:60
Cryptonote protocol initialized OK
2017-03-02 19:41:49.529 4776    INFO    global  src/daemon/p2p.h:63     Initiali
zing p2p server...

Again, I never got these with 0.10.1.0.

template
Hero Member
*****
Offline Offline

Activity: 980
Merit: 500


View Profile WWW
March 03, 2017, 10:51:20 AM
 #34190

XMR next week price $25+ waiting for it  Wink

MoneroMooo
Legendary
*
Offline Offline

Activity: 1280
Merit: 1001


View Profile
March 03, 2017, 11:17:59 AM
 #34191

I'm having issues with 0.10.2.1 that I never got with 0.10.1.0. Firstly, though it runs and syncs as expected, why am I getting a "FATAL" warning of some sort each time I start this latest version of the daemon (2nd line)?

There's no error here. Just because the string "FATAL" is somewhere doesn't mean something broke. It depends on the context the word is used in.

Secondly, it doesn't like it when I introduce the arg, "--rpc-bind-ip 0.0.0.0 --restricted-rpc" and craps out as soon as it starts to initialize the p2p server. Right about here:

That does not include the error, but it's likely the bit you omitted also tells you to use either --disable-rpc-login or other arguments. Try doing one of those (--disable-rpc-login will behave as previous monero versions).


░░░░░░░░░░░░░░░░░░░░▄▄
░░░░░░░░░░░░░░░░░░░░████▄▄
░░░░░░░░░▄▄░░░░░░░░░████████
░░░░░▄▄██████▄▄░░░░░███████████▄▄
░▄▄██████████████▄▄███████████████▄
░▀▀██████████████▀▀░░░▀▀████████████
██▄▄▀▀██████▀▀░░░░░░░░░░░▀▀████████
██████▄▄▀▀░░░░░░░░░░░░░░░░░░▀███████
████████░░░░░░░░░▄▄▄░░░░░░░░░░░▀▀███
████████░░░░░▄▄███████▄▄░░░░░███▄▄░░▀
████████░░░███████████████░░░███████▄
░░▀▀████░░░░░▀▀███████▀▀░░░░░████████
██▄▄░░▀▀░░░░░░░░░▀▀▀░░░░░░░░░████████
██████▄▄░░░░░░░░░░░░░░░░░▄▄░░▀███████
████████░░░░░░░░░░░░░▄▄██████▄▄▀▀███
██████████▄▄░░░░▄▄██████████████▄▄
██████████████▄▄▀▀██████████████▀▀
░░▀▀████████████░░░░▀▀██████▀▀
░░░░░░▀▀████████░░░░░░░░▀▀
░░░░░░░░░▀▀██████
░░░░░░░░░░░░░▀▀██
OATH

████▀
███▀  ▀
██▀  ▀
█▀  ▀
▀  ▀
▄  ▄
█▄  ▄
██▄  ▄
███▄  ▄
████▄


▀████
▀  ▀███
▀  ▀██
▀  ▀█
▀  ▀
▄  ▄
▄  ▄█
▄  ▄██
▄  ▄███
▄████


             ▄████▄▄   ▄
█▄          ██████████▀▄
███        ███████████▀
▐████▄     ██████████▌
▄▄██████▄▄▄▄█████████▌
▀████████████████████
  ▀█████████████████
  ▄▄███████████████
   ▀█████████████▀
    ▄▄█████████▀
▀▀██████████▀
    ▀▀▀▀▀


                   ▄▄████
              ▄▄████████▌
         ▄▄█████████▀███
    ▄▄██████████▀▀ ▄███▌
▄████████████▀▀  ▄█████
▀▀▀███████▀   ▄███████▌
      ██    ▄█████████
       █  ▄██████████▌
       █  ███████████
       █ ██▀ ▀██████▌
       ██▀     ▀████
                 ▀█▌


█▄▄              █▄▄
█████▄▄         ██████▄▄
████████       ████████ █
████████ ██   ████████ ██
████████ ███ ████████ ███
████████ ████ ██████ ████
████████ █████ ████ █████
████████ ▀█████ ██ ██████
████████    ▀▀██  ███████
▀███████         ▀███████
   ▀▀███            ▀▀███
       ▀                ▀
visdude
Legendary
*
Offline Offline

Activity: 1060
Merit: 1001


View Profile
March 03, 2017, 12:32:04 PM
Last edit: March 03, 2017, 01:01:19 PM by visdude
 #34192

I'm having issues with 0.10.2.1 that I never got with 0.10.1.0. Firstly, though it runs and syncs as expected, why am I getting a "FATAL" warning of some sort each time I start this latest version of the daemon (2nd line)?

There's no error here. Just because the string "FATAL" is somewhere doesn't mean something broke. It depends on the context the word is used in.

Secondly, it doesn't like it when I introduce the arg, "--rpc-bind-ip 0.0.0.0 --restricted-rpc" and craps out as soon as it starts to initialize the p2p server. Right about here:

That does not include the error, but it's likely the bit you omitted also tells you to use either --disable-rpc-login or other arguments. Try doing one of those (--disable-rpc-login will behave as previous monero versions).


Noted. It's disconcerting to see "WARNING" AND "FATAL" nevertheless.

I'm now very confused. So it's "--disable-rpc-login --rpc-bind-ip 0.0.0.0 --restricted-rpc" then? BTW, I don't have CLI savvy like you folks. In fact, it horrifies me. I'm only copying and pasting the arg  mentioned from the suggestions on previous pages of this thread for purposes of being able to remotely access/connect to my node with GUI wallet (in conjunction with router port forwarding).

Edit:

By "craps out", I meant the CLI window closes at that particular point. Therefore, no displayed error.

Chicken76
Newbie
*
Offline Offline

Activity: 58
Merit: 0


View Profile
March 03, 2017, 01:06:16 PM
 #34193

I'm getting a lot of these messages from the daemon:
Code:
2017-03-03 12:49:20.929 [P2P6]  WARN    net.cn  src/cryptonote_protocol/cryptonote_protocol_handler-base.cpp:125        RATE LIMIT NOT IMPLEMENTED HERE YET (download at unlimited speed?)
Can anyone explain what this means? I have not set any limits. Do I need to?
mrtrodonet
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
March 03, 2017, 04:25:07 PM
 #34194

Fellow monero miners, please help!

I'm building a 6 x MSI rx480 4gb(stock bios) mining rig. Using Biostar TB85 Mobo with windows 7x64.
I installed the latest updates and AMD drivers, but I have an issue where only 4 of 6 vide cards are recognized by the system.
The other two report error 43 device manager.

I have tried moving the cables around, always the same 2 cards in the device manager. Card 3 and card 5. This makes me believe that cards and risers are not an issue, but it is either os/driver or the mobo.
I have the same mobo running 6 GTX1070 with no issues...
 
Any insight would be very appreciated.
If you don't know what my issue is, but know what motherboard works, please let me know.

make sure you set your PCIE lanes in the bios to x1. Thats all thats needed for mining and i found any higher setting like x16 stopped me from using all cards.

I found a setting that allows me to select 1gen/2gen for regular pci-e ports and gen1-gen3 for pci-e x16. Is that an equivalent?
I booted removed all GPUS and re-discovered them in device manager but 2 of them still report error 43 Sad


You need to use 6+GPU mod to make all the GPU recognized in Windows.

Can you give me more details? Is it a driver mod? where do i find the Patch?
luigi1111
Legendary
*
Offline Offline

Activity: 1113
Merit: 1000



View Profile
March 03, 2017, 10:11:24 PM
 #34195

I'm having issues with 0.10.2.1 that I never got with 0.10.1.0. Firstly, though it runs and syncs as expected, why am I getting a "FATAL" warning of some sort each time I start this latest version of the daemon (2nd line)?

There's no error here. Just because the string "FATAL" is somewhere doesn't mean something broke. It depends on the context the word is used in.

Secondly, it doesn't like it when I introduce the arg, "--rpc-bind-ip 0.0.0.0 --restricted-rpc" and craps out as soon as it starts to initialize the p2p server. Right about here:

That does not include the error, but it's likely the bit you omitted also tells you to use either --disable-rpc-login or other arguments. Try doing one of those (--disable-rpc-login will behave as previous monero versions).


Noted. It's disconcerting to see "WARNING" AND "FATAL" nevertheless.

I'm now very confused. So it's "--disable-rpc-login --rpc-bind-ip 0.0.0.0 --restricted-rpc" then? BTW, I don't have CLI savvy like you folks. In fact, it horrifies me. I'm only copying and pasting the arg  mentioned from the suggestions on previous pages of this thread for purposes of being able to remotely access/connect to my node with GUI wallet (in conjunction with router port forwarding).

Edit:

By "craps out", I meant the CLI window closes at that particular point. Therefore, no displayed error.



It's telling you "WARNING" and "FATAL" are active log categories, which I would assume should be a comfort. Smiley

For your second thing, I'd run the commands from a terminal, which shouldn't close if an error happens (if you were running it in a script, you can just launch the script from the terminal instead).
phishead
Hero Member
*****
Offline Offline

Activity: 1232
Merit: 575


Keep what's important, and know who's your friend


View Profile WWW
March 04, 2017, 04:36:48 AM
 #34196

Any body feel like throwing a couple romeritos on a March Madness bracket?

Join us over at the Monero Madness thread


██████████
█████████████████
██████████████████████
█████████████████████████
████████████████████████████
████
████████████████████████
█████
███████████████████████████
█████
███████████████████████████
██████
████████████████████████████
██████
████████████████████████████
██████
████████████████████████████
██████
███████████████████████████
██████
██████████████████████████
█████
███████████████████████████
█████████████
██████████████
████████████████████████████
█████████████████████████
██████████████████████
█████████████████
██████████

Monero
"I just opened a 2004 barolo in your and all the devs honour"  eyejay:  Decemeber 22nd, 2016

"Don't buy Monero, join our new ICO: 'The Monero Enterprise Alliance"  fluffypony:  May 24th, 2017
visdude
Legendary
*
Offline Offline

Activity: 1060
Merit: 1001


View Profile
March 04, 2017, 08:13:22 AM
 #34197

I'm having issues with 0.10.2.1 that I never got with 0.10.1.0. Firstly, though it runs and syncs as expected, why am I getting a "FATAL" warning of some sort each time I start this latest version of the daemon (2nd line)?

There's no error here. Just because the string "FATAL" is somewhere doesn't mean something broke. It depends on the context the word is used in.

Secondly, it doesn't like it when I introduce the arg, "--rpc-bind-ip 0.0.0.0 --restricted-rpc" and craps out as soon as it starts to initialize the p2p server. Right about here:

That does not include the error, but it's likely the bit you omitted also tells you to use either --disable-rpc-login or other arguments. Try doing one of those (--disable-rpc-login will behave as previous monero versions).


Noted. It's disconcerting to see "WARNING" AND "FATAL" nevertheless.

I'm now very confused. So it's "--disable-rpc-login --rpc-bind-ip 0.0.0.0 --restricted-rpc" then? BTW, I don't have CLI savvy like you folks. In fact, it horrifies me. I'm only copying and pasting the arg  mentioned from the suggestions on previous pages of this thread for purposes of being able to remotely access/connect to my node with GUI wallet (in conjunction with router port forwarding).

Edit:

By "craps out", I meant the CLI window closes at that particular point. Therefore, no displayed error.



It's telling you "WARNING" and "FATAL" are active log categories, which I would assume should be a comfort. Smiley

For your second thing, I'd run the commands from a terminal, which shouldn't close if an error happens (if you were running it in a script, you can just launch the script from the terminal instead).

No dice running it from a terminal but at least, it's showing the ERROR. What does it mean? The same arg runs fine in 0.10.1.0 (even as a shortcut target). Shouldn't commands consistently be valid across all versions?

To reiterate, the extent of my CLI proficiency is copying and pasting command lines that's given to me. I'm not a coder; just a regular Joe User trying to make sense of these technicalities, hoping to comprehend enough to be able to get by and participate in Monero's success. So please consider this when offering an explanation. Thanks.

Code:
C:\monero>monerod --rpc-bind-ip 0.0.0.0 --restricted-rpc
2017-03-03 23:30:23.096 7412    INFO    global  contrib/epee/src/mlog.cpp:145
New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,global:INFO,verify:FATAL,s
tacktrace:INFO
2017-03-03 23:30:23.097 7412    INFO    global  src/daemon/main.cpp:282 Monero '
Wolfram Warptangent' (v0.10.2.1-release)
2017-03-03 23:30:23.097 7412    INFO    global  src/daemon/protocol.h:55
Initializing cryptonote protocol...
2017-03-03 23:30:23.097 7412    INFO    global  src/daemon/protocol.h:60
Cryptonote protocol initialized OK
2017-03-03 23:30:23.097 7412    INFO    global  src/daemon/p2p.h:63     Initiali
zing p2p server...
2017-03-03 23:30:30.921 7412    INFO    global  src/daemon/p2p.h:68     P2p serv
er initialized OK
2017-03-03 23:30:30.921 7412    INFO    global  src/daemon/rpc.h:58     Initiali
zing core rpc server...
2017-03-03 23:30:30.923 7412    ERROR   default src/rpc/rpc_args.cpp:76 --rpc-bi
nd-ip permits inbound unencrypted external connections. Consider SSH tunnel or S
SL proxy instead. Override with --confirm-external-bind
2017-03-03 23:30:30.923 7412    INFO    global  src/daemon/p2p.h:90     Deinitia
lizing p2p...
2017-03-03 23:30:30.927 7412    INFO    global  src/daemon/core.h:89    Deinitia
lizing core...
2017-03-03 23:30:30.928 7412    ERROR   daemon  src/daemon/core.h:94    Failed t
o deinitialize core...
2017-03-03 23:30:30.928 7412    INFO    global  src/daemon/protocol.h:77
Stopping cryptonote protocol...
2017-03-03 23:30:30.928 7412    INFO    global  src/daemon/protocol.h:81
Cryptonote protocol stopped successfully
Daemon stopped successfully
2017-03-03 23:30:30.929 7412    ERROR   daemon  src/daemon/main.cpp:290 Exceptio
n in main! Failed to initialize core rpc server.

MoneroMooo
Legendary
*
Offline Offline

Activity: 1280
Merit: 1001


View Profile
March 04, 2017, 09:51:33 AM
 #34198

I understand you're not used to command line, but this is just text to read.
The error message tells you what to do. While some error messages can be cryptic, this one plainly tells you "Override with --confirm-external-bind".
In command line terms, it means adding "--confirm-external-bind" to whatever command line you're using at the moment. Don't forget a space before adding, so it reads, eg: monerod --confirm-external-bind rather than monerod--confirm-external-bind.


░░░░░░░░░░░░░░░░░░░░▄▄
░░░░░░░░░░░░░░░░░░░░████▄▄
░░░░░░░░░▄▄░░░░░░░░░████████
░░░░░▄▄██████▄▄░░░░░███████████▄▄
░▄▄██████████████▄▄███████████████▄
░▀▀██████████████▀▀░░░▀▀████████████
██▄▄▀▀██████▀▀░░░░░░░░░░░▀▀████████
██████▄▄▀▀░░░░░░░░░░░░░░░░░░▀███████
████████░░░░░░░░░▄▄▄░░░░░░░░░░░▀▀███
████████░░░░░▄▄███████▄▄░░░░░███▄▄░░▀
████████░░░███████████████░░░███████▄
░░▀▀████░░░░░▀▀███████▀▀░░░░░████████
██▄▄░░▀▀░░░░░░░░░▀▀▀░░░░░░░░░████████
██████▄▄░░░░░░░░░░░░░░░░░▄▄░░▀███████
████████░░░░░░░░░░░░░▄▄██████▄▄▀▀███
██████████▄▄░░░░▄▄██████████████▄▄
██████████████▄▄▀▀██████████████▀▀
░░▀▀████████████░░░░▀▀██████▀▀
░░░░░░▀▀████████░░░░░░░░▀▀
░░░░░░░░░▀▀██████
░░░░░░░░░░░░░▀▀██
OATH

████▀
███▀  ▀
██▀  ▀
█▀  ▀
▀  ▀
▄  ▄
█▄  ▄
██▄  ▄
███▄  ▄
████▄


▀████
▀  ▀███
▀  ▀██
▀  ▀█
▀  ▀
▄  ▄
▄  ▄█
▄  ▄██
▄  ▄███
▄████


             ▄████▄▄   ▄
█▄          ██████████▀▄
███        ███████████▀
▐████▄     ██████████▌
▄▄██████▄▄▄▄█████████▌
▀████████████████████
  ▀█████████████████
  ▄▄███████████████
   ▀█████████████▀
    ▄▄█████████▀
▀▀██████████▀
    ▀▀▀▀▀


                   ▄▄████
              ▄▄████████▌
         ▄▄█████████▀███
    ▄▄██████████▀▀ ▄███▌
▄████████████▀▀  ▄█████
▀▀▀███████▀   ▄███████▌
      ██    ▄█████████
       █  ▄██████████▌
       █  ███████████
       █ ██▀ ▀██████▌
       ██▀     ▀████
                 ▀█▌


█▄▄              █▄▄
█████▄▄         ██████▄▄
████████       ████████ █
████████ ██   ████████ ██
████████ ███ ████████ ███
████████ ████ ██████ ████
████████ █████ ████ █████
████████ ▀█████ ██ ██████
████████    ▀▀██  ███████
▀███████         ▀███████
   ▀▀███            ▀▀███
       ▀                ▀
visdude
Legendary
*
Offline Offline

Activity: 1060
Merit: 1001


View Profile
March 04, 2017, 12:55:05 PM
 #34199

I understand you're not used to command line, but this is just text to read.
The error message tells you what to do. While some error messages can be cryptic, this one plainly tells you "Override with --confirm-external-bind".
In command line terms, it means adding "--confirm-external-bind" to whatever command line you're using at the moment. Don't forget a space before adding, so it reads, eg: monerod --confirm-external-bind rather than monerod--confirm-external-bind.

That did it! Thanks for the clear instruction.

GingerAle
Legendary
*
Offline Offline

Activity: 1190
Merit: 1004


View Profile WWW
March 05, 2017, 05:09:10 AM
 #34200

Free VMs for Monero Development

https://moneroworld.com/#developer

So, I bought a server and thought I could drop some opterons in it that could mine some Monero... and turns out this stupid proliant can't take 6200 series CPUs ... so mining is worthless. So now I'm offering it out for Monero development!

If you like to hack on monero, but get tired of waiting for your code to compile on your sad little laptop, get a VM on my box - Monero compiles in 8 minutes.

Everyone gets full resources (24 cores, ~80 GB ram). You don't get your own IP, just a port. Don't be a dick - if your running over 1% load for over an hour, I'll get mad and kill your VM.  This isn't for services, its for compiling.

Email me at gingeropolous@tutanota.com

< Track your bitcoins! > < Track them again! > <<< [url=https://www.reddit.com/r/Bitcoin/comments/1qomqt/what_a_landmark_legal_case_from_mid1700s_scotland/] What is fungibility? >>> 46P88uZ4edEgsk7iKQUGu2FUDYcdHm2HtLFiGLp1inG4e4f9PTb4mbHWYWFZGYUeQidJ8hFym2WUmWc p34X8HHmFS2LXJkf <<< Free subdomains at moneroworld.com!! >>> <<< If you don't want to run your own node, point your wallet to node.moneroworld.com, and get connected to a random node! @@@@ FUCK ALL THE PROFITEERS! PROOF OF WORK OR ITS A SCAM !!! @@@@
Pages: « 1 ... 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 [1710] 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 ... 2038 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!