Description of problem: Unable to tail logs for any kinds of app, following error are shown: # rhc tail jboseap Password: * nil ********** Could not find any files matching glob Version-Release number of selected component (if applicable): devenv_2295 client: built from fork_ami_US2597_US2599_US2813_US2817_US2872_US2816_US2814_209 How reproducible: always Steps to Reproduce: 1.Create an app 2.Tail app log: # rhc tail jboseap Actual results: Could not find any files matching glob Expected results: App log should be shown. Additional info:
default glob most likely not set. Assigning to Chris
The default glob is set, looking into the issue in more detail...
This fix is available on J5's fork. https://github.com/J5/rhc/commits/commands-merge-master
fork_ami_US2597_US2599_US2813_US2817_US2872_US2816_US2814_213
This bug has been verified and fixed. Please refer to the details as below: Verified build: rhc client built from fork_ami_US2597_US2599_US2813_US2817_US2872_US2816_US2814_213 devenv_2303 Verified steps: 1. Create an app 2. Tail app log: #rhc tail app Verified results: It's fixed, app log are shown correctly as below: # rhc tail jboseap Password: * ==> jbosseap-6.0/logs/boot.log <== 22:18:56,689 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.4.GA-redhat-1 22:18:56,830 INFO [org.jboss.remoting] JBoss Remoting version 3.2.8.GA-redhat-1 22:18:56,994 INFO [org.jboss.as.configadmin] JBAS016200: Activating ConfigAdmin Subsystem 22:18:57,056 INFO [org.jboss.as.clustering.jgroups] JBAS010260: Activating JGroups subsystem. 22:18:57,077 INFO [org.jboss.as.security] JBAS013101: Activating Security Subsystem 22:18:57,079 INFO [org.jboss.as.jacorb] JBAS016300: Activating JacORB Subsystem 22:18:57,087 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers 22:18:57,050 INFO [org.jboss.as.clustering.infinispan] JBAS010280: Activating Infinispan subsystem. 22:18:57,094 INFO [org.jboss.as.naming] JBAS011800: Activating Naming Subsystem 22:18:57,085 INFO [org.jboss.as.osgi] JBAS011906: Activating OSGi Subsystem ==> jbosseap-6.0/logs/server.log <== 2012/10/09 22:19:08,613 INFO [org.hornetq.jms.server.recovery.RecoveryDiscovery] (MSC service thread 1-1) Starting RecoveryDiscovery on XARecoveryConfig [transportConfiguration = [org-hornetq-core-remoting-impl-invm-InVMConnectorFactory?server-id=0], discoveryConfiguration = null, username=null, password=null] 2012/10/09 22:19:08,927 INFO [org.hornetq.jms.server.recovery.RecoveryDiscovery] (MSC service thread 1-1) RecoveryDiscovery started fine on XARecoveryConfig [transportConfiguration = [org-hornetq-core-remoting-impl-invm-InVMConnectorFactory?server-id=0], discoveryConfiguration = null, username=null, password=null] 2012/10/09 22:19:08,928 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-1) HornetQ resource adaptor started So mark it as Verified. Thanks.
*** Bug 863937 has been marked as a duplicate of this bug. ***