Not found: Unable to find container postgresql
-
I moved my cloudron instance from one ec2 instance to another in another AWS account. I was able to setup the new instance using the cloudron backup. But when trying to recover a custom app, I get this error:
Not found: Unable to find container postgresql
The custom app uses its own postgresql container. How can I fix this?
-
@saikarthik Is the service running under Services? Is Postgresql green there?
Also, when you say the app uses it's own postgresql container, do you mean you wrote a custom app that has postgresql inside it?
-
- postgresql service was off. I clicked on restart and started the recovery from backup option again and I got a new error:
An error occurred during the import operation: External Error: EPERM: operation not permitted, utime '/home/yellowtent/appsdata/42aecba7-1aa8-43c5-a183-8a27d2c3a6d8/'
From the logs:
Nov 23 16:45:16 box:backuptask tarExtract: extract stream error. [Error: EPERM: operation not permitted, utime '/home/yellowtent/appsdata/42aecba7-1aa8-43c5-a183-8a27d2c3a6d8/'] { errno: -1, code: 'EPERM', syscall: 'utime', path: '/home/yellowtent/appsdata/42aecba7-1aa8-43c5-a183-8a27d2c3a6d8/'
Quick follow-up, how should I access what services need to be on in the services section?
- No, the custom app uses the PostgreSQL addon.
-
@saikarthik if an app (in this case your custom app) wants to use any of the available addons, then they have to be added to the services section of the CoudronManifest.json see https://docs.cloudron.io/packaging/addons/ for all addons
Regarding the permissions, this seems to be now related to the app itself. Can you check if this folder is owned by the user
yellowtent
? -
@nebulon Yes, this was a working app. Still works in the old instance. I am just trying to move it to another instance using backups and facing these issues.
I do not recognize yellowtent. Is this something internally used by cloudron? I don't have a user called yellowtent for the app itself.
-
@saikarthik
yellowtent
is just the name of the unix user for the Cloudron related processes (it used to be the codename of our first prototype ). It is not available to the app, but in this case you have to ensure the permissions on the system itself for that folder are correct. So do this via SSH. -
Would be good to know what the permissions of
/home/yellowtent/appsdata/42aecba7-1aa8-43c5-a183-8a27d2c3a6d8/
are as it stands right now. Strange to seeEPERM
error there. The restore logic usually cleans up the old directory content (as root) and then restores as a "normal" user (theyellowtent
user).(I have a task to rename the 'yellowtent' user to 'cloudron' at some point, but it requires some work. And unfortunately, some users have already created a 'cloudron' user in some of their installations.)
-
@girish said in Not found: Unable to find container postgresql:
(I have a task to rename the 'yellowtent' user to 'cloudron' at some point, but it requires some work. And unfortunately, some users have already created a 'cloudron' user in some of their installations.)
The owner was ubuntu. I manually changed the owner and group to yellowtent and that fixed the issues, and the app is running fine now. However, the old postgres data is missing. Is there some manual process required to move the postgres data from old instance to new instance? How can I achieve this?
-
Followed this guide and everything is back to normal. Thanks guys!
https://docs.cloudron.io/guides/import-postgresql/