I have previously installed the Cloud Code tools on mac before upgrading to Yosemite. Now when installing with the following command
curl -s https://www.parse.com/downloads/cloud_code/installer.sh | sudo /bin/bash
that I found on the most recent documentation on the parse site i get the following error.
/bin/bash: line 1: html: No such file or directory
/bin/bash: line 2: syntax error near unexpected token <'
'bin/bash: line 2:301 Moved Permanently
I have also just entered "https://www.parse.com/downloads/cloud_code/installer.sh" into a browser and ran the shell script. It states that it is installing and it creates a directory in /usr/local/bin/ and contains the file "parse" with no extension.
When i examine the file in VI i see the following text.
I have previously installed the Cloud Code tools on mac before upgrading to Yosemite. Now when installing with the following command
curl -s https://www.parse.com/downloads/cloud_code/installer.sh | sudo /bin/bash
that I found on the most recent documentation on the parse site i get the following error.
/bin/bash: line 1: html: No such file or directory
/bin/bash: line 2: syntax error near unexpected token <'
'bin/bash: line 2:301 Moved Permanently
I have also just entered "https://www.parse.com/downloads/cloud_code/installer.sh" into a browser and ran the shell script. It states that it is installing and it creates a directory in /usr/local/bin/ and contains the file "parse" with no extension.
When i examine the file in VI i see the following text.
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.6.0</center>
</body>
</html>
Clearly I am doing something wrong here..or could it be that something has actually been moved and the documentation is just not up to date?
I just had the same problem (OS X 10.9.5). So it´s not OS related.
But I found out that you can do a manual install.
First download the install.sh file with a web browser.
Then check the file by right clicking it and check the file info or open it with a text editor.
In the file you see that it downloads the parse binary from here:
https://www.parse.com/downloads/cloud_code/parse
Download that file.
Start terminal and go to where you downloaded the file.
Enter:
mv parse /usr/local/bin/parse
chmod 755 /usr/local/bin/parse
Test that it is working.
Works for me! :-)
Related
I am trying to install nagios-plugins-2.2.1 on redhat machine
when running this command:
Nagios /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
i am getting the error as
no such file or directory
pls help
https://www.youtube.com/watch?v=VsIrAsXzbx4
It looks like the nagios binary is located in another location not in /usr/local/nagios/bin/nagios
To find where it is run:
which nagios
If nagios was installed using the RHEL package manager so it will be usually in:
/usr/sbin/nagios
If it did not come back with result just type the first 3 letters "nag" then type the "Tab" key and it will complete it.
Once you find it then use it instead of /usr/local/nagios/bin/nagios
Then make sure you get the right nagios.cfg file location by running the 2 following commands:
updatedb
locate nagios.cfg
If when you run updatedb you got "Command not found" error message then mlocate package is not installed and you can get the nagios.cfg location by running this command instead
find / -xdev -type f -name "nagios.cfg"
So by that you should have both "nagios binary" and "nagios.cfg file", you can then re-run the command with the right file paths
It looks like "nagios.cfg" does not exist.
Try to create it and configuring it manually.
Then try again.
You can try to look at where your nagios.cfg file has been created, using
locate nagios.cfg
for instance, to make sure your file is in the right path and maybe call that newly displayed path instead.
/usr/local/nagios/bin/nagios -v [path_of_nagios_cfg]
Also you need to omit the first "Nagios" from the command line as it is in Capital N which sure is supposed to come back with "no such file or directory" message
The command should only be like this:
/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
you will find nagios.cfg file in #/usr/local/nagios/etc
then run that command giving this path.
I have been trying to pip install psycopg2 for some time now
I have just updated to python 3.7.4, before this problem started.
To set my path to a specific python version I used the code below.
nano .bash_profile
I thought that it would now be easy for my system to identify the path of the newly installed python, as to enable it to install psycopg2. Then the below started happening.
The second line of system terminal or python terminal is now always showing:
-bash: zzzzz#: command not found on my terminal
No matter what I type on my terminal, I am always getting command not found
This would mean you literally have "zzzzz" somewhere in the bash_profile. Bash is seeing "zzzzz" as just another command to run at startup like the rest of the profile script. As there is nothing in your PATH matching that string, bash reports the issue back to you.
Either remove the extra line from your .bash_profile. OR use a terribly wasteful work-around!
ln -s /bin/true /bin/zzzzz
This will create a symbolic link to the "true" binary (all it ever does is return true) from zzzzz. Now bash can find zzzzz and run it during start up, which does nothing. No more error and an absurd work around. You should fix the file.
I have created a model now I am using this command to restart the module
but it is showing this error
using this command to restart module
odoo start --config=/etc/odoo/odoo.conf -i HelloModule
the error is
odoo: error: The config file '/etc/odoo/odoo.conf' selected with -c/--config doesn't exist or is not readable, use -s/--save if you want to generate it
the screenshot of the file which error shows that it is not available
Try adding readable permission to config file by chmod command
sudo chmod +r etc/odoo/odoo.conf
Check this link to know more about modifying file permissions.
I have a strange issue on my LAMP installation. I have a php script with function that save a log to a file using fopen().
If I run the script by shell_exec($scriptfilewithpath) nothing happens (it may give some errors but I am not sure how to get it from shell_exec.
If I run the script from the ssh console (sudo php /opt/bitnami/apache2/htdocs/script.php ) I get " PHP Warning: fopen(/opt/bitnami/apache2/htdocs/log.log): failed to open stream: No such file or directory in /opt/bitnami/apache2/htdocs/script.php on line 18" .
root and bitnami(used to install and set up LAMP) users have full access to script folder.
Any ideas where I am going wrong?
Thanks
I am trying to install Postgres in order to use Heroku.
I am following the instructions in the Heroku tutorial, and after Postgres installation (which was successful), it says to configure my .bash_profile to allow for Postgres command line functionality.
I am following the instructions here, but I am unable to successfully add this line:
export PATH=$PATH:/Applications/Postgres.app/Contents/Versions/latest/bin
That folder does in fact contain "psql" on my computer, so it should work. Here is my current .bash_profile:
# Setting PATH for Python 2.7
# The orginal version is saved in .bash_profile.pysave
PATH="/Library/Frameworks/Python.framework/Versions/2.7/bin:${PATH}"
export PATH
# The next line updates PATH for the Google Cloud SDK.
source '/Users/user/google-cloud-sdk/path.bash.inc'
# The next line enables shell command completion for gcloud.
source '/Users/user/google-cloud-sdk/completion.bash.inc'
I tried to add the Postgres line to the end of that file, but it is not working. After searching online, there does not seem to be consensus on how to add PATHs to .bash_profile. I have tried many versions listed, but none have worked.
Please let me know if I'm doing this incorrectly!
Add this line to the end of your .bash_profile:
export PATH=/Applications/Postgres.app/Contents/Versions/latest/bin:$PATH
This makes the search of a binary to look in that location "BEFORE the rest of the PATH"
Kill all instances of terminal and open it again, then it should work.
Try which xxx where xxx is the name of some binary inside /Applications/Postgres.app/Contents/Versions/latest/bin and check if it's returning that location.
Tell me if it works.