Re: [galaxy-dev] Cloudman - is it possible to still use depreciated AMIs ?
The cluster status log has the following: * 14:49:00 - Setting up SGE... * 14:49:09 - Postgres service prerequisites OK; starting the service * 14:49:10 - PostgreSQL daemon NOT running. * 14:49:10 - PostgreSQL daemon NOT running. * 14:50:11 - --- PROBLEM, running command '/bin/su - postgres -c /usr/lib/postgresql/8.4/bin/pg_ctl -w -D /mnt/galaxy/db -l /tmp/pgSQL.log -o\-p 5910\ start' returned code '1' and following stderr: '' * 14:50:18 - PostgreSQL daemon NOT running. * 14:50:18 - Hadoop service prerequisites OK; starting the service * 14:50:31 - PostgreSQL daemon NOT running. * 14:50:45 - PostgreSQL daemon NOT running. * 14:50:58 - Done adding Hadoop service; service running. * 14:50:58 - PostgreSQL daemon NOT running. From: galaxy-dev-boun...@lists.bx.psu.edu [galaxy-dev-boun...@lists.bx.psu.edu] on behalf of Ravpreet Setia [ravpreet.se...@oicr.on.ca] Sent: Tuesday, July 23, 2013 7:00 PM To: Dannon Baker Cc: galaxy-dev@lists.bx.psu.edu Subject: Re: [galaxy-dev] Cloudman - is it possible to still use depreciated AMIs ? Hey, thanks for the response. The ssh issue was on my end and is now resolved. However, when I try the old AMI (ami-da58aab3), it mounts the new directory structure (meaning galaxyTools does not exist). Why does the old AMI have the directory structure of the new AMI? Along with that, PostgreSQL does not load properly, it is stuck at Starting up. I get the following error: FATAL: database files are incompatible with server DETAIL: The data directory was initialized by PostgreSQL version 9.1, which is not compatible with this version 8.4.7. From: Dannon Baker [dannon.ba...@gmail.com] Sent: Monday, July 22, 2013 5:01 PM To: Ravpreet Setia Cc: galaxy-dev@lists.bx.psu.edu Subject: Re: [galaxy-dev] Cloudman - is it possible to still use depreciated AMIs ? Yes, you can still use the deprecated AMIs. What error are you seeing when you try to ssh in? On Mon, Jul 22, 2013 at 4:30 PM, Ravpreet Setia ravpreet.se...@oicr.on.camailto:ravpreet.se...@oicr.on.ca wrote: I tried launching an instance specifying ami-da58aab3 as the AMI but I am unable to SSH or access Cloudman using the instance's URL. ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Re: [galaxy-dev] Cloudman - is it possible to still use depreciated AMIs ?
Hey, thanks for the response. The ssh issue was on my end and is now resolved. However, when I try the old AMI (ami-da58aab3), it mounts the new directory structure (meaning galaxyTools does not exist). Why does the old AMI have the directory structure of the new AMI? Along with that, PostgreSQL does not load properly, it is stuck at Starting up. I get the following error: FATAL: database files are incompatible with server DETAIL: The data directory was initialized by PostgreSQL version 9.1, which is not compatible with this version 8.4.7. From: Dannon Baker [dannon.ba...@gmail.com] Sent: Monday, July 22, 2013 5:01 PM To: Ravpreet Setia Cc: galaxy-dev@lists.bx.psu.edu Subject: Re: [galaxy-dev] Cloudman - is it possible to still use depreciated AMIs ? Yes, you can still use the deprecated AMIs. What error are you seeing when you try to ssh in? On Mon, Jul 22, 2013 at 4:30 PM, Ravpreet Setia ravpreet.se...@oicr.on.camailto:ravpreet.se...@oicr.on.ca wrote: I tried launching an instance specifying ami-da58aab3 as the AMI but I am unable to SSH or access Cloudman using the instance's URL. ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
[galaxy-dev] Cloudman - is it possible to still use depreciated AMIs ?
I tried launching an instance specifying ami-da58aab3 as the AMI but I am unable to SSH or access Cloudman using the instance's URL. ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Re: [galaxy-dev] Cloudman - is it possible to still use depreciated AMIs ?
Yes, you can still use the deprecated AMIs. What error are you seeing when you try to ssh in? On Mon, Jul 22, 2013 at 4:30 PM, Ravpreet Setia ravpreet.se...@oicr.on.cawrote: I tried launching an instance specifying ami-da58aab3 as the AMI but I am unable to SSH or access Cloudman using the instance's URL. ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
