Does anyone know how to fix this?

WonderlandWonderland Posts: 6,793

I can't download anything through DIM or access the store. This was in the log:

2020-12-07 00:01:30.318 Json Parser (1,1): Syntax error - expected '{' or '['
2020-12-07 00:01:30.318 Unable to parse purchased products

I've tried a zillion times to log in and uninstalled and reinstalled DIM several times and restarted my computer...

I also get this message:

Well, I submitted a ticket. But do any geniuses know what this means???

LOG:  database system was shut down at 2020-12-06 18:10:01 PST
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
FATAL:  role "Alici" does not exist
LOG:  received fast shutdown request
LOG:  aborting any active transactions
FATAL:  terminating connection due to administrator command
LOG:  autovacuum launcher shutting down
LOG:  shutting down
LOG:  database system is shut down
LOG:  database system was shut down at 2020-12-06 18:10:11 PST
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
FATAL:  role "Alici" does not exist
LOG:  received fast shutdown request
LOG:  aborting any active transactions
FATAL:  terminating connection due to administrator command
LOG:  autovacuum launcher shutting down
LOG:  shutting down
LOG:  database system is shut down
LOG:  database system was shut down at 2020-12-06 18:14:38 PST
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
FATAL:  role "Alici" does not exist
LOG:  received fast shutdown request
LOG:  aborting any active transactions
FATAL:  terminating connection due to administrator command
LOG:  autovacuum launcher shutting down
LOG:  shutting down
LOG:  database system is shut down
LOG:  database system was shut down at 2020-12-06 18:15:05 PST
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
FATAL:  role "Alici" does not exist
LOG:  received smart shutdown request
LOG:  autovacuum launcher shutting down
LOG:  shutting down
LOG:  database system is shut down
LOG:  database system was shut down at 2020-12-06 18:19:58 PST
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
FATAL:  role "Alici" does not exist
LOG:  received smart shutdown request
LOG:  autovacuum launcher shutting down
LOG:  shutting down
LOG:  database system is shut down
LOG:  database system was shut down at 2020-12-06 18:33:40 PST
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
FATAL:  role "Alici" does not exist
ERROR:  relation "customer" does not exist at character 15
STATEMENT:  SELECT * FROM "customer"
LOG:  checkpoints are occurring too frequently (21 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (23 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (17 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (21 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (17 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (15 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (18 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (17 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (17 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (17 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (15 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (15 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (16 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (20 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (16 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (16 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (17 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (17 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (14 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (19 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (16 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (15 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (15 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (18 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (13 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (17 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (15 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (16 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (23 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (17 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (16 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (13 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
ERROR:  duplicate key value violates unique constraint "tblSceneID_fldAssetUri_key"
DETAIL:  Key ("fldAssetUri")=(/data/Design%20Anvil/DA%20Rust%20and%20Grime/DA%20Geo%20Shell%20Mid/Geometry%20Shell%201.dsf#Geometry%20Shell%201) already exists.
STATEMENT:  INSERT INTO "tblSceneID" ("fldAssetUri","fldCompatibilityBase","fldIsVendor") VALUES ('/data/Design%20Anvil/DA%20Rust%20and%20Grime/DA%20Geo%20Shell%20Mid/Geometry%20Shell%201.dsf#Geometry%20Shell%201', 44012, 't') RETURNING "RecID"
LOG:  checkpoints are occurring too frequently (17 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (18 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (18 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
ERROR:  duplicate key value violates unique constraint "tblSceneID_fldAssetUri_key"
DETAIL:  Key ("fldAssetUri")=(/data/Ravnheart/Marcoor%20Lifts/u_wall_panel/u_wall_panel_84.dsf#u_wall_panel_84) already exists.
STATEMENT:  INSERT INTO "tblSceneID" ("fldAssetUri","fldCompatibilityBase","fldIsVendor") VALUES ('/data/Ravnheart/Marcoor%20Lifts/u_wall_panel/u_wall_panel_84.dsf#u_wall_panel_84', 48226, 't') RETURNING "RecID"
LOG:  checkpoints are occurring too frequently (20 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (22 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (18 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (23 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (21 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (22 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (22 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (25 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (22 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (15 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (22 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (27 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (23 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (24 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (24 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (21 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (16 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (16 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (19 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (10 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (15 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (22 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (15 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (20 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (20 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
ERROR:  duplicate key value violates unique constraint "tblSceneID_fldAssetUri_key"
DETAIL:  Key ("fldAssetUri")=(#V4SpDwDress_23874) already exists.
STATEMENT:  INSERT INTO "tblSceneID" ("fldAssetUri","fldCompatibilityBase","fldIsVendor") VALUES ('#V4SpDwDress_23874', 90827, 't') RETURNING "RecID"
LOG:  checkpoints are occurring too frequently (17 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (21 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (9 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (20 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
ERROR:  duplicate key value violates unique constraint "tblSceneID_fldAssetUri_key"
DETAIL:  Key ("fldAssetUri")=(/data/Jack%20Tomalin/DHMBD/DH_MBD/dh_mbd_24238.dsf#dh_mbd_24238) already exists.
STATEMENT:  INSERT INTO "tblSceneID" ("fldAssetUri","fldCompatibilityBase","fldIsVendor") VALUES ('/data/Jack%20Tomalin/DHMBD/DH_MBD/dh_mbd_24238.dsf#dh_mbd_24238', 93419, 't') RETURNING "RecID"
LOG:  checkpoints are occurring too frequently (18 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (18 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (22 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  checkpoints are occurring too frequently (19 seconds apart)
HINT:  Consider increasing the configuration parameter "checkpoint_segments".
LOG:  received fast shutdown request
LOG:  aborting any active transactions
FATAL:  terminating connection due to administrator command
FATAL:  terminating connection due to administrator command
FATAL:  terminating connection due to administrator command
FATAL:  terminating autovacuum process due to administrator command
LOG:  autovacuum launcher shutting down
LOG:  shutting down
LOG:  database system is shut down
LOG:  could not bind IPv6 socket: No error
HINT:  Is another postmaster already running on port 17237? If not, wait a few seconds and retry.
LOG:  could not bind IPv4 socket: No error
HINT:  Is another postmaster already running on port 17237? If not, wait a few seconds and retry.
WARNING:  could not create listen socket for "localhost"
FATAL:  could not create any TCP/IP sockets

 

Screenshot 2020-12-06 214048.png
796 x 219 - 36K
Post edited by Wonderland on

Comments

  • Worlds_EdgeWorlds_Edge Posts: 2,148

    It's happening to me too.  I haven't been able to download anything - this is the second day.  I see nothing in the list of available downloads even though I'm buying new products.

  • In the recent days I have noticed a few purchases which I download manually, that do not appear to have DIM [or any other] types of downloads available.

  • Nester751Nester751 Posts: 387
    edited December 2020

    I have been getting this for the past 4 days. It seems like the installer is losing user credentials during the download. What helps a little is to only try to Que one item at a time while downloading. Putting more in the Que always seems to make it fail. Also this seems to mostly happen with larger sized files of over 250 mb. Looking at your log it's like Daz's server is not responding and then reading the reconnect attempt as too many connections.

    Post edited by Nester751 on
  • Not sure how it could lose credentials but the DB process is pretty badly messed up. I'd guess that syntax error is at the heart of the problem. Someone at Daz needs to get the whole product DL thing fixed. Somehow they broke the links that opened DIM/DazCentral and now they have straight removed the DIM link entirely again. Since this is at the heart of how they make money I'd hope they take this seriously and fix it quickly.

  • dawnbladedawnblade Posts: 1,723

    I read this by Daz _rawb. Happens if you're logged in multiple places. The json error is also a known issue so it's good that you submitted a ticket so they can help clear it up, as I  think it is account specific.

Sign In or Register to comment.