so I just sit there and the block chain does not update, tried to get the partial down load and all sorts of things nope nope nope...
Set "communicationLoggingMask" to "3". It's in web.xml.
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2201. (Read 2761632 times)
Set "communicationLoggingMask" to "3". It's in web.xml.
so I just sit there and the block chain does not update, tried to get the partial down load and all sorts of things nope nope nope...
Working on node infrastructure with a full redesign of nxtbase to support 100+. I won't open source my new management stuff for a bit, but here's a handy one for you VPSers running ubuntu.
Then copy file like this to /etc/supervisor/conf.d/nrs.conf:
Replace $MIN and $MAX with your memory limits. Replace $USER with your user. The run:
Now, what do you get for your efforts?
Restart on crash
Restart on reboot
handy commands for start/stop/restart/status (sudo supervisorctl CMD nrs).
Cool huh?
Code:
$ sudo apt-get install --yes supervisor
$ sudo service supervisor restart
$ sudo service supervisor restart
Then copy file like this to /etc/supervisor/conf.d/nrs.conf:
Code:
[program:nrs]
command=java -Xms$MIN -Xmx$MAX -jar start.jar
autostart=true
autorestart=true
stderr_logfile=/home/$USER/nxt/logs/stderr.log
stdout_logfile=/home/$USER/nxt/logs/stdout.log
user=$USER
directory=/home/$USER/nxt
command=java -Xms$MIN -Xmx$MAX -jar start.jar
autostart=true
autorestart=true
stderr_logfile=/home/$USER/nxt/logs/stderr.log
stdout_logfile=/home/$USER/nxt/logs/stdout.log
user=$USER
directory=/home/$USER/nxt
Replace $MIN and $MAX with your memory limits. Replace $USER with your user. The run:
Code:
$ sudo supervisorctl reread
$ sudo supervisorctl update
$ sudo supervisorctl status
$ sudo supervisorctl update
$ sudo supervisorctl status
Now, what do you get for your efforts?
Restart on crash
Restart on reboot
handy commands for start/stop/restart/status (sudo supervisorctl CMD nrs).
Cool huh?
This deserves to be quoted again, thank you! Edit: Lol, just noticed someone quoted two posts earlier.
I am in negative now ?? there was 59000 on my account, wrong blocks?
I had the same problem. Scared the hell out of me.
Solved by restarting client.
Yea that was weird... just happened to me too. Account went to negative balance and it looked like the coins were sent out, restart fixed it though.
Working on node infrastructure with a full redesign of nxtbase to support 100+. I won't open source my new management stuff for a bit, but here's a handy one for you VPSers running ubuntu.
Then copy file like this to /etc/supervisor/conf.d/nrs.conf:
Replace $MIN and $MAX with your memory limits. Replace $USER with your user. The run:
Now, what do you get for your efforts?
Restart on crash
Restart on reboot
handy commands for start/stop/restart/status (sudo supervisorctl CMD nrs).
Cool huh?
Code:
$ sudo apt-get install --yes supervisor
$ sudo service supervisor restart
$ sudo service supervisor restart
Then copy file like this to /etc/supervisor/conf.d/nrs.conf:
Code:
[program:nrs]
command=java -Xms$MIN -Xmx$MAX -jar start.jar
autostart=true
autorestart=true
stderr_logfile=/home/$USER/nxt/logs/stderr.log
stdout_logfile=/home/$USER/nxt/logs/stdout.log
user=$USER
directory=/home/$USER/nxt
command=java -Xms$MIN -Xmx$MAX -jar start.jar
autostart=true
autorestart=true
stderr_logfile=/home/$USER/nxt/logs/stderr.log
stdout_logfile=/home/$USER/nxt/logs/stdout.log
user=$USER
directory=/home/$USER/nxt
Replace $MIN and $MAX with your memory limits. Replace $USER with your user. The run:
Code:
$ sudo supervisorctl reread
$ sudo supervisorctl update
$ sudo supervisorctl status
$ sudo supervisorctl update
$ sudo supervisorctl status
Now, what do you get for your efforts?
Restart on crash
Restart on reboot
handy commands for start/stop/restart/status (sudo supervisorctl CMD nrs).
Cool huh?
Thanks!
Yeah, I meant it works for those zombies?
If u switch hallmark protection off then ur node will start picking peers randomly like all of them have equal weight.
Right. And zombies too. So I better keep it to true
The whales are buying up a lot of NXT today on dgex.com
Working on node infrastructure with a full redesign of nxtbase to support 100+. I won't open source my new management stuff for a bit, but here's a handy one for you VPSers running ubuntu.
will it work on debian 7 x64?Code:
$ sudo apt-get install --yes supervisor
$ sudo service supervisor restart
$ sudo service supervisor restart
It should. Let us know!
i got the supervisor thing installed. do i also need to install nxtbase or what? where does my web.xml go?
Doesn't need nxtbase. web.xml goes in it's normal spot.
Yeah, I meant it works for those zombies?
If u switch hallmark protection off then ur node will start picking peers randomly like all of them have equal weight.
last hour:
just a question. i bought 30 hours ago 85 nxt over dgex.com and transfered them to my nxt wallet. After 2 hours my transaction has only 1200 confirmations. How long does the last confirmations take so that i can forge my coins?
cheers,
cheers,
1440
i mean how many time does the last 240 confirmations take? The FAQ says about 24 hours for all confirmations.
One block/confirmation per min on average, so approximately 240 min left
DDOS just killed the node with HallMark protection intentionally set to false. Setting it to true now.
True/false works for outbound requests only. It doesn't change hallmark status of the node it's set on.
Yeah, I meant it works for those zombies?
just a question. i bought 30 hours ago 85 nxt over dgex.com and transfered them to my nxt wallet. After 2 hours my transaction has only 1200 confirmations. How long does the last confirmations take so that i can forge my coins?
cheers,
cheers,
1440
i mean how many time does the last 240 confirmations take? The FAQ says about 24 hours for all confirmations.
Does anyone know of a Linux terminal grapher of bandwidth usage over time?
iftop does a good enough job imho. Shows you instantaneous bitrates as well as averaged bitrates, also aggregated data volumes.
DDOS just killed the node with HallMark protection intentionally set to false. Setting it to true now.
True/false works for outbound requests only. It doesn't change hallmark status of the node it's set on.
Quote
Next time try to refresh the web page. Blocks should appear again.
That didn't work for me last time.
Didn't work for me either, had to restart the process
yes i see another fork starting after 24101
This is normal and called orphaned blocks. Bitcoin has the same issue, 1 min between blocks greatly increases number of orphans.
Quote
Next time try to refresh the web page. Blocks should appear again.
That didn't work for me last time.
I can not transfer money to someone I have problems when transferring to another account? Deadline 1 hours.
just a question. i bought 30 hours ago 85 nxt over dgex.com and transfered them to my nxt wallet. After 2 hours my transaction has only 1200 confirmations. How long does the last confirmations take so that i can forge my coins?
cheers,
cheers,
1440
Jump to: