AlexTheMenace 1 Posted January 3 Share Posted January 3 Hi all, I'm operating three XRP full nodes for our service. I had made a raw transaction having the base fee as 10drops, and then submitted and got failed with an error message "insufficient base fee". The base fee value depends on the load of the node as I know. but when I checked the logs of the nodes, cannot find any evidence of the heavy load. Are there any reasons or factors for the elevation of the base fee? Can I find the queue's status in a log file (debug.log) or in anything? Thanks in advance! Link to post Share on other sites
Duke67 1,921 Posted January 3 Share Posted January 3 I've just briefly checked fees and did not see anything unusual - fee is consistently 10 drops. Link to post Share on other sites
tulo 3,333 Posted January 3 Share Posted January 3 15 minutes ago, AlexTheMenace said: Hi all, I'm operating three XRP full nodes for our service. I had made a raw transaction having the base fee as 10drops, and then submitted and got failed with an error message "insufficient base fee". The base fee value depends on the load of the node as I know. but when I checked the logs of the nodes, cannot find any evidence of the heavy load. Are there any reasons or factors for the elevation of the base fee? Can I find the queue's status in a log file (debug.log) or in anything? Thanks in advance! What error did you exactly get? The ter_*, tef_*.... Link to post Share on other sites
nikb 4,390 Posted January 3 Share Posted January 3 1 hour ago, AlexTheMenace said: Hi all, I'm operating three XRP full nodes for our service. That's great! Thanks for supporting the XRP Ledger by operating infrastructure. 1 hour ago, AlexTheMenace said: I had made a raw transaction having the base fee as 10drops, and then submitted and got failed with an error message "insufficient base fee". The base fee value depends on the load of the node as I know. but when I checked the logs of the nodes, cannot find any evidence of the heavy load. Are there any reasons or factors for the elevation of the base fee? Can I find the queue's status in a log file (debug.log) or in anything? Thanks in advance! Do you have the actual error code? tecINSUFF_FEE? telINSUF_FEE_P? Something else? Link to post Share on other sites
AlexTheMenace 1 Posted January 4 Author Share Posted January 4 8 hours ago, nikb said: That's great! Thanks for supporting the XRP Ledger by operating infrastructure. Do you have the actual error code? tecINSUFF_FEE? telINSUF_FEE_P? Something else? I got the "telINSUF_FEE_P". Link to post Share on other sites
AlexTheMenace 1 Posted January 4 Author Share Posted January 4 9 hours ago, tulo said: What error did you exactly get? The ter_*, tef_*.... I got the "telINSUF_FEE_P". Link to post Share on other sites
AlexTheMenace 1 Posted January 4 Author Share Posted January 4 9 hours ago, Duke67 said: I've just briefly checked fees and did not see anything unusual - fee is consistently 10 drops. Hmm...I got the error in testnet. Link to post Share on other sites
tulo 3,333 Posted January 4 Share Posted January 4 I don't know how the load is calculated in rippled, but since it's your nodes, you can always send the transaction as admin and skip that check. The transaction will be sent to the network (with the risk of not passing consensus because of low fee). mDuo13 1 Link to post Share on other sites
nikb 4,390 Posted January 5 Share Posted January 5 The local load fee can be spiky; it’s a product of many factors, including the number of transactions per ledger and the rate of change from ledger to ledger, so it can be a little hard to predict. You said you’re experiencing this on the testnet; I’ll keep an eye out on the fee using https://testnet.xrpl.org/ and see if I notice anything strange. If this is a transient spike, resubmitting the transactions a few seconds later should work. Link to post Share on other sites
xerxesramesepolybius 309 Posted January 6 Share Posted January 6 Well that's one relief Link to post Share on other sites
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now