Problems with a specific user and device

[robertwbrandt]

We are still using Z-Push version (althought we are upgrading very soon)

I have a user that can't setup her account, when I try to look at her account I get:
Just for reference if I try a user that doesn't have a device I get:
Knowing that she only has one device, I ran the following commands:
Still the device won't sync and I get an error when looking up the user...

thinking there might be "hidden" state data for this user or device I ran these commands:
Nothing!!!

Any ideas?
Thanks, Bob

---------- Post added ----------

So I think I found the problem...

There is a file called "users" with a weird format...
I think it can be expanded like this...
I'm also assuming the 261 at the beginning is the number of users.

I did find zpushuser in this list, and I removed that entry, compacted the file and restarted Apache... But the z-push-admin commands showed that NO ONE had any devices after that. I had to quickly return to a backup of the file and after that everythign worked...

I think this file is the problem but I'm wondering how best to fix it.

Bob

[fbartels]

Hi Bob,

are you maybe looking for "z-push-admin -a fixstates"? What kind of a problem do you see with the users file? That he user in question is listed there?

I think a wbxml of the user could be interesting to see why the devices does not want to sync. As well as the actual version and device you are using (you only write "still using Z-Push version" without the actual version).

[robertwbrandt]

I tried "fixstates" and that didn't do anything...

The problem is I can see the problem user in question and the device it is complaining about in the users file. But there is no state file for that device anywhere in the states folder structure.

Is there a way to "fix" the users file?

Thanks
Bob

[fbartels]

If there is something to fix, then fixstates should fix it. While it may be true that the user is already in the users file, I am not really sure that is is also why it does not synchronise. This bit of information should be in the wbxml of that user.

[Sebastian]

Let me try put some light in this. The format of the users file is php's serialization format. The first number is not the amount of users, but the amount of elements in the array this file holds (which you could define as almost the same). Still, if you remove one line you need to adjust the number here. In general I wouldn't advise manipulating these files manually!

A few questions:
- Which version of Z-Push are you using? I think you wanted to say it in the first post, but the number is actually not there.
- What is the exact problem the user is having? What means "can't setup her account" exactly?
- What Android version is installed on this samsung device?

From the device id, the states should be located in /usr/lib/z-push/a/e/ and the filename starts with sec19e47bc96f3ea-*. If there is nothing there, then the states were already deleted (or never created). You can manually delete these files. This is btw exactly what "z-push-admin -a remove" does. It just removes these files.

The line in the 'users' file does not influence anything. It's just a mapping and you can leave it there.

In general, account setup is not related to any states. You should always be able to setup the account. This should not be blocked by any state, unless perhaps you have some permissions issue on your state directory.

I guess there is some issue on the OPTIONS request or in the provisioning.

Try creating a special log (add the username to $specialLogUsers in the config) for the user. This way the log is only created for the specified user and others are not affected.
I really think this is not state related at all, probably some other issue which we can probably figure out by looking at the log.
Feel free to send me/post this log.

Cheers,
Sebastian

[robertwbrandt]

You mentioned WBXML a couple times, but I can't find how to get the WBXML of a specific user.

Bob

[Sebastian]

Edit your config file. There is this block there. Put the username in the setting, so it looks like this:

If the user uses an email address as login, fill that one in.

Tell the user to try again. In your /var/log/z-push there will be a file named zpushuser.log.

Cheers,
Sebastian

[robertwbrandt]

This was spot on! Once I got ahold of the phone and could perform the tests we found that the FATAL error in the log was:
I later found that the directory /var/lib/z-push/a/e was owned by root, the www-data user had no access! How this happened is beyond me, but changing the permissions for the directory back fixed the problem immediately!