This is mainly so that this is documented somewhere: It seems at some point, either during move of the shorturl service to the current server or sometimes afterwards, the shorturl service must have broken in some way. This led to short urls not being generated, delays in the UI because of those requests and probably also existing shorturls not working.
Somehow, the files used as a counter and as a database were not accessible (the regular user had no read rights, and both permissions and user/group were shown as ????.
This is fixed for now, by using db_new as a directory for data storage, instead of db. However, this also means old urls do not work anymore. As it was probably broken for a long time, it should not affect too many people I hope. That said, long term maybe either an appropriate external service should be used, or the service should use sqlite instead of plaintext files. It might also be possible to restore old entries, if the data is actually still there and just not accessible.
step21
commented
4 months ago
This is mainly so that this is documented somewhere: It seems at some point, either during move of the shorturl service to the current server or sometimes afterwards, the shorturl service must have broken in some way. This led to short urls not being generated, delays in the UI because of those requests and probably also existing shorturls not working. Somehow, the files used as a counter and as a database were not accessible (the regular user had no read rights, and both permissions and user/group were shown as
????. This is fixed for now, by usingdb_newas a directory for data storage, instead ofdb. However, this also means old urls do not work anymore. As it was probably broken for a long time, it should not affect too many people I hope. That said, long term maybe either an appropriate external service should be used, or the service should use sqlite instead of plaintext files. It might also be possible to restore old entries, if the data is actually still there and just not accessible.