Loading...
> >

CMS not connecting

aaráribel caađoaaráribel caađo Posts: 690
in Technical Help (nuts n bolts)

I just started to get an error message about DS not being able to connect to the PostgreSQL CMS (screenshot attached). I'm using the Beta 4.12.1.40 on a Mac (10.15.2). I checked with the non-Beta DS and got the same error message. 

Can I repair the database? Is there something else I can do to fix this? I have a lot of custom content stuff, so I don't want to rebuild from scratch if I can avoid it. 

Screen Shot 2019-12-28 at 10.32.35 PM.png
836 x 316 - 43K

Comments

  • Richard HaseltineRichard Haseltine Posts: 102,437

    I would initially suspect a security update - to the OS, or to separate security software if yiu use any. You might try repairing permissions on the ContetCluster folder tree - check Daz Studio>Preferences>CMS Settings tab for its location.

  • aaráribel caađoaaráribel caađo Posts: 690

    Unless there's a MacOS security update I dind't notice, I don't think it's that (I don't run a separate security blocker, other tha a VPN), and repairing permissions + restarting didn't help. Any other suggestions to troubleshoot this?

  • TotteTotte Posts: 14,064

    I've head several people excperiencing this on Mac OS X recently. One Mac user did restore from TimeMachine backup of the database which fixed it.
    One thing I would like you to do is to see of there is any mention of AUTOVACUUM or VACUUM in the postgres logfile, I have a suspicion that there might be an issue with that. As I haven't experienced the issue myself as I do not run osx 10.5. 

    VACCUM is the postgres process that "tidy up the database", which basically is removing holes in indexes etc. If that fails, the database will suddenly be impossible to connect to, but Postgres might then as a self preservation step, run VACUUM, and while tha is going, the database is locked. The problem I sense is that if the error happens and you then close down DS and DS shuts down postgres before the VACCUM is complete, bad things might happen.

    My guess from experience though, not a definite fact on the issue.

  • aaráribel caađoaaráribel caađo Posts: 690
    edited December 2019

    Looking for the dblog helped diagnose this (aka, my attempt to repair the permissions didn't work). The fail message is:

    FATAL:  data directory "/Users/london/Library/Application Support/DAZ 3D/cms/ContentCluster" has group or world access
    DETAIL:  Permissions should be u=rwx (0700)

    I was going to change the permission in Terminal since I don't know how to set read-write-execute with the information panel, but I'm not sure how to do it in Terminal, either. The current permissions are:

    drwxr-xr-x  22 london  staff  704 Dec 28 11:39 ContentCluster

    -rw-r--r--@  1 london  staff  100 Nov 15 17:12 cmscfg.json

    Prior to this, the dblog does show a VACCUM event. Actually, this repeats frequently throughout the log, including times before the problem began.

    LOG:  autovacuum launcher started
    FATAL:  pg_hba.conf rejects connection for host "[local]", user "london", database "postgres", SSL off

    Post edited by aaráribel caađo on
  • TotteTotte Posts: 14,064
    edited December 2019

    700 is the permission you should have, first digit is user, second is group 3 is world, so 700 is rwx------ 
    I don't think I can write the command here as it is considered "dangerous" by the Cloudflare server so I try to put it into a file

    0 drwx------+ 23 totte  staff  736 28 Dec 22:08 ContentCluster
     

     

    pdf
    pdf
    fixit.pdf
    15K
    Post edited by Totte on
  • aaráribel caađoaaráribel caađo Posts: 690

    ¡Muchas gracias! That did it. 

  • TotteTotte Posts: 14,064

    You're Welcome.
    So, next question (not to you, but i general), why is osx 10.5 suddenly changing permissions of that directory? 

Sign In or Register to comment.