I can't run ColdFusion 2016 after installed. I open terminal window and type in this command:
/Applications/Coldfusion2016/cfusion/bin/coldfusion start
After that, it prompted me to type the command: sudo ./coldfusion start
You must be the root user to configure the ColdFusion connector.
Start ColdFusion as "sudo ./coldfusion start" to configure the
connector. Once connector has been configured, start ColdFusion as
"./coldfusion start" to run ColdFusion as non-root user".
I did all the steps however it failed to run. Can anyone help me with this problem? I greatly appreciate your answer.
You literally need to add the sudo command to the beginning of your start command. MacOS is requiring admin access to start the server.
sudo /Applications/Coldfusion2016/cfusion/bin/coldfusion start
When this runs, you'll be prompted for your admin password before it starts.
Related
I try'd many time using ssh to remove this banner but ssh alway show in bnconfig not found.
enter image description here
Have a look at the documentation Remove The Bitnami Banner:
To remove the banner link to the Bitnami Info page, follow these steps:
Log in to into your server console using SSH and execute the following command. Remember to replace APPNAME with the actual name or
directory location of your application. sudo /opt/bitnami/apps/APPNAME/bnconfig --disable_banner 1
Restart the Web server.
If you’re using Apache, execute the command below:
sudo /opt/bitnami/ctlscript.sh restart apache
If you’re using NGINX, execute the command below:
sudo /opt/bitnami/ctlscript.sh restart nginx
NOTE: The above steps will only remove the corner banner. The Bitnami Info page will still be available by visiting
http://DOMAIN/bitnami/index.html.
I've installed Ghost Certified by Bitnami from GCP Marketplace and found no issues with command sudo /opt/bitnami/apps/ghost/bnconfig --disable_banner 1.
If you're still facing this issue, you can try to reinstall Ghost CMS from the Marketplace or/and reach Bitnami Community.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
The community reviewed whether to reopen this question 2 months ago and left it closed:
Original close reason(s) were not resolved
Improve this question
Do I have to restart cron after changing the crontable file?
No.
From the cron man page:
...cron will then examine the modification time on all crontabs
and reload those which have changed. Thus cron need not be restarted
whenever a crontab file is modified
But if you just want to make sure its done anyway,
sudo service cron reload
or
/etc/init.d/cron reload
On CentOS with cPanel sudo /etc/init.d/crond reload does the trick.
On CentOS7: sudo systemctl start crond.service
I had a similar issue on 16.04 VPS Digital Ocean. If you are changing crontabs, make sure to run
sudo service cron restart
Commands for RHEL/Fedora/CentOS/Scientific Linux user
Start cron service
To start the cron service, use: /etc/init.d/crond start
OR RHEL/CentOS 5.x/6.x user: service crond start
OR RHEL/Centos Linux 7.x user: systemctl start crond.service
Stop cron service
To stop the cron service, use: /etc/init.d/crond stop
OR RHEL/CentOS 5.x/6.x user: service crond stop
OR RHEL/Centos Linux 7.x user: systemctl stop crond.service
Restart cron service
To restart the cron service, use: /etc/init.d/crond restart
OR RHEL/CentOS 5.x/6.x user: service crond restart
OR RHEL/Centos Linux 7.x user: systemctl restart crond.service
Commands for Ubuntu/Mint/Debian based Linux distro
Debian Start cron service
To start the cron service, use: /etc/init.d/cron start
OR sudo /etc/init.d/cron start
OR sudo service cron start
Debian Stop cron service
To stop the cron service, use: /etc/init.d/cron stop
OR sudo /etc/init.d/cron stop
OR sudo service cron stop
Debian Restart cron service
To restart the cron service, use: /etc/init.d/cron restart
OR sudo /etc/init.d/cron restart
OR sudo service cron restart
Source: https://www.cyberciti.biz/faq/howto-linux-unix-start-restart-cron/
Depending on distribution, using "cron reload" might do nothing. To paste a snippet out of init.d/cron (debian squeeze):
reload|force-reload) log_daemon_msg "Reloading configuration files for periodic command scheduler" "cron"
# cron reloads automatically
log_end_msg 0
;;
Some developer/maintainer relied on it reloading, but doesn't, and in this case there's not a way to force reload. I'm generating my crontab files as part of a deploy, and unless somehow the length of the file changes, the changes are not reloaded.
try this one for centos 7 : service crond reload
If file /var/spool/cron/crontabs/root edited via SFTP client - service cron restart needed.
Reload service not work.
If edited file /var/spool/cron/crontabs/root via console linux (nano, mc) - restart NOT needed.
If edited cron via crontab -e - restart NOT needed.
Try this out: sudo cron reload
It works for me on ubuntu 12.10
Try this: service crond restart, Hence it's crond not cron.
There are instances wherein cron needs to be restarted in order for the start up script to work. There's nothing wrong in restarting the cron.
sudo service cron restart
On CentOS (my version is 6.5) when editing crontab you must close the editor to reflect your changes in CRON.
crontab -e
After that command You can see that new entry appears in /var/log/cron
Sep 24 10:44:26 ***** crontab[17216]: (*****) BEGIN EDIT (*****)
But only saving crontab editor after making some changes does not work. You must leave the editor to reflect changes in cron. After exiting new entry appears in the log:
Sep 24 10:47:58 ***** crontab[17216]: (*****) END EDIT (*****)
From this point changes you made are visible to CRON.
Ubuntu 18.04
* Usage: /etc/init.d/cron {start|stop|status|restart|reload|force-reload}
I'm following the "Installing CKAN from source" guide. And in the step to start the jetty service: sudo service jetty start. But it doesn't work, it prints "Failed to start jetty.service: Unit jetty.service not found".
Now, if instead that command, I use: sudo /etc/init.d/jetty8 start, the server starts correctly.
So, my guess (not totally sure) is that the jetty.home is not set properly.
For what it's worth, I'm using Ubuntu 16.04, running in virtualbox.
Thanks in advance to anyone who can help me.
P.S: If additional information is needed, please let me know.
For Ubuntu 16, just run sudo systemctl unmask jetty8 then sudo service jetty8 start
If sudo /etc/init.d/jetty8 start works then you should be able to use
sudo service jetty8 start
(note the use of jetty8 instead of jetty).
This is a pretty basic question, but I coiuld nto for the life of me find a straight answer about it on google.
I have logstash/Kibana/Elastisearch installed and working on an AWS server. Due to some complications, logstash stopped sending files to Kibana, and I wanted to restart it to see if it would fix the issue. (This is on an Ubuntu 14.04.2).
All of the commands I looked up on google would not restart the service properly. If I check the services running, logstash is on that list and has a -.
restart logstash gives the error "Unknown job: logstash", and some of the others I found gave a similar kind of error.
What is the proper command to run in order to restart logstash?
if you installed .deb or .rpm package then you can restart using command
sudo service logstash restart
or
sudo /etc/init.d/logstash restart
or
sudo service logstash stop
sudo service logstash start
if you logstash creating problem to starting or stoping then you can start it manually also
go to /opt/logstash/bin and run logstash script (logstash.bat for window)
cd /opt/logstash/bin
./logstash -f logstash-simple.conf
logstash-simple.conf is your logstash config file you can change it to any name
or
if you downloaded .zip or any other compressed file then go that path and run same way.
I am trying to deploy a Django application on Google Compute Engine. I'm using a Debian 7 image and want to set up Django with Nginx, Gunicorn, virtualenv, supervisor and PostgreSQL. I have everything running fine on my development machine which is running Ubuntu 14.04 with Django installed and PostgreSQL as the backend.
I'm using the tutorial located at http://datacommunitydc.org/blog/2013/12/a-tutorial-for-deploying-a-django-application-that-uses-numpy-and-scipy-to-google-compute-engine-using-apache2-and-modwsgi/. I'm also using the tutorial located at http://michal.karzynski.pl/blog/2013/06/09/django-nginx-gunicorn-virtualenv-supervisor/ as it's specific to virtualenv and PostgreSQL which I'm using on my development machine. I've setup my GCE instance, instaled and updated aptitude. I've installed PostgreSQL however when I attempt to create a database user and a new database for the app I get an error and nothing is created.
Following the tutorial I've run:
$ sudo su - postgres
postgres#django:~$ createuser -P
Enter name of role to add: hello_django
Enter password for new role:
Enter it again:
Shall the new role be a superuser? (y/n) n
Shall the new role be allowed to create databases? (y/n) n
Shall the new role be allowed to create more new roles? (y/n) n
When it attempts to create the new user role I receive the following error:
createuser: could not connect to database postgres: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
When I run the shell script ls /etc/init.d it says that postgresql is running, but I still can't add the new role. Can someone tell me what I'm doing wrong?
Regards.
I wasn't able to reproduce the issue on my end, but it appears to be an issue with PostgreSQL and its dependencies. You can try removing all installed PostgreSQL components and dependencies and then reinstalling PostgreSQL:
sudo apt-get remove --purge postgresql-9.1*
sudo apt-get install postgresql-9.1
If it's still unable to connect to the database, the issue might be originating from your $PATH, in which case you'll need to point it to /usr/local/bin/psql.
I have just had the same problem.
This is most likely cause the postgres cluster has not been initialised yet.
And the reason that this didn't install automatically is because you have set up the locale of the box yet. This is something that has to be done on Amazon EC2 instances as well.
You need to run:
sudo apt-get install locales
And then:
sudo dpkg-reconfigure locales
I had to choose which locales I wanted to setup, I chose en_AU UTF-8.
After this I rebooted, then I could run this to initialise the cluster:
sudo pg_createcluster 9.1 main --start
This started the service and created the pg_hba.conf files etc.
I faced a similar problem a while back. It can resolved using a few simple steps:
As postgres user run : initdb --locale en_US.UTF-8 -E UTF8 -D 'var/lib/postgres/data'. Note depending on the distro postgres in the command can be pgsql. You can easily check if the directory exists with an ls command.
systemctl start postgresql (if you have systemd) or just a /etc/init.d/postgresql start should do. These commands must be rub as the superuser.
All this is from the ArchWiki.