liskarchive/lisk-build

🏗️ Lisk binary package building tool

lisk-build's Issues

Correct user check failure`

When shellcheck was introduced some text wrapping changed and this has caused the user check for root to fail. This should be resolved so users dont get unexpected issues when installing.

Signed and checksummed Lisk files

From: LiskArchive/lisk-sdk#53

There should be a way for a delegate to check the integrity of the lisk core files and lisk itself before launching to prevent malicious modification of files and processes implemented in the client.

Update to Node.js 6.9.5 LTS

See: https://nodejs.org/en/blog/release/v6.9.5/

Forging after rebuild

With the new build of 0.3.1 forging won't start after a rebuild and needs a reload/restart to make the delegate forge again.

Allow users to synchronize from 0 as part of installLisk.sh

I think installLisk.sh should ask user if prefers to resync from beginning or use snapshot instead, i've already mentioned before that forcing users to download "official" snapshot is just terrible in decentralised network. By default it should sync from scratch with possibility to pick faster way with snapshot.

Show progress indicator when downloading blockchain.db.gz

A small feature request. To show percentage / speed when downloading blockchain.db.gz. Quite often it takes a while to download, so some progress indication would help here I think.

Can't run on FreeBSD 10

On FreeBSD even when you install all packages without any errors you can't run Lisk itself because of the following error:

/usr/home/lisk/lisk-main/node_modules/sodium/build/Release/sodium.node: Undefined symbol "sodium_init"
error: Forever detected script exited with code: 1

Relative path / reference link issue

The error come from an rpm build using the tar.gz provided by lisk-hq

here is an example:
ERROR 0002: file '/opt/lisk/client/node_modules/sodium/deps/libsodium/test/default/.libs/scalarmult7' contains an invalid rpath '/home/lisk/lisk-build/src/lisk-0.7.0a-Linux-x86_64/node_modules/.staging/sodium-c2c29825/deps/build/lib' in [/home/lisk/lisk-build/src/lisk-0.7.0a-Linux-x86_64/node_modules/.staging/sodium-c2c29825/deps/build/lib]

to find where the problem is, you can just use the command: strings /opt/lisk/client/node_modules/sodium/deps/libsodium/test/default/.libs/scalarmult7

you will see invalid path reference inside the libraries

Restart in Lisk.sh only cycles Node Process

From: LiskArchive/lisk-sdk#95

When using bash lisk.sh restart only the node processes are restarted. If the node process is running, but postgres is not, restart will not start it. This is inconsistent behavior when compared to both the start and stop commands.

To fix this, stop_postgresql and start_postgresql would need to be added to the case clause for restart at the bottom of lisk.sh

Additionally, a new command could be added in with the syntax being bash lisk.sh reload which could perform the stop_lisk and start_lisk function that the existing restart function performs. This would allow reloading of config.json without needing to restart the database processes.

Courtesy of: @Isabello

Homepage says "Cannot GET /" after a reboot

Moved from: LiskArchive/lisk-sdk#72

In the logs I get:
error error: could not connect to server: Connection refused
After a bash lisk.sh restart It becomes available again and loads fine, It seems the postgre DB dont load in time after a reboot (tested on two different vps), so I added a "sleep x" seconds to crontab job and still testing...

EDIT: Adding a 3 seconds sleep mitigate the problem, after many many tries it get a refused connection on reboot but then it loads normally (Cannot GET appears for a second refreshing the page many times on loading)

EDIT2: Adding a 5 seconds pause delay I dont get problems.

Courtesy of: @metal494

Update to Postgres 9.6.2

See: https://www.postgresql.org/docs/9.6/static/release-9-6-2.html

Add checks for prerequisites

Currently prerequisites are not checked. Checks need to be added to the install script and point the user to the prereq documentation if they do not pass.

Add Logrotate config to installLisk.sh

From: LiskArchive/lisk-sdk#245

I have some node running for 60 days with 15GB+ app.log file
I want to keep the level of logging at high rate especially on testnet
I think it would be great if the client handle this for end-user.

i solve it for myself using:

sed -r -i 's/^LOG_FILE=.*/LOG_FILE="/var/log/lisk/app.log"/g' /opt/lisk/client/lisk.sh

mkdir /var/log/lisk
touch /var/log/lisk/log.json
touch /var/log/lisk/app.log
chown -R ${GLOBAL[lisk_user]}:${GLOBAL[lisk_user]} /var/log/lisk
chmod 700 /var/log/lisk
chmod 600 /var/log/lisk/log.json
chmod 600 /var/log/lisk/app.log

cat > /etc/logrotate.d/lisk-log-json << EOF_lisk-log-json_logrotate
/var/log/lisk/log.json {
su ${GLOBAL[lisk_user]} ${GLOBAL[lisk_user]}
weekly
dateext
copytruncate
missingok
rotate 2
compress
delaycompress
notifempty
}
EOF_lisk-log-json_logrotate

chmod 644 /etc/logrotate.d/lisk-log-json

cat > /etc/logrotate.d/lisk-app-log << EOF_lisk-app-log_logrotate
/var/log/lisk/app.log {
su ${GLOBAL[lisk_user]} ${GLOBAL[lisk_user]}
weekly
dateext
copytruncate
missingok
rotate 2
compress
delaycompress
notifempty
}
EOF_lisk-app-log_logrotate

chmod 644 /etc/logrotate.d/lisk-app-log

Update to Node.js 0.12.15

Following this security update:

https://groups.google.com/forum/#!topic/nodejs-sec/pnACRfB7LBI

• node
• lisk-node

Add support for compiling libsodium / node-sodium

The recent switch in Lisk core from js-nacl to node-sodium requires a statically linked libsodium to be compiled / cross-compiled as part of each build.

rebuild_lisk stops in download_blockchain if blockchain.db exists

gunzip asks for overwrite confirmation, but invisible because of -q option. Add -f?

Block height is sometimes returned as empty

Sometimes the lisk.sh script fails to get the block height and is returned as empty.

We should try to improve its reliability, and also gracefully handle the empty height like so: Current Block Height: Unavailable.

lisk-build on Debian Jessie

bash build.sh does not work for me.

I searched for some time, but i don't know what the problem is yet. Postgresql has not been installed.

I will post the last 50ish lines before the error.

postgresql-9.5.2/doc/src/sgml/test-decoding.sgml
postgresql-9.5.2/doc/src/sgml/diskusage.sgml
postgresql-9.5.2/doc/src/sgml/spi.sgml
postgresql-9.5.2/doc/src/sgml/user-manag.sgml
postgresql-9.5.2/doc/src/sgml/storage.sgml
postgresql-9.5.2/doc/src/sgml/mk_feature_tables.pl
postgresql-9.5.2/doc/src/sgml/intro.sgml
postgresql-9.5.2/doc/src/sgml/gist.sgml
postgresql-9.5.2/doc/src/sgml/release-8.3.sgml
postgresql-9.5.2/doc/src/sgml/pgstattuple.sgml
postgresql-9.5.2/doc/src/sgml/uuid-ossp.sgml
postgresql-9.5.2/doc/src/sgml/start.sgml
postgresql-9.5.2/doc/src/sgml/planstats.sgml
postgresql-9.5.2/doc/src/sgml/nls.sgml
postgresql-9.5.2/doc/src/sgml/stylesheet.css
postgresql-9.5.2/doc/src/sgml/contacts.sgml
postgresql-9.5.2/doc/src/sgml/sslinfo.sgml
postgresql-9.5.2/doc/src/sgml/json.sgml
postgresql-9.5.2/doc/src/sgml/intarray.sgml
postgresql-9.5.2/doc/src/sgml/pgbuffercache.sgml
postgresql-9.5.2/doc/src/sgml/dblink.sgml
postgresql-9.5.2/doc/src/sgml/pgtrgm.sgml
postgresql-9.5.2/doc/src/sgml/xindex.sgml
postgresql-9.5.2/doc/src/sgml/sources.sgml
postgresql-9.5.2/doc/src/sgml/Makefile
postgresql-9.5.2/doc/src/sgml/earthdistance.sgml
postgresql-9.5.2/doc/src/sgml/release-8.2.sgml
postgresql-9.5.2/doc/src/sgml/tcn.sgml
postgresql-9.5.2/doc/src/sgml/information_schema.sgml
postgresql-9.5.2/doc/src/sgml/catalogs.sgml
postgresql-9.5.2/doc/src/sgml/auth-delay.sgml
postgresql-9.5.2/doc/src/sgml/tablefunc.sgml
postgresql-9.5.2/doc/src/sgml/pgrowlocks.sgml
postgresql-9.5.2/doc/src/sgml/tablesample-method.sgml
postgresql-9.5.2/doc/src/sgml/lobj.sgml
postgresql-9.5.2/doc/src/sgml/dfunc.sgml
postgresql-9.5.2/doc/src/sgml/ddl.sgml
postgresql-9.5.2/doc/src/sgml/pltcl.sgml
postgresql-9.5.2/doc/src/sgml/event-trigger.sgml
postgresql-9.5.2/doc/src/sgml/biblio.sgml
postgresql-9.5.2/doc/src/sgml/release-old.sgml
postgresql-9.5.2/doc/src/sgml/hstore.sgml
postgresql-9.5.2/doc/src/sgml/protocol.sgml
postgresql-9.5.2/doc/src/sgml/libpq.sgml
postgresql-9.5.2/doc/src/sgml/btree-gist.sgml
postgresql-9.5.2/doc/src/sgml/gin.sgml
postgresql-9.5.2/doc/src/sgml/auto-explain.sgml
postgresql-9.5.2/doc/src/sgml/monitoring.sgml
postgresql-9.5.2/doc/src/sgml/sourcerepo.sgml
postgresql-9.5.2/doc/src/sgml/passwordcheck.sgml
postgresql-9.5.2/doc/src/sgml/wal.sgml
postgresql-9.5.2/doc/src/sgml/pgcrypto.sgml
postgresql-9.5.2/doc/src/sgml/maintenance.sgml
postgresql-9.5.2/doc/src/sgml/fuzzystrmatch.sgml
postgresql-9.5.2/doc/src/sgml/keywords.sgml
postgresql-9.5.2/doc/src/sgml/recovery-config.sgml
postgresql-9.5.2/doc/src/sgml/lo.sgml
postgresql-9.5.2/doc/src/sgml/syntax.sgml
postgresql-9.5.2/doc/src/sgml/geqo.sgml
postgresql-9.5.2/doc/src/sgml/release-9.2.sgml
postgresql-9.5.2/doc/src/sgml/datetime.sgml
postgresql-9.5.2/doc/src/sgml/xml2.sgml
postgresql-9.5.2/doc/src/sgml/release-8.0.sgml
postgresql-9.5.2/doc/src/sgml/chkpass.sgml
postgresql-9.5.2/doc/src/sgml/release-8.4.sgml
postgresql-9.5.2/doc/src/sgml/dml.sgml
postgresql-9.5.2/doc/src/sgml/xfunc.sgml
postgresql-9.5.2/doc/src/sgml/release-8.1.sgml
postgresql-9.5.2/doc/src/sgml/plhandler.sgml
postgresql-9.5.2/doc/src/sgml/rangetypes.sgml
postgresql-9.5.2/doc/src/sgml/logicaldecoding.sgml
postgresql-9.5.2/doc/src/sgml/replication-origins.sgml
postgresql-9.5.2/doc/src/sgml/release.sgml
postgresql-9.5.2/doc/src/sgml/jadetex.cfg
postgresql-9.5.2/doc/src/sgml/perform.sgml
postgresql-9.5.2/doc/src/sgml/acronyms.sgml
postgresql-9.5.2/doc/src/sgml/rules.sgml
postgresql-9.5.2/doc/src/sgml/btree-gin.sgml
postgresql-9.5.2/doc/src/sgml/high-availability.sgml
postgresql-9.5.2/doc/src/sgml/textsearch.sgml
postgresql-9.5.2/doc/src/sgml/features.sgml
postgresql-9.5.2/doc/src/sgml/html-stamp
postgresql-9.5.2/doc/src/sgml/ltree.sgml
postgresql-9.5.2/doc/src/sgml/trigger.sgml
postgresql-9.5.2/doc/src/sgml/seg.sgml
postgresql-9.5.2/doc/src/sgml/client-auth.sgml
postgresql-9.5.2/doc/src/sgml/postgres.sgml
postgresql-9.5.2/doc/src/sgml/func.sgml
postgresql-9.5.2/doc/src/sgml/tsm-system-time.sgml
postgresql-9.5.2/doc/src/sgml/plpgsql.sgml
postgresql-9.5.2/doc/src/sgml/sql.sgml
postgresql-9.5.2/doc/src/sgml/README.links
postgresql-9.5.2/doc/src/sgml/tsearch2.sgml
postgresql-9.5.2/doc/src/sgml/pgstatstatements.sgml
postgresql-9.5.2/doc/src/sgml/xaggr.sgml
postgresql-9.5.2/doc/src/sgml/stylesheet.xsl
postgresql-9.5.2/doc/src/sgml/contrib.sgml
postgresql-9.5.2/doc/src/sgml/man-stamp
postgresql-9.5.2/doc/src/sgml/bki.sgml
postgresql-9.5.2/doc/src/sgml/unaccent.sgml
postgresql-9.5.2/doc/src/sgml/release-7.4.sgml
postgresql-9.5.2/doc/src/sgml/external-projects.sgml
postgresql-9.5.2/doc/src/sgml/problems.sgml
postgresql-9.5.2/doc/src/sgml/arch-dev.sgml
postgresql-9.5.2/doc/src/sgml/pageinspect.sgml
postgresql-9.5.2/doc/src/sgml/info.sgml
postgresql-9.5.2/doc/src/sgml/installation.sgml
postgresql-9.5.2/doc/src/sgml/xplang.sgml
postgresql-9.5.2/doc/src/Makefile
postgresql-9.5.2/doc/KNOWN_BUGS
postgresql-9.5.2/doc/Makefile
postgresql-9.5.2/doc/TODO
postgresql-9.5.2/doc/MISSING_FEATURES
postgresql-9.5.2/doc/bug.template
postgresql-9.5.2/HISTORY
postgresql-9.5.2/Makefile
postgresql-9.5.2/README
postgresql-9.5.2/COPYRIGHT
postgresql-9.5.2/GNUmakefile.in
postgresql-9.5.2/.gitattributes
postgresql-9.5.2/aclocal.m4
postgresql-9.5.2/configure.in
postgresql-9.5.2/INSTALL

• ./configure --prefix=/home/neo/lisk-build/src/postgresql-9.5.2/pgsql --host=arm-linux --without-readline --without-zlib --disable-spinlocks
  checking build system type... armv7l-unknown-linux-gnueabihf
  checking host system type... arm-unknown-linux-gnu
  checking which template to use... linux
  checking whether to build with 64-bit integer date/time support... yes
  checking whether NLS is wanted... no
  checking for default port number... 5432
  checking for block size... 8kB
  checking for segment size... 1GB
  checking for WAL block size... 8kB
  checking for WAL segment size... 16MB
  checking for arm-linux-gcc... arm-linux-gnueabihf-gcc
  checking whether the C compiler works... no
  configure: error: in /home/neo/lisk-build/src/postgresql-9.5.2': configure: error: C compiler cannot create executables Seeconfig.log' for more details
  Error executing command, exiting

and FYI
uname -a
Linux bitcoinuser 3.10.77 #7393 SMP Thu Jun 2 19:48:22 CST 2016 armv7l GNU/Linux

It is synology DS-715

Config.json migration when updating

Phoenix1969 commented 2 minutes ago • edited
Plz forgive, didn't know where else to put this, but....
Just a gentle reminder that the upgrade script could use some migration code for the config.json file.
Updating and upgrading multiple nodes becomes a hefty chore when json customizations like ssl, forging and api options are needing altered after every update..
thx.

From LiskArchive/lisk-sdk#291

lisk.sh script is not able to stop a node

Moved from: LiskArchive/lisk-sdk#116

The lisk.sh script try do stop the process by invoking the "forever" binary. When the node is forked this process does not work anymore. and the forever command can not stop the application anymore. Because of this the rebuild option will not work anymore.

Maybe if the forever application is not able to stop the process and the pid is still available, in this case should the process be "kill"-ed and the databese stop..

Section 1

+ stop_lisk
+ forever stop lisk
+ '[' 1 '!=' 0 ']'
+ echo 'X Failed to stop lisk.'
X Failed to stop lisk.
+ sleep 1
+ start_postgresql
+ pg_ctl -D /opt/lisk/lisk-Linux-x86_64/pgsql/data -l /opt/lisk/lisk-Linux-x86_64/pgsql.log start
+ '[' 0 '!=' 0 ']'
+ sleep 1
+ rebuild_lisk
+ create_database
+ dropdb --if-exists lisk_test
+ createdb lisk_test
+ '[' 1 '!=' 0 ']'
+ echo 'X Failed to create postgres database.'
X Failed to create postgres database.
+ exit 1

Section 2

user@tudorsiilinca:/opt/lisk/lisk-Linux-x86_64$ ps aux | grep lisk
user  14218  0.0  1.2 170204 13204 ?        S    May10   0:01 /opt/lisk/lisk-Linux-x86_64/pgsql/bin/postgres -D /opt/lisk/lisk-Linux-x86_64/pgsql/data
user  14241  0.0  5.6 611596 57316 ?        Ss   May10   0:22 /opt/lisk/lisk-Linux-x86_64/bin/node /opt/lisk/lisk-Linux-x86_64/node_modules/forever/bin/monitor app.js
user  14242  6.9 24.5 1089888 250220 ?      Sl   May10  67:28 /opt/lisk/lisk-Linux-x86_64/bin/node /opt/lisk/lisk-Linux-x86_64/app.js
user  14247  0.3  7.1 174760 73088 ?        Ss   May10   3:06 postgres: user lisk_test 127.0.0.1(46326) idle
user  14248  0.3  7.4 179184 76116 ?        Ss   May10   3:05 postgres: user lisk_test 127.0.0.1(46327) idle
user  14249  0.3  7.0 175276 71712 ?        Ss   May10   3:07 postgres: user lisk_test 127.0.0.1(46328) idle
user  14250  0.3  7.2 178180 74240 ?        Ss   May10   3:05 postgres: user lisk_test 127.0.0.1(46330) idle
user  14251  0.3  7.1 174612 73192 ?        Ss   May10   3:04 postgres: user lisk_test 127.0.0.1(46331) idle
user  14254  0.3  7.2 178192 73900 ?        Ss   May10   3:02 postgres: user lisk_test 127.0.0.1(46345) idle
user  14255  0.3  6.6 172636 67780 ?        Ss   May10   3:01 postgres: user lisk_test 127.0.0.1(46346) idle
user  14509  0.1  6.0 174776 61992 ?        Ss   May10   0:57 postgres: user lisk_test 127.0.0.1(46459) idle
user  14510  0.1  6.3 178168 64304 ?        Ss   May10   0:58 postgres: user lisk_test 127.0.0.1(46460) idle
user  14511  0.1  6.3 178172 64828 ?        Ss   May10   0:58 postgres: user lisk_test 127.0.0.1(46461) idle
user  14512  0.1  6.0 175372 61628 ?        Ss   May10   0:57 postgres: user lisk_test 127.0.0.1(46465) idle
user  14513  0.1  6.4 178184 65260 ?        Ss   May10   0:59 postgres: user lisk_test 127.0.0.1(46466) idle
user  14514  0.1  6.0 174792 61140 ?        Ss   May10   0:59 postgres: user lisk_test 127.0.0.1(46467) idle
user  14515  0.1  5.9 174744 60948 ?        Ss   May10   0:59 postgres: user lisk_test 127.0.0.1(46468) idle
user  14516  0.1  6.0 174704 61296 ?        Ss   May10   0:59 postgres: user lisk_test 127.0.0.1(46469) idle
user  14517  0.1  6.0 174604 61080 ?        Ss   May10   0:58 postgres: user lisk_test 127.0.0.1(46470) idle
user  14518  0.1  6.3 178148 65112 ?        Ss   May10   0:57 postgres: user lisk_test 127.0.0.1(46471) idle
user  14722  0.0  5.9 174632 60820 ?        Ss   May10   0:56 postgres: user lisk_test 127.0.0.1(47930) idle
user  14723  0.1  5.9 174708 60836 ?        Ss   May10   0:58 postgres: user lisk_test 127.0.0.1(47931) idle
user  14724  0.0  6.3 178140 65008 ?        Ss   May10   0:56 postgres: user lisk_test 127.0.0.1(47932) idle
user  20132  0.0  0.0  11984   936 pts/0    S+   12:11   0:00 grep --color=auto lisk

maybe something like this;

stop_lisk() {
  forever stop lisk &> /dev/null
  if [ $? !=  0 ] && [ -f "$PID_FILE" ]; then
    local PID=$(cat "$PID_FILE")
  fi

  if [ ! -z "$PID" ]; then
        ps -p "$PID" > /dev/null 2>&1
     local STATUS=$?
  else
    local STATUS=1
  fi

  if [ -f $PID_FILE ] && [ ! -z "$PID" ] && [ $STATUS == 0 ]; then
    kill -9 "$PID" > /dev/null 2>&1
    echo "X Lisk has been killed."
  fi

  if [ $? !=  0 ] || [$STATUS ==1]; then
    echo "√ Lisk stopped successfully."
  fi

}

Courtesy of @cezarsn

lisk_snapshot.sh not working on v0.4.0a

The following line in the script stall:

bash lisk.sh snapshot -s highest -c $SNAPSHOT_CONFIG

The highest word look unsupported.

On-screen output is:

Beginning snapshot verification process at Wed Sep 14 22:50:23 EDT 2016
Snapshot flag must be a number and greater than 0

Clearly related to (now closed) issue:

LiskArchive/lisk-sdk#258

So I don't know first one that will be fixed...

Update to Node.js 6.9.4 LTS

The 0.12.* LTS branch has now reached its end of life, therefore we need to move to the latest LTS release on 6.9.*. See: https://github.com/nodejs/LTS.

• node
• lisk-node

Add support for hardfork in installLisk.sh

On testnet we now practice cutting off old versions to make the network clean. In order to make this easier a flag should be added to trigger a rebuild after the upgrade rather than recycling the existing database which could be on the forked chain.

restore -f option of the lisk.sh script still download the blockchain from the source

bash lisk.sh rebuild -f blockchain.db.gz 
√ Lisk stopped successfully.
√ Postgresql is running.
√ Postgresql database created successfully.
√ Downloading blockchain.db.gz from https://downloads.lisk.io/lisk/test
######################################################################## 100.0%
√ Blockchain snapshot downloaded successfully.
Restoring blockchain with blockchain.db.gz
√ Blockchain restored successfully.
√ Lisk started successfully.
√ Lisk is running as PID: 3958
Current Block Height: 782043

this option should not dowload the snapshot.

Sources archive unpacking error

When running build.sh it produces an error, when trying to rename unpacked source folder.

+ mv -f 0.2.1 lisk-0.2.1-FreeBSD-amd64
mv: rename 0.2.1 to lisk-0.2.1-FreeBSD-amd64: No such file or directory
Error executing command, exiting

Mac OS x Build

https://github.com/Doweig/lisk-build/edit/development/release/installLisk.sh#L209

Md5 output on Mac looks like this:

MD5 (Makefile) = 8df5b28ea83e381a01e2f96bc35282b4

Should be $4 not $1

Add support for ARMv8 builds

Courtesy of MalReynolds:

Hi - could you please do an ARMv8 build of the next version of Lisk to go along with the current ARMv6 and ARMv7 versions? I'd like to try Lisk on an ODROID C2, which is ARMv8....it has 2GHz quad processors, 2GB RAM, eMMC memory clocked at 120 Mbit/sec transfer time and gig ethernet clocked at 900 Mbit/sec transfer time. At $40 per unit, it could be a game changer for Lisk.

Mac build

I have a few issues with building on mac. I think installLisk.sh would need some adaption to be runnable on Mac.

./installLisk.sh: line 160: md5sum: command not found
Checksum Failed, aborting installation

Starting Lisk with all parameters in place
Error: forever command was not found. Aborting.

defaultLiskLocation

"Where do you want to install Lisk to? (Default $defaultLiskLocation):"

I think this should be current path where installLisk.sh is by default.

Bug: -r parameter not working in lisk_snapshot.sh

New round of test on v0.4.0b for snapshot feature found most issue solved.
But one ...

Test 1

bash /opt/lisk/client/lisk_snapshot.sh -t /opt/lisk/client/snapshot.json -s /opt/lisk/client/config.json -b /opt/lisk/backup -d 3 -r 10

• -r 10 didn't worked, it used highest round

Test 2

bash lisk.sh snapshot -s 10 -c snapshot.json

• -s 10 worked

Add flag to lisk.sh to support syncing from specified peer

Per issue LiskArchive/lisk-sdk#389 on lisk core that adds this flag. To expose it to binaries we need to add a new flag to the script.

Idea to explore: letsencrypt client written for nodejs

from:
LiskArchive/lisk-sdk#88

from @Gr33nDrag0n69
letsencrypt client written for nodejs
https://github.com/Daplie/letsencrypt-express
https://github.com/Daplie/letsencrypt-cli
Maybe the ssl cert generation and renewal in the lisk client could be implemented (as an option command).

installLisk.sh upgrade remove/overwrite previous config

installLisk.sh upgrade indirectly caused blockchain fork:3 i guess. Since i have did upgrade before, backup directory has been already created and i couldn't upgrade again due error with mkdir, there should be check if backup directory already exists to remove it or not.
Also i have noticed that i can upgrade the same version and it will always remove current lisk and install again (the same version) there should be check if current version matches or not latest released.

Not sure if this is correct repo, but couldn't find repository with this script.

Rebuild from 0 Parameter for lisk.sh

In addition to rebuilding from snapshots, we need a way to rebuild from 0 using only database schema, genesis block and seed nodes.

"upgrade" function in installLisk.sh is broken

After upgrading to 0.4.1 to 0.5.0, 3/3 servers couldn't be upgraded using this feature in script.
First and Second node resulted with corrupted database, database name and/or username was invalid, it couldn't fix itself after rebuild or/and coldstart.

Third resulted in missing "blocks" table, it also couldn't be repaired with lisk.sh or installLisk.sh.

After removing all files related to Lisk on each server and doing clean install everything is working fine.

Add support for other Linux distributions (other than Debian/Ubuntu)

The installation script is not taking into consideration that database can be installed just on Ubuntu like distro and not CentOS/Fedora/Redhat.
The script should be able to detect based on output of "lsb_release -i" if is running on the right distro.

Thank you.
@wannabe

Wait for existing process to exit during restart

When issuing the bash lisk.sh restart command, the script should wait for the old process to exit before starting a new one.

Add travis badge to README.md

Now that we have static code analysis, we should display a badge for it in the README

Refactor delegate page to update more frequently

In the current implementation there is a lag between block reciept and updating the forger on the delegate list. We need to adjust the method this page will be updated by to update more frequently to keep data as realtime as possible.

installLisk.sh upgrade remove/overwrite previous config

installLisk.sh upgrade remove/overwrite previous config

Flagify lisk.sh, add sync from 0

Lisk.sh is somewhat difficult to use currently. Flags need to be implemented to allow for new flags such as config.json, log locations, and snapshotting.

BUG: Fixing extra characters at the end of l command.

On my Linux Mint machine after 63c176b it fails to build with the following message:

+ sed -i '' "s%#!/home/caldeireiro/Desktop/lisk-build/src/node-v0.12.9/compiled/bin/node%#\!.\/bin\/node%g" lisk-0.1.1-Linux-armv6l/lib/node_modules/npm/bin/npm-cli.js sed: can't read s%#!/home/caldeireiro/Desktop/lisk-build/src/node-v0.12.9/compiled/bin/node%#\!.\/bin\/node%g: No such file or directory Error executing command, exiting

But it works using

sed -i \"s%$(head -1 $NPM_CLI)%#\!.\/bin\/node%g\" $NPM_CLI

Voting on Lisk client

Some delegates are able to vote for more then 104 other delegates.

Postgres log file does not contain any timestramp

The postgres log file does not contain any timestamp and is hard to figure out when an issue has happened

Example:

LOG:  autovacuum launcher started
PANIC:  semop(id=196614) failed: Invalid argument
STATEMENT:  UPDATE peers SET "os" = 'linux3.19.0-65-generic', "version" = '0.4.0d' , "state" = CASE WHEN "state" = 0 THEN "state" ELSE 2 END WHERE "ip" = '52.169.191.86' and "port" = 7000;
PANIC:  semop(id=196614) failed: Invalid argument
LOG:  WAL writer process (PID 829) was terminated by signal 6: Aborted
LOG:  terminating any other active server processes
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

Improve process management for more reliable restarts on failure

With reference to the following forum post: https://forum.lisk.io/viewtopic.php?f=13&p=1054#p1054

Removal of old backup in ~/backup

Recursion should be added to the install script to be able to delete the previous backup. (-rf)

Provide a flag on the command line to bypass the "Sync from 0?" question

There should be a flag on the installLisk.sh command that allows the automatic installation by bypassing the mentioned question.

Add a verbose logs for lisk.sh and installLisk.sh

Currently all messages are supressed in lisk.sh. To make troubleshooting easier, we can direct these messages to a log while still keeping the execution responses clean. Additionally, error messages can indicate where this log lives in order to give users the ability to help themselves, or so they can bring the log to others (or us) for help.

built in script to backup database

Courtesy of: @ByronAP

It would be nice if there was a built in script we could run that would cc the current db and also a restore command. This would make it possible to restore from a local copy instead of downloading the entire chain from peers or bootstrap. This shouldn't be too hard as the script can stop Lisk and then restart it once the operation is complete.

Correct issue with updateConfig.js - Seed Peers Overwriting

When updating seed peers, the existing implementation overwrites the new peers with the old. This needs to be corrected to allow peers to be updated with the client correctly.