updated code and clients are posted if you get sick of looking at the warning::::
https://github.com/hyperstake/HyperStake/releases/tag/1.1.1.2
Topic: [HYP] HyperStake | Generous Reward Staking | Advanced Staking Controls & Wallet - page 140. (Read 679332 times)
May 29, 2015, 12:31:54 PM
May 29, 2015, 12:27:06 PM
Anyone seeing the synccheckpoint is too old error? We don't use a checkpoint server so I am going to delete this shitty line of code for the next wallet release.
Also I am going to be out of town from Saturday the 30th to Saturday the 6th, with little to no internet. Am giving the janitors keys to trusted members of the community while I am gone.
Also I am going to be out of town from Saturday the 30th to Saturday the 6th, with little to no internet. Am giving the janitors keys to trusted members of the community while I am gone.
I just started seeing this. It didn't seem to have any effect on minting, so I didn't pay much attention to it.
I'm glad to know that it's a benign warning.
May 29, 2015, 12:15:26 PM
It cracks me up looking at the commit history of some of the other coins around here. Usually has one or two. Also the cool thing about HYP is how many different users have made commits.
May 29, 2015, 02:34:56 AM
pi@raspberrypi ~ $ cat /etc/dphys-swapfile
CONF_SWAPSIZE=512
pi@raspberrypi ~ $
Thanks, i'll swap it right away. CONF_SWAPSIZE=512
pi@raspberrypi ~ $
May 29, 2015, 12:59:03 AM
May 29, 2015, 12:02:59 AM
Anyone seeing the synccheckpoint is too old error? We don't use a checkpoint server so I am going to delete this shitty line of code for the next wallet release.
Also I am going to be out of town from Saturday the 30th to Saturday the 6th, with little to no internet. Am giving the janitors keys to trusted members of the community while I am gone.
Also I am going to be out of town from Saturday the 30th to Saturday the 6th, with little to no internet. Am giving the janitors keys to trusted members of the community while I am gone.
Badges? We don't need no stinking badges!
also
... and the moral of the story? All my online passwords should be banking strength!
Thou hast reclaimed your identity?
shiiiiiit yes! I made theymos an offer he couldn't refuse (OR I came up with a convincing enough method to confirm my ID that he was really lax on me. Did confirm that my account was hacked though which sucks. First time thats happened to me)
May 29, 2015, 12:00:41 AM
updated the latest build to get rid of the checkpoint server warnings.
https://github.com/hyperstake/HyperStake/releases/tag/v1.1.1.0
https://github.com/hyperstake/HyperStake/releases/tag/v1.1.1.0
May 28, 2015, 10:44:09 PM
Anyone seeing the synccheckpoint is too old error? We don't use a checkpoint server so I am going to delete this shitty line of code for the next wallet release.
Also I am going to be out of town from Saturday the 30th to Saturday the 6th, with little to no internet. Am giving the janitors keys to trusted members of the community while I am gone.
Also I am going to be out of town from Saturday the 30th to Saturday the 6th, with little to no internet. Am giving the janitors keys to trusted members of the community while I am gone.
May 28, 2015, 09:42:17 PM
well i got PM about RPI and HYP daemon issue since i compiled it earlier but deleted it accidently that PM and dont know who sent it to me. Sharing my experience here might it will help that person.
being a noob it took me a week to compile 2 wallets on RPi and learn basics of Linux
after bootstraping if not wrong it took around 2 days for wallet to run so just keep it intact bcoz it during the process your RPi will be frozen due to its limited resources.
if not mistaken white screen issue i read somewhere on RPi forums that it is bcoz of mem of RPI so i swap it to 512MB using following commands to use max of ram
pi@raspberrypi ~ $ cat /etc/dphys-swapfile
CONF_SWAPSIZE=512
pi@raspberrypi ~ $
i used tight VNC which has task manager option so it helped me to kill/stop and task since PID thingy is kind a hell for the beginer.
now i m running multiple wallets in each RPi without any issues.
being a noob it took me a week to compile 2 wallets on RPi and learn basics of Linux
after bootstraping if not wrong it took around 2 days for wallet to run so just keep it intact bcoz it during the process your RPi will be frozen due to its limited resources.
if not mistaken white screen issue i read somewhere on RPi forums that it is bcoz of mem of RPI so i swap it to 512MB using following commands to use max of ram
pi@raspberrypi ~ $ cat /etc/dphys-swapfile
CONF_SWAPSIZE=512
pi@raspberrypi ~ $
i used tight VNC which has task manager option so it helped me to kill/stop and task since PID thingy is kind a hell for the beginer.
now i m running multiple wallets in each RPi without any issues.
May 28, 2015, 09:30:59 PM
... and the moral of the story? All my online passwords should be banking strength!
Thou hast reclaimed your identity?
May 28, 2015, 09:01:09 PM
... and the moral of the story? All my online passwords should be banking strength!
May 28, 2015, 04:10:11 PM
or killall hyperstaked...
for segmentation fault, by chance, have you tried recookin? I get that time to time on my lower power vm. IF that wont sort it out, maybe try increasing swap size?
Ugh i'm done cooking for today. I'll do it tomorrow and see how it goes.for segmentation fault, by chance, have you tried recookin? I get that time to time on my lower power vm. IF that wont sort it out, maybe try increasing swap size?
My swap should be 64 mb i'll bring it to 128
May 28, 2015, 04:06:15 PM
or killall hyperstaked...
for segmentation fault, by chance, have you tried recookin? I get that time to time on my lower power vm. IF that wont sort it out, maybe try increasing swap size?
for segmentation fault, by chance, have you tried recookin? I get that time to time on my lower power vm. IF that wont sort it out, maybe try increasing swap size?
May 28, 2015, 03:45:39 PM
Yeah,about mid afternoon i gave up and started the deamon, i remembered about it just now.
But thx for the trick, i'll write it down somewhere
But thx for the trick, i'll write it down somewhere
May 28, 2015, 03:41:42 PM
The QString errors have been fixed in the newer wallets. But it shouldnt be impacting your ability to start up the wallet. When bootstrapping, your client is supposed to hang on the splashscreen for quite some time.
K. Compiling again.Edit: Found one problem. The deamon was running the whole time and preventing the wallet from starting.
Heres the other one:
Code:
EGLFS: Unable to query physical screen size, defaulting to 100 dpi.
EGLFS: To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters).
EGLFS: Unable to query screen depth, defaulting to 32.
EGLFS: To override, set QT_QPA_EGLFS_DEPTH.
Segmentation fault
Can't help yo with that one, but the "can't bind" error ALWAYS means an instance is running. In most versions of linux (don't know RPi, so I could be wrong) you can type "top" in a terminal and it will show you all running instances of everything. If you see hyperstaked when you shouldn't, note down it's PID number, exit top by hitting ctrl-c, and then type kill
It took me FOREVER to find that simple little trick, so forgive me if you already knew it
May 28, 2015, 12:55:29 PM
The QString errors have been fixed in the newer wallets. But it shouldnt be impacting your ability to start up the wallet. When bootstrapping, your client is supposed to hang on the splashscreen for quite some time.
K. Compiling again.Edit: Found one problem. The deamon was running the whole time and preventing the wallet from starting.
Heres the other one:
Code:
EGLFS: Unable to query physical screen size, defaulting to 100 dpi.
EGLFS: To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters).
EGLFS: Unable to query screen depth, defaulting to 32.
EGLFS: To override, set QT_QPA_EGLFS_DEPTH.
Segmentation fault
ha you think the bootstrap takes a long time try sync'in from scratch
I usually do that. I'm kind of an impatient guy, if i see a splash screen with "Loading bootstrap plz wait" i get mad. Whereas if i leave the wallet running all night i have the lil thingy that says exactly the progress and how many blocks are left. May 28, 2015, 12:51:03 PM
The QString errors have been fixed in the newer wallets. But it shouldnt be impacting your ability to start up the wallet. When bootstrapping, your client is supposed to hang on the splashscreen for quite some time.
May 28, 2015, 12:49:19 PM
Installed precompiled version, i get this:
Terminal log:
Code:
HyperStake
Unable to bind to 0.0.0.0:18775 on this computer. HyperStake is probably already running.
Code:
HyperStake
Failed to listen on any port. Use -listen=0 if you want this.
Code:
QGtkStyle was unable to detect the current GTK+ theme.
QString::arg: Argument missing: Not minting because wallet is offline.
Network weight is 0.
MultiSend: 0, Active
QString::arg: Argument missing: Not minting because wallet is offline.
Network weight is 0.
MultiSend: 0, Active
QString::arg: Argument missing: Not minting because wallet is offline.
Network weight is 0.
MultiSend: 0, Active
Many more...
May 28, 2015, 12:34:33 PM
ha you think the bootstrap takes a long time try sync'in from scratch
Could always trim off the blocks
May 28, 2015, 12:31:52 PM
ha you think the bootstrap takes a long time try sync'in from scratch
Jump to: