以太坊監聽pending

⑴ 如何在SLES下配置Bonding

To avoid problems it is advisable that all network cards use the same driver. If they use different drivers, please take the following into consideration:

There are three driver-dependent methods for check whether a network card has a link or a network connection.

* MII link status detection
* Register in the driver netif_carrier
* ARP monitoring

It is very important that the used drivers support the same method. If this is not the case because e.g. the first network card driver only supports MII link status detection whereas the second driver just supports netif_carrier, the only solution is to replace the network card in order to use a different driver.

To find out what method is supported by your driver, proceed as follows:

* MII link status can be determined with the tools mii-tool or ethtool.

* In the case of netif_carrier and ARP monitoring, refer to the driver's source code to find out whether these methods are supported or not. The corresponding kernel sources must be installed for this purpose. Regarding netif_carrier, search exactly for this string in the driver's source code, e.g.

grep netif_carrier via-rhine.c

As for the ARP monitoring method, the driver must support either the register last_rx or trans_start. Thus, you can search in the driver's source code for:

grep "last_rx\|trans_start" via-rhine.c

Start with the setup only after having verified this.
Procere

In this sample scenario, two network cards will be combined by way of bonding mode=1 (active backup).

1. Configure your network cards with YaST. Allocate the IP address that must be used for the bonding device to one network card and a mmy IP address to the rest of network cards.

2. Copy the configuration of the network card with the right IP address to a file ifcfg-bond0.

cd /etc/sysconfig/network
cp ifcfg-eth-id--xx:xx:xx:xx:xx:01 ifcfg-bond0

3. Find out and write down the PCI IDs of all the involved network cards.

For example:

linux:~ # grep bus-pci ifcfg-eth-id--xx:xx:xx:xx:xx:01
_nm_name='bus-pci-0000:00:09.0'
linux:~ # grep bus-pci ifcfg-eth-id--xx:xx:xx:xx:xx:02
_nm_name='bus-pci-0000:00:0a.0'
linux:~ #

4. Edit the file ifcfg-bond0 previously created and insert the following lines.

BONDING_MASTER=yes
BONDING_SLAVE_0='bus-pci-0000:00:09.0'
BONDING_SLAVE_1='bus-pci-0000:00:0a.0'

Now insert the options for the bonding mole. Depending on what link detection method you are using, the line may look like this:
* MII link detection method
BONDING_MODULE_OPTS='miimon=100 mode=1 use_carrier=0'

* netif_carrier method
BONDING_MODULE_OPTS='miimon=100 mode=1 use_carrier=1'

* ARP monitoring method
BONDING_MODULE_OPTS='arp_interval=2500 arp_ip_target=192.168.1.1 mode=1'

5. Remove the old configuration files

linux:~ # rm ifcfg-eth-id--xx:xx:xx:xx:xx:01
linux:~ # rm ifcfg-eth-id--xx:xx:xx:xx:xx:02

6. Restart the network with

rcnetwork restart

Additional Information

Occasionally it has been experienced that not all network interfaces come up after a system reboot. To prevent this, the loading of the moles should start earlier ring the reboot process. The following procere is helpful in this case:

1. Edit the file /etc/sysconfig/kernel and add this line:

MODULES_LOADED_ON_BOOT="bcm5700"

2. Reboot the server and check the status of all network interfaces, using commands lspci and ifconfig.

3. If this method is not successful, edit the file /etc/sysconfig/kernel again and remove the line inserted at step 1. Modify the line containing the INITRD_MODULES statement; add the bcm5700 to this line. It should read like INITRD_MODULES="cdrom scsi_mod ide-cd ehci-hcd reiserfs bcm5700"

4. Call command mkinitrd

5. Reboot the server as in step 2

Another method is to delay the starting of the network interfaces after loading the moles. To do this, edit the file /etc/sysconfig/network/config and change the variable WAIT_FOR_INTERFACES to the wanted delay in seconds. To delay the interfaces 3 seconds, enter

WAIT_FOR_INTERFACES=3

Reboot the server to verify the success of this measure.

當然也可以採用一些簡單的辦法，例如直接修改 /etc/init.d/network 網路啟動腳本。
在start) 部分的結尾處添加 ipbonding 的手工腳本，例如：

ifconfig eth0 0.0.0.0
ifconfig eth1 0.0.0.0
modprobe bonding miimon=100 mode=1 use_carrier=1
ifconfig bond0 192.168.1.123 netmask 255.255.255.0
ifenslave bond0 eth0
ifenslave bond0 eth1
route add default gw 192.168.1.1

然後在 stop) 部分開始考慮添加：
ifdown bond0
rmmod bonding

⑵ 電腦藍屏 0x000000CERIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

代碼名：0x0000000A

描述：環境不正確。 停機代碼 0x0000000A: IRQL_NOT_LESS_OR_EQUAL ◆錯誤分析:主要是由有問題的驅動程序，有缺陷或不兼容的硬體與軟體造成的。從技術角度講，表明在內核模式中存在以太高的進程內部請求級別(IRQL)訪問其沒有許可權訪問的內存地址。 實例1:在安裝Windows 2000/XP 時出現 除檢查硬體是否符合兼容性列表外，還應採取以下措施。 (1)在安裝啟動過程中，當「Setup is inspecting yourcomputer's hardware configuration」消息出現時按F5 鍵，當得到提示時，指定正確的計算機類型和硬體抽象層 (HAL)。一般用戶(只安裝了一個CPU)，請指定「Standard PC HAL」。 (2)關閉CMOS 設置中所有緩存及映射(shadowing)設置項、即插即用選項以及病毒保護功能。 (3)斷開那些對於電腦啟動非必需的硬體，包括網卡、內置數據機、音效卡、第二塊硬碟。同時檢查硬碟的跳線是否設置為主跳線，並檢查光碟機的跳線是否正確。 (4)如果是從Windows 2000 升級到Windows XP，還需要卸載所有殺毒軟體和啟動管理軟體(比如:Norton GoBack等)，並且去掉所有不必要的硬體，斷開所有USB 設備和列印機。 實例2:在使用Windows 2000/XP 時出現 (1)檢查最新安裝的軟體和硬體驅動程序卸載或禁用它們，推薦使用安全模式來完成這個任務，如果是驅動程序，則推薦使用Windows XP 的驅動程序返回功能來恢復原有的驅動程序。 (2)如果Windows 無法啟動首先嘗試使用「最後一次正確配置」來解決問題。如果無效，則按照下面的方法來解決。 ★ Windows XP:使用安裝光碟進入故障恢復控制台，運行「%systemroot%\system32\restore\rstrui.exe」命令，然後按照提示進行系統還原操作即可。 ★ Windows 2000:記下藍屏信息中顯示的文件名，找到一台和你的電腦軟、硬體配置類似的電腦，打開「注冊表編輯器」，找到[ H K E Y _ L O C A L _ M A C H I N E \ S Y S T E M\CurrentControlSet\Services]，這里保存了系統中每一個設備、服務的注冊信息，請細細查看每條信息，特別是右側窗格中的「DiskPlayName」，一些驅動程序會在這里標明設備驅動用途的描述，另外，在「ImagePath」鍵值後面有相應文件名，這也是關注的要點，需要對照你抄下來的文件名。用Windows 2000 安裝光碟進入「故障恢復控制台」，接著進入C:\WINNT\System32 目錄，輸入「listsvc」，回車後會列出當前系統所安裝的服務或設備，找到並記下與新裝硬體或軟體相關的服務或設備名，然後輸入「disable 服務或設備名」，回車即可將其停止。

⑶ 以太坊架構是怎麼樣的

以太坊最上層的是DApp。它通過Web3.js和智能合約層進行交換。所有的智能合約都運行在EVM（以太坊虛擬機）上，並會用到RPC的調用。在EVM和RPC下面是以太坊的四大核心內容，包括：blockChain, 共識演算法，挖礦以及網路層。除了DApp外，其他的所有部分都在以太坊的客戶端里，目前最流行的以太坊客戶端就是Geth（Go-Ethereum）

⑷ 以太坊如何使用web3.js或者rpc介面獲取交易數據交易時間與確認數

如果要查詢主網上的交易記錄，可以使用etherscan。但是，如果是你自己搭建的私鏈，應該如何查詢交易記錄呢？

答案是你需要自己監聽鏈上的日誌，存到資料庫里，然後在這個資料庫中查詢。例如：

varaddr=""
varfilter=web3.eth.filter({fromBlock:0,toBlock:'latest',address:addr});
filter.get(function(err,transactions){
transactions.forEach(function(tx){
vartxInfo=web3.eth.getTransaction(tx.transactionHash);
//這時可以將交易信息txInfo存入資料庫
});
});

web3.eth.filter()用來監聽鏈上的日誌，web3.eth.getTransaction()用來提取指定交易的信息，一旦獲得交易信息，就可以存入資料庫供查詢用了。

推薦一個實戰入門，你可以看看：以太坊教程