Recurrent postgreSQL issues
Today is another time of the year I got this "CMS failed to connect error", unlike previous few times, I wasn't able to relink to my main Daz files even after a clean system restart or a manual shut down, now i have to rebuild the whole environment, will take days of my effort, and this cycle will continue whenever Daz postrgreSQL decide to error (very positive it's not a problem on my end) this time i really find myself at the end of my patient. As a long time blender, UE4/5, CC3/4 user, never have I encountered this much app generated issue require exceeding trouble shooting effort form its user.
Why this background hijacking postgreSQl + CMS is garbage beyond repair?
1. it can't stop messing with users' local environment, doesn't matter if you "work offline", it always find a way to "update the metadata" and screw the users when things go wrong on their end, when users choose "work offline' we really meant it!
2. it makes custom content folder relocation far more complicated than it needs to be
3. it always running in the background while other software treat it like a virus(and your system have to shut down twice for this reason)
4. It's broken ALL THE TIME, and then ask users to relink or lose everything.
Daz still has a lot things going for it, it's fast character and content rendering is still very temping, but if they can't help to screw their users local environment a self generated database running on users background, I don't know if this app still worth it!
Mod edited title and post:
Comments
1. It really can't
3. It doesn't run unless DS, DIM, DazCentral or Carrara are running.
1. it really can, thro multply ways...say when DAZ postgreSQL gets shutdowned or restarted, for example, when you have to shutdown your computer, there's a higher chance all your data will be corrupted
3. Do yourself a favor and see how many "why daz doesn't close" threads you can find in tech issue section, or simply open up windows task mannger to see if postgreSQL isn't running in the background, and no, feel free to close all DS related apps, daz postgreSQL will always running in the background
1. That has nothing to do with going online and/or updating metadata.
3. I always check Task Manager if I intend to back up the database or I need to make sure DS has completely closed. I have never found PostgreSQL running in the background when DIM and DS have closed.
CMS and the Post grey squirrel are dead as a doornail on my Win10 since I had my C drive replaced
... and I was so happy smart content actually worked on it in Carrara too before that happened
now I don't even have smart content in DAZ studio
I can cope, just use VoidTools Everything to search instead
starting CMS in DIM or D|S does zilch
and yes my antivirus did the damage, it had the cheek to tell me, but after trying every suggestion in the firewall and permissions I never managed to fix it
There are other programs that use PostgresSql server - I currently have 7 instances of it running on this Win 8.1 machine I'm writing this from, but I haven't used any of the installed DAZ programs on it for months, as I'm using another PC for rendering now.
The render PC (Win 10) is also running but no PostgresSql servers were running on that one until now where I tried to start DS, and they are attached as subnodes to DS in Task Manager.
If you are not online (or, now, if you leave the log-in options at the default do not update metadata) then the CMS will not get updated except when you edit it or install/uninstall files
Moving an entire content directory, as long as DS is correctly pointed to the new location, should be frictionless as far as the CMS goes (DIM, if you use that to install, does need updating - via editing the manifests or just reinstalling using the new paths). Of coruse moving files within the content directory in a way that the CMS can't see will break referencs (but will not corrupt the database) - Daz provides multiple ways to avoid this (you can move within the Content Library pan, you can use links leaving the original files in situ, or you can just use categories).
As already covered, it does not run in the background as long as you allow DS to close down properly. There are ample warning of the perils of force-quitting.
Not true for most users.