Hi all,
Updating my erpnext to the latest version 11.
I am getting the below error at the end.
Tried to install the yarn with ‘npm install -g yarn’ command and was successful as below
Tried to run the ‘bench update’ again and getting the below error.
I am able to loign to the erpnext with the latest version. But, many features are missing like ‘print format builder page is blank’, ‘print to pdf is not opening the doc in new window’, etc.
Please help to resolve it. Thanks
KR Fasil.
Hi All,
Anyone to help to fix this?
Kindest Regards
Fasil.
Do you have customizations to your JS code?
Or
cd frappe-bench
rm -rf node_modules
bench setup requirements
Same issue for me, I tried the following one and working fine.
It looks like you are running the bench update (after you installed via yarn…) as the root user. This is not advisable, and often breaks the environment. Rather do the bench update as user frappe
Hi Mehta
I have run the commands mentioned. Instead of deleting the node_modules folder I have moved it to /root/.
It gives the same error.
Hi Rkroot
I have tried changing the permissions. Didn’t help.
Hi trentmu
I have run the bench update as user frappe too. Didn’t help.
It gave the same error everytime.
Hi
I am really stuck up as this is our production server. Bench updates used to be very smooth.
I have tried yarn install in many ways with no luck. Anyone please???
I also run into the same Yarn error as posted in your opening post. After installing Yarn I’m getting the following error:
Hi
Anyone got a solution for this?
I am not able to view many of the documents. If I go to item and click on an item, I am getting the below error.
Traceback (most recent call last):
File “/home/frappe/frappe-bench/apps/frappe/frappe/app.py”, line 61, in application
response = frappe.handler.handle()
File “/home/frappe/frappe-bench/apps/frappe/frappe/handler.py”, line 21, in handle
data = execute_cmd(cmd)
File “/home/frappe/frappe-bench/apps/frappe/frappe/handler.py”, line 56, in execute_cmd
return frappe.call(method, **frappe.form_dict)
File “/home/frappe/frappe-bench/apps/frappe/frappe/init.py”, line 1019, in call
return fn(*args, **newargs)
File “/home/frappe/frappe-bench/apps/frappe/frappe/desk/notifications.py”, line 279, in get_open_count
filters=filters, limit=100, distinct=True, ignore_ifnull=True))
File “/home/frappe/frappe-bench/apps/frappe/frappe/init.py”, line 1274, in get_all
return get_list(doctype, *args, **kwargs)
File “/home/frappe/frappe-bench/apps/frappe/frappe/init.py”, line 1247, in get_list
return frappe.model.db_query.DatabaseQuery(doctype).execute(None, *args, **kwargs)
File “/home/frappe/frappe-bench/apps/frappe/frappe/model/db_query.py”, line 93, in execute
result = self.build_and_run()
File “/home/frappe/frappe-bench/apps/frappe/frappe/model/db_query.py”, line 117, in build_and_run
return frappe.db.sql(query, as_dict=not self.as_list, debug=self.debug, update=self.update)
File “/home/frappe/frappe-bench/apps/frappe/frappe/database.py”, line 210, in sql
self._cursor.execute(query)
File “/home/frappe/frappe-bench/env/lib/python2.7/site-packages/pymysql/cursors.py”, line 170, in execute
result = self._query(query)
File “/home/frappe/frappe-bench/env/lib/python2.7/site-packages/pymysql/cursors.py”, line 328, in _query
conn.query(q)
File “/home/frappe/frappe-bench/env/lib/python2.7/site-packages/pymysql/connections.py”, line 516, in query
self._affected_rows = self._read_query_result(unbuffered=unbuffered)
File “/home/frappe/frappe-bench/env/lib/python2.7/site-packages/pymysql/connections.py”, line 727, in _read_query_result
result.read()
File “/home/frappe/frappe-bench/env/lib/python2.7/site-packages/pymysql/connections.py”, line 1066, in read
first_packet = self.connection._read_packet()
File “/home/frappe/frappe-bench/env/lib/python2.7/site-packages/pymysql/connections.py”, line 683, in _read_packet
packet.check_error()
File “/home/frappe/frappe-bench/env/lib/python2.7/site-packages/pymysql/protocol.py”, line 220, in check_error
err.raise_mysql_exception(self._data)
File “/home/frappe/frappe-bench/env/lib/python2.7/site-packages/pymysql/err.py”, line 109, in raise_mysql_exception
raise errorclass(errno, errval)
InternalError: (1054, u"Unknown column ‘tabAuto Repeat.item_code’ in ‘where clause’")
As we can see below, the item does not show any of the previous transactions
Please help to resolve this asap.
Kind Regards,
Fasil
Same issue - style broken on update -
Checked permissions in dir and seems to be fine. Changed yarn.lock to bench user & group.
bench@erpbox:~/erpnext$ ls -la
drwxrwxr-x 9 bench bench 4096 Feb 4 14:12 .
drwxr-xr-x 14 bench bench 4096 Feb 4 14:56 …
drwxrwxr-x 7 bench bench 4096 Jan 17 07:27 apps
drwxrwxr-x 3 bench bench 4096 Sep 23 08:14 archived_sites
drwxrwxr-x 3 bench bench 4096 Dec 17 11:47 config
drwxrwxr-x 8 bench bench 4096 Jan 31 05:52 env
-rw-rw-r-- 1 bench bench 199 Dec 17 20:10 howtorenewcerts.txt
drwxrwxr-x 2 bench bench 4096 Feb 4 16:30 logs
drwxrwxr-x 411 bench bench 20480 Feb 4 14:17 node_modules
-rw-rw-r-- 1 bench bench 930 Feb 3 10:20 package.json
-rw-rw-r-- 1 bench bench 159860 Feb 4 13:59 package-lock.json
-rw-rw-r-- 1 bench bench 194 Feb 4 13:55 patches.txt
-rw-rw-r-- 1 bench bench 429 Sep 22 19:59 Procfile
drwxrwxr-x 4 bench bench 4096 Dec 26 09:22 sites
-rw-rw-r-- 1 bench bench 394 Nov 3 18:07 wget-log
-rw-rw-r-- 1 bench bench 155109 Feb 3 11:19 yarn.lock
Further error –
==> schedule.log <==
enqueue_events_for_site(site=site, queued_jobs=jobs_per_site[site])
File “/opt/bench/erpnext/apps/frappe/frappe/utils/scheduler.py”, line 103, in enqueue_events_for_site
log_and_raise()
File “/opt/bench/erpnext/apps/frappe/frappe/utils/scheduler.py”, line 93, in enqueue_events_for_site
if is_scheduler_disabled():
File “/opt/bench/erpnext/apps/frappe/frappe/utils/scheduler.py”, line 237, in is_scheduler_disabled
return not frappe.utils.cint(frappe.db.get_single_value(“System Settings”, “enable_scheduler”))
File “/opt/bench/erpnext/apps/frappe/frappe/database.py”, line 635, in get_single_value
tabSingles where doctype=%s and field=%s"“”, (doctype, fieldname))
File "/opt/benc
It appears to be a permission error, but unable to pinpoint the error so far.
Dear All
Please help to resolve this…
KR
Fasil
I am getting this error does any have solution for this.
Please help i need post my returns and today i am stuck
I had the same error as Fasil on Centos 7. For now we switched back to v.10.
Hopefully someone will find a solution.
I am having the same error…
my instance stuck
Hi All
Any update how to resolve this yarn error.
KR
Fasil
Hi
Tried some commands following the forums
[root@erp frappe-bench]# curl -sL https://rpm.nodesource.com/setup_6.x | bash -
## Installing the NodeSource Node.js 6.x LTS Boron repo...
## Inspecting system...
+ rpm -q --whatprovides redhat-release || rpm -q --whatprovides centos-release || rpm -q --whatprovides cloudlinux-release || rpm -q --whatprovides sl-release
+ uname -m
## Confirming "el7-x86_64" is supported...
+ curl -sLf -o /dev/null 'https://rpm.nodesource.com/pub_6.x/el/7/x86_64/nodesource-release-el7-1.noarch.rpm'
## Downloading release setup RPM...
+ mktemp
+ curl -sL -o '/tmp/tmp.IMrgfHhXOZ' 'https://rpm.nodesource.com/pub_6.x/el/7/x86_64/nodesource-release-el7-1.noarch.rpm'
## Installing release setup RPM...
+ rpm -i --nosignature --force '/tmp/tmp.IMrgfHhXOZ'
## Cleaning up...
+ rm -f '/tmp/tmp.IMrgfHhXOZ'
## Checking for existing installations...
+ rpm -qa 'node|npm' | grep -v nodesource
## Run `sudo yum install -y nodejs` to install Node.js 6.x LTS Boron and npm.
## You may also need development tools to build native addons:
sudo yum install gcc-c++ make
## To install the Yarn package manager, run:
curl -sL https://dl.yarnpkg.com/rpm/yarn.repo | sudo tee /etc/yum.repos.d/yarn.repo
sudo yum install yarn
[root@erp frappe-bench]# yum install nodejs
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
* base: mirror.teknoboss.com.tr
* epel: my.fedora.ipserverone.com
* extras: mirror.hosting.com.tr
* updates: repo.boun.edu.tr
Resolving Dependencies
--> Running transaction check
---> Package nodejs.x86_64 0:5.12.0-1nodesource.el7.centos will be updated
---> Package nodejs.x86_64 1:6.16.0-1.el7 will be an update
--> Processing Dependency: npm = 1:3.10.10-1.6.16.0.1.el7 for package: 1:nodejs-6.16.0-1.el7.x86_64
--> Processing Dependency: libuv >= 1:1.9.1 for package: 1:nodejs-6.16.0-1.el7.x86_64
--> Processing Dependency: libuv.so.1()(64bit) for package: 1:nodejs-6.16.0-1.el7.x86_64
--> Running transaction check
---> Package libuv.x86_64 1:0.10.34-2.el7 will be updated
--> Processing Dependency: libuv(x86-64) = 1:0.10.34-2.el7 for package: 1:libuv-devel-0.10.34-2.el7.x86_64
--> Processing Dependency: libuv.so.0.10()(64bit) for package: 1:libuv-devel-0.10.34-2.el7.x86_64
---> Package libuv.x86_64 1:1.24.1-1.el7 will be an update
---> Package npm.x86_64 1:3.10.10-1.6.16.0.1.el7 will be installed
--> Running transaction check
---> Package libuv-devel.x86_64 1:0.10.34-2.el7 will be updated
---> Package libuv-devel.x86_64 1:1.24.1-1.el7 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
===============================================================================================================================================================================
Package Arch Version Repository Size
===============================================================================================================================================================================
Updating:
nodejs x86_64 1:6.16.0-1.el7 epel 4.7 M
Installing for dependencies:
npm x86_64 1:3.10.10-1.6.16.0.1.el7 epel 2.5 M
Updating for dependencies:
libuv x86_64 1:1.24.1-1.el7 epel 131 k
libuv-devel x86_64 1:1.24.1-1.el7 epel 31 k
Transaction Summary
===============================================================================================================================================================================
Install ( 1 Dependent package)
Upgrade 1 Package (+2 Dependent packages)
Total size: 7.4 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction check error:
file /usr/lib/node_modules/npm/node_modules/node-gyp from install of npm-1:3.10.10-1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
file /usr/lib/node_modules/npm/doc from install of npm-1:3.10.10-1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
file /usr/lib/node_modules/npm/html from install of npm-1:3.10.10-1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
file /usr/lib/node_modules/npm/man from install of npm-1:3.10.10-1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
file /usr/lib/node_modules/npm/node_modules/uid-number from install of npm-1:3.10.10-1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
file /usr/lib/node_modules/npm/node_modules/umask from install of npm-1:3.10.10-1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
file /usr/lib/node_modules/npm/node_modules/unique-filename from install of npm-1:3.10.10-1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
file /usr/lib/node_modules/npm/node_modules/unpipe from install of npm-1:3.10.10-1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
file /usr/lib/node_modules/npm/node_modules/validate-npm-package-license from install of npm-1:3.10.10-1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
file /usr/lib/node_modules/npm/node_modules/validate-npm-package-name from install of npm-1:3.10.10-1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
file /usr/lib/node_modules/npm/node_modules/which from install of npm-1:3.10.10-1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
file /usr/lib/node_modules/npm/node_modules/wrappy from install of npm-1:3.10.10-1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
file /usr/lib/node_modules/npm/node_modules/write-file-atomic from install of npm-1:3.10.10-1.6.16.0.1.el7.x86_64 conflicts with file from package nodejs-5.12.0-1nodesource.el7.centos.x86_64
Error Summary
[root@erp frappe-bench]# yum remove nodejs
Loaded plugins: fastestmirror, langpacks
Resolving Dependencies
--> Running transaction check
---> Package nodejs.x86_64 0:5.12.0-1nodesource.el7.centos will be erased
--> Finished Dependency Resolution
Dependencies Resolved
===============================================================================================================================================================================
Package Arch Version Repository Size
===============================================================================================================================================================================
Removing:
nodejs x86_64 5.12.0-1nodesource.el7.centos @nodesource 30 M
Transaction Summary
===============================================================================================================================================================================
Remove 1 Package
Installed size: 30 M
Is this ok [y/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Erasing : nodejs-5.12.0-1nodesource.el7.centos.x86_64 1/1
Verifying : nodejs-5.12.0-1nodesource.el7.centos.x86_64 1/1
Removed:
nodejs.x86_64 0:5.12.0-1nodesource.el7.centos
Complete!
[root@erp frappe-bench]# yum install nodejs
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
* base: mirror.teknoboss.com.tr
* epel: my.fedora.ipserverone.com
* extras: mirror.hosting.com.tr
* updates: repo.boun.edu.tr
Resolving Dependencies
--> Running transaction check
---> Package nodejs.x86_64 1:6.16.0-1.el7 will be installed
--> Processing Dependency: npm = 1:3.10.10-1.6.16.0.1.el7 for package: 1:nodejs-6.16.0-1.el7.x86_64
--> Processing Dependency: libuv >= 1:1.9.1 for package: 1:nodejs-6.16.0-1.el7.x86_64
--> Processing Dependency: libuv.so.1()(64bit) for package: 1:nodejs-6.16.0-1.el7.x86_64
--> Running transaction check
---> Package libuv.x86_64 1:0.10.34-2.el7 will be updated
--> Processing Dependency: libuv(x86-64) = 1:0.10.34-2.el7 for package: 1:libuv-devel-0.10.34-2.el7.x86_64
--> Processing Dependency: libuv.so.0.10()(64bit) for package: 1:libuv-devel-0.10.34-2.el7.x86_64
---> Package libuv.x86_64 1:1.24.1-1.el7 will be an update
---> Package npm.x86_64 1:3.10.10-1.6.16.0.1.el7 will be installed
--> Running transaction check
---> Package libuv-devel.x86_64 1:0.10.34-2.el7 will be updated
---> Package libuv-devel.x86_64 1:1.24.1-1.el7 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
===============================================================================================================================================================================
Package Arch Version Repository Size
===============================================================================================================================================================================
Installing:
nodejs x86_64 1:6.16.0-1.el7 epel 4.7 M
Installing for dependencies:
npm x86_64 1:3.10.10-1.6.16.0.1.el7 epel 2.5 M
Updating for dependencies:
libuv x86_64 1:1.24.1-1.el7 epel 131 k
libuv-devel x86_64 1:1.24.1-1.el7 epel 31 k
Transaction Summary
===============================================================================================================================================================================
Install 1 Package (+1 Dependent package)
Upgrade ( 2 Dependent packages)
Total size: 7.4 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Updating : 1:libuv-1.24.1-1.el7.x86_64 1/6
Installing : 1:npm-3.10.10-1.6.16.0.1.el7.x86_64 2/6
Installing : 1:nodejs-6.16.0-1.el7.x86_64 3/6
Updating : 1:libuv-devel-1.24.1-1.el7.x86_64 4/6
Cleanup : 1:libuv-devel-0.10.34-2.el7.x86_64 5/6
Cleanup : 1:libuv-0.10.34-2.el7.x86_64 6/6
Verifying : 1:libuv-devel-1.24.1-1.el7.x86_64 1/6
Verifying : 1:nodejs-6.16.0-1.el7.x86_64 2/6
Verifying : 1:libuv-1.24.1-1.el7.x86_64 3/6
Verifying : 1:npm-3.10.10-1.6.16.0.1.el7.x86_64 4/6
Verifying : 1:libuv-0.10.34-2.el7.x86_64 5/6
Verifying : 1:libuv-devel-0.10.34-2.el7.x86_64 6/6
Installed:
nodejs.x86_64 1:6.16.0-1.el7
Dependency Installed:
npm.x86_64 1:3.10.10-1.6.16.0.1.el7
Dependency Updated:
libuv.x86_64 1:1.24.1-1.el7 libuv-devel.x86_64 1:1.24.1-1.el7
Complete!
[root@erp frappe-bench]# curl -sL https://dl.yarnpkg.com/rpm/yarn.repo | sudo tee /etc/yum.repos.d/yarn.repo
[yarn]
name=Yarn Repository
baseurl=https://dl.yarnpkg.com/rpm/
enabled=1
gpgcheck=1
gpgkey=https://dl.yarnpkg.com/rpm/pubkey.gpg
[root@erp frappe-bench]# yum install yarn
Loaded plugins: fastestmirror, langpacks
yarn | 2.9 kB 00:00:00
yarn/primary_db | 19 kB 00:00:00
Loading mirror speeds from cached hostfile
* base: mirror.teknoboss.com.tr
* epel: my.fedora.ipserverone.com
* extras: mirror.hosting.com.tr
* updates: repo.boun.edu.tr
Resolving Dependencies
--> Running transaction check
---> Package yarn.noarch 0:1.13.0-1 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
===============================================================================================================================================================================
Package Arch Version Repository Size
===============================================================================================================================================================================
Installing:
yarn noarch 1.13.0-1 yarn 1.1 M
Transaction Summary
===============================================================================================================================================================================
Install 1 Package
Total download size: 1.1 M
Installed size: 4.7 M
Is this ok [y/d/N]: y
Downloading packages:
warning: /var/cache/yum/x86_64/7/yarn/packages/yarn-1.13.0-1.noarch.rpm: Header V4 RSA/SHA512 Signature, key ID 6963f07f: NOKEY============= ] 1.5 MB/s | 1.1 MB 00:00:00 ETA
Public key for yarn-1.13.0-1.noarch.rpm is not installed
yarn-1.13.0-1.noarch.rpm | 1.1 MB 00:00:01
Retrieving key from https://dl.yarnpkg.com/rpm/pubkey.gpg
Importing GPG key 0x6963F07F:
Userid : "Yarn RPM Packaging <yarn@dan.cx>"
Fingerprint: 9a6f 73f3 4beb 7473 4d8c 6914 9cbb b558 6963 f07f
From : https://dl.yarnpkg.com/rpm/pubkey.gpg
Is this ok [y/N]: y
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : yarn-1.13.0-1.noarch 1/1
Verifying : yarn-1.13.0-1.noarch 1/1
Installed:
yarn.noarch 0:1.13.0-1
Complete!
After that restarted the server
[root@erp frappe-bench]# cd ..
[root@erp frappe]# cd bench-repo/
[root@erp bench-repo]# git pull
Already up-to-date.
[root@erp bench-repo]# cd ../frappe-bench/
[root@erp frappe-bench]# ls
apps archived_sites config env logs node_modules package.json patches.txt Procfile sites
[root@erp frappe-bench]# cd apps/
erpnext/ frappe/
[root@erp frappe-bench]# cd apps/erpnext/
[root@erp erpnext]# git pull
remote: Enumerating objects: 94, done.
remote: Counting objects: 100% (94/94), done.
remote: Compressing objects: 100% (18/18), done.
remote: Total 95 (delta 77), reused 91 (delta 76), pack-reused 1
Unpacking objects: 100% (95/95), done.
From https://github.com/frappe/erpnext
da1dc7f..665ee4a develop -> upstream/develop
7612030..504f317 hotfix -> upstream/hotfix
Already up-to-date.
[root@erp erpnext]# cd ../erpnext/
[root@erp erpnext]# git pull
Already up-to-date.
[root@erp erpnext]# su frappe
[frappe@erp erpnext]$ cd /home/frappe/frappe-bench/
[frappe@erp frappe-bench]$ bench update
INFO:bench.utils:updating bench
INFO:bench.utils:git pull
Already up-to-date.
INFO:bench.utils:./env/bin/pip install Pillow
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Requirement already satisfied: Pillow in ./env/lib/python2.7/site-packages (5.3.0)
INFO:bench.app:pulling frappe
INFO:bench.utils:git pull upstream master
From https://github.com/frappe/frappe
* branch master -> FETCH_HEAD
Already up-to-date.
INFO:bench.utils:find . -name "*.pyc" -delete
INFO:bench.app:pulling erpnext
INFO:bench.utils:git pull upstream master
From https://github.com/frappe/erpnext
* branch master -> FETCH_HEAD
Already up-to-date.
INFO:bench.utils:find . -name "*.pyc" -delete
Updating Python libraries...
INFO:bench.utils:./env/bin/pip install --upgrade pip
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Requirement already up-to-date: pip in ./env/lib/python2.7/site-packages (19.0.1)
INFO:bench.utils:./env/bin/pip install -q -r /home/frappe/bench-repo/requirements.txt
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
INFO:bench.app:installing frappe
INFO:bench.utils:./env/bin/pip install -q -e ./apps/frappe
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
INFO:bench.app:installing erpnext
INFO:bench.utils:./env/bin/pip install -q -e ./apps/erpnext
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Updating node packages...
INFO:bench.utils:yarn install
yarn install v1.13.0
node: relocation error: node: symbol SSL_set_cert_cb, version libssl.so.10 not defined in file libssl.so.10 with link time reference
Traceback (most recent call last):
File "/usr/bin/bench", line 9, in <module>
load_entry_point('bench==4.0.0', 'console_scripts', 'bench')()
File "/home/frappe/bench-repo/bench/cli.py", line 40, in cli
bench_command()
File "/usr/lib/python2.7/site-packages/click/core.py", line 716, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/click/core.py", line 696, in main
rv = self.invoke(ctx)
File "/usr/lib/python2.7/site-packages/click/core.py", line 1060, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python2.7/site-packages/click/core.py", line 889, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python2.7/site-packages/click/core.py", line 534, in invoke
return callback(*args, **kwargs)
File "/home/frappe/bench-repo/bench/commands/update.py", line 60, in update
_update(pull, patch, build, bench, auto, restart_supervisor, restart_systemd, requirements, no_backup, force=force, reset=reset)
File "/home/frappe/bench-repo/bench/commands/update.py", line 77, in _update
update_node_packages(bench_path=bench_path)
File "/home/frappe/bench-repo/bench/utils.py", line 449, in update_node_packages
update_yarn_packages(bench_path)
File "/home/frappe/bench-repo/bench/utils.py", line 462, in update_yarn_packages
exec_cmd('yarn install', cwd=app_path)
File "/home/frappe/bench-repo/bench/utils.py", line 159, in exec_cmd
raise CommandFailedError(cmd)
bench.utils.CommandFailedError: yarn install
Any help please…
KR
Fasil
Hi antiquark100
could you please provide the steps that you followed to resolve it?
KR
Fasil
Hi Fasil, the original question in this thread was the issue of the build breaking because of yarn. I had a similar issue and one or two small changes were required to ensure that yarn / npm runs as a non-root user. See my previous email above to get around the issue - a path variable must be added on Ubuntu 18 server to allow running the commands globally. I broke the implementation because I was not paying attention and for some reason ran some command as sudo. If I am not mistaking you are running all commands directly as root. That is not wise. You will have to follow the installation or upgrade guide strictly.