eos常见错误

最新推荐文章于 2024-04-10 16:46:49 发布
最新推荐文章于 2024-04-10 16:46:49 发布
阅读量9.6k 收藏 2
点赞数
文章标签： eos 区块链 error

EOS 目前大约有180种错误类型，虽然有错误码，但是还是很笼统的，具体的报错信息还得看detail里面的内容:

一、常见的错误码以及issue上对应的错误记录

3010001 Invalid name：账户名格式1-12位（a-z，1-5，“.” ) 且”.”不能在首尾

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3010001

3010004 Invalid authority：检查参数是否填写正确

authorization”: [{
“actor”: “accountname1”,
“permission”: “active”
}]

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3010004

3010008 Invalid block ID

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3010008

3010010 Invalid packed transaction：一般报这个错误就是打包交易的参数传的不正确

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3010010

3010011 Invalid asset：检查资产格式是否正确，如”stake_net_quantity”:”0.0001 EOS” 1.确保正确的精度 空格加Symbol

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3010011

3030000 Block exception

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3030000

3030001 Unlinkable block

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3030001

3030002 Transaction outputs in block do not match transaction outputs from applying block

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3030002

3030003 Block does not guarantee concurrent execution without conflicts

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3030003

3030008 Block is not signed with expected key 检查是否对块信息签名

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3030008

3040000 Transaction exception

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3040000

3040002 Transaction should have at least one normal action：查看action是否添加，是否正确

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3040002

3040005 Expired Transaction：交易过期，过期时间可以设置长一点

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3040005

3040006 Transaction Expiration Too Far：过期时间设置太长

3040007 Invalid Reference Block：引用块无效或不匹配，节点间不同有关

https://github.com/EOSIO/eos/issues/4659

3050000 Action validate exception：检查Action是否正确

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3050000

3050001 Account name already exists：账户名已存在

3050002 Invalid Action Arguments：检查Action参数

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3050002

3050003 eosio_assert_message assertion failure：账户不存在，资产金额不正确等

3060003 Contract Table Query Exception

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3060003

3060004 Contract Query Exception

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3060004

3070002 Runtime Error Processing WASM

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3070002

3080001 Account using more than allotted RAM usage：内存不足，买些内存

3080002 Transaction exceeded the current network usage limit imposed on the transaction：网络资源不足，抵押一些资源

3080004 Transaction exceeded the current CPU usage limit imposed on the transaction：CPU不足，抵押一些CPU

3080006 Transaction took too long

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3080006+

3081001 Transaction reached the deadline set due to leeway on account CPU limits

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3081001

3090003 Provided keys, permissions, and delays do not satisfy declared authorizations：检查权限，签名等是否正确

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3090003

3090004 Missing required authority

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3090004

3110001 Missing Chain API Plugin

https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=3110001

二、EOS 错误码大全

  • 3000000 blockchain exception
  • 3010001 Invalid name
  • 3010002 Invalid public key
  • 3010003 Invalid private key
  • 3010004 Invalid authority
  • 3010005 Invalid action
  • 3010006 Invalid transaction
  • 3010007 Invalid ABI
  • 3010008 Invalid block ID
  • 3010009 Invalid transaction ID
  • 3010010 Invalid packed transaction
  • 3010011 Invalid asset
  • 3010012 Invalid chain ID
  • 3010013 Invalid fixed key
  • 3010014 Invalid symbol
  • 3020000 Fork database exception
  • 3020001 Block can not be found
  • 3030000 Block exception
  • 3030001 Unlinkable block
  • 3030002 Transaction outputs in block do not match transaction outputs from applying block 交易不匹配
  • 3030003 Block does not guarantee concurrent execution without conflicts
  • 3030004 Shard locks in block are incorrect or mal-formed
  • 3030005 Block exhausted allowed resources
  • 3030006 Block is too old to push
  • 3030007 Block is from the future
  • 3030008 Block is not signed with expected key
  • 3030009 Block is not signed by expected producer
  • 3040000 Transaction exception
  • 3040001 Error decompressing transaction
  • 3040002 Transaction should have at least one normal action
  • 3040003 Transaction should have at least one required authority
  • 3040004 Context-free action should have no required authority
  • 3040005 Expired Transaction
  • 3040006 Transaction Expiration Too Far
  • 3040007 Invalid Reference Block
  • 3040008 Duplicate transaction
  • 3040009 Duplicate deferred transaction
  • 3040010 Context free action is not allowed inside generated Transaction
  • 3040011 The transaction can not be found
  • 3040012 Pushing too many transactions at once
  • 3040013 Transaction is too big
  • 3040014 Unknown transaction compression
  • 3050000 Action validate exception
  • 3050001 Account name already exists
  • 3050002 Invalid Action Arguments
  • 3050003 eosio_assert_message assertion failure
  • 3050004 eosio_assert_code assertion failure
  • 3050005 Action can not be found
  • 3050006 Mismatch between action data and its struct
  • 3050007 Attempt to use unaccessible API
  • 3050008 Abort Called
  • 3050009 Inline Action exceeds maximum size limit
  • 3060000 Database exception
  • 3060001 Permission Query Exception
  • 3060002 Account Query Exception
  • 3060003 Contract Table Query Exception
  • 3060004 Contract Query Exception
  • 3060100 Database exception
  • 3060101 Database usage is at unsafe levels
  • 3060102 Reversible block log usage is at unsafe levels
  • 3070000 WASM Exception
  • 3070001 Error in WASM page memory
  • 3070002 Runtime Error Processing WASM
  • 3070003 Serialization Error Processing WASM
  • 3070004 memcpy with overlapping memory
  • 3070005 binaryen exception
  • 3080000 Resource exhausted exception
  • 3080001 Account using more than allotted RAM usage
  • 3080002 Transaction exceeded the current network usage limit imposed on the transaction
  • 3080003 Transaction network usage is too much for the remaining allowable usage of the current block
  • 3080004 Transaction exceeded the current CPU usage limit imposed on the transaction
  • 3080005 Transaction CPU usage is too much for the remaining allowable usage of the current block
  • 3080006 Transaction took too long
  • 3080007 Transaction exceeded the current greylisted account network usage limit
  • 3081001 Transaction reached the deadline set due to leeway on account CPU limits
  • 3090000 Authorization exception
  • 3090001 Duplicate signature included
  • 3090002 Irrelevant signature included
  • 3090003 Provided keys, permissions, and delays do not satisfy declared authorizations
  • 3090004 Missing required authority
  • 3090005 Irrelevant authority included
  • 3090006 Insufficient delay
  • 3090007 Invalid Permission
  • 3090008 The action is not allowed to be linked with minimum permission
  • 3090009 The parent permission is invalid
  • 3100000 Miscellaneous exception
  • 3100001 Internal state is no longer consistent
  • 3100002 Unknown bloc
  • 3100003 Unknown transaction
  • 3100004 Corrupted reversible block database was fixed
  • 3100005 Extracted genesis state from blocks.log
  • 3100006 Subjective exception thrown during block production
  • 3100007 Multiple voter info detected
  • 3100008 Feature is currently unsupported
  • 3100009 Node management operation successfully executed
  • 3110000 Plugin exception
  • 3110001 Missing Chain API Plugin
  • 3110002 Missing Wallet API Plugin
  • 3110003 Missing History API Plugin
  • 3110004 Missing Net API Plugin
  • 3110005 Missing Chain Plugin
  • 3110006 Incorrect plugin configuration
  • 3120000 Wallet exception
  • 3120001 Wallet already exists
  • 3120002 Nonexistent wallet
  • 3120003 Locked wallet
  • 3120004 Missing public key
  • 3120005 Invalid wallet password
  • 3120006 No available wallet
  • 3120007 Already unlocked
  • 3120008 Key already exists
  • 3120009 Nonexistent key
  • 3120010 Unsupported key type
  • 3120011 Wallet lock timeout is invalid
  • 3120012 Secure Enclave Exception
  • 3130000 Actor or contract whitelist/blacklist exception
  • 3130001 Authorizing actor of transaction is not on the whitelist
  • 3130002 Authorizing actor of transaction is on the blacklist
  • 3130003 Contract to execute is not on the whitelist
  • 3130004 Contract to execute is on the blacklist
  • 3130005 Action to execute is on the blacklist
  • 3130006 Public key in authority is on the blacklist
  • 3140000 Exceptions that are allowed to bubble out of emit calls in controller
  • 3140001 Block does not match checkpoint
  • 3150000 ABI exception
  • 3150001 No ABI found
  • 3150002 Invalid Ricardian Clause
  • 3150003 Invalid Ricardian Action
  • 3150004 The type defined in the ABI is invalid
  • 3150005 Duplicate type definition in the ABI
  • 3150006 Duplicate struct definition in the ABI
  • 3150007 Duplicate action definition in the ABI
  • 3150008 uplicate table definition in the ABI
  • 3150009 Duplicate error message definition in the ABI
  • 3150010 ABI serialization time has exceeded the deadline
  • 3150011 ABI recursive definition has exceeded the max recursion depth
  • 3150012 Circular definition is detected in the ABI
  • 3150013 Unpack data exception
  • 3150014 Pack data exception
  • 3160000 Contract exception
  • 3160001 The payer of the table data is invalid
  • 3160002 Table access violation
  • 3160003 Invalid table iterator
  • 3160004 Table can not be found inside the cache
  • 3160005 The table operation is not allowed
  • 3160006 Invalid contract vm type
  • 3160007 Invalid contract vm version
  • 3160008 Contract is already running this version of code
  • 3160009 No wast file found
  • 3160010 No abi file found
  • 3170000 Producer exception
  • 3170001 Producer private key is not available
  • 3170002 Pending block state is missing
  • 3170003 Producer is double confirming known rang
  • 3170004 Producer schedule exception
  • 3170006 The producer is not part of current schedule
  • 3180000 Reversible Blocks exception
  • 3180001 Invalid reversible blocks directory
  • 3180002 Backup directory for reversible blocks already existg
  • 3180003 Gap in the reversible blocks database
  • 3190000 Block log exception
  • 3190001 unsupported version of block log
  • 3190002 fail to append block to the block log
  • 3190003 block log can not be found
  • 3190004 block log backup dir already exists
  • 3200000 http exception
  • 3200001 invalid http client root certificate
  • 3200002 invalid http response
  • 3200003 service resolved to multiple ports
  • 3200004 fail to resolve host
  • 3200005 http request fail
  • 3200006 invalid http request
  • 3210000 Resource limit exception
  • 3220000 Mongo DB exception
  • 3220001 Fail to insert new data to Mongo DB
  • 3220002 Fail to update existing data in Mongo DB
  • 3230000 Contract API exception
  • 3230001 Crypto API Exception
  • 3230002 Database API Exception
  • 3230003 Arithmetic Exception
RedShround
关注
  • 0
    点赞
  • 踩
  • 2
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
EOS错误代码集
12-18
首先，我们来看看EOS错误代码集中的部分常见错误代码及其含义： 1. 错误代码3000000，表示的是区块链异常(blockchainexception)，意味着区块链在执行过程中遇到了非预期的问题。这可能是由于多种原因导致的，需要...
ESD EOS
m0_73549240的博客
04-09 2616
本文从这两种失效的机理入手，首先对芯片的失效背景进行调查，然后借助芯片去层技术对这两种失效的失效位置进行研究，同时利用化学染色技术以及聚焦离子束(FIB)和扫描电子显微镜(SEM)等仪器对失效的微观物理表象进行分析，根据这些差异对短脉冲EOS失效和ESD失效进行推断，最终通过模拟实验验证结果，并对这两种失效路径进行分析，为这两种失效的鉴别提供重要依据，也对产品的可靠性改善起着重要作用。B组样品内部金属走线 (M1，M2，M3)熔化，氧化层熔融，衬底存在大面积烧损，击穿深度约4.34μm。
EOS 错误码整理
agecntao的专栏
07-26 6161
EOS 目前大约有180种错误类型，虽然有错误码，但是还是很笼统的，具体的报错信息还得看detail里面的内容 一、常见的错误码以及issue上对应的错误记录 3010001 Invalid name 账户名格式1-12位（a-z，1-5，“.” ) 且”.”不能在首尾https://github.com/EOSIO/eos/issues?utf8=%E2%9C%93&q=301000...
如何解决 EOSIO 上的常见报错
dfuse 的官方博客
05-21 1884
在 EOSIO 上做开发，用户可能会遇上一些报错信息。有时这些报错信息很不好被理解，导致我们经常在开发群里看到各种截图和问题。 为了帮助刚上手的开发者克服这些挑战，我们对一些最常见报错信息做了一个小总结。 请注意，一些钱包和其它的应用界面可能会对原消息格式做更改，让它更易懂。比如nodeos（EOSIO 的操作软件）的原输出可能会是这样的： { "code": 500, "message": "Internal Service Error", "error": { ...
eos cpu_limit
yhc166188的博客
12-06 1200
Eos中，通过抵押token的方式，提供cpu运算时间以供用户完成交易。 net资源计算方式与cpu类似。 本文旨在理清变量间关系，故略过大部分中间变量，仅记录关联度较大的部分。 在eos测试中，用账号进行高频的transfer（转账）操作，出现了以下报错。 所以决定做一份关于cpu限制的笔记。 3080004 tx_cpu_usage_exceeded: Transaction excee...
EOS常见错误解析
iteye_3782的博客
04-11 1689
EOS常见错误解析 -------------------------------------------------------------------------------- 发布时间:2005-08-19 00:00:00 作者:cservice 出处:goComDevCenter 语言:中文 阅读次数:1304次 【适用范围】 通用 【内容】 1、页面中提...
基于JS实现EOS隐藏错误提示层代码
10-22
在网页开发中，用户交互的反馈是非常重要的，错误提示层就是其中一种常见的方式，它能帮助用户理解输入的信息是否有误。本文主要探讨如何使用JavaScript（JS）来实现EOS（可能是一个框架或库）中的错误提示层的隐藏...
EOS常见问题与解答 .docx
07-31
在使用EOS平台开发过程中，初学者经常会遇到一些常见的问题，这些问题通常涉及到XPath定位错误、文件找不到、调试时自动跳转到登录页面以及Entity找不到或对象名无效等。下面将对这些常见问题进行详细解答。 首先，...
EOS8安装指南
12-04
### EOS8安装指南知识点 #### 一、EOS Platform 8.0 ...综上所述，EOS Platform 8.0 安装指南不仅为用户提供了详细的安装流程说明，还涵盖了各种实用技巧和常见问题解决方案，非常适合初次接触该平台的用户快速上手。
普元EOS7.6安装步骤.pdf
06-12
安装过程可能会遇到各种问题，比如端口冲突、文件权限设置、数据库配置错误等，都可以通过查阅附录中的FAQ来寻找解决方案。此外，对于不同环境下的安装，如Windows系统、Linux系统，安装指南会提供特定的操作步骤和...
EOS错误解决
fxiaoyaole的博客
07-31 3952
今天练习中项目启动报错：Spring Application。。。,"jxt....."在清理项目，更新.classpath，删除项目重新建立都没解决的情况下，采纳另一种办法：删除安装目录apache-tomcat和apps_config，成功启动。此原因：某个项目存在错误，被eos永久记录了，即使删除项目新建项目，此错误记录仍然存在（貌似是tomcat和config中的governor在控制）
docker登录问题
Strong_Foo的博客
04-07 1120
docker login err： Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) solution： 1、在 /etc/resolv.conf 中添加 nameserver 8.8.8.8，nameserver 8.
区块链节点启动报错3190000
最新发布
04-10 489
根据报错信息，出现了’3190000 block_log_exception: Block log exception’的错误，并指出区块日志（block log）中的范围从1到20565，但不包含最后确定性的区块（irreversible block）40430。回滚到最后一个已知的有效快照，然后重新同步区块链数据：可以尝试删除节点的数据文件并重新启动节点，让节点重新同步区块链数据。检查区块链数据文件的完整性：检查并验证区块链数据文件的完整性，确保节点正常读取数据，并且数据文件没有任何损坏。
EOS - 错误码记录
biezhihua的专栏
08-19 2350
Error 3120000: Wallet exception 该错误是由于不小心把默认的钱包文件夹删除了，在/home/xxx/目录下再创建个新的eosio-wallet文件夹就好了。
EOS各种问题汇总，EOS入门必读
区块链斜杠青年(爱踢门)
05-28 7431
传送门     1.【EOS开发环境搭建源码编译】     2.【EOS源码调试】     3.【EOS智能合约开发实践】     4.【主网测试网络实践】 EOS资源问题     消耗的CPU,NET资源何时恢复，目前是一天内不执行任何action,消耗的CPU就会恢复，但是它不是自动恢复的，所以一天后你执行get account会发现消耗的CPU量没有变化。但是你如果执行一个新的a...
EOS错误总结
zjuwzp的博客
12-16 691
1、开启nodeos时，报了一个如下错误 171101ms thread-0 chain_plugin.cpp:209 plugin_initialize ] initializing chain plugin 171102ms thread-0 main.cpp:123 main ] database dirty flag set (likely due to unclean shutdo...
eos报表部署出现的异常，请求指点，不胜感谢
蜜蜂的专栏
04-17 396
这两天在使用eos的报表模块编写报表的时候，碰到如下一个问题，被困扰了好几天，求哪位大虾帮忙解答一下，不胜感谢！问题现象：在开发环境下调试没有问题，可以生成报表；部署到服务器上出现异常，无法生成报表；另外，可以在服务器的 “eos/eosserver/reportServer/output” 下生成报表的临时hmtl文件，里面的表格是正确的，但是表格下方有如下内容： There are err...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值