> thank you, Roberto. I tried that config, but got the error > > [cache-sync] getting cache dump from 127.0.0.1:7171 ... > [cache-sync] unable to connect to the server > > then I remove the sync=127.0.0.1:7171 part on slave, the error is > gone, but the slave can not get data in cache2 from master. With this > config (no sync=...) applied, i monitored the udp traffics on both > nodes. > > I use netstat -uanp | grep uwsgi on master, and get the following results: > udp 0 0 0.0.0.0:39792 0.0.0.0:* 15242/uwsgi > udp 0 0 127.0.0.1:7171 0.0.0.0:* 15242/uwsgi > > while on slave: > udp 0 0 127.0.0.1:7172 0.0.0.0:* 9431/uwsgi > > I think that means that the udp server on master is successfully > started up, and the slave is listening. Then I run tcpdump on them to > monitor udp traffic: > > on slave: > tcpdump -v -i em1 udp 7172 > > on master: > tcpdump -v -i em1 udp 7171 > > but no udp packets captured. what's going wrong? > > thanks, > >
the first sync happens at tcp level. Start in this way: uwsgi --socket :4040 --cache2 name=master,items=100 --load-file-in-cache /etc/passwd then uwsgi --socket :4041 --cache2 name=master,items=100,sync=127.0.0.1:4040 the second instance should print [uwsgi-cache] restored 1 items does it work ? -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
