~whynothugo/pimsync#165: 
"Could not parse configuration file" when can't fetch password

I see this in my logs

mars 16 23:42:58 tatooine systemd[2729]: Starting pimsync calendar&contacts synchronization...
mars 16 23:42:58 tatooine pimsync[2995214]: Error: Could not parse configuration file at /home/teto/.config/pimsync/pimsync.conf
mars 16 23:42:58 tatooine pimsync[2995214]: Caused by:
mars 16 23:42:58 tatooine pimsync[2995214]:     0: resolving password for storage
mars 16 23:42:58 tatooine pimsync[2995214]:     1: Command exited with status 127.

If I run the command in a shell I get

pimsync sync                              
Error: initialising application
Caused by:
    0: initialising storage calendar_nova_gmail_remote
    1: input/output error: error performing webdav request: http request returned 401 Unauthorized
    2: error performing webdav request: http request returned 401 Unauthorized
    3: http request returned 401 Unauthorized

so I believe the message "Could not parse configuration file" is faulty. In the first excerpt, pimsync is just not able to fetch my password. The 2nd example gives another error but it shows that pimsync can parse the config.

With pimsync 0.3.0

Status
REPORTED
Submitter
~teto
Assigned to
No-one
Submitted
a month ago
Updated
a month ago
Labels
0:bug

~whynothugo a month ago

Commands are resolved while parsing the configuration, that's why you'll see Could not parse configuration file … when the command fails. This should be improved upon.

The failure which you're seeing in your logs is entirely different from the one that you're seeing when running via a shell; it seems that your password command fails to run in that environment.

Register here or Log in to comment, or comment via email.