Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ensure AMI has completed installation before continuing (in particular before installing agents) #7

Open
mdennis opened this issue Jul 3, 2012 · 3 comments

Comments

@mdennis
Copy link

mdennis commented Jul 3, 2012

see below error log. It appears that agent installation was attempted before the AMI finished installing other packages

2012-07-03 01:25:15 +0000 Removing old opscenter-agent files.
2012-07-03 01:25:15 +0000 opscenter-agent: unrecognized service
2012-07-03 01:25:15 +0000 E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
2012-07-03 01:25:15 +0000 E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
2012-07-03 01:25:15 +0000 Starting agent installation process for version 2.9-1
2012-07-03 01:25:15 +0000 E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
2012-07-03 01:25:15 +0000 E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
2012-07-03 01:25:15 +0000 FAILURE: The package "sysstat" does not appear to be available or installable

@harshvladha
Copy link

Try Installing SYSSTAT on that particular node manually.. That fixed my problem for one node. But now I am getting another error on another while installing SYSSTAT that its a dependent package.

I am also getting " scp: /tmp/tmpuK1_Wc: Permission denied " even though I have given 777 permission to /tmp directory

@harshvladha
Copy link

oh! That was posted on 2012 :P Can I get a help?

@joaquincasares
Copy link
Owner

@harshvladha I haven't seen this sort of issue for a while. You may want to check your user-data string and make sure everything is correct first. You can find your user-data string in the first few line of ~/datastax_ami/ami.log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants