I moved my content to a NAS and I broke the world.
I'm on a Mac running Big Sur, and have repeatedly used DAZ3DIM to update to latest, Mac-fixed v4.15.1.76. I continually get the PostgreSQL CMS connection error. I'm sure this has to do with me compounding the install of the new Mac version with moving my content to an external NAS at the same time. (I have way too much cool DAZ stuff to live on my system drive.)
I have tried looking at help here and elsewhere, but one thing that's odd is the mention of using pgAdmin3 to fix this, yet my installed version is slashed out, I guess being a 32-bit version. DIM never is able to install a correct 64-bit replacement.
BTW, this content set-up works fine on a PC I have (but rarely use - different discussion) but I have obviously done something wrong with this latest Mac upgrade.
I see many people have run into this in the past, but always on Windows machines... Any suggestions or help would be appreciated.
Comments
So you have the 32 bit version of PostgreSQL installed? I'm not sure it will help, as I think the databse is different depending on bit architecture, but have you tried uninstalling PostgreSQL 32 bit first? You certainly can't have more than one version isntalled, and trying to install the 64 bit version should automatcially remove the 32 bit (as long as the manifests are still found, at least).
I assumed the 64bit version in DIM would upgrade that automatically, but I guess not. I don't see a legit uninstaller, but I have renamed the folder _old and tried a new install through DIM. Gave me the same 32 bit version, which has a circle and slash symbol on it because it the wrong version.
Each version of PostgreSQL has its own installer, make sure you haven't hidden the betas and 64 bit version (check Show Hidden in the ready to Download tab).
Yep, done that. Even if I delete or remane the old version, DIM installs the 64bit beta, then shows the 64bit public, then wants to install the beta again... It seems to be in an install loop because the 32bit version keeps being installed instead, even though it doesn't appear as an option in the DIM Download/Install process. Something is broken here since the Mac upgrade.
Have you checked it wasn't a stand-alone installation, presumably with its own uninstaller? Though I'm not sure there ever has been a Mac stand-alone installer.
I used an "ln -s" from the normal location to the external drive so that DIM couldn't tell I had done anything. Avoids a lot of pain since I don' t need to deal.
In the /users/Shared directory I have:
DAZ 3D@ -> /Volumes/Daz/DAZ 3D
My DAZ 3D Library@ -> /Volumes/Daz/My DAZ 3D Library
Not sure what this indicates..."ln -s"
Trying to upload pictures.
Using DIM, first I get this... I install, which doesn't work.
Then, I get this... I install,which doesn't work.
And Finally, I get back to where I started, which, just to check, doesn't work.
I really don't know where I'm making an eror. Could it be the paths I have chosen? The Apps on my system drive, and content on the external?
Ok. Uninstalled DAZ everything except my content directory. Re-installed DAZ 4.16.03 on my Mac running Monterey (I figured Big Sur wrecked my set-up, so why not update again?)
Also installed Daz Central, which freezes before I can even enter my password.
Installed new Install Manager and pointed the content path to my external NAS' My Library file. That stil shows I have 1,500 + things to install...
Then the DAZ program still has this PostgreSQL communication issue, so it;s unusable.
I'd like to start by getting the DAZ3D app working first, so solving this Postgre thing would be first.
I have deleted library files and aplication support files prior to re-install, but I have hit a roadblock.
Any other thoughts on how I can get back to making this work? Thanks - KK
I suggest creating a new CMS directory. You can leave everything as it is and simply change the CMS directory path from DAZ Studio. Do not log in to DAZ Central - do everything offline or DAZ Central will start working in the background and that is likely to create confusion.
Do not put the CMS on a NAS. It might work, but databases uses special features of the file system and these are often not implemented by NAS servers, or by network file systems in general. This link explains it for people who are familiar with NFS/Samba/etc, here's the executive summary:
Most NASs are more Windows compatible than UNIX compatible (even though most of them run a UNIX variant...)
You should be able to start DAZ (offline, do not log in) and change the CMS directory to a new directory on your root or home folder (i.e. not the network). Make sure you can see the "Content Library" tab (preferably select it.) Then try this; if you have a PostgreSQL installation issue you won't get to the end:
You might see something in "Smart Content" if you get this far. In any case you can repeat from step (9) and include more products - just don't include all of them because it will take far too long.
If you do get this far you have a working PostgreSQL and there is something wrong with the original directory, from step (3). These directories can be copied around - you just have to update the "Cluster Directory" setting to the new location. If your content is on a NAS you really want to copy a working CMS directory rather than recreate it from scratch, but if it has been damaged or was for a diffferent version of Postgre that may not work. If you have to re-import all the metadata from content on a NAS you need to accept that it will take a day or two; you can guesstimate the time by trying a small number of products at a time. Incidentally it isn't actually necessary to manually start/stop the CMS - Daz does that automatically if the cluster directory is changed, but I find it makes me feel safer ;-)
Thanks for all the info... (Sorry for the delay - Work has been crazy) Well I have way too much to keep on system drives, and I like having the content "safe", soi I guess I can buy another RAID system, or use DAZ only on my PC, which does seem to be happy with the NAS even though I only keep the PC around for situations like this and I prefer not to really even touch that keyboard... Ha!
Thanks again, and I will try to give these steps a shot once the holidays are past. - KK