Time
S
Nick
Message
02:50
djbrooke joined #dataverse
04:13
bjonnh
where are we with ansible playbooks? anybody know? (pdurbin?)
05:25
soU joined #dataverse
08:52
djbrooke joined #dataverse
11:32
donsizemore joined #dataverse
11:33
donsizemore
@bjonnh there are several floating around. @pdurbin may or may not still be on Snow Time. what's your end-goal re: playbooks?
11:55
pdurbin joined #dataverse
12:17
donsizemore joined #dataverse
13:19
andrewSC joined #dataverse
13:28
djbrooke joined #dataverse
13:33
djbrooke_ joined #dataverse
13:37
djbrooke_
bjonnh: There was some discussion of the two flavors of Dataverse ansible the other day - http://irclog.iq.harvard.edu/dataverse/2017-02-09#i_48489 - not sure if it's helpful
13:38
djbrooke_
(I do see that donsizemore is here as well though - hello Don!)
13:44
pdurbin
bjonnh: you should use https://github.com/IQSS/dataverse-ansible and give feedback to donsizemore
14:03
pameyer joined #dataverse
14:24
soU
Hello pdurbin ,you ware suggesting from the log its because the war file is not deployed. but i can see the application with the glassfish admin and also through asadmin list-application
14:24
pameyer joined #dataverse
14:27
pdurbin
soU: right, it sounds like it's deployed. That's great. Probably the root dataverse wasn't created though. What do you see when you go to http://localhost:8080 ?
14:29
soU
the default glassfish index is not replaced. and also i checked dataverese table from the db and its empty so i think defiantly the root datavese was not created
14:32
pdurbin
Oh! If you see the default glassfish index page, that usually means that the dataverse war file was *not* deployed. What do you see when you run `asadmin list-applications`?
14:32
soU
dataverse-4.6 <ejb, web>
14:33
pdurbin
huh, but the default glassfish page at http://localhost:8080 ... that doesn't make any sense
14:34
pdurbin
I wonder if it got deployed at a context-root other than "/" ... What do you see at http://localhost:8080/dataverse ?
14:34
soU
and tried localhost:8080/dataverse-4.6/ and it come up with 500-internal server error and when ever i try that i see some new entry in server.log
14:35
pdurbin
are you seeing "NoResultException: getSingleResult() did not retrieve any entities" as the 500 error?
14:37
soU
on the server log, yes
14:44
pdurbin
It sounds like the dataverse app is being deployed to http://localhost:8080/dataverse-4.6 rather than http://localhost:8080 ... When this happens, none of the API endpoints work at the expected locations. The dataverseAdmin user isn't created and that user can't create the root dataverse.
14:45
pdurbin
soU: can you please open src/main/webapp/WEB-INF/glassfish-web.xml and tell me what you see on the line with "context-root"?
14:47
jeffspies______ joined #dataverse
14:57
soU
pdurbin i checked the file and there is no line with "context-root"
15:00
soU
https://ctrlv.it/id/15701/2244344779
15:04
soU
I think i should add that, i don't know why it is not there
15:05
bjonnh
pdurbin: well I started to work on mine
15:05
bjonnh
for the docker integration
15:06
bjonnh
based on the IQSS one
15:06
bjonnh
but an old one
15:06
bjonnh
it seems way better than what I started to do :)
15:07
soU
i forked https://github.com/IQSS/dataverse/blob/develop/src/main/webapp/WEB-INF/glassfish-web.xml i don't know how that only that line missed. any way let me add it and try again
15:17
pdurbin
soU: probably what you should do is `git checkout src/main/webapp/WEB-INF/glassfish-web.xml` so that the file goes back to how it is in git
15:18
pdurbin
if you do `git diff src/main/webapp/WEB-INF/glassfish-web.xml` I assume it's going to show a difference
15:19
pdurbin
bjonnh: ok, I'm not an Ansible user but I assume you know who to talk to. donsizemore, pameyer and iamtimmo
15:19
pameyer joined #dataverse
15:19
bjonnh
yep
15:19
bjonnh
I would love to have just one thing for deployment be it in vagrant, docker or whatever else
15:20
djbrooke joined #dataverse
15:20
pdurbin
well, vagrant isn't for production
15:25
pameyer
bjonnh: it seems like there can be variation in deployment for production, testing or development
15:26
donsizemore joined #dataverse
15:26
pameyer
I've had reasonable luck with ansible, although I've been rolling my own (due to some test/dev specifics not being generalized)
15:27
pameyer
one of the things I've run into with automated deployment is the fact that the installer assumes it's running interactively
15:28
pameyer
soU: this might be something I've missed from the IRC logs, but is dataverse the only application you've got in glassfish?
15:29
soU
yes
15:32
pdurbin
soU: again, your local glassfish-web.xml should look like the version on GitHub with a line that has this: <context-root>/</context-root>
15:32
soU
ok i checkout glassfish-web.xml and now it runs at a context-root but still no root-dataverse
15:33
pameyer
if `curl http://localhost:8080 ` (locally on the glassfish) box shows a redirect, then it probably just needs the root-dataverse to be published
15:33
pdurbin
soU: sounds like progress! :) Now you need to run the scripts that create the dataverseAdmin user who creates the root dataverse
15:33
pameyer
if it gives 500; then there's something else
15:35
soU
pameyer it shows 500, let me check the server.log
15:40
bjonnh
pameyer: ansible can handle production/testing/development too
15:42
bjonnh
I mean for production people will have to tweak their stuff anyway
15:42
pameyer
bjonnh: I've found dev to be slightly tricker, but that may be due to using things in ways they're not designed for
15:42
bjonnh
yeah it has ways to do it properly
15:44
pameyer
I haven't dug into the glassfish / debugger intergrations with ansible yet
15:45
pdurbin
bjonnh: have you set up a dev environment yet? soU is having a little trouble getting set up, which is somewhat common, unfortunately.
15:52
djbrooke joined #dataverse
15:54
soU
pdurbin it works now
15:56
soU
the problem after i correct the context issue it was the change i made in setup-all.sh to much the api address the app path but now i restore it and works.
15:57
pdurbin
soU: nice! Good job.
15:57
soU
thanks! pdurbin ,pameyer
15:57
pameyer
soU: glad to hear it's working
15:58
djbrooke joined #dataverse
16:15
djbrooke joined #dataverse
16:15
pameyer joined #dataverse
16:17
pameyer joined #dataverse
16:23
bjonnh
I had it running on docker
16:23
bjonnh
didn't try recently
16:48
pdurbin
ok, thanks
17:01
djbrooke joined #dataverse
17:02
pameyer joined #dataverse
17:24
djbrooke joined #dataverse
17:29
djbrooke joined #dataverse
17:43
djbrooke joined #dataverse
17:59
pameyer joined #dataverse
18:03
djbrooke joined #dataverse
18:05
djbrooke joined #dataverse
18:05
djbrooke joined #dataverse
18:25
djbrooke joined #dataverse
18:36
pameyer joined #dataverse
18:43
donsizemore joined #dataverse
18:50
pameyer joined #dataverse
19:02
pameyer joined #dataverse
19:14
djbrooke joined #dataverse
19:44
djbrooke joined #dataverse
19:53
djbrooke joined #dataverse
19:55
djbrooke joined #dataverse
19:56
djbrooke_ joined #dataverse
20:03
pameyer joined #dataverse
20:09
donsizemore joined #dataverse
20:15
djbrooke joined #dataverse
20:20
djbrooke joined #dataverse
20:23
axfelix joined #dataverse
20:36
axfelix joined #dataverse
21:02
pameyer joined #dataverse
21:27
pameyer joined #dataverse
22:00
pameyer joined #dataverse
22:53
iqlogbot joined #dataverse
22:53
Topic for #dataverse is now Dataverse is open source research data repository software: http://dataverse.org | IRC Logs: http://irclog.iq.harvard.edu/dataverse/today | Who's who: https://docs.google.com/spreadsheets/d/16h3jv24usMGq18495C-JA-yNcQCKiKDa65MTraNDd7k/edit?usp=sharing
22:54
JonathanNeal joined #dataverse