Time
S
Nick
Message
06:28 Virgile joined #dataverse
07:12 Fernando joined #dataverse
07:54 Virgile joined #dataverse
10:19 Virgile joined #dataverse
10:23 Benjamin_Peuch joined #dataverse
12:43 donsizemore joined #dataverse
13:20 swebshet joined #dataverse
13:20 swebshet
Hi All am not able to manage or publish the root dataverse. Here are the steps to create the dataverse via API . Can you please correct me over the code below. swebshethttp://swebshet:8080/ swebshet
13:23 swebshet
can you provide me the real address of url for api over localhost http://swebshet:8080/
13:24 donsizemore
@swebshet when you try to publish the root dataverse, more helpful information should be written to server.log
13:24 donsizemore
@swebshet if you're on 5.0, that log might be /usr/local/payara5/glassfish/domains/domain1/logs/server.log
13:30 pameyer joined #dataverse
13:33 pameyer
swebshet: that curl command should create a new dataverse under root (although in the logs, the "--upload-file $jsonfile" bit looks to have been truncated
13:35 pameyer
to publish an existing dataverse, you want to use actions - eg "curl -H X-Dataverse-key:$API_TOKEN -X POST $SERVER_URL/api/dataverses/$ID/actions/:publish"
13:53 swebshet joined #dataverse
13:54 swebshet
Thanks guys I will try
13:54 pdurbin joined #dataverse
14:40 dataverse-user joined #dataverse
14:42 dataverse-user
Hi guys its me again, the one with this github issue: https://github.com/IQSS/dataverse/issues/7270
14:43 pdurbin
It looks like restarting didn't help.
14:46 dataverse-user
Yes, I even deleted the dirs that qqmyers mentioned
14:46 pdurbin
Right, "generated" and the other one.
14:47 pdurbin
What changed?
14:47 pdurbin
What changes occurred before this problem?
14:49 dataverse-user
nothing, our dataverse was working fine last week
14:49 pdurbin
very strange
14:52 pdurbin
donsizemore or poikilotherm: any ideas?
14:52 donsizemore
i'd want to see server.log
14:52 pdurbin
donsizemore: there's some in the issue ^^
14:53 pdurbin
but I can't make head nor tail of it
14:53 pameyer
looked like a prov problem to me - but prov was turned off, so not sure how that could happen
14:54 pdurbin
yeah, that was a good thought
14:54 donsizemore
does server.log say the same thing after deleting both generated/ and osgi-cache/?
14:54 dataverse-user
let me check
14:54 pdurbin
dataverse-user: something else to check... can you download the dataset metadata via API ?
14:54 dataverse-user
or should I add the new server.log to the github issue?
14:55 dataverse-user
@pdurbin how can I try that?
14:55 pdurbin
dataverse-user: as long are there aren't any passwords in there, it's probably safe to put the server.log in the github issue.
14:56 poikilotherm
No ideas without a complete server.log since bootup of glassfish/payara and a detailed description of the environment. Sry, but I haven't seen this error happening before.
14:57 pameyer
pdurbin: are datacite credentials still in server.log, or did that get sorted?
14:57 pdurbin
pameyer: I don't know
14:57 pdurbin
dataverse-user: this dataset looks ok via API : https://research-data.urosario.edu.co/api/datasets/export?exporter=dataverse_json&persistentId=doi:10.34848/FK2/RD5NIK
14:58 pdurbin
dataverse-user: are you running a fork?
14:59 dataverse-user
There are some things that I can't show from the server log... I'll try to add the new warnings that were thrown on the first visit to a dataset after the reboot
15:00 dataverse-user
@pdurbin, we're running a dataverse with some developments made by a programmer
15:02 poikilotherm
@dataverse-user did you try to rebuild your WAR from a clean state and see if it differs from your current deployment?
15:02 poikilotherm
Sometimes I had strange issues when my build cache was misbehaving
15:03 poikilotherm
Simply create an md5sum or sha256sum over both WARs and see if they match.
15:26 dataverse-user
@poikilotherm I don't thing they will match due to the developments that we have ... but we'll try that
15:27 dataverse-user
We're also gonna try what landreev said on the github post (with our tech team)
15:27 pdurbin
Yes, doing what he said is a very good idea.
15:27 dataverse-user
Thank you guys, we'll let you know if it works
15:28 pdurbin
Great. I also looked at server-log-after-reboot.txt but I didn't see anything obvious. It just feels like a weird Glassfish error at this point, to me anyway.
15:30 poikilotherm
Actually there is loads of stuff missing from that logfile. The complete startup is not there, so we can't see what happens during deployment.
15:31 poikilotherm
Maybe it has been rotated already
15:31 poikilotherm
There are loads of EJB queries going wild...
16:41 pdurbin
yeah, weird to see those EJB queries in there but I assume it's unrelated
17:56 pameyer
for no rational reason, I'm wondering if https://github.com/IQSS/dataverse/issues/7270 could be trying to load something json-schema related over https and having cert issues
17:58 pameyer
but "broken pipe" for the error page is also odd
17:59 pdurbin
it's a head-scratcher
18:01 pameyer
well, certificates and CA trust stores have joined selinux on my list of things causing weird unexplained behavior
18:06 pdurbin
also a full disk :)
18:07 pameyer
yeah :) ....
