Having issues with a postgres database after migrating to new server. This is a moodle application, the symptom is a setup screen after the migration rather than the migrated site, this indicates that moodle can't find it's path, config or database tables. After verifying the path and config...
update = ERROR: role "admin" cannot be dropped because some objects depend on itDETAIL: owner of database domain_moodle5 objects in database domain_moodle5
I am having a very similar issue - but the database is created as is the user and tables but it appears that the user has no access to the tables!
It is a moodle installation - when going to the page it defaults to the install screen - indicating moodle either can't find the tables or database...
increasing the log verbosity does now show that notifies are being refused:
```
26-Feb-2025 11:00:36.414 general: info: zone _domain_.com/IN: refused notify from non-primary: _ns1_#60939
26-Feb-2025 11:00:36.414 general: info: zone _domain_.ca/IN: refused notify from non-primary: _ns1_#46639...
Same behavior from both the source and target servers, notifies are sent, only the source receives a transfer request. no errors or warnings on bind logs on any of the 4 servers...
I'm having an issue with: Slave DNS servers not updating zone from target server after migrating domain from source server.
I have a new Plesk server (target) setup and am trying to migrate all domains from the old server (source).
Both slaves (ns1 & ns2) are set up on both source and target...
trying to migrate subscriptions to a fresh Plesk installation but the migrator is giving me an error:
Problem is that on the new installation systemd is not listed as an option!
What is the solution for this?
It happens frequently - on a weekly basis at least. Starting and stopping processes isn't resolving the root problem, you just have to repeat it a week later.
Having strange problems with any operations that plesk queues , the task manager appears to be trying to run a task with an ID that does not exist in the longtasks table, furthermore, the config file the plesk-task-manager service is trying to use does not exist!
The result is that...
Found the solution:
select d.`name`, l.* from SubscriptionProperties sp
left join Subscriptions s on s.id = sp.subscription_id
left join domains d on d.id = s.object_id
left join Limits l on l.id = sp.value
where sp.`name` = 'limitsId' and l.limit_name = 'expiration'
order by value;
the...
still does not match up.
select s.id, s.object_id, d.name, l.* from Subscriptions s
left join domains d on d.id = s.object_id
left join Limits l on l.id = s.id
where l.limit_name = "expiration"
order by d.name DESC;
the object id seems to match the domain id, but not the limits... whether you...
I don't see anything in the domains table indicating a subscription ID, the domain id and cl_id do not match the limits table. I don't see any tables indicating they might be a subscription.
Where does the subscription ID come from & how does it relate to the domain & limit table?
Sorry -...
@IgorG - I see you found the question on stackexchange as well. I have not tested your solution, it may work fine, but I'm running the report from a replicated copy of the psa database [I run a nightly backup of the production environment to my development environment] & the plesk...
I used to have this neat little report that ran on a dashboard I have for my daily stuff that would report on the expiration dates of all my hosted plesk domains [Plesk 9]
It looked like this:
select d.name, l.* from Limits l
left join domains d on l.id =d.id
where l.limit_name =...