Hi Dhrubajit, Sorry for the late reply.
1. I was hoping for the actual log output of yum, tomcat logs, etc., but your attachment actually just shows a directory listing of your /var/log directory 2. Your DSpace logs do show some potentially useful information... it seems there is a duplicate key in your bitstream format registry for Adobe PDF... this is probably causing problems whenever a bitstream of this type is submitted, and possibly viewed? 2018-03-15 13:07:08,497 WARN org.hibernate.engine.jdbc.spi. SqlExceptionHelper @ SQL Error: 0, SQLState: 23505 2018-03-15 13:07:08,497 ERROR org.hibernate.engine.jdbc.spi. SqlExceptionHelper @ Batch entry 0 update public.bitstreamformatregistry set description='Adobe Portable Document ', internal='1', mimetype= 'application/pdf', short_description='Adobe PDF', support_level=1 where bitstream_format_id=77 was aborted: ERROR: duplicate key value violates unique constraint "bitstreamformatregistry_short_description_key" Detail: Key (short_description)=(Adobe PDF) already exists. Call getNextException to see other errors in the batch. 2018-03-15 13:07:08,497 WARN org.hibernate.engine.jdbc.spi. SqlExceptionHelper @ SQL Error: 0, SQLState: 23505 2018-03-15 13:07:08,497 ERROR org.hibernate.engine.jdbc.spi. SqlExceptionHelper @ ERROR: duplicate key value violates unique constraint "bitstreamformatregistry_short_description_key" Detail: Key (short_description)=(Adobe PDF) already exists. I'm not sure how this duplicate key could happen during an upgrade, this constraint is related to the "short_description" field (in this case, "Adobe PDF") Could you run this SQL query manually in your dspace database (if you're not sure how, you can probably log in with the postgres client using a command like *psql -U dspace dspace -h localhost -W *and entering the dspace db user password when prompted) and share the output? SELECT * FROM bitstreamformatregistry WHERE short_description='Adobe PDF'; I'm guessing you'll see two rows... and we'll want to remove one of them. Cheers Kim On Friday, April 6, 2018 at 2:42:57 AM UTC+12, Dhrubajit Das wrote: > > Hi Kim Shephard, > I am waiting for your suggestions and guidance. CentOS update file and > DSpace log files have already submitted for your reference. Problem is > still persist in my system. File system in the item collection is not > showing for view and upload content to the library. Hope your suggestion > will help me resolve the problem. > > regards, > Dhrubajit > > > On Tuesday, 20 March 2018 23:57:46 UTC+5:30, Dhrubajit Das wrote: >> >> I am facing a problem. Recently I updated CentOS 7 OS, and immediately >> after updating the OS, I was unable to submit new collection in the >> community and also can not view the exiting digital resources as the files >> are not viewing in Dspace, Bitstreams are found in proper order, but >> already submitted digital files are not there for viewing or adding a new >> collection in the community. I am using Dspace 6.2 on CentOS 7 Linux. >> Before updating CentOS 7 , my Dspace was working perfectly. I need your >> help to solve the problem >> > -- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
