Then, you need to assign erpnext user to sudo group and assign the password. Looks like you have installed mariadb under a different user and did not do the necessary config.
Reinstall the system with the sequence I have laid down and you will be up and running in no time.
Reinstall Ubuntu 18.0.4LTS. Do apt update and apt upgrade as root. Reboot.
Install pyhton3-setuptools python3-minimal redis-server build-essential
reboot
Download and run the Easy Install script with proper parameters on sudo -H switch.
assign a password to erpnext user and add it to sudoers
login with erpnext user and go to bench folder
I tried your method above and ran into the same issue when “bench init frappe-bench” runs as the last part of the install. In addition, I still had to to a manual wget for the wkhtmltox file.
Any ideas what I could be doing wrong.
The install base is a clean 18.04.1 VM guest on Proxmox.
Hi @ekabyte could you please put a note in the forum with lessons learned so any other community member could get benefit of your experience. you can add mistakes to avoid and clean steps (detailed) so even beginner can follow.
Then install the erpnext by using this command (it will take nearly 45 minits to run in 4GB virtualbox image, below command install all the requisite for erpnext (example nginx, mariadb etc ):
Just a doubt, by the way Thanks a lot to write steps it’s very helpfull I like it,
below command I see “–mysql-root-password your_password --admin-password your_password --bench-name your_bench_name” shall I changed or keep it as it is?
ex: your_password I should remove this text and replace it right? or can you give dummy command sample…
One tricky point:
In case you receive redis-server configuration errors, possibly you have disabled ipv6 on the system. The default configuration does not recognize this and throws error while trying to bind to the ipv6 loopback interface.
Just edit /etc/redis/redis_conf file and edit the bind line erasing ipv6 related address.
This is extremely helpful. Don’t know how many times I was going around in circles with the documentation on Github trying to resolve dependencies. This method cleared the fog out of my eyes and I’ve spun up a working instance finally. To anyone reading this - use @ekabyte 's process here for v12!
Glad to see things shifting out of the “inbetween time” and full time python3 but I think that might be a bit of what’s been causing confusion in the documentation for some. Guess it hasn’t been updated yet!
In particular, it’s mentioned as an option in the github docs but then there is the suggestion to use an alias to the old python names before the easy-install script, which causes errors of course and makes the script fail (ie: alias python=python3 implies that the install wants python, but really it’s python3…don’t use the alias any longer I guess)
Perhaps you meant to type the other, but did you try python3 for the packages instead of python? AFAIK the new ERPNext requires python3 (correct me if I’m wrong?)