BAD JSON RESPONSE on SearchDirectoryRequest

[anthony.rasat]

Hey all,

I just installed a brand new zcs-5.0.8_GA_2462.RHEL5 32bit and already filled it with 250+ users (without archives, just username+password) in 5+ domains.

A problem occur during admin console session, when I searched for an account from top bar. The error window said:

Server error encountered
Error code: BAD_JSON_RESPONSE Method: SearchDirectoryRequest

Dazzled, I continue to click "Accounts" in left sidebar. There it was again, same warning window as above.
Any suggestions? I'm using Firefox 3 browser on Hardy desktop.

Add more:
I tried Firefox 2.0 too. Still no luck.

Corresponding log entry in /opt/zimbra/log/mailbox.log

2008-08-14 00:00:38,660 INFO [btpool0-120] [name=admin@mydomain;mid=2;ip=xxx.xxx.xxx.xxx;ua=Zi mbraWebClient - FF2.0 (Linux);] soap - SearchDirectoryRequest

[rperez]

I am having the same exact issue, with the BAD_JSON_RESPONSE on Search Directory Request. Any way to solve this?

I am also seeing another JSON error on one of our users shared document.
A network error has occurred.
msg: A network error has occurred.
code: BAD_JSON_RESPONSE
method: GetWikiRequest

Any help would be great.

Thanks

RP

[grexk]

Same as Anthony but on windows using FF 3.0.1 and ZCS 5.0.9 on Centos5 64bit.

[Mudasar]

Before creating the account with the following command, i can edit my domain. but after that i am getting the same error.

Command

./zmprov createAccount user1@domain.com password displayName 'User1' givenName User sn 1


Mudasar

Thanks,

[sn00p]

The same problem.
After the execution of zmprov got the same error.

zcs-5.0.10_GA_2638.UBUNTU8_64.20081003052844

UPD
After zmproving ~12000 accounts error has changed to another
Message: number of results exceeded the limit: too many search results returned Error code: account.TOO_MANY_SEARCH_RESULTS Method: SearchDirectoryRequest Details:soap:Receiver

As the result - can't edit domain settings.

[wisu]

I am also having the same error, running

zcs-5.0.7_GA_2444.UBUNTU6.20080626025548

on dapper drake (Ubuntu 6.06.2 LTS)

any clues?

[cosmicwombat]

Ya, 5.0.10 GA Redhat 4 32... me too.

[jholder]

Can Someone please file a bug? If an NE customer, please contact support.

[anthony.rasat]

I think I partially narrowed down the cause of BAD JSON. The bandwidth. I said partially because sometimes I can't replicate it yet I was succeeded to do so just few seconds before.You see, instead of placing in DMZ part of my network's firewall, I placed Zimbra server in a remote colocation rack. I was starting to aware of bandwidth problem when it occured to me that it happened ocassionally when I use HSDPA modem. So, I built a test machine, connected to a multi-homed machine with linux bridge and CBQ traffic control, and that bridge connected to my laptop which act as requestor.My unconfirmed result is BAD JSON RESPONSE sometimes appeared when I instructed CBQ script to choke bandwidth down to 40Kbps and sometimes even 50kbps. I was using Advanced Mode of Zimbra Web client. But it was so sporadic that just few seconds after BAD JSON RESPONSE appeared, I was unable to replicate that error anymore. It left me scratching my head.Based on that partially successful (or partially failed) test, I tried to avoid BAD JSON error by placing traffic QoS based on my Zimbra's IP address for my network users. I think that this is (partially) solve questions from my original thread.

[sn00p]

Not our case )) Our servers are connected with each other through 10Gb link. Admin interface interacts with admin user through 1Gb link. The problem arises when we have over 4000 users in domain After ~12000 accounts error changes to another.
Some kind of users' limit I guess. Nevertheless this error is web-admin error but you could manage your server with CLI.