I am getting this error every time I ran puppet agent -t on the agent.
Error: Facter: error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/ipaddresses.rb: cannot load such file -- facter/util/ip
Can anyone help me in resolving this error?
I have tried various solutions but nothing seems to be working. Like installing gems package etc.
Puppet version I am ones 5.5.2
Are you calling/storing the file from the correct directory?
Error: Facter: error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/ipaddresses.rb:
The file ipaddresses.rb seems to be in folder 'facter', however, in the error you have a path facter/util/ip.
'Util' folder is within the 'Facter' folder, so you might have an incorrect path hence why the agent run is failing.
Related
I am trying to execute a ReactJS application on my Windows 10 system using npm.
On running the execution script, it is giving me a compilation error that states:
Module not found: Can't resolve '../assets_new/fonts/lato_bold.woff' in '\src\assets_new\scss'
The file lato_bold.woff does exist in the given path, yet the script isn't able to locate it.
Can someone pls let me know how could this be resolved?
From this message:
Can't resolve '../assets_new/fonts/lato_bold.woff' in '\src\assets_new\scss'
It seems that you are trying to fetch lato_bold.woff from fonts folder in assests_new but you are searching in scss folder of assests_new. Try changing it to fonts folder.
I'm tired of getting this error every third/fourth time I try to build project:
ERROR: Unable to resolve dependency for ':app#debug/compileClasspath': Could not resolve androidx.fragment:fragment:[1.2.0].
Show Details
Affected Modules: app
It also effects ':app#debugUnitTest/compileClasspath' and ':app#debugAndroidTest/compileClasspath' (shows the same error for them).
Also sometimes it goes after the following build error (internet connection is surely stable):
Unknown host 'repo.maven.apache.org: nodename nor servname provided, or not known'. You may need to adjust the proxy settings in Gradle.
Enable Gradle 'offline mode' and sync project
Learn about configuring HTTP proxies in Gradle
There were no changes in build.gradle files or any other gradle files before this error came.
It would be nice if you help to get rid of it. Gradle-plugin version = "1.3.71".
I generate app thanks to jhipster but when I run it I have the following error:
.m2\repository\org\liquibase\liquibase-core\3.5.3\liquibase-core-3.5.3.jar referenced one or more files that do not exist: .m2\repository\org\liquibase\liquibase-core\3.5.3\lib\snakeyaml-1.13.jar
The error happens in my IDE and when I run mvnw.
I can't find any solutions or workarounds.
Ok it seems that in fact my application failed to start cause my application-dev.yml was malformatted. But the error message what really not explicite and believed that the error come from the liquibase classpath.
I'm trying to install Apache Thrift on my system, which performs a cabal update command. This command fails with the following message:
Downloading the latest package list from stackage cabal: Failed to download
http://www.stackage.org/stackage/7ae494fec2db3161dfb8e64677149285857478e0/00-index.tar.gz
: ErrorMisc "Error HTTP code: 404"
I normally use stack and I never had to do a cabal update manually. I don't know if the interaction between cabal and stack is a problem here.
Any ideas on how to fix this?
EDIT: Looking at my `~/.cabal/config~ I see the following entry:
remote-repo: stackage:http://www.stackage.org/stackage/7ae494fec2db3161dfb8e64677149285857478e0
So it seems that line is the culprit, but I don't know whether stack could have changed this for a good reason.
Error Unable to read package metadata.This may be due to a missing
repodata directory.Please ensure that your install tree has been
correctly generated. Cannot retrieve repository metadata(repomd.xml)
for repository:CentOs. Please verify its path and try again.
('custom',[_Exit installer],'Edit','_Retry'，‘_Continue’)]
This problem is different from this question:
Unable to read package metadata. This may be due to missing repodata directory. Please ensure that your install tree has been correctly generated.
Becase I verify the repodata,the file is right.