| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Change-Id: Ib414b8496ca65a48bbe42936e32a863c9c1072e4
Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
After changing the type of unit file from INFO
to DEBUG. Performing daemon reload. Earlier using
running commands continuosly to generated debug
messages instead of running continuosly, restarted
glusterd in one of the nodes so that while handshake
the logs will be in Debug mode. After validating
reverting back the unit file to INFO and daemon
reload
Change-Id: I8c99407eff2ea98a836f37fc2d89bb99f7eeccb7
Signed-off-by: Bala Konda Reddy M <bmekala@redhat.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
While running test_enabling_gluster_debug_mode through jenkins
it was observed that running volume operation once wasn't
generating enough of logs by the time the logs were checked
which lead to failure of the test case in the jenkins run.
So modifying the logic which generates logs to run operation
in a loop to generated a good amount of logs.
Change-Id: Id7a12c86a04dc86d4856dbe30d945e70e64ea4f7
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
|
|
|
In this test case we will enable glusterd in
debug mode and check the glusterd log for the debug messages.
Steps followed:
1. Stop glusterd.
2. Change log level to DEBUG in
/usr/local/lib/systemd/system/glusterd.service.
3. Remove glusterd log.
4. Start glusterd.
5. Issue some gluster commands.
6. Check for debug messages in glusterd log.
Change-Id: Id1173be6da2ef1c2233459fb23f4b27308c923f2
Signed-off-by: Sanju Rakonde <srakonde@redhat.com>
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
|
