Hi Nate,
Thanks for the reply. In syslog I'm getting;
Jul 16 20:36:41 galaxy kernel: [ 117.123921] Out of memory: Kill process 1390
(python) score 986 or sacrifice child
Jul 16 20:36:41 galaxy kernel: [ 117.124087] Killed process 1390 (python)
total-vm:43496348kB, anon-rss:32611892kB, file-r
Hi Nate,
Problem solved (with one small exception) with much help from Marius. I
followed his instructions to apply the three patches via mercurial:
You can get the diff of a pull request by adding .diff, like so:
https://patch-diff.githubusercontent.com/raw/galaxyproject/galaxy/pull/345.diff
h
Jelle and I have been debugging over IRC, crossposting here for awareness
until I can get proper fixes pushed all the right places.
Jelle, like I, have "proper" enterprise deployments. I.e. SSL, galaxy under
a proxy-prefix, etc.
galaxy.ini:
1. galaxy_infrastructure_web_port = 8090
2. dyna
Hi Martin,
Is there anything in the syslog?
--nate
On Thu, Jul 16, 2015 at 11:26 AM, Martin Vickers wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi All,
>
> I have a weird issue that's just cropped up. After a new install of
> galaxy (checked out on Monday from github) on a ubu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
I have a weird issue that's just cropped up. After a new install of
galaxy (checked out on Monday from github) on a ubuntu vm, using
postgres rather than sqlite as well as a few other production
recommendations, I started playing around with t
Sometimes histories will not load and appear to error if the server is
being restarted when the load is attempted. Difficult to say if that's what
happened here. It's on the list to give better feedback in that case and
let the user know the server is down.
At any rate, glad it's working and let u
All of the volumes will be SSD from now on, large or small (technically,
gp2 type as defined here
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html) but
no, it's not currently possibly to specify the type via user data.
Regardless, to specify the *volume_type* the volume needs
Thanks, Carl! I will try and update the installation to a newer version!
I just got an email from the user that the history loaded again on its own.
I took a look at the javascript console as you suggested but found no error
messages. I'm not sure if the issue is fixed, but upgrading to a newer
ve
Hi Nate,
I have managed to update to the latest version of the default branch but I do
not see the ‘max_metadate_value_size’ in my universe_wsgi.ini (this file was
not changed during the update). Same thing if I use hg pull && hg update stable
or hg pull && hg update release_15.05.
Does this m
