-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: "No contacts here" for address books with many contacts #258
Comments
any news? |
Do you have any error in your browser logs? |
And could you post the response from chrome network's tab on the contacts request? |
Please find below the network response from the contacts request: This is the XML output for the address book
This is the XML output for the contacts. Are these what you are looking for? I have only pasted the first 107 lines out of 76’808 response lines; please let me know if you need the entire output.
|
I've recently upgraded from owncloud 8.2.x to nextcloud 12 which comes with contacts 1.5.3. In the data base there are about 40 address books which are shared with different groups of people and there are totally about 2700 contacts. Even though the old owncloud app took very long to load all contacts when the contact page is opened, this new app takes even significantly longer to load, and in the mean time I also see this message. Also, once the contacts list has been loaded, if I click on one contact to see or change its details, it takes many seconds until the page is updated and the details are shown. :-( |
@mburnicki The next contact update will change a lot of things! |
@skjnldsv is there anything wrong with the XML output I posted? |
@CamZie Do you have access to your database? |
@skjnldsv Yes, I do have access to the database. How should I proceed? |
Could you go to the oc_cards table and get the vcard raw data of the biggest row you have? You can sort it by the carddata column since it includes the size as default blob sorting option :) I suspect a too big vcard breaking the php lib :) |
Any news? |
@skjnldsv We have removed the largest vcard with the size of 1018515 but still no success. Would you be able to tell us what the maximum recommended size would be for a vcard? |
Depends on your installation. But it could be a corrupted vcard. Maybe the PHOTO binary is corrupted and it's not a size issue. I'm sorry, but it's hard to see from my point of view! 😕 If you want, you can send me your vcf file at skjnldsv@protonmail.com, I won't use it other than testing. If you're trusting enough, it would greatly help me debug! :) |
Unfortunately I cannot share the vcf file, since it belongs to a customer. I will do some more tests and will let you know if there is some progress. Do you by any chance have a quick tip on checking the integrity of the vcf file? Or any other tests I can do to verify the problem? |
@CamZie I understand! :) |
@skjnldsv Sorry for the late response, but I have been doing some tests on my side. Error message in nextcloud.log
|
@CamZie is this still occurring with latest 2.1.1? |
@skjnldsv This issue with the "No contacts here" has been solved since the upgrade to 2.0.1. About the error "Invalid or unknown sync token" in the logs mentioned on my last post, I have opened another issue about this on the nextcloud/server repository #7793. |
Awesome! |
Steps to reproduce
Expected behaviour
Contacts should appear
Actual behaviour
No contacts are showing with "No contacts here" message
Server configuration
Operating system: Debian 7 (wheezy)
Web server: nginx 1.8.1
Database: MySQL 5.6.36
PHP version: 5.6
Nextcloud version: 11.0.2
Contacts version: 1.5.3
Updated from an older Nextcloud or fresh install: Updated from Nextcloud version 10.0.3
Signing status:
List of activated apps:
Nextcloud configuration:
Are you using encryption: yes
Client configuration
Browser: Safari/603.2.4 and others
Operating system: Mac OS X/10.12.5
CardDAV-clients: Apple contacts and Android CardDAV-Sync
Logs
Nextcloud log (data/nextcloud.log)
I have tried increasing the php memory limit from 512MB to 1024MB, but this did not help.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: