Linux

lazy-result.js ReferenceError: Promise is not defined

[code lang=”javascript”] node_modules/postcss/lib/lazy-result.js:157 this.processing = new Promise(function (resolve, reject) { ^ ReferenceError: Promise is not defined [/code] When I install the FoundationPress, after I run gulp build I saw this message, this is because the node version problem. the have mention in this post https://github.com/postcss/postcss-nested/issues/30 Solution [code lang=”shell”] vim node_modules/postcss/lib/lazy-result.js [/code] Put this to the …

lazy-result.js ReferenceError: Promise is not defined Read More »

How to Install MongoDB 3.2 on CentOS 7

[code lang=”shell”] vim /etc/yum.repos.d/mongodb.repo [/code] Paste this to the file and save using :wq [code lang=”shell”] [MongoDB] name=MongoDB Repository baseurl=http://repo.mongodb.org/yum/redhat/$releasever/mongodb-org/3.2/x86_64/ gpgcheck=0 enabled=1 [/code] Download and install mongodb using yum [code lang=”shell”] yum install mongodb-org -y [/code] Start mongod and configure auto start while system boot [code lang=”shell”] /etc/init.d/mongod restart chkconfig mongod on [/code] Check all …

How to Install MongoDB 3.2 on CentOS 7 Read More »

WARNING: /sys/kernel/mm/transparent_hugepage/enabled is ‘always’.

After I install MongoDB 3.2.3 in Centos 7, I received this error when I start mongo in shell. [code lang=”shell”] [[email protected] ~]# mongo MongoDB shell version: 3.2.3 connecting to: test Server has startup warnings: 2016-02-29T14:11:49.308-0500 I CONTROL [initandlisten] 2016-02-29T14:11:49.308-0500 I CONTROL [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is ‘always’. 2016-02-29T14:11:49.308-0500 I CONTROL [initandlisten] ** We suggest setting …

WARNING: /sys/kernel/mm/transparent_hugepage/enabled is ‘always’. Read More »

WARNING: Cannot detect if NUMA interleaving is enabled. Failed to probe “/sys/devices/system/node/node1”: Permission denied

[code lang=”shell”] [[email protected] ~]# mongo MongoDB shell version: 3.2.3 connecting to: test Server has startup warnings: 2016-02-29T23:11:36.666+0700 I CONTROL [initandlisten] 2016-02-29T23:11:36.667+0700 I CONTROL [initandlisten] ** WARNING: Cannot detect if NUMA interleaving is enabled. Failed to probe "/sys/devices/system/node/node1": Permission denied 2016-02-29T23:11:36.667+0700 W CONTROL [initandlisten] 2016-02-29T23:11:36.667+0700 W CONTROL [initandlisten] Failed to probe "/sys/kernel/mm/transparent_hugepage": Permission denied 2016-02-29T23:11:36.667+0700 W …

WARNING: Cannot detect if NUMA interleaving is enabled. Failed to probe “/sys/devices/system/node/node1”: Permission denied Read More »

WARNING: soft rlimits too low. rlimits set to 4096 processes, 64000 files. Number of processes should be at least 32000 : 0.5 times number of files.

I’ve received this error while starting mongo in shell while installing on [code lang=”shell”] [[email protected] ~]# mongod –version db version v3.2.3 git version: b326ba837cf6f49d65c2f85e1b70f6f31ece7937 OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013 allocator: tcmalloc modules: none build environment: distmod: rhel70 distarch: x86_64 target_arch: x86_64 [[email protected] ~]# mongo –version MongoDB shell version: 3.2.3 CentOS Linux release 7.2.1511 …

WARNING: soft rlimits too low. rlimits set to 4096 processes, 64000 files. Number of processes should be at least 32000 : 0.5 times number of files. Read More »

exit code of #128 fatal: unable to connect to github.com

I follow the Quickstart guide from FoundationPress and it display this error [code lang=”bash”] bower install && grunt build bower foundation#* not-cached git://github.com/zurb/bower-foundation.git#* bower foundation#* resolve git://github.com/zurb/bower-foundation.git#* bower fontawesome#~4.3.0 not-cached git://github.com/FortAwesome/Font-Awesome.git#~4.3.0 bower fontawesome#~4.3.0 resolve git://github.com/FortAwesome/Font-Awesome.git#~4.3.0 bower fontawesome#~4.3.0 ECMDERR Failed to execute “git ls-remote –tags –heads git://github.com/FortAwesome/Font-Awesome.git”, exit code of #128 fatal: unable to connect to …

exit code of #128 fatal: unable to connect to github.com Read More »