[XMR] Monero - A secure, private, untraceable cryptocurrency - page 419.

visdude

legendary

Activity: 1081

Merit: 1001

Quote from: MoneroMooo on March 04, 2017, 04:51:33 AM

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.

MoneroMooo

legendary

Activity: 1276

Merit: 1001

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.

visdude

legendary

Activity: 1081

Merit: 1001

Quote from: luigi1111 on March 03, 2017, 05:11:24 PM

Quote from: visdude on March 03, 2017, 07:32:04 AM

Quote from: MoneroMooo on March 03, 2017, 06:17:59 AM

Quote from: visdude on March 03, 2017, 04:36:30 AM

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.

Quote from: visdude on March 03, 2017, 04:36:30 AM

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.

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.

phishead

hero member

Activity: 1874

Merit: 840

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

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

Join us over at the Monero Madness thread

luigi1111

legendary

Activity: 1105

Merit: 1000

Quote from: visdude on March 03, 2017, 07:32:04 AM

Quote from: MoneroMooo on March 03, 2017, 06:17:59 AM

Quote from: visdude on March 03, 2017, 04:36:30 AM

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.

Quote from: visdude on March 03, 2017, 04:36:30 AM

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.

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).

mrtrodonet

newbie

Activity: 14

Merit: 0

Quote from: Dodnastes on March 03, 2017, 03:31:06 AM

Quote from: mrtrodonet on March 02, 2017, 11:26:23 PM

Quote from: ozkraut on March 02, 2017, 03:05:32 AM

Quote from: mrtrodonet on March 02, 2017, 12:41:52 AM

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?

Chicken76

newbie

Activity: 58

Merit: 0

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?

visdude

legendary

Activity: 1081

Merit: 1001

Quote from: MoneroMooo on March 03, 2017, 06:17:59 AM

Quote from: visdude on March 03, 2017, 04:36:30 AM

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.

Quote from: visdude on March 03, 2017, 04:36:30 AM

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.

MoneroMooo

legendary

Activity: 1276

Merit: 1001

Quote from: visdude on March 03, 2017, 04:36:30 AM

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.

Quote from: visdude on March 03, 2017, 04:36:30 AM

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).

template

hero member

Activity: 1085

Merit: 500

XMR next week price $25+ waiting for it Wink

visdude

legendary

Activity: 1081

Merit: 1001

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.

Dodnastes

newbie

Activity: 58

Merit: 0

Quote from: mrtrodonet on March 02, 2017, 11:26:23 PM

Quote from: ozkraut on March 02, 2017, 03:05:32 AM

Quote from: mrtrodonet on March 02, 2017, 12:41:52 AM

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.

Bobo81

sr. member

Activity: 476

Merit: 250

Quote from: phytosaw22 on March 02, 2017, 12:49:38 PM

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

Or not...

mrtrodonet

newbie

Activity: 14

Merit: 0

Quote from: ozkraut on March 02, 2017, 03:05:32 AM

Quote from: mrtrodonet on March 02, 2017, 12:41:52 AM

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

c789

hero member

Activity: 850

Merit: 1000

Quote from: B8888 on March 02, 2017, 06:38:50 PM

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.

Quote from: B8888 on March 02, 2017, 06:38:50 PM

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

B8888

newbie

Activity: 59

Merit: 0

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.

luigi1111

legendary

Activity: 1105

Merit: 1000

Quote from: CryptShark on March 02, 2017, 12:45:35 PM

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).

phytosaw22

member

Activity: 84

Merit: 10

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

CryptShark

full member

Activity: 150

Merit: 100

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,

axlroses

hero member

Activity: 672

Merit: 500

monero vs bitcoin Kiss

Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 419. (Read 4671575 times)