If you are extending AbstractTransactionalJUnit4SpringContextTests, are you sure you need to do that? Removing that might fix it.
Fatal error during compilation org.springframework.beans.factory.BeanDefinitionStoreException: Failed to read candidate component class: URL [jar:file:/Users/lrussell/.grails/ivy-cache/org.grails/grails-hibernate/jars/grails-hibernate-2.2.4.jar!/org/codehaus/groovy/grails/compiler/gorm/GormTransformer.class]; nested exception is java.lang.NoClassDefFoundError: org/springframework/core/type/classreading/AnnotationMetadataReadingVisitor
First tried removing ~/.grails/
And then running the grails RunApp again. It downloaded the cache fresh, might take a while. Didn’t seem to make any difference though…
Then in the Groovy Grails Tools Suite, I went to the Grails Plugin Manager (right click project > Grails Tools > Grails Plugin Manager), showed all plugins currently installed. Some required an update, so updated everything. That worked 🙂
I had a problem connecting to a vagrant virtualbox cluster from the host (OS X 10.10.4 Yosemite).
There are three hosts set up as a vagrant private_network, each having an assigned IP in the range 192.168.37.2 – 192.168.37.4
The virtual network I wanted to connect to (vboxnet0) had a status of Up and the hosts were running. I could connect with
vagrant ssh to all of the hosts in the network, but I was unable to ping the virtual host from the host OS.
arp -a showed no entry for the virtual network (vboxnet0):
? (192.168.0.1) at 14:cc:20:4c:37:40 on en0 ifscope [ethernet]
? (192.168.0.100) at b8:e9:37:ec:1c:c4 on en0 ifscope [ethernet]
? (192.168.0.106) at 14:10:9f:de:62:e7 on en0 ifscope permanent [ethernet]
? (192.168.0.255) at ff:ff:ff:ff:ff:ff on en0 ifscope [ethernet]
vboxmanage list hostonlyifs showed six other virtual networks setup, most with status Down, possibly from other vagrant installations
Running these steps fixed it:
Shutdown all nodes with
Remove all the virtual networks with
vboxmanage hostonlyif remove vboxnet0for every network returned by
vboxmanage list hostonlyifs
vboxmanage hostonlyif create. This recreated the vboxnet0 network which was the only one I was interested in
vboxmanage hostonlyif ipconfig vboxnet0 –ip 192.168.37.1
This seems to reset the state, now I can connect to each of the hosts in the network.
Maybe caused by the particular version of PHP shipped with AMMPS and symlinked by default (PHP 5.3.21 at this time).
For example this command:
/Applications/AMPPS/php/bin/php ~/wp-cli.phar --info
To fix it, update AMMPS to the latest. This includes PHP 5.4.11, but does not link it as the default.
Now this command:
/Applications/AMPPS/php-5.4/bin/php ~/wp-cli.phar --info
PHP binary: /Applications/AMPPS/php-5.4/bin/php-5.4.11
PHP version: 5.4.11
WP-CLI root dir: phar://wp-cli.phar
WP-CLI global config:
WP-CLI project config:
WP-CLI version: 0.15.0
Now fix it more permanently by adding that version to your PATH, i.e.
A quick summary of what might go wrong when trying to connect to an Oracle database. Based on this excellent article. Read the whole thing, this is just a quick reference.
|ORA-12154||TNS:could not resolve the connect identifier specified||No entry with the requested name in tnsnames.ora|
|ORA-12545||Connect failed because target host or object does not exist||There is an entry in tnsnames.ora, but the hostname doesn’t resolve to an IP, or the IP is bad. The server can’t be reached|
|ORA-12541||TNS:no listener||All the above are OK, but there is no listener process running on the server we’re trying to connect to|
|ORA-12560||TNS:protocol adapter error||The connection to the server is OK, and there is a listener process on the target server, but it is running on a different port than that specified in the tnsnames.ora|
|ORA-12514||TNS:listener does not currently know of service requested in connect descriptor/td>||We got as far as connecting to the listener process on the server, but the service name in the tnsnames.ora is wrong|