Unable to access rdiffweb-backup data, permissions issue?

[Andy Forceno]

I'm having an issue where the repository information is not updating for one user (who I'll call andy). I am seeing errors in rdiffweb.log: 

[2017-01-08 17:07:15,739][WARNING][68.229.69.23][none][CP Server Thread-9][rdiffweb.librdiff] fail to parse date ['2017-01-03T06;05832;05803-05;05800']

Traceback (most recent call last):

  File "build/bdist.linux-i686/egg/rdiffweb/librdiff.py", line 316, in extract_date

    return rdw_helpers.rdwTime(date_string.decode())

  File "build/bdist.linux-i686/egg/rdiffweb/rdw_helpers.py", line 102, in __init__

    self._initFromString(value)

  File "build/bdist.linux-i686/egg/rdiffweb/rdw_helpers.py", line 128, in _initFromString

    raise ValueError(timeString)

ValueError: 2017-01-03T06;05832;05803-05;05800

Could this be a permissions issue? The rdiffweb-backup folder is owned by root. I've noticed the "admin" user has no such issue (admin's root directory is also owned by root). I had hoped that if I made andy an admin, the issue would go away. However, when I check the administrator box for andy (while logged in as admin), it never applies, and the count of admin users doesn't budge. I don't see anything in the log indicating what went wrong. I'm also getting a 500 error on the status page for andy, which again, makes me think this is a permission issue (the logs suggest rdiffweb can't parse the date files with the backup session information).

Does being an admin in rdiffweb grant you any special permissions to access files? If not, why can my admin user read the root-owned rdiffweb-backup folder by user andy cannot? Any thoughts or suggestions for this issue?>

[Patrik Dufresne]

Sorry for the long delay. I'm very busy these days.

Looking at the error message, it look like a filename or directory name contains the string "2017-01-03T06;05832;05803-05;05800". This is not a valid date format and it's not expected to happen.

May you have a look at the repository and try to find which files contains the given value. Then report back so I understand where it's coming from.

The expected date format is similar to the following

2017-01-03T06:32:03-05:00

The only valid reason this might happen is if rdiff-backup is broken. You may try to verify the version used to make the backup.

--

Patrik Dufresne Service Logiciel inc.

http://www.patrikdufresne.com/

514-971-6442

1-114 rue des Hautbois,

St-Colomban, QC J5K 2H6

--
You received this message because you are subscribed to the Google Groups "rdiffweb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdiffweb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Andy]

Thank you for replying. 

I believe I've found the issue. I have two repositories that backup to NTFS. It seems the colons in the filenames have been changed to semicolons. I suspect this is because colons are forbidden by NTFS. In that case, I will have to come up with an alternate way to keep an eye on those repositories, they must remain on the NTFS partition for various reasons. 

I use the same version of rdiff-backup (1.2.8) for other repositories on ext4 partitions, and the filenames look correct, so again, I suspect NTFS is at fault here. 

-Andy 

To unsubscribe from this group and stop receiving emails from it, send an email to rdiffweb+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "rdiffweb" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rdiffweb/w6Omvlpqq3A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rdiffweb+u...@googlegroups.com.