Rohan Joshi

Hi @leochr, Yes, this failure is consistent in all our s390x travis builds... In some of my previous failed builds, I was seeing this error at `RUN configure.sh` command which...

> @Rohanjos97 Are the latest logs from starting and stopping the server within populate_scc.sh? Noticed some feature definition missing error (CWWKF0042E), so wanted to clarify. Thank you Hi @leochr, sorry...

Hi all, I tried to get the logs using `dmesg` and `journalctl` command as suggested by @ymanton, but I was not able to fetch the logs of `dmesg` command output...

Hi All, I resolved the sudo error that I was getting earlier on using`dmesg` command, but it seems it wasn't a sudo error, but something else... been trying to work...

Hi @ymanton, I tried both commands, `sudo journalctl` still returns same output: ``` #15 330.3 + sudo journalctl #15 330.6 No journal files were found. #15 330.6 -- No entries...

> Just so we are on the same page, you are checking the journal, dmesg, `/var/log`, etc on the Travis build node, not inside the build container where `server stop`...

> Try the previous suggestions on the Travis build node, not in the container. Here's the output of `dmesg` that I ran on travis ndoe... I guess I got it...

Hi Guys, I had shared the output of `dmesg` command that I ran on travis node (instead of running inside the container), please let me know if these logs are...