Try ERPNext Buy Support Partners Foundation

ERPNext On Windows 10

Thx @netmanthan right now I am doing installation and still not finish on windows home.

my windows version – Microsoft Windows [Version =10.0. build =18362.356]

I will update on result.

1 Like

Finally got installed ERPNext successfully, Thx a lot @netmanthan for you support and any other member who give me hints.

Now how to launch application, I have used http://localhost but no luck.

I have used exactly above steps , and below command submitted

sudo -H python3 install.py --production --site frappe.local --user frappe

1 Like

Congratulations nami

Try 127.0.0.1

Thx, same cannot get login page

Cannot reach this page

•Make sure the web address http://127.0.0.1 is correct

Hi,
Restart bench or Mariyadb

result
frappe@LAPTOP-5F23F7J8:~/frappe-bench$ bench restart
INFO:bench.utils:sudo supervisorctl restart frappe:
unix:///var/run/supervisor.sock no such file

1 Like

I think you should be using the port number 8000 or whatever number mentioned in the bench start trace after localhost like this:

localhost:8000

Already tried localhost:8000

Below my supervisor status
frappe@LAPTOP-5F23F7J8:~$ sudo supervisorctl status
frappe-bench-redis:frappe-bench-redis-cache RUNNING pid 335, uptime 0:02:30
frappe-bench-redis:frappe-bench-redis-queue RUNNING pid 333, uptime 0:02:30
frappe-bench-redis:frappe-bench-redis-socketio RUNNING pid 341, uptime 0:02:29
frappe-bench-web:frappe-bench-frappe-web RUNNING pid 328, uptime 0:02:30
frappe-bench-web:frappe-bench-node-socketio RUNNING pid 331, uptime 0:02:30
frappe-bench-workers:frappe-bench-frappe-default-worker-0 RUNNING pid 323, uptime 0:02:30
frappe-bench-workers:frappe-bench-frappe-long-worker-0 RUNNING pid 325, uptime 0:02:30
frappe-bench-workers:frappe-bench-frappe-schedule RUNNING pid 324, uptime 0:02:30
frappe-bench-workers:frappe-bench-frappe-short-worker-0 RUNNING pid 327, uptime 0:02:30

Any debug advice here,
all services are running, but cannot get login page?? how to trace it?

1 Like

Hi,

Try below command.
sudo mkdir -p /run/dbus
sudo service dbus start
sudo bench start

But I have created directory at install steps, shall I create them again?

and bench start why? I am in production where supervisor is there?am I wrong?

here all services status [-] means not started, [+] started…

frappe@LAPTOP-5F23F7J8:~/frappe-bench$ service --status-all
[ - ] acpid
[ - ] apparmor
[ ? ] apport
[ - ] atd
[ - ] console-setup.sh
[ - ] cron
[ ? ] cryptdisks
[ ? ] cryptdisks-early
[ + ] dbus
[ - ] dnsmasq
[ - ] ebtables
[ - ] fail2ban
[ ? ] hwclock.sh
[ + ] irqbalance
[ + ] iscsid
[ - ] keyboard-setup.sh
[ - ] kmod
[ - ] lvm2
[ + ] lvm2-lvmetad
[ + ] lvm2-lvmpolld
[ - ] lxcfs
[ - ] lxd
[ - ] mdadm
[ - ] mdadm-waitidle
[ - ] mysql
[ + ] nginx
[ - ] ntp
[ + ] open-iscsi
[ - ] open-vm-tools
[ ? ] plymouth
[ ? ] plymouth-log
[ - ] postfix
[ - ] procps
[ - ] redis-server
[ - ] rsync
[ - ] rsyslog
[ - ] screen-cleanup
[ - ] ssh
[ + ] supervisor
[ - ] udev
[ - ] ufw
[ - ] unattended-upgrades
[ - ] uuidd
[ - ] x11-common

my bench start command output

frappe@LAPTOP-5F23F7J8:~/frappe-bench$ bench start
15:07:21 system | redis_cache.1 started (pid=2197)
15:07:21 system | redis_socketio.1 started (pid=2199)
15:07:21 system | redis_queue.1 started (pid=2201)
15:07:21 system | web.1 started (pid=2204)
15:07:21 system | socketio.1 started (pid=2211)
15:07:21 system | watch.1 started (pid=2215)
15:07:21 system | schedule.1 started (pid=2217)
15:07:21 redis_socketio.1 | 2207:C 21 Sep 15:07:21.620 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
15:07:21 redis_socketio.1 | 2207:C 21 Sep 15:07:21.621 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=2207, just started
15:07:21 redis_socketio.1 | 2207:C 21 Sep 15:07:21.621 # Configuration loaded
15:07:21 redis_cache.1 | 2205:C 21 Sep 15:07:21.620 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
15:07:21 redis_cache.1 | 2205:C 21 Sep 15:07:21.621 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=2205, just started
15:07:21 redis_cache.1 | 2205:C 21 Sep 15:07:21.621 # Configuration loaded
15:07:21 redis_socketio.1 | 2207:M 21 Sep 15:07:21.622 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
15:07:21 redis_socketio.1 | 2207:M 21 Sep 15:07:21.623 # Server can’t set maximum open files to 10032 because of OS error: Invalid argument.
15:07:21 redis_socketio.1 | 2207:M 21 Sep 15:07:21.623 # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase ‘ulimit -n’.
15:07:21 redis_cache.1 | 2205:M 21 Sep 15:07:21.623 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
15:07:21 redis_cache.1 | 2205:M 21 Sep 15:07:21.623 # Server can’t set maximum open files to 10032 because of OS error: Invalid argument.
15:07:21 redis_cache.1 | 2205:M 21 Sep 15:07:21.623 # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase ‘ulimit -n’.
15:07:21 redis_cache.1 | 2205:M 21 Sep 15:07:21.629 * Running mode=standalone, port=13000.
15:07:21 redis_cache.1 | 2205:M 21 Sep 15:07:21.629 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
15:07:21 redis_cache.1 | 2205:M 21 Sep 15:07:21.629 # Server initialized
15:07:21 redis_cache.1 | 2205:M 21 Sep 15:07:21.629 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
15:07:21 redis_cache.1 | 2205:M 21 Sep 15:07:21.630 * Ready to accept connections
15:07:21 redis_socketio.1 | 2207:M 21 Sep 15:07:21.629 * Running mode=standalone, port=12000.
15:07:21 redis_socketio.1 | 2207:M 21 Sep 15:07:21.629 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
15:07:21 redis_socketio.1 | 2207:M 21 Sep 15:07:21.630 # Server initialized
15:07:21 redis_socketio.1 | 2207:M 21 Sep 15:07:21.630 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
15:07:21 redis_socketio.1 | 2207:M 21 Sep 15:07:21.631 * Ready to accept connections
15:07:21 system | worker_long.1 started (pid=2227)
15:07:21 redis_queue.1 | 2210:C 21 Sep 15:07:21.645 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
15:07:21 redis_queue.1 | 2210:C 21 Sep 15:07:21.646 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=2210, just started
15:07:21 redis_queue.1 | 2210:C 21 Sep 15:07:21.646 # Configuration loaded
15:07:21 redis_queue.1 | 2210:M 21 Sep 15:07:21.649 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
15:07:21 redis_queue.1 | 2210:M 21 Sep 15:07:21.649 # Server can’t set maximum open files to 10032 because of OS error: Invalid argument.
15:07:21 redis_queue.1 | 2210:M 21 Sep 15:07:21.649 # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase ‘ulimit -n’.
15:07:21 system | worker_short.1 started (pid=2219)
15:07:21 redis_queue.1 | 2210:M 21 Sep 15:07:21.652 * Running mode=standalone, port=11000.
15:07:21 redis_queue.1 | 2210:M 21 Sep 15:07:21.652 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
15:07:21 redis_queue.1 | 2210:M 21 Sep 15:07:21.652 # Server initialized
15:07:21 redis_queue.1 | 2210:M 21 Sep 15:07:21.653 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
15:07:21 redis_queue.1 | 2210:M 21 Sep 15:07:21.653 * Ready to accept connections
15:07:22 system | worker_default.1 started (pid=2228)
15:07:24 socketio.1 | listening on *: 9000
15:07:31 watch.1 | yarn run v1.17.3
15:07:31 watch.1 | $ node rollup/watch.js
15:07:32 web.1 | * Running on http://0.0.0.0:8000/ (Press CTRL+C to quit)
15:07:33 web.1 | * Restarting with inotify reloader
15:07:34 watch.1 |
15:07:34 watch.1 | Rollup Watcher Started
15:07:34 watch.1 |
15:07:34 watch.1 | Watching…
15:07:35 web.1 | * Debugger is active!
15:07:35 web.1 | * Debugger PIN: 197-908-859
15:07:36 watch.1 | Rebuilding frappe-web-b4.css
15:07:36 watch.1 | Rebuilding chat.js
15:07:37 watch.1 | Rebuilding frappe-recorder.min.js
15:07:40 watch.1 | Rebuilding frappe-web.min.js
15:07:42 watch.1 | Rebuilding bootstrap-4-web.min.js
15:07:43 watch.1 | Rebuilding control.min.js
15:07:45 watch.1 | Rebuilding dialog.min.js
15:07:46 watch.1 | Rebuilding desk.min.css
15:07:46 watch.1 | Rebuilding frappe-rtl.css
15:07:47 watch.1 | Rebuilding printview.css
15:07:47 watch.1 | Rebuilding desk.min.js
15:07:50 watch.1 | Rebuilding module.min.css
15:07:50 watch.1 | Rebuilding form.min.css
15:07:50 watch.1 | Rebuilding form.min.js
15:07:53 watch.1 | Rebuilding list.min.css
15:07:53 watch.1 | Rebuilding list.min.js
15:07:53 watch.1 | Rebuilding report.min.css
15:07:53 watch.1 | Rebuilding report.min.js
15:07:55 watch.1 | Rebuilding web_form.min.js
15:07:55 watch.1 | Rebuilding web_form.css
15:07:55 watch.1 | Rebuilding email.css
15:07:55 watch.1 | Rebuilding social.min.js
15:07:56 watch.1 | Rebuilding modules.min.js
15:07:56 watch.1 | Rebuilding barcode_scanner.min.js
15:07:57 watch.1 | Rebuilding erpnext.css
15:07:57 watch.1 | Rebuilding marketplace.css
15:07:57 watch.1 | Rebuilding erpnext-web.min.js
15:07:57 watch.1 | Rebuilding erpnext-web.css
15:07:57 watch.1 | Rebuilding marketplace.min.js
15:08:00 watch.1 | Rebuilding erpnext.min.js
15:08:00 watch.1 | Rebuilding item-dashboard.min.js

1 Like

bingooooo

2 Likes

Wow great!!

Congratulation

1 Like

thx a lot for your support, I will compile a note to share in the forum with lessons learned soon…

2 Likes

can i installed v11 instead of v12 version

try steps on this Tutorial, I am not sure but should work,

1 Like

thanks for replaying i will try my best installing erpnext windows 10 :wink: @nmami

Could you guide to me to lunch to erpnext after my bench start is okay but I link with that url (0.0.0.0:8000)

Bench Start