I tried updating various instances each time after update/ upgrade from 8.0.18/7.2.13 getting below error in console log. This has started happening after v8.0.20, even tried on latest release v8.0.23.
server os: Ubuntu 15 & Ubuntu 16
http:6787/socket.io/?EIO=3&transport=polling&t=1493040979461-36 Failed to load resource: net::ERR_NAME_NOT_RESOLVED
http:6787/socket.io/?EIO=3&transport=polling&t=1493040988459-37 Failed to load resource: net::ERR_NAME_NOT_RESOLVED
http:6787/socket.io/?EIO=3&transport=polling&t=1493040997461-38 Failed to load resource: net::ERR_NAME_NOT_RESOLVED
Please suggest solution if I can correct is without resorting to back-up, Thanks
update: bench setup socketio got below log: Console ERROR is still same
INFO:bench.utils:npm install socket.io redis express superagent cookie
/home/ubuntu/frappe-bench
├── babel-core@6.24.1
├── babel-preset-babili@0.0.12
├── babel-preset-es2015@6.24.1
├── babel-preset-es2016@6.24.1
├── babel-preset-es2017@6.24.1
├── chokidar@1.6.1
├── cookie@0.3.1
├── express@4.15.2
├── redis@2.7.1
├── socket.io@1.7.3
└── superagent@3.5.2
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.1.1
npm WARN enoent ENOENT: no such file or directory, open '/home/ubuntu/frappe-bench/package.json'
npm WARN frappe-bench No description
npm WARN frappe-bench No repository field.
npm WARN frappe-bench No README data
npm WARN frappe-bench No license field.
I tried: Google Chrome’s DNS Prefetching: Settings > Show Advanced Settings > Privacy and disable the option Predict network actions to improve page load performance.
But there’s no change in error, I don’t think this is browser related issue o/w I wouldn’t been able to replicate in other browser (eg edge/IE).
Even though the issue has not been reported, but I have gut feeling there is some fix required in frappe v 8.0.20 to fix this issue. Multiple instances giving same error doesn’t happen that often unless there a bug.
Tried restarting PC event tried on 2 other PCs, getting same error.
Still not able to identify root cause, but tried update on one more instance from frappe 8.0.18 to 8.0.23, getting same error in browser console
Everything seems to be working fine apart from this error, so its easy to be missed out unless one happens to check the browser console, this might be the reason its not been reported.
This can also be specific to Ubuntu server, and may not be getting replicated on CentOS. I would request core team to check if they are able to replicate the error.
Yes it looks like config error, tried bench setup production & restarted nginx & supervisor. Rebooted server as well.
Even manually compared config files of other instances with new, there is no difference in there.
Surprising thing is, I have tried updating 5 different instances all has os ubuntu 14/16, current version frappe version between 7.2.xx to 8.0.19 & in all after update getting same error. But no one else has reported it.
Can you check if it can be replicated at your end on Ubuntu.
supervisor.conf already exists and this will overwrite it. Do you want to continue? [y/N]: y
Port configuration list:
Site site1.local assigned port: 80
nginx.conf already exists and this will overwrite it. Do you want to continue? [y/N]: y
INFO:bench.utils:sudo /usr/bin/supervisorctl reread
No config updates to processes
INFO:bench.utils:sudo /usr/bin/supervisorctl update
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
INFO:bench.utils:sudo service nginx reload
nc -v localhost 9000 output is Connection to localhost 9000 port [tcp/*] succeeded!
I tried fresh install of ERPNEXT on ubuntu, it doesn’t have any errors.
I copied full config folder from new install to instance where I was getting error, run bench migrate & even rebooted server, still no success. Same error is still there
frappe@erpnext:~/frappe-bench/config$ sudo nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
In /var/log/nginx/error.log compare a working instance with one that does not.
Confirm the nginx startup has no errors. Here is an example of a client connection:
(In my case the web browser client runs on 192.168.0.104 that also hosts a kvm guest 192.168.0.105 that runs erpnext.vm - )
sudo nginx -t output
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
There are repeated errors in /var/log/nginx/error.log file
You want to check earlier in the log for signs that might explain what caused the error events later in the log - log areas to inspect are server startup, web client connections and client http requests.
To raise the log level output from say INFO to NOTICE in /etc/nginx/nginx.conf edit this line:
error_log /var/log/nginx/error.log info;
then restart the service with this command:
sudo service nginx reload
