OK. I will. The weird thing is that the Custom scripts do indeed run on the launched instances.
On Tuesday, June 12, 2012 4:26:43 AM UTC-7, Nick Toursky wrote: > > For some reason Scalr is unable to connect to Scalarizr running on this > server. > Error message seems to be "Permission denied". You can try to connect to > this port from Scalr server to investigate this problem. > > On Tue, Jun 12, 2012 at 1:50 AM, Val <[email protected]> wrote: > >> I am seeing the following error in my Event Log when I try to run a >> Custom Script. Why does this happen? >> >> Jun 11, 2012 16:47:49 >> Condor-Cluster <https://vmtest-vm1.lbl.gov:44444/#/farms/13/view> >> <https://vmtest-vm1.lbl.gov:44444/#/servers//view>/DBServer >> Cannot deliver message 'ExecScript' (message_id: >> 2b61519c-61f6-40ab-b879-e77d79bb4a96) via REST to server '50.16.9.129' >> (server_id: b9121848-05ab-4388-964f-cd91a7c22466). Error: 0 Couldn't >> connect to server; Failed to connect to 50.16.9.129: Permission denied ( >> http://50.16.9.129:8013/control) >> >> *Caller:* <https://vmtest-vm1.lbl.gov:44444/#/servers//view>/DBServer >> >> *Message:* Cannot deliver message 'ExecScript' (message_id: >> 2bxxx519c-61f6-40ab-b879-e77d79bb4a96) via REST to server 'x.x.x.x' >> (server_id: b9xxx1848-05ab-4388-964f-cd91a7c22466). Error: 0 Couldn't >> connect to server; Failed to connect to x.x.x.x: Permission denied ( >> http://x.x.x.x:8013/control) >> >> On Monday, June 11, 2012 2:17:40 PM UTC-7, Val wrote: >>> >>> I have scripts running on the HostUp event. >>> >>> On Wednesday, June 6, 2012 7:22:01 AM UTC-7, Nick Toursky wrote: >>>> >>>> Val, >>>> >>>> I assumed you're talking about already running instance. >>>> Which event do you have your script assigned to? >>>> >>>> Regards, >>>> Nick >>>> >>>> On Tue, Jun 5, 2012 at 7:56 PM, Val <[email protected]> wrote: >>>> >>>>> Nick, >>>>> >>>>> I am already using the scripting engine. Is executing a dummy script >>>>> different from this? I am getting this error when I run the szradm inside >>>>> of a script that is run during an event on instance launch. >>>>> >>>>> Cheers, >>>>> Val >>>>> >>>>> >>>>> On Tuesday, June 5, 2012 4:19:49 AM UTC-7, Nick Toursky wrote: >>>>>> >>>>>> Hi Val, >>>>>> >>>>>> By default Scalarizr using the latest communication protocol it is >>>>>> aware of. >>>>>> Scalr indicates the latest version of communication protocol in all >>>>>> messages sent to Scalarizr. So, just sending a message from Scalr to >>>>>> Scalarizr should fix the issue. You can execute a dummy script through >>>>>> Scalr UI. >>>>>> >>>>>> Regards, >>>>>> Nick >>>>>> >>>>>> On Tue, Jun 5, 2012 at 6:59 AM, Val <[email protected]> wrote: >>>>>> >>>>>>> I have updated to scalarizr 0.7.231 but I am still having the same >>>>>>> error on szradm. >>>>>>> >>>>>>> [root@ec2-23-22-12-55 ~]# /usr/local/bin/szradm list-roles >>>>>>> Traceback (most recent call last): >>>>>>> File "/usr/local/bin/szradm", line 10, in <module> >>>>>>> main() >>>>>>> File >>>>>>> "/usr/lib/python2.6/site-**packa**ges/scalarizr/util/**szradm.py", >>>>>>> line 630, in main >>>>>>> raise LookupError("Cant execute command or option. Error: %s" >>>>>>> % (e)) >>>>>>> LookupError: Cant execute command or option. Error: Request failed. >>>>>>> HTTP Error 500: Error. URL: https://vmtest-vm1.lbl.gov:**444** >>>>>>> 44/query-env <https://vmtest-vm1.lbl.gov:44444/query-env>. Service >>>>>>> message: Version '2012-04-17' not supported >>>>>>> [root@ec2-23-22-12-55 ~]# yum list scalarizr* >>>>>>> Loaded plugins: fastestmirror >>>>>>> Loading mirror speeds from cached hostfile >>>>>>> * base: centos.vipernetworksystems.com >>>>>>> * extras: mirror.cogentco.com >>>>>>> * updates: mirrors.lga7.us.voxel.net >>>>>>> Installed Packages >>>>>>> scalarizr-base.noarch 0.7.231-1.el5 >>>>>>> installed >>>>>>> scalarizr-ec2.noarch 0.7.231-1.el5 >>>>>>> installed >>>>>>> Available Packages >>>>>>> scalarizr-cloudstack.noarch 0.7.231-1.el5 >>>>>>> scalr >>>>>>> scalarizr-eucalyptus.noarch 0.7.231-1.el5 >>>>>>> scalr >>>>>>> scalarizr-nimbula.noarch 0.7.231-1.el5 >>>>>>> scalr >>>>>>> scalarizr-openstack.noarch 0.7.231-1.el5 >>>>>>> scalr >>>>>>> scalarizr-rackspace.noarch 0.7.231-1.el5 >>>>>>> scalr >>>>>>> [root@ec2-23-22-12-55 ~]# >>>>>>> >>>>>>> On Friday, June 1, 2012 3:26:58 AM UTC-7, Marat wrote: >>>>>>> >>>>>>>> Please update to 0.7.231 We've missed to review szradm >>>>>>>> >>>>>>>> On Friday, June 1, 2012 7:44:49 AM UTC+3, Val wrote: >>>>>>>>> >>>>>>>>> Now my scripts that use "szradm" are still not working. Do I need >>>>>>>>> to update this too? The error was the same as the scalarizr >>>>>>>>> 0.7.228 gave. >>>>>>>>> >>>>>>>>> *Message:* Script 'Condor_Simple' execution result (Time: 57.52 >>>>>>>>> s, Exit code: 0). Traceback (most recent call last): >>>>>>>>> File "/usr/local/bin/szradm", line 10, in <module> >>>>>>>>> main() >>>>>>>>> File >>>>>>>>> "/usr/lib/python2.6/site-**packa****ges/scalarizr/util/**szradm.py", >>>>>>>>> line 616, in main >>>>>>>>> raise LookupError("Cant execute command or option. Error: %s" % >>>>>>>>> (e)) >>>>>>>>> LookupError: Cant execute command or option. Error: Request >>>>>>>>> failed. HTTP Error 500: Error. URL: https://vmtest-vm1.lbl.gov:** >>>>>>>>> 444****44/query-env <https://vmtest-vm1.lbl.gov:44444/query-env>. >>>>>>>>> Service message: Version '2012-04-17' not supported >>>>>>>>> >>>>>>>>> On Thursday, May 31, 2012 8:55:53 PM UTC-7, Val wrote: >>>>>>>>>> >>>>>>>>>> On centos 5, I needed to enable the scalr repo in >>>>>>>>>> /etc/yum.repos.d/scalr-latest.******repo. I first uncommented >>>>>>>>>> the repo entries, set the enable flag to 0. I then ran the >>>>>>>>>> following >>>>>>>>>> command. >>>>>>>>>> >>>>>>>>>> $ cat /etc/yum.repos.d/scalr-latest.******repo >>>>>>>>>> [scalr] >>>>>>>>>> gpgcheck = 0 >>>>>>>>>> enabled = 0 >>>>>>>>>> name = scalr >>>>>>>>>> baseurl = http://rpm.scalr.net/rpm/rhel/****** >>>>>>>>>> $releasever/$basearch<http://rpm.scalr.net/rpm/rhel/$releasever/$basearch> >>>>>>>>>> >>>>>>>>>> $ yum --enablerepo=scalr install scalarizr-ec2 >>>>>>>>>> >>>>>>>>>> On Thursday, May 31, 2012 6:45:19 PM UTC-7, Val wrote: >>>>>>>>>>> >>>>>>>>>>> This happens on Centos 5.7 >>>>>>>>>>> >>>>>>>>>>> On Thursday, May 31, 2012 3:31:42 PM UTC-7, Val wrote: >>>>>>>>>>>> >>>>>>>>>>>> yum -y install scalarizr-ec2 >>>>>>>>>>>> Loaded plugins: fastestmirror >>>>>>>>>>>> Repository base is listed more than once in the configuration >>>>>>>>>>>> Repository updates is listed more than once in the configuration >>>>>>>>>>>> Repository extras is listed more than once in the configuration >>>>>>>>>>>> Repository centosplus is listed more than once in the >>>>>>>>>>>> configuration >>>>>>>>>>>> Repository contrib is listed more than once in the configuration >>>>>>>>>>>> Loading mirror speeds from cached hostfile >>>>>>>>>>>> * base: mirror.symnds.com >>>>>>>>>>>> * extras: mirror.symnds.com >>>>>>>>>>>> * updates: mirror.symnds.com >>>>>>>>>>>> Setting up Install Process >>>>>>>>>>>> Package scalarizr-ec2-0.7.228-1.el5.**no****arch already >>>>>>>>>>>> installed and latest version >>>>>>>>>>>> Nothing to do >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Thursday, May 31, 2012 3:29:36 PM UTC-7, Val wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> "yum -y install scalarizer-ec2" did not upgrade to Scalarizr >>>>>>>>>>>>> 0.7.230 >>>>>>>>>>>>> >>>>>>>>>>>>> On Thursday, May 31, 2012 10:08:29 AM UTC-7, Dale-Kurt Murray >>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Did the latest release fix your issues? >>>>>>>>>>>>>> >>>>>>>>>>>>>> I'm still getting 0.7.228 when I attempt to build a role >>>>>>>>>>>>>> >>>>>>>>>>>>>> http://cl.ly/**431L2Z3c1X0R121e1****Q0b<http://cl.ly/431L2Z3c1X0R121e1Q0b> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thursday, May 31, 2012 3:38:27 AM UTC-5, Marat wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Scalarizr 0.7.230 is available. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wednesday, May 30, 2012 9:09:48 PM UTC+3, DicsyDel wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> This is compatibility issue in new scalarizr. Fixed version >>>>>>>>>>>>>>>> will be >>>>>>>>>>>>>>>> available within 12 hours. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>> Igor >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On 30 May 2012 21:03, Val <[email protected]> wrote: >>>>>>>>>>>>>>>> > I got the exact same error. My Scalr version is 3.0. >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > On Wednesday, May 30, 2012 8:07:35 AM UTC-7, Pawel Kilian >>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>> >> 2012-05-30 10:51:35,457 - ERROR - scalarizr.handlers - >>>>>>>>>>>>>>>> Request failed. >>>>>>>>>>>>>>>> >> HTTP Error 500: Error. URL: >>>>>>>>>>>>>>>> https://scalr.nellymoser.com/**q****uery-env<https://scalr.nellymoser.com/query-env>. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >> Service message: Version '2012-04-17' not supported >>>>>>>>>>>>>>>> >> Traceback (most recent call last): >>>>>>>>>>>>>>>> >> File >>>>>>>>>>>>>>>> >> "/usr/lib/python2.6/site-**packa****ges/scalarizr/handlers/ >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >> __init__.py", line 301, in __call__ >>>>>>>>>>>>>>>> >> handler(message) >>>>>>>>>>>>>>>> >> File >>>>>>>>>>>>>>>> >> "/usr/lib/python2.6/site-**packa****ges/scalarizr/handlers/ >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >> script_executor.py", line 213, in __call__ >>>>>>>>>>>>>>>> >> target_ip=target_ip, local_ip=local_ip) >>>>>>>>>>>>>>>> >> File "/usr/lib/python2.6/site-**packa**** >>>>>>>>>>>>>>>> ges/scalarizr/queryenv.**py", line >>>>>>>>>>>>>>>> >> 147, in list_scripts >>>>>>>>>>>>>>>> >> return self._request("list-scripts",**p****arameters, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >> self._read_list_scripts_**respon****se) >>>>>>>>>>>>>>>> >> File "/usr/lib/python2.6/site-**packa**** >>>>>>>>>>>>>>>> ges/scalarizr/queryenv.**py", line >>>>>>>>>>>>>>>> >> 193, in _request >>>>>>>>>>>>>>>> >> xml = self.fetch(command, **params) >>>>>>>>>>>>>>>> >> File "/usr/lib/python2.6/site-**packa**** >>>>>>>>>>>>>>>> ges/scalarizr/queryenv.**py", line >>>>>>>>>>>>>>>> >> 70, in fetch >>>>>>>>>>>>>>>> >> response = opener.open(req) >>>>>>>>>>>>>>>> >> File "/usr/lib64/python2.6/urllib2.******py", line >>>>>>>>>>>>>>>> 397, in open >>>>>>>>>>>>>>>> >> response = meth(req, response) >>>>>>>>>>>>>>>> >> File "/usr/lib64/python2.6/urllib2.******py", line >>>>>>>>>>>>>>>> 510, in http_response >>>>>>>>>>>>>>>> >> 'http', request, response, code, msg, hdrs) >>>>>>>>>>>>>>>> >> File "/usr/lib64/python2.6/urllib2.******py", line >>>>>>>>>>>>>>>> 435, in error >>>>>>>>>>>>>>>> >> return self._call_chain(*args) >>>>>>>>>>>>>>>> >> File "/usr/lib64/python2.6/urllib2.******py", line >>>>>>>>>>>>>>>> 369, in _call_chain >>>>>>>>>>>>>>>> >> result = func(*args) >>>>>>>>>>>>>>>> >> File "/usr/lib64/python2.6/urllib2.******py", line >>>>>>>>>>>>>>>> 518, in >>>>>>>>>>>>>>>> >> http_error_default >>>>>>>>>>>>>>>> >> raise HTTPError(req.get_full_url(), code, msg, hdrs, >>>>>>>>>>>>>>>> fp) >>>>>>>>>>>>>>>> >> QueryEnvError: Request failed. HTTP Error 500: Error. >>>>>>>>>>>>>>>> URL: >>>>>>>>>>>>>>>> >> https://scalr.nellymoser.com/**q****uery-env<https://scalr.nellymoser.com/query-env>. >>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>> Service message: Version >>>>>>>>>>>>>>>> >> '2012-04-17' not supported >>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>> >> so it looks like my version of scalr does not support >>>>>>>>>>>>>>>> 2012-04-17 api >>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>> >> is there a way that i can fix it temporarly? >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > -- >>>>>>>>>>>>>>>> > You received this message because you are subscribed to >>>>>>>>>>>>>>>> the Google Groups >>>>>>>>>>>>>>>> > "scalr-discuss" group. >>>>>>>>>>>>>>>> > To view this discussion on the web visit >>>>>>>>>>>>>>>> > https://groups.google.com/d/**ms****g/scalr-discuss/-/** >>>>>>>>>>>>>>>> neYGfBXT7cEJ<https://groups.google.com/d/msg/scalr-discuss/-/neYGfBXT7cEJ> >>>>>>>>>>>>>>>> ****. >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > To post to this group, send email to >>>>>>>>>>>>>>>> [email protected]******. >>>>>>>>>>>>>>>> > To unsubscribe from this group, send email to >>>>>>>>>>>>>>>> > scalr-discuss+unsubscribe@**goog****legroups.com<scalr-discuss%[email protected]>. >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> > For more options, visit this group at >>>>>>>>>>>>>>>> > http://groups.google.com/**group****/scalr-discuss?hl=en<http://groups.google.com/group/scalr-discuss?hl=en>. >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "scalr-discuss" group. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/**ms**g/scalr-discuss/-/**DLtJ2GbFHcMJ<https://groups.google.com/d/msg/scalr-discuss/-/DLtJ2GbFHcMJ> >>>>>>> **. >>>>>>> >>>>>>> To post to this group, send email to [email protected]* >>>>>>> ***. >>>>>>> To unsubscribe from this group, send email to >>>>>>> scalr-discuss+unsubscribe@**goog**legroups.com<scalr-discuss%[email protected]> >>>>>>> . >>>>>>> For more options, visit this group at http://groups.google.com/** >>>>>>> group**/scalr-discuss?hl=en<http://groups.google.com/group/scalr-discuss?hl=en> >>>>>>> . >>>>>>> >>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "scalr-discuss" group. >>>>> To view this discussion on the web visit https://groups.google.com/d/* >>>>> *msg/scalr-discuss/-/**I2bz1CcHJ90J<https://groups.google.com/d/msg/scalr-discuss/-/I2bz1CcHJ90J> >>>>> . >>>>> >>>>> To post to this group, send email to [email protected]**. >>>>> To unsubscribe from this group, send email to >>>>> scalr-discuss+unsubscribe@**googlegroups.com<scalr-discuss%[email protected]> >>>>> . >>>>> For more options, visit this group at http://groups.google.com/** >>>>> group/scalr-discuss?hl=en<http://groups.google.com/group/scalr-discuss?hl=en> >>>>> . >>>>> >>>> >>>> -- >> You received this message because you are subscribed to the Google Groups >> "scalr-discuss" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/scalr-discuss/-/GE2zupGZ4WgJ. >> >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/scalr-discuss?hl=en. >> > > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/scalr-discuss/-/PVSnVGjwKUQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en.
