The new data in docType list view doesn't update immediately

1

Hi, all

I just updated my local from V4 to V6. The updating seems success, but after I created a new user, I couldn’t see in User List even I clicked refresh, but if I use filter to input the ID I just created, it will be shown. I also tried in other doctype, it’s same, It seems the data is inserted into the database, but just not visible in the list immediately because if I tried to restart server, it will be shown as well.

Any reply will be appreciated.

2

Is there any error on console? If so please share a screen shot of console.

Here’s the help to open javascript console: web development - How do I open the JavaScript console in different browsers? - Webmasters Stack Exchange

3

Hi, saurabh6790

Thanks your reply. it’s my screen shot. looks everything is ok.
I suspect if it is my redis cache issue. when I’m running ‘sudo supervisorctl status’, there is just three lines which are pid frappe-web, frappe-worker and frappe-workerbeat.

4

Try by running, bench setup procfile then bench start

5

I run ‘bench setup procfile’, still same, no redis cache pid.

This is screen shot of bench start:

start.png899×583 45.9 KB

6

Is your proc file is same as,

web: bench serve
redis_async_broker: redis-server config/redis_async_broker.conf
socketio: /usr/local/bin/node apps/frappe/socketio.js
workerbeat: sh -c 'cd sites && exec ../env/bin/python -m frappe.celery_app beat -s scheduler.schedule'
worker: sh -c 'cd sites && exec ../env/bin/python -m frappe.celery_app worker'
redis_cache: redis-server config/redis_cache.conf
redis: redis-server
7

Could you tell me Where proc file is?

8

frappe-bench/Procfile

9

web: bench serve
redis_async_broker: redis-server config/redis_async_broker.conf
socketio: None apps/frappe/socketio.js
workerbeat: sh -c ‘cd sites && exec …/env/bin/python -m frappe.celery_app beat -s scheduler.schedule’
worker: sh -c ‘cd sites && exec …/env/bin/python -m frappe.celery_app worker’
redis_cache: redis-server config/redis_cache.conf

10

add above line to ypur procfile and check again.

11

After I added this line:
frappe:frappe-web RUNNING pid 2131, uptime 0:01:09
frappe:frappe-worker RUNNING pid 2130, uptime 0:01:09
frappe:frappe-workerbeat FATAL Exited too quickly (process log may have details)

Is my socketio having some problem? In my procfile is different with yours:
socketio: None apps/frappe/socketio.js

12

Now socketio problem is solved. Now my procfile is
web: bench serve
redis_async_broker: redis-server config/redis_async_broker.conf
socketio: /usr/local/bin/node apps/frappe/socketio.js
workerbeat: sh -c ‘cd sites && exec …/env/bin/python -m frappe.celery_app beat -s scheduler.schedule’
worker: sh -c ‘cd sites && exec …/env/bin/python -m frappe.celery_app worker’
redis_cache: redis-server config/redis_cache.conf

When I add ‘redis: redis-server’ at the bottom manually, the result is:
frappe:frappe-web RUNNING pid 2131, uptime 0:01:09
frappe:frappe-worker RUNNING pid 2130, uptime 0:01:09
frappe:frappe-workerbeat FATAL Exited too quickly (process log may have details)

By the way, I found there isn’t a redis.conf file in the config folder. Is it normal?

13

Hi,saurabh6790
today my v6 again, I found error on the console. Can you help me see again?

14

Everything is ok after I changed to using Chrome instead of IE.