I had an issue that looked like this suddenly start after a crash a couple of weeks ago. I don't know if this'll help anyone else, but what eventually got it working was, in Studio, selecting "Stop CMS" from the menu (even though no CMS-related process was running, this was the essential step), followed by "Start CMS".
I had an issue that looked like this suddenly start after a crash a couple of weeks ago. I don't know if this'll help anyone else, but what eventually got it working was, in Studio, selecting "Stop CMS" from the menu (even though no CMS-related process was running, this was the essential step), followed by "Start CMS".
Thanks a lot !
it was just what I needed to do after a crash of the mac. I guess the DAZ Studio is still finding previously created temporary files by postgresql (like a "run.pid" file, indicating the service is running, or a socket file to connect to it) and have no solutions when the postgresql service is dead but temporary files were not cleaned properly.
I'm now on the latest version of Daz Studio 4.12 and uninstalling and reinstalling the PostgreSQL to changing the ports in preferences of Daz Studio as suggested with a restart has not helped to resolve this issue. And neither for many other users experiencing the same problem. And interesting to note that this has been an issue with all versions of Daz Studio for both Windows and Mac users and for any number of reasons there is no one simple fix. I'm done with this program and not happy to have spent money on some great content.
This was killing me at first, I did EVERYTHING, however what worked for me was making sure in the preferences the Cluster Directory was part of the path.
Originally it was:
/Users/Home/Library/Application Support/DAZ 3D/cms
Once I made it this it finally worked:
/Users/Home/Library/Application Support/DAZ 3D/cms/ContentCluster
Thanks a lot !
I have solved my problem by your way ( DAZ stdio 4.12 for MAC ).
I'm now on the latest version of Daz Studio 4.12 and uninstalling and reinstalling the PostgreSQL to changing the ports in preferences of Daz Studio as suggested with a restart has not helped to resolve this issue. And neither for many other users experiencing the same problem. And interesting to note that this has been an issue with all versions of Daz Studio for both Windows and Mac users and for any number of reasons there is no one simple fix. I'm done with this program and not happy to have spent money on some great content.
Chris
This was killing me at first, I did EVERYTHING, however what worked for me was making sure in the preferences the Cluster Directory was part of the path.
Originally it was:
/Users/Home/Library/Application Support/DAZ 3D/cms
Once I made it this it finally worked:
/Users/Home/Library/Application Support/DAZ 3D/cms/ContentCluster
I have solved problem by this way, you can try it.
You will now see the privilegies of the files here rwx rwx rwx (which are Owner, Group, World, a Read, Write & eXecute)
You also see owner and group of the owers.
Thank you so much, Totte! When I followed this suggestion, it revealed that the permissions for the CMS folder were set to root or system, not to my account. My account had the permissions for all the other folders. I made the change through Finder > Get Info, and Daz immediately started working again. Woo! You are awesome!
Seems the postgresql that comes with Daz isn't supported on OSX Catalina?
“pgAdmin3.app” needs to be updated.
The developer of this app needs to update it to work with this version of macOS. Contact the developer for more information.
Any ideas?
pgAdmin is just a user tool that "has to be shipped with postgres, opn source licenses" but it has nothing to do with the actual database backend functionllity. So, nothing to worry about at all as you re not supposed to fiddle in the CMS db anyway.
I had an issue that looked like this suddenly start after a crash a couple of weeks ago. I don't know if this'll help anyone else, but what eventually got it working was, in Studio, selecting "Stop CMS" from the menu (even though no CMS-related process was running, this was the essential step), followed by "Start CMS".
so where is that "start CMS" in the menu. what menu. looked everywhere in studio.
I had an issue that looked like this suddenly start after a crash a couple of weeks ago. I don't know if this'll help anyone else, but what eventually got it working was, in Studio, selecting "Stop CMS" from the menu (even though no CMS-related process was running, this was the essential step), followed by "Start CMS".
so where is that "start CMS" in the menu. what menu. looked everywhere in studio.
Options menu on the Content Library or Smart Content tabs.
Comments
I'll check that tonight. Hope this tweak will work... Thanks guys :)
I had an issue that looked like this suddenly start after a crash a couple of weeks ago. I don't know if this'll help anyone else, but what eventually got it working was, in Studio, selecting "Stop CMS" from the menu (even though no CMS-related process was running, this was the essential step), followed by "Start CMS".
Thanks a lot !
it was just what I needed to do after a crash of the mac. I guess the DAZ Studio is still finding previously created temporary files by postgresql (like a "run.pid" file, indicating the service is running, or a socket file to connect to it) and have no solutions when the postgresql service is dead but temporary files were not cleaned properly.
I'm now on the latest version of Daz Studio 4.12 and uninstalling and reinstalling the PostgreSQL to changing the ports in preferences of Daz Studio as suggested with a restart has not helped to resolve this issue. And neither for many other users experiencing the same problem. And interesting to note that this has been an issue with all versions of Daz Studio for both Windows and Mac users and for any number of reasons there is no one simple fix. I'm done with this program and not happy to have spent money on some great content.
Chris
Thanks a lot !
I have solved my problem by your way ( DAZ stdio 4.12 for MAC ).
This was killing me at first, I did EVERYTHING, however what worked for me was making sure in the preferences the Cluster Directory was part of the path.
Originally it was:
/Users/Home/Library/Application Support/DAZ 3D/cms
Once I made it this it finally worked:
/Users/Home/Library/Application Support/DAZ 3D/cms/ContentCluster
I have solved problem by this way, you can try it.
Thank you so much, Totte! When I followed this suggestion, it revealed that the permissions for the CMS folder were set to root or system, not to my account. My account had the permissions for all the other folders. I made the change through Finder > Get Info, and Daz immediately started working again. Woo! You are awesome!
Seems the postgresql that comes with Daz isn't supported on OSX Catalina?
“pgAdmin3.app” needs to be updated.
The developer of this app needs to update it to work with this version of macOS. Contact the developer for more information.
Any ideas?
pgAdmin is just a user tool that "has to be shipped with postgres, opn source licenses" but it has nothing to do with the actual database backend functionllity. So, nothing to worry about at all as you re not supposed to fiddle in the CMS db anyway.
so where is that "start CMS" in the menu. what menu. looked everywhere in studio.
Options menu on the Content Library or Smart Content tabs.