im trying to install cloud manager on ubuntu 12.04.
But im failed and below is the error :
oracle-j2sdk1.7 installation failed. See /var/log/cloudera-manager-installer/3.install-oracle-j2sdk1.7.log for details. Click OK to revert this installation.
Any help can be appricaited now.
Regards,
BJ
Looks like its some kind of lock already in place which might occur at login or because of the first attempt at the installation failing.
Try logging in, maybe even rebooting and trying again.
If this still fails, try the following:
sudo rm /var/lib/apt/lists/* -vf
sudo apt-get update
This should force an update and recreate the directory correctly. There's a thread about this on the Ubuntu forums which might be more useful and provide a lot more information on this problem:
http://ubuntuforums.org/showthread.php?t=1986288
If this is still a problem. Provide the full stack trace/log that is mentioned in the error.
We can't blindly provide advice, we need the actual error from the log in order to help you.
Related
I am trying to start a Spring project using a PSQL database.
I have installed PSQL using Homebrew but,
When i run :
brew services start postgresql
I get this error:
Error: Failure while executing; /bin/launchctl bootstrap gui/501 /Users/[myusername]/Library/LaunchAgents/homebrew.mxcl.postgresql.plist exited with 5.
I am following this tutorial:
https://medium.com/#viviennediegoencarnacion/getting-started-with-postgresql-on-mac-e6a5f48ee399
Using a mac which is up to date.
Any help is greatly appreciated!
So my postgres service was started apparently.
Therefore when i was trying to start it again it causes an error.
Fix was to stop it and re run.
This error is due to the fact the server is already running. We need to stop and start it.
For Mac Users:
brew services stop postgresql
brew services start postgresql
EDIT: This may be a track, but it doesn't happen for me again since I updated to Monterey and running PSQL13
A full computer restart did solve it for me.
PS: I think the problem is related to the checkbox on log off "Reopen windows when logging back in".
I have a fresh EC2 setup on AWS and have loaded Mautic files into the main /html directory. When I go to that directory, I just get a screen saying:
"The site is currently offline due to encountering an error. If the problem persists, please contact the system administrator."
I have been digging everywhere to find a solution. I know this is not a real error message and it gives no details. The error logs are not being helpful either. There is one thing that shows over and over in error_log which is:
AH01071: Got error 'Primary script unknown\n'
I have rebooted this server, tried different combos of ownership and permissions, etc. I'm at a loss. I'm hoping someone can provide some insight to get me over this hump and actually get Mautic installed.
SIDE NOTE: Please do not suggest using Bitnami to install Mautic. We've already done that and found it to be very unstable. We are hoping a clean install that isn't dependant on anything else will work better for us. Thanks.
run following commands:
sudo chown -R www-data:www-data /var/www/html/mautic/
sudo chmod -R 755 /var/www/html/mautic/
h all ,
i am trying to uninstall sonarqube from the ubuntu machine using command "sudo apt-get remove --purge autoremove sonarqube-6.4.1" but I am getting error as no packages foun some one kindly help me with uninstalling soanrqube complaetly from ubuntu machine
Your purge isn't working because SonarQube likely wasn't installed via apt-get. So how was it installed? The docs offer clues:
Installing the Web Server tells you to download the SonarQube zip, expand it, and configure the properties file. So your first step would be to wipe out the SonarQube directory.
Of course, if SonarQube is running as a service on your machine, just deleting the diretory could lead to errors at the next startup, so you'll need to unwind that part too. For setting up a service, the docs advise you to:
create /etc/init.d/sonar
create a link in /usr/bin/sonar to the SonarQube start script
update your defaults
So you'll want to back those things out too.
I am installing a sensu server inside a docker container running ubuntu 14.04 but when I install it for some reason it does not install the sensu-dashboard.
When I run the following command to set up the defaults I get a file does not exist error
> Command: update-rc.d sensu-dashboard defaults
Error: update-rc.d: /etc/init.d/sensu-dashboard: file does not exist
I have searched for the file but does not seem to be installed anywhere.
Has anyone else had this problem before when installing sensu or know how to fix it?
Thank you
The default Dashboard was removed on July 28th so you missed it by a day!! :( You now have to use a different dashboard. Uchiwa is a great choice and is under very heavy development, so I am sure it will continue to become more feature rich.
link to uchiwa's github page
The default Dashboard was removed that is true but if want to use sensu-dashboard then go for Sensu-Enterprise.
Here is the link: http://sensuapp.org/enterprise
I have just installed MariaDB via homebrew on my Mac. At the end of the installation I got the following error:
Warning: The post-install step did not complete successfully
You can try again using `brew postinstall mariadb`
If I run brew postinstall mariadb I get:
==> /usr/local/Cellar/mariadb/5.5.34/bin/mysql_install_db --verbose --user=andrew --basedir=/usr/loca
MariaDB is hosted on launchpad; You can find the latest source and
email lists at http://launchpad.net/maria
Please check all of the above before mailing us! And remember, if
you do mail us, you should use the /usr/local/Cellar/mariadb/5.5.34/scripts/mysqlbug script!
READ THIS: https://github.com/mxcl/homebrew/wiki/troubleshooting
Which isn't helpful! The tutorial I was following told me to run unset TEMPDIR, then mysql_install_db --user=mysql --basedir=$(brew --prefix mariadb); running those results in the following:
/usr/local/opt/mariadb/bin/my_print_defaults: Can't read dir of '/usr/local/etc/my.cnf.d' (Errcode: 2)
Fatal error in defaults handling. Program aborted
chown: ./data: Operation not permitted
Cannot change ownership of the database directories to the 'mysql'
user. Check that you have the necessary permissions and try again.
I suspect the problem has something to do with the /usr/local/etc/my.cnf.d folder. I've seen this referred to in a couple of things I've tried, but it doesn't exist on my machine. I have tried a few different mysql_install_db commands I've found in other tutorials, but they all throw up a (different) error message.
Thanks for any help!
Just open the config file at /usr/local/etc/my.cnf with your editor and comment out the following line:
!includedir /usr/local/etc/my.cnf.d
Having been unsuccessful with further Googling of the problem I tried manually creating a /usr/local/etc/my.cnf.d and now the mysql_install_db command seems to have worked okay. I'm not sure if this is the appropriate solution or if my.cnf.d not existing is indicative of a deeper problem with the install but, as things seem to be working, I'll mark as resolved.
[Update] As I was a little unsure in my answer whether this was the 'correct' solution I just wanted to confirm that, after a month, everything is still working fine.
None of the solution here helped, I had to do this:
The post-install step did not complete successfully MySQL Mac OS Sierra
in short,
I made a backup of the folder /usr/local/var/mysql , then removed it
removed Mariadb brew remove mariadb
reinstalled Mariadb brew install mariadb
run brew services start mariadb
After that I could access with mysql -u root
You might have an orphaned configuration file. I was able to solve this problem by deleting an old /usr/local/etc/my.cnf. YMMV.
If you're having this problem in 2021
This worked for me:
sudo mysql_install_db
sudo chown -R <YOUR USER NAME HERE> /usr/local/mysql # for example sudo chown -R jperez /usr/mysql
sudo chgrp -R admin /usr/local/mysql
After that, running mysql or mariadb will show the database prompt.
This problem seems to have recently gone away.
A simple bew upgrade resolved the problem for me.
You may want to go
/usr/local/mysql
and delete the old MySQL file and install again