I've touched a few other threads about this, but wanted to start a clean, focused thread. Today I upgraded one of my boxes from 3.1 to 3.2.1. So far everything seems fine execpt for one issue that I've been unable to figure out. When you navigate to the Infrastructure tab (by default landing on the Devices page) the page shell is rendered, however you see the "Loading please wait" for 5-10 minutes. It goes away without error however no devices are listed, and none of the organizers are shown on the left. If I search for a device using device search they are found, also if I type anything into the filter box on type of the device column the devices show up (still no organizers though). Some additional data points:

1) Navigating through the the ZOPE interface I can see all my devices, and groups so they appear to be there

2) Other screens on the Infrastructure tab are fine. I can view proccesses and networks without issues

3) Firebug indicates its the post to device_router that never returns

This seems to be common after upgrades but it seems to be resolved by clearing browser caches. I tried that without success. I even tried from a machine thats never logged in before.

Based on some feedback in the IRC channel I have tried to run:

zencatalog run --forceindex --createcatalog

This ran without incident, but my problem persists.

I've trolled through the logs and I am not seeing anything that is jumping out at me as a problem.

Anyone seen this before, or have any suggestions on what I can check next?

To add a little more details around the device_router post. I can see that it churns for a while before showing as aborted. I grapped the post parameters that it was sending to see if I could reproduce the stall using the JSON API. Here are the post params, wrapped for readability:

{"action":"DeviceRouter","method":"getProductionStates","data":[{}],"type":"rpc","tid":4}

{"action":"DeviceRouter","method":"getPriorities","data":[{}],"type":"rpc","tid":5}

{"action":"DeviceRouter","method":"getCollectors","data":[{}],"type":"rpc","tid":6}

{"action":"DeviceRouter","method":"getDevices","data":[{"sort":"name","dir":"ASC","params":"{\"productionState\":[\"1000\"]}","start":0,"limit":50}],"type":"rpc","tid":7}

{"action":"DeviceRouter","method":"getUserCommands","data":[{"uid":"/zport/dmd/Devices"}],"type":"rpc","tid":8}

{"action":"DeviceRouter","method":"asyncGetTree","data":["/zport/dmd/Devices"],"type":"rpc","tid":9}

{"action":"DeviceRouter","method":"asyncGetTree","data":["/zport/dmd/Groups"],"type":"rpc","tid":10}

{"action":"DeviceRouter","method":"asyncGetTree","data":["/zport/dmd/Systems"],"type":"rpc","tid":11}

{"action":"DeviceRouter","method":"asyncGetTree","data":["/zport/dmd/Locations"],"type":"rpc","tid":12}]

I went through each one these one by one hitting the JSON API and they all return quickly, and with what appears to be accurate data.