Hi NiLuJe
A request: where did you get that syntax to talk with cvm??? SDK??? Is that still available?
I went a little further... It seems that I can read access the cc.db file without any problem with sqlite3 (No I did NOT try to write anything). So I started to wonder if the error is really a password related issue (HTTP returning 401) as suggested by the
Unauthorized request! message output by cvm...
So I mofified the cc_update.py so that it output the http request status.
It now reads :
Code:
log(LIBRARIAN_SYNC, "cc_update", "Oh, no. It failed. error: "+str(r.status_code), "E")
The answer is now:
Code:
200802:143003 system: I tinyrot:def:Removing /var/local/log/messages_00000808_*.gz to save storage space
200802:143003 system: I tinyrot:def::Rotating file /var/log/netlog with max size 256
200802:143004 syslog-ng[880]: SIGHUP received, restarting syslog-ng
200802:143004 system: I LibrarianSync:main:: Starting...
200802:143004 system: I LibrarianSync:rebuild_from_calibre_plugin_json:: Rebuilding collections (Calibre)...
200802:143004 system: I tinyrot:def::Rotating file /var/log/odotlite with max size 2048
200802:143004 system: I LibrarianSync:cc_update:: Sending commands...
200802:143004 system: I tinyrot:def::No file to rotate: /var/log/odotlite
200802:143005 syslog-ng[880]: new configuration initialized
200802:143005 system: I tinyrot:def::Rotating file /var/log/wpa_supplicant with max size 128
200802:143005 system: I tinyrot:def::No file to rotate: /var/log/wpa_supplicant
200802:143005 cvm[4966]: E rc:request_callback:Unauthorized request!:
200802:143005 system: E LibrarianSync:cc_update:: Oh, no. It failed. error: 403
200802:143005 system: I LibrarianSync:main:: Done in 0.29s.
200802:143005 system: I tinyrot:def::Rotating file /var/log/metrics_generic with max size 64
200802:143005 syslog-ng[880]: SIGHUP received, restarting syslog-ng
200802:143005 system: I tinyrot:def:Removing /var/local/log/metrics_generic_00000338_*.gz to save storage space
This seems to suggest that the request
was refused (HTTP Status 403) probably because it expected a different environment...