Topic: CryptoCoin Explorer - Coin Block Explorers. - page 15. (Read 30831 times)
I moved the DNS back to the primary. I will wait and see and hope.
This might require a database rebuild.
I would doubt it, just an SQL update of chain_code3.
Thank you. That just saved me the trouble of rebuilding.
This is starting to look like an attack. The backup server (which is at the same same level as the primary), was knocked completely out within a very short period of time. CPU usage >200% and traffic so locked up I could not SSH into it.
On the primary server, all I have done is change all the passwords, and magically every works like normal. I have switched the DNS back to the primary and if it goes down again, I will have to keep both servers down until this gets sorted.
Something strange is going on with the server and the error pages suddenly coming up. I have switched over to the backup server and DNS should propagate soon.
The back-up IP address is : 198.58.105.9
The back-up IP address is : 198.58.105.9
This might require a database rebuild.
I would doubt it, just an SQL update of chain_code3.
The coin formerly known as FC is now called FTC
As soon as I get official word from bushstar, I will work on changing the code 3 for Feathercoin.
This might require a database rebuild.
The coin formerly known as FC is now called FTC
Just what we needed in the cryptocoin community: a Federal Trade Commission.
The coin formerly known as FC is now called FTC
PS: Thank you for the donation 
Who says it was me?
Would people ever do searchs that have a whitespace in the middle of the search term? I tend to think of all searches being hashes and block numbers. If spaces should never happen, you could do a little script to remove them on submission.
You are correct..I will add that to the "list"
I was also thinking about opening the backup CCE for site owners that use the explorer API on CCE.
I think this would be good for three reasons:
1. Free up traffic on the public CCE site, giving regular users a faster system, and site owners faster API response.
2. The public site is more apt to go down due to overload, malicious acts, or even unintentional bad queries. As only sites using the API would have access to the backup CCE, sites depending on CCE would not be effected in terms of a break in service. However, the backup site primary purpose is to make an easy switch over in case the primary CCE site goes down. So if the Public site goes down, i will switch the DNS of the public site to point to the backup site until the public site is back up.
3. I can cater the backup CCE site to the needs of API users and in the reverse tune the public site for regular users.
Would people ever do searchs that have a whitespace in the middle of the search term? I tend to think of all searches being hashes and block numbers. If spaces should never happen, you could do a little script to remove them on submission.
I don't know if I've found a bug, or if you're just keeping some data out for privacy:
If I plug this transaction ID into bytecoin chain search:
9a450a3d2c252d18f058dc78321cc3ec872668ed7230b8cd5a862b95e7568f79
I see 10.0 BTE that went to 8KavvVegRXmYRUetYEEA1rMCrLjuZzmyrg (your BTE donation address).
But if I plug that address into search, I have been consistently getting "not found" for days.
This never worked until I searched by transaction ID.
Caching issue?
If I plug this transaction ID into bytecoin chain search:
9a450a3d2c252d18f058dc78321cc3ec872668ed7230b8cd5a862b95e7568f79
I see 10.0 BTE that went to 8KavvVegRXmYRUetYEEA1rMCrLjuZzmyrg (your BTE donation address).
But if I plug that address into search, I have been consistently getting "not found" for days.
This never worked until I searched by transaction ID.
Caching issue?
I can pull it up ok:
Code:
Address 8KavvVegRXmYRUetYEEA1rMCrLjuZzmyrg
Short Link: http://cryptocoinexplorer.com:7750/a/8KavvVegRX
Balance: 10 BTE
Transactions in: 1
Received: 10 BTE
Transactions out: 0
Sent: 0 BTE
Transactions
Transaction Block Approx. Time Amount Balance Currency
9a450a3d2c... 15216 2013-04-26 02:53:26 10 10 BTE
API (machine-readable pages)
I have gotten a few messages about searches that do not work over the time CCE has been up. This first thing to check, is to make sure you have no spaces at the beginning or end of the search term, as the search is white space sensitive.
PS: Thank you for the donation
I don't know if I've found a bug, or if you're just keeping some data out for privacy:
If I plug this transaction ID into bytecoin chain search:
9a450a3d2c252d18f058dc78321cc3ec872668ed7230b8cd5a862b95e7568f79
I see 10.0 BTE that went to 8KavvVegRXmYRUetYEEA1rMCrLjuZzmyrg (your BTE donation address).
But if I plug that address into search, I have been consistently getting "not found" for days.
This never worked until I searched by transaction ID.
Caching issue?
If I plug this transaction ID into bytecoin chain search:
9a450a3d2c252d18f058dc78321cc3ec872668ed7230b8cd5a862b95e7568f79
I see 10.0 BTE that went to 8KavvVegRXmYRUetYEEA1rMCrLjuZzmyrg (your BTE donation address).
But if I plug that address into search, I have been consistently getting "not found" for days.
This never worked until I searched by transaction ID.
Caching issue?
QUICK GUIDE CCE API USAGE
All CCE explorers have an API for both utility and detailed information. The API is capable of both comma separated and JSON outputs with the nethash command. The exception is the Novacoin explorer, as it is based on an older version of ABE. Append “?format=json” to the url.
The API for any of the explorers can be accessed using the following patterns:
http://cryptocoinexplorer.com:
or
http://cryptocoinexplorer.com:
Port = The explorer port for the coin you want to use.
PPC=2750
TRC=3750
FRC=4750
FC=5750
NVC=6750
BTE=7750
chain = The literal word “chain”, no need to change
Coin Name = Except for PPCoin, Coin Name is First character upper case, the rest lower case. Example: Terracoin
q = literal “q”
Examples:
Returns the version encoded in ADDRESS as a hex string.
If ADDRESS is invalid, returns either X5, SZ, or CK for BBE compatibility.
/q/checkaddress/ADDRESS
http://cryptocoinexplorer.com:2750/q/checkaddress/PAYCKSPFGRUdWPyYt2pDs1WYXdPEkah9Qy
Shows statistics every INTERVAL blocks.
Negative values count back from the last block.
/chain/CHAIN/q/nethash[/INTERVAL[/START[/STOP]]]
http://cryptocoinexplorer.com:5750/chain/Feathercoin/q/nethash/100/1000/2000
or
http://cryptocoinexplorer.com:5750/chain/Feathercoin/q/nethash/100/1000/2000?format=json
Shows ADDRESS's version byte(s) and public key hash as hex strings separated by colon (":").
/q/decode_address/ADDRESS
http://cryptocoinexplorer.com:4750/q/decode_address/6xRWJA31C1p2fuZg8cT9Y9iwLAUb9ZeKUE
Shows the amount of currency ever mined.
This does not support future block numbers, and it returns a sum of observed generations rather than a calculated value.
/chain/CHAIN/q/totalbc[/HEIGHT]
http://cryptocoinexplorer.com:2750/chain/PPCoin/q/totalbc/40000
I hope this post gives enough basic information to allow one to figure out the API if they wish to use it.
Descriptions of all the functions can be found by clicking the API link on each every page or directly by simply using a "q" after the port.
Example: http://cryptocoinexplorer.com:2750/q
PPC explorer is broken right now
class '_mysql_exceptions.ProgrammingError'>: (2014, "Commands out of sync; you can't run this command now")
args = (2014, "Commands out of sync; you can't run this command now")
class '_mysql_exceptions.ProgrammingError'>: (2014, "Commands out of sync; you can't run this command now")
args = (2014, "Commands out of sync; you can't run this command now")
The errors should be gone now.
After a bit of research I found this is a quirk of MySQL that can happen often if someone (Like me
) is accessing Mysql through the console while other processes are working with Mysql at the same time.I just happened to be accessing the databases from console around the time you were getting those errors.
As I rarely directly access the databases through console, especially while the explorers are running, this error has not been noticed before.
Lesson learned, I will be more careful in the future and possibly switch to the back up if I need to directly access Mysql databases while the explorers are live.
PPC explorer is broken right now
class '_mysql_exceptions.ProgrammingError'>: (2014, "Commands out of sync; you can't run this command now")
args = (2014, "Commands out of sync; you can't run this command now")
class '_mysql_exceptions.ProgrammingError'>: (2014, "Commands out of sync; you can't run this command now")
args = (2014, "Commands out of sync; you can't run this command now")
In light of what happened Friday(4/26), I have purchased a VPS from a different provider to act as backup. The backup server is fully operational and the databases are updated as if it were a running CCE site.
On the backup VPS, the web server is shut down.
If the need arises I can simply bring the web server up and change the DNS record for CCE to point to the backup server.
On the backup VPS, the web server is shut down.
If the need arises I can simply bring the web server up and change the DNS record for CCE to point to the backup server.
The Terracoin explorer is back online..
It looks as if the Terracoin database is corrupted.
I have temporary shut down the TRC explorer until the database is reconstructed.
I have temporary shut down the TRC explorer until the database is reconstructed.
The CCE server is back, (Just as I was about to bring the second server up..... 
)
I had to take the web server down for a few to allow the explorers to get caught up and reconstruct the BTE database which got corrupted in the shutdown.
CCE was getting hit so hard by web requests that the explorers were having a hard time catching up with a days worth of blocks
Anyway, I have the web server back up and I will keeps a close eye on it.
)I had to take the web server down for a few to allow the explorers to get caught up and reconstruct the BTE database which got corrupted in the shutdown.
CCE was getting hit so hard by web requests that the explorers were having a hard time catching up with a days worth of blocks
Anyway, I have the web server back up and I will keeps a close eye on it.
Jump to: