Hey all, is there a place this info can be found if your dashboard is down and you don't have access to the system info page / update section? Need to restore but unsure what version I was on around ~apr9th (7.6.___?)
ethanxrosen
Posts
-
What is Cloudron latest version? -
Renaming book throws permission error after using cloudron file managerthis is what i get from ls -ld
drwxr-xr-x 147 ubuntu ubuntu 4096 Jan 14 19:16 library/
-
Renaming book throws permission error after using cloudron file managerHi All, I attempted to upload a number of audiobooks to calibre web using the cloudron file manager, as 1-by-1 via the calibre web interface would have been painstakingly slow.
I downloaded /library to my desktop, opened it with calibre locally, added the audio files, then re-uploaded the entire folder (including metadata.db based on advice from previous threads). Things seemed to be working fine and this process was fairly quick, until attempting to fetch metadata on some books which renamed author and/or title. Calibre web threw this error:
Rename title from: '/app/data/library/Betty Smith/A Tree Grows in Brooklyn (154)' to '/app/data/library/Betty Smith/A Tree Grows in Brooklyn (154)' failed with error: [Errno 2] No such file or directory: '/app/data/library/Betty Smith/A Tree Grows in Brooklyn (154)'
When i look in file manager I can see a duplicate folder with different capitalization, and in calibre the book formats/files I had in the older folder are no longer accessible.
I believe this has something to do with permissions of the calibre web user as I'm seeing a similar error to https://github.com/janeczku/calibre-web/issues/637. I thought this might be related to the specific library folder I uploaded so I restored to a previous backup of calibre-web, however (quite unfortunately) the issue still persists now even when using my old un-tampered library.
Anybody have advice on how to fix the permissions of my library folder, or other insights into the source of the issue?
-
Joplin not responding - db: Could not connect@girish this was an old install, and it looks like a new install works OK
there's one extra line in the new config vs old:
# add custom configuration here. be sure to restart the app if you edit this file # https://github.com/laurent22/joplin/blob/dev/packages/server/src/env.ts SIGNUP_ENABLED=0 TERMS_ENABLED=0 MAX_TIME_DRIFT=100 <--- wasn't in old install
I tried copying it over to see what it would do but the app still seems unresponsive. When i try cloning from backup the same error appears. Is there a way to repair / restore the env file?
-
Joplin not responding - db: Could not connect@girish, are there any other logs / info that would be helpful or things I could try on my end?
-
Joplin not responding - db: Could not connect -
Joplin not responding - db: Could not connectHi All,
Joplin on my server hasn't responding the last week or so. So far I've tried app reboot, reconfigure, and a server reboot. It looks like the app has been looping through this error in the logs:
Apr 08 11:19:02 2023-04-08 18:19:02: App: Starting server v2.10.11 (prod) on port 3000 and PID 35... Apr 08 11:19:02 2023-04-08 18:19:02: App: NTP time offset: -35ms Apr 08 11:19:02 2023-04-08 18:19:02: App: Running in Docker: true Apr 08 11:19:02 2023-04-08 18:19:02: App: Public base URL: ___________________ Apr 08 11:19:02 2023-04-08 18:19:02: App: API base URL: _______________ Apr 08 11:19:02 2023-04-08 18:19:02: App: User content base URL: _____________ Apr 08 11:19:02 2023-04-08 18:19:02: App: Log dir: /app/code/packages/server/logs Apr 08 11:19:02 2023-04-08 18:19:02: App: DB Config: { Apr 08 11:19:02 client: 'pg', Apr 08 11:19:02 name: '_____________________', Apr 08 11:19:02 slowQueryLogEnabled: false, Apr 08 11:19:02 slowQueryLogMinDuration: 1000, Apr 08 11:19:02 autoMigration: true, Apr 08 11:19:02 user: '__________________', Apr 08 11:19:02 password: '********', Apr 08 11:19:02 port: 5432, Apr 08 11:19:02 host: 'postgresql' Apr 08 11:19:02 } Apr 08 11:19:02 2023-04-08 18:19:02: App: Mailer Config: { Apr 08 11:19:02 enabled: true, Apr 08 11:19:02 host: 'mail', Apr 08 11:19:02 port: 2525, Apr 08 11:19:02 security: 'none', Apr 08 11:19:02 authUser: '____________________________', Apr 08 11:19:02 authPassword: '********', Apr 08 11:19:02 noReplyName: 'Joplin', Apr 08 11:19:02 noReplyEmail: '___________________' Apr 08 11:19:02 } Apr 08 11:19:02 2023-04-08 18:19:02: App: Content driver: { type: 1 } Apr 08 11:19:02 2023-04-08 18:19:02: App: Content driver (fallback): null Apr 08 11:19:02 2023-04-08 18:19:02: App: Trying to connect to database... Apr 08 11:19:02 2023-04-08 18:19:02: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:03 2023-04-08 18:19:03: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:04 2023-04-08 18:19:04: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:05 2023-04-08 18:19:05: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:06 2023-04-08 18:19:06: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:07 2023-04-08 18:19:07: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:08 2023-04-08 18:19:08: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:09 2023-04-08 18:19:09: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:10 2023-04-08 18:19:10: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:11 2023-04-08 18:19:11: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:12 2023-04-08 18:19:12: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:13 2023-04-08 18:19:13: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:14 2023-04-08 18:19:14: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:15 2023-04-08 18:19:15: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:16 2023-04-08 18:19:16: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:17 2023-04-08 18:19:17: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:18 2023-04-08 18:19:18: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:19 2023-04-08 18:19:19: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:20 2023-04-08 18:19:20: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:21 2023-04-08 18:19:21: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:22 2023-04-08 18:19:22: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:23 2023-04-08 18:19:23: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:24 2023-04-08 18:19:24: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:25 2023-04-08 18:19:25: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:26 2023-04-08 18:19:26: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:27 2023-04-08 18:19:27: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:28 2023-04-08 18:19:28: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:29 2023-04-08 18:19:29: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Healtheck error: Error: connect ECONNREFUSED 172.18.18.23:30002023-04-08T18:19:30.000Z 2023-04-08 18:19:30: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:31 2023-04-08 18:19:31: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:32 2023-04-08 18:19:32: db: Could not connect. Will try again. Cannot read properties of undefined (reading 'name') Apr 08 11:19:32 2023-04-08 18:19:32: [error] db: Timeout trying to connect to database: TypeError: Cannot read properties of undefined (reading 'name') Apr 08 11:19:32 at /app/code/packages/server/src/db.ts:411:25 Apr 08 11:19:32 at Generator.next (<anonymous>) Apr 08 11:19:32 at fulfilled (/app/code/packages/server/dist/db.js:5:58) Apr 08 11:19:32 at processTicksAndRejections (node:internal/process/task_queues:95:5) Apr 08 11:19:32 Error: Timeout trying to connect to database. Last error was: Cannot read properties of undefined (reading 'name') Apr 08 11:19:32 at /app/code/packages/server/src/db.ts:118:10 Apr 08 11:19:32 at Generator.next (<anonymous>) Apr 08 11:19:32 at fulfilled (/app/code/packages/server/dist/db.js:5:58) Apr 08 11:19:32 at processTicksAndRejections (node:internal/process/task_queues:95:5)
Does anyone have advice on how to get it working again?
-
Customize '3 week app update' special backup retention policy for nextcloudUse case-
Nextcloud updates very frequently, meaning that even if you only intend to keep 1-2 app backups at a time, you can end up with 5 or 6 due to cloudron's 3 week app update policy: https://docs.cloudron.io/backups/#retention-policyIf you have a 1tb nextcloud, this triples the storage costs / box space and adds up really quick. I think this is especially unnecessary when many people will also have a physical drive synced via the nextcloud client as a third backup.
You can delete these backups manually from your storage provider if you remember to, but it would be awesome to have an option to customize this, so people can enable automatic updates+backups of large apps in cloudron without driving too much cost.
-
Optimal settings for Backblaze or other s3 backup servicesFinally managed to get backups stable with backblaze for a ~1TB cloudron with these settings (using encryption and rsync):
Some notes:
- During initial backups, memory was by far the most common failure. The amount needed was higher than I first expected for a given upload size and concurrency. I found (upload part size) x (upload concurrency) x 4 was roughly the amount needed. i.e. (64mb)*(20)*4 = ~5120mb.
- Scheduling backups at a time when server load is low and allotting as much memory as comfortable helped stability a lot. I ended up keeping my memory limit much higher than strictly necessary. This could probably be reduced, but stability is more important to me at the moment.
- In the graph above memory tended to spike once per backup- @girish maybe this is an issue that could be optimized?
- After initial upload, the memory required for subsequent rsyncs dropped off significantly as expected
- Uploading ~1TB of data with the above took approx. 24h
Curious to see what others find from optimizing these further, but glad to have a working baseline in the mean time.
I'm also curious to see what people's monthly bills tally up to. Waiting for the first month's bill to come in but B2 seems more cost effective than Wasabi so far!
-
Backblaze encrypted backup with Rsync failsFor future reference i managed to clear it up by using a slightly modified version of Girish's search command. It seems like the length limit applies to path length not just the filename length
find . -type f -print|awk '{print length($0), $0}' | sort -n
Went into the web interface and deleted / renamed files longer than 156 bytes and finally cleared trashbin/versioned files
(wipes all deleted / old versions of files - careful):
sudo -u www-data php -f /app/code/occ versions:cleanup sudo -u www-data php -f /app/code/occ trashbin:cleanup
@robi @girish agreed it would be awesome if there was an automated way to handle this in the future
-
Backblaze encrypted backup with Rsync failsHi All, I am unable to complete backup of a nextcloud instance (~500gb) with backblaze. I know cloudron backup is not usually recommended for larger apps but I thought I'd give it a shot again now that more backup parameters are tweakable. The error I am seeing seems related to encrypted file name length, here it is below:
Error uploading snapshot/app_<nextcloud app id here>/KQtuToxscu6Wp+TQwes2r+Zt37fqVz9KBKw9r3zlGFo/rLwS54KpQJ5BUWx9Wf57gBjNtYl00DkPTpRIO7DHr6E/TQkmjgv8A-8ri6mQv26IOC3SBV98HjxGQYu7Wj942Bc/uROadiwRY44JGJ7Dx8MZs9Tl43w1dViTXgkUZQELVs4/gfgicTfaoUCSMjUN1MOOBnZV3VIOt-jmyeRQIYHGPgs/yROzi4S0rB1UDLZciqxuJMHauKsCowwWvn14ymMFMCo/zK0oecogUE+CWK3JQQCDlW2mmn2Ny-BzrmGk3QokTgk/jOMbp4bhfQklbq5PlI9VYAxfjWMDqO-kd04br5t9gp4/Bdj3Hxfg03RHtuW1vhWh30hEtbB9hS75XLlvUkpdn5M-orp0303DwHg86Kj0jH+Z/hVvdpoNTbKd5ttdU9ZK5JkxtksDlRByNTlLrKZ0Kd5w/7Z2EkbU6DDooF1el4rNzETh4Hi9hW4gqC1yNKEy2byo/s788Z0aGNJt5k5t4LUbO8bmitJ+Y2lTTeYbNV-aDguk/TyEoW0Ge6PJHTg6BeGnNuN4ATowyTxWeejACY22-tgeQA7KJlA7-LVNN-ANz+xc8/DYluRyzYVRZRwR+OtWyLsND675uSdAq7WOzPwbl7tH4/jLUYu3qxS96Fj5-MwYq0YowSytZATPSJkcoBi-JbVgY/Hnvhas87QQpcrWkXBVoITd-eMTXxw6Gh4xCov9sqVsc/0y6Kh1Lt99UO6RdBTII7kgHHoPVLeSu9r-6HWmzi5MSBa9ioD6J9pkSDgI6bPq6a/7Z2EkbU6DDooF1el4rNzETh4Hi9hW4gqC1yNKEy2byo/Hnvhas87QQpcrWkXBVoITd-eMTXxw6Gh4xCov9sqVsc/1GQ+V1wtz+KCmZU1hEcQb0Wf0ZxKEAZhoejV31Cr6Lg/+tqCfG-K-nTRG3LiFmWOSqRg1HmzpiqY2ytGbHNF8Xxh4xhfznEEAfrMKhJIKDFl. Message: File name in UTF8 must be no more than 1024 bytes HTTP Code: InvalidRequest
-
/run/udev/data folder fills up over time, eventually crashing dashboard@girish Ubuntu 16.04.4 LTS, ah I just spotted this article: https://docs.cloudron.io/guides/upgrade-ubuntu-20/ will try upgrading and see if the issue persists
-
Cannot connect to transmissionThanks for the quick response @mehdi !
Noted, switching to using black hole in that case
-
Cannot connect to transmissionHey All,
I get an error when attempting to link couchpotato and transmission in the downloader settings menu with these inputs:
Host: https://transmission.my-example-cloudron.com
RPC url: transmission
user: [cloudron username]
password [cloudron password]These seem to be work fine in SickChill but CP returns this error:
ERROR[.downloaders.transmission] Config properties are not filled in correctly, port is missing.
Adding a port to the end of the transmission url doesn't seem to solve it. Anyone else having this issue?
-
/run/udev/data folder fills up over time, eventually crashing dashboardHi All,
I've seen an issue twice in the last few months where /run/udev/data will fill up the /run partition overtime, eventually crashing the dashboard. Restarting the server seems to clear this folder and the server comes back online, but obviously it would be best not to have the server go down every few weeks.
Below is output of some disk usage commands. Please let me know if there's any other info I can provide!
Best,
Ethanroot@localhost:~# df -h Filesystem Size Used Avail Use% Mounted on udev 2.0G 0 2.0G 0% /dev tmpfs 393M 393M 0 100% /run /dev/sda2 20G 11G 8.0G 57% / tmpfs 2.0G 0 2.0G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup /dev/sda1 487M 36M 422M 8% /boot /dev/sda3 1.8T 795G 927G 47% /home overlay 1.8T 795G 927G 47% /home/docker/overlay2/9a5e282fdcd9ec4681c0d1c0fb15f7a7ff7eda0ece5e4b9e0a68762692eae35e/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/0bdf5e13f8a83ca3ebebc87212922638eb4d9ded7d7accaa3e20ddeda5dced92/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/45613b260840f06be967ef5fdf248007199891fa2f7f9d4847e6ba6398804db4/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/476f326bbc83b1900d923072d7ba3e263b27e9467d4cf4a6e1920bf33ce03e58/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/a237010796d9a5da3b27631eca065d2e103da31dcaba2e1877d7c4fade19d218/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/7169515c216da9e1913b8c39ea96296790571f7c022c988496b76ae49ba73436/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/193a0fd036a1b7deaba4fbcf59b7cb64e37178df637b7cd65c041d55151bdf3e/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/a29651b2ee737f945aadbf52e025e5a1bb0fad78b4a2eed0f1e50f51eec1b268/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/8d142cc736c9e0512dc809a99e45158f9a9ba2552fb741935a2de26ea2a80165/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/942491a3968de0663f8116d94afe22f0e0e8755676e7c4f2d82e8649fb587857/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/0ca4d556581ee79190f7948caa097be42fc9cf7c8e928f759a7af8022c682fb9/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/242df83b4d74aa35ca500b2eda722b96210fcbffa1cce39a6332d4d2d23fc8ac/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/a196773d462838d7b38a8f44d9b44557022ed24784bcc2f700331fa471fc5272/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/dd4da96ca820fbe61e77a27cb02346742d4c1afc710097b74d8f52d31e8b0517/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/bc6b0bea1be9dae8eb85b73b38f54c7504216b1941cf9f1e9a528c442696c6d5/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/37fbe6e6b9b452c17f1f8de2a5267018f85c6a3983f46998052f80278dbe50b1/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/a2b82c8008d0f0e210866b2c77864d26b2b1fcb1d8ea195ecf81f50f7bdbb4ed/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/9ad83b3b2ab5055882503162f952c9c442a10fbc17c80d09f62084c42f23bfe6/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/cfd2bd3867197e60d4eebf99e8df3423ab5dde864b3191fdf7b9393afe22b3ef/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/d7e51bc7bae2d8cdc16799e7b9579e8a1f85c443d35acd6b028c07e2f8576b74/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/02dcfe4cdb631a7121cb8a37efccefe70ef5adbef9aa1f2ccaff2bd09fa48002/merged overlay 1.8T 795G 927G 47% /home/docker/overlay2/aba28e860dab3232388fee0d24a7e36dbbbe9bffa8738742fe2461b74f42569e/merged tmpfs 393M 0 393M 0% /run/user/0
root@localhost:/run# du -a | sort -n -r | head -n 5 402000 . 400320 ./udev/data 400320 ./udev 708 ./docker/runtime-runc/moby 708 ./docker/runtime-runc
-
How can I customize the folder for listening for new .torrents, and moving a file to once downloaded?Hi @mehdi, Wondering if this feature is included in the app / if these folders can be set to Cloudron volumes
-
No mailbox selected errorThanks Girish that is it- I'll have to manually move over my calendar / contacts it looks like but the emails are there
-
No mailbox selected error@girish yup you are correct - nu.sogo.cloudronapp@2.0.1