Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

BDB exception in Bitcoin-Qt (0.6.2 / Windows 7 x64 SP1) #1165

Closed
Diapolo opened this issue Apr 29, 2012 · 4 comments
Closed

BDB exception in Bitcoin-Qt (0.6.2 / Windows 7 x64 SP1) #1165

Diapolo opened this issue Apr 29, 2012 · 4 comments

Comments

@Diapolo
Copy link

Diapolo commented Apr 29, 2012

  • start instance 1 in DataDir_1 listening on port 8333 -> OK
  • start instance 2 in DataDir_2 listening on port 8333, too -> hard crash of instance 2 after message that client could not be bound to port 8333

From the debug.log of instance 2:
04/29/12 22:06:48 EnvShutdown exception: DbEnv::close: Invalid argument (22)

No further GUI exception was displayed at all, as I wrote a hard crash! Guess this is something for @sipa / @laanwj.
@Diapolo
Copy link
Author

Diapolo commented May 11, 2012

I should have mentioned this happens with the Qt version ... could anyone verify this behaviour?

@Diapolo
Copy link
Author

Diapolo commented May 18, 2012

Still present with official 0.6.2:

05/18/12 11:18:32 Fehler beim registrieren des Ports 8333 auf diesem Computer. Evtl. wurde Bitcoin bereits gestartet.
05/18/12 11:18:34 05/18/12 11:18:34 Flushing wallet.dat
05/18/12 11:18:34 Flushed wallet.dat 10ms
05/18/12 11:18:40 EnvShutdown exception: DbEnv::close: Invalid argument (22)

@sipa
Copy link
Member

sipa commented May 18, 2012

Sounds like maybe EnvShutdown is called before the DbEnv is initialized.

@Diapolo
Copy link
Author

Diapolo commented Aug 18, 2012

Also fixed with current master, 2 error messages are displayed but no crash occurs, good :) -> closed.

@Diapolo Diapolo closed this as completed Aug 18, 2012
lateminer pushed a commit to lateminer/bitcoin that referenced this issue Dec 25, 2019
@furszy
Merge bitcoin#1165: [GUI][Bug] Cold staking screen, total amount was …
c54dad3 
…not being updated.

5b901ee [GUI] Removing cold staking "unconfirmed balance will not be shown" warning label. (furszy)
811fb41 [Wallet] GetAvailableP2CSCoins permitting unconfirmed tx. (furszy)
fe4a9b0 [GUI] Cold staking, always update staking total amount (furszy)
6bf8770 [GUI][Bug] Cold staking screen, delegations list, total amount was not being updated. This solves the issue + re organize the UI form to present it aligned to the texts in the left. (furszy)

Pull request description:

  The total amount in the cold staking screen (delegations list section) was not being updated. This solves the issue + re organize the UI form to present it aligned to the texts in the left.

ACKs for top commit:
  random-zebra:
    ACK 5b901ee
  Fuzzbawls:
    utACK 5b901ee

Tree-SHA512: f0aff6a1203b1d91b7eafe2a27bf04d02122093409a489f0008be1c62567285c62b4d1fbaaad62b6361a999b633240bec5d711e48771626311ad948a8c8bc91c
dexX7 added a commit to dexX7/bitcoin that referenced this issue Sep 23, 2020
@dexX7
Merge bitcoin#1165: Add bitcore indexing
ec116e4 
5e6d739 Add Bitcore indexing to Omnicore (Peter Bushnell)

Pull request description:

  This adds the following RPC calls to the Omni client, to access them configure needs to be run with <code>--enable-bitcore-rpc</code>, indexing needs to be enabled in bitcoin.conf file with <code>addressindex=1</code>.

  ```
  getaddresstxids
  Returns the txids for an address(es)
  ```
  ```
  getaddressdeltas
  Returns all changes for an address
  ```
  ```
  getaddressbalance
  Returns the balance for an address(es)
  ```
  ```
  Returns all unspent outputs for an address
  getaddressutxos
  ```
  ```
  getaddressmempool
  Returns all mempool deltas for an address
  ```
  ```
  getblockhashes
  Returns array of hashes of blocks within the timestamp range provided
  ```
  ```
  getspentinfo
  Returns the txid and index where an output is spent
  ```

Tree-SHA512: 331e4f529c34513bf8e1595799dd5d89d758988503e1eec4f8bc1ec713bfc107eadb48051933799fecce9b2568f0b43f5a56771dbc838e4bd7068881dfbc5b95
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sipa @Diapolo